Browser: Chrome 110
OS: Windows
URL: Realtors – Kiwanda Shores Maintenance Association
Video: Jam
Once I apply a password to the page, the password protection template applies with a boxed layout even though wide is specified. The template content is in an article tag instead of main and a “wordpress” class is applied.
The dynamic post title in a heading element stops outputting as well. You can see the heading tag is in the hero section though.
Hi Travis,
Thanks so much for your report!
That’s usually an indication that the page is rendered with WordPress instead of Bricks. While logged in and looking at the page on the frontend, check the wp admin bar. If it says “Render with WordPress”, click “Render with Bricks”.
Best regards,
timmse
Hmm… Please send temporary login credentials and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase.
Login sent. THANK YOU!
While you’re logged in, can you check on that session variable issue as well?
Hi Travis,
Thanks for the login credentials!
I’m able to replicate the issue now and added the following custom CSS to Bricks » Settings » Custom Code as an interim fix:
#brx-content.wordpress.post-password-required {
width: 100%;
}
We’ll take a look at your other report as soon as possible.
Did you investigate how the dynamic page title stopped working?
That’s the developers’ job, but I have, of course, pointed this out 
Needed to change password to “realtorsdelight”
I found this same issue is still happening in Bricks 2.3.9.
For the password page, when viewing either the template, or an actual password page on the front end the ‘Render with Bricks / WordPress’ doesn’t show in admin menu.
I found that this renders full with when viewing the template on the front end, but then when viewing on a password protected page it’s rendering boxed (It’s a CPT if that makes a difference).
We’ve addressed this in Bricks 2.4-beta (beta release), now available for manual download from your Bricks account.
Please read the changelog entry before testing, and let us know if you experience any issues. Note: beta builds are not recommended for production sites.