Browser: Chrome 117
OS: Windows
Hi bricks team,
I want the header and footer not to be displayed on the 404 page. So I enabled ؛Disable header and footer" in general settings, But the header and footer are still displayed in the front end.
Browser: Chrome 117
OS: Windows
Hi bricks team,
I want the header and footer not to be displayed on the 404 page. So I enabled ؛Disable header and footer" in general settings, But the header and footer are still displayed in the front end.
This doesn’t only happen on the 404 page, it doesn’t work everywhere, in the editor it is removed but not in the frontend.
I think in the header/ footer page templates, you need to add an additional condition to EXCLUDE the 404/ Error Page from showing. Simply disabling the header/ footer will just stop showing it in the editor…not on a live site.
Thanks for the great solution. But anyway, this is a bug that I hope will be fixed.
Hi Hosein,
Thanks so much for your report!
I reproduced the issue and added it to our bug tracker. This seems to affect not only the error page template, but templates in general.
Best regards,
timmse
Hi @timmse,
Is it possible that this bug will be fixed in version beta 1.9.2?
Seems like this bug issue also applies to template elements inside of a template.
Example:
Footer Template (template conditions = Entire Site include)
-Section element
-Template element > “Floating Menu Template” (element condition = dynamic data > options_enable_float > !=)
Floating Menu Template (template conditions = Front Page exclude, Entire Site include)
The same issue even if there is no template element condition with ACF data (only using brick’s template conditions)
Issue is that Bricks is not honoring the child template’s conditions. Is this related to this case @timmse @HOSEIN ?
Thanks!!
What type is the “Floating Menu Template”?
It’s a section template. It works fine and honors it’s template conditions if added to a single template - just not footer.
We can’t quite follow your setup @FranklyCo, unfortunately However, your problems don’t seem to match the actual one.
Would you be so kind as to send temporary login credentials, information on where we can see your issue(s) and a link to this thread to help@bricksbuilder.io using the email address you used during the purchase?
Hi guys,
We’ve fixed this issue in Bricks 1.9.5, now available as a one-click update in your WordPress Dashboard.
Changelog: Bricks 1.9.5 Changelog – Bricks
Please let us know if you are still experiencing issues.