Browser: Chrome 110
OS: macOS
Video: https://download.johannes-glaser.de/bricks-bug-password-protection-template.mp4
Steps to reproduce:
- On a fresh instance, enable Bricks for posts and also enable the feature “password protection templates” (experimental)
- First, create a “Single” template for the entire website: Add a new template, set it to “Single”, then set its conditions to “Entire website”.
- Then, create a “Password protection” template for the entire website: Add a new template, set it to “Password protection”, then set its conditions to “Entire website” and its mode to “Post password”.
- Create a test post. Go to “WP menu > Posts” and add a post. Set it to “Published” and set a post password.
- Visit the test post.
Expected result:
You see the password protection template that you just created.
Actual result:
You see the native WP password protection input form.
Confirmation that this is a bug:
If you follow the above steps to reproduce the issue, but switch step 2 and 3 (i.e., you create the password protection template BEFORE the single template), the issue does not appear. In this case, you can then see the password protection template.
My guess is that the Bricks condition-check goes by template-post-ID. However, password protection templates should be prioritized here.
