Skip to main content

Brizy Editor Unable to Save or Update After Editing Global Section

Comments

5 comments

  • Ariel H.

    Hi Ardy,

    To help us investigate this issue, could you please provide temporary access to your WordPress admin dashboard? This will allow us to take a closer look at your setup and identify the cause of the issue. 

    Kindly send the following details to communitysupport@brizy.io:

    We’ll review it as soon as we receive the access.

    Best regards,  
    Ariel H.

    0
  • Ariel H.

    Hi Ardy,

    Upon checking, we found that the WordPress Administrator account has lost the required access to save the headers, which is why it is returning an Error 403 in the browser console. This issue was likely caused by the site migration from staging to production.

    To correct this, you can change or set the current Administrator role to Editor, then grant the user Full Access through Brizy’s Role Manager. This process is demonstrated in this screencast:

    https://youtu.be/wbY86AveBSI

    We also created a second temporary Administrator account so we could update the brizy_tech user account to Editor, since a user cannot change its own role while logged into the same account.

    Feel free to test the setup and delete the temporary Administrator credentials afterward if they are no longer needed.

    If you have any further questions or need any assistance, please let us know.

    Best regards,
    Ariel H.

    0
  • Ardy Lingatong

    Awesome!!

    Thank you so much, Ariel!

    Everything is now working fine regarding the issue.

    My client hired a 3rd party marketing specialist who made some edits in the website and it somehow messed up some features. 

    I have other concern though, kindly refer to the below info:

    Issue

    The main navigation menu displays correctly, but the submenu dropdowns sometimes fail to appear or function, particularly when viewing the website as a logged-out visitor or in incognito mode.

    During previous troubleshooting, we found that disabling certain caching/optimisation settings restored the submenu functionality.

    In particular, WP Rocket's Optimise CSS Delivery / Remove Unused CSS appeared to affect the Brizy header and navigation. Disabling this feature helped restore the dropdown menus.

    We have therefore tried to avoid overlapping CSS and JavaScript optimisation between WP Rocket and SiteGround Speed Optimizer.

    The concern is that the website may appear and function correctly while logged into WordPress, but cached versions served to normal visitors can experience problems with the Brizy submenu dropdowns.

    Current Optimisation Setup

    We have deliberately limited SiteGround Speed Optimizer's CSS and JavaScript optimisation because WP Rocket is also installed.

    WP Rocket's more aggressive CSS optimisation, particularly Remove Unused CSS / Optimise CSS Delivery, has also been disabled because of the submenu issue.

    Request for Brizy Support

    Could you please investigate whether Brizy navigation dropdowns have any known compatibility issues with WP Rocket or SiteGround Speed Optimizer?

    In particular, could you advise:

    1. Whether Brizy requires specific CSS or JavaScript files to be excluded from WP Rocket optimisation.
    2. Whether any Brizy scripts should be excluded from JavaScript defer, delay, minification or other optimisation.
    3. Whether Brizy-generated CSS should be excluded from Remove Unused CSS processing.
    4. Whether caching can cause the dropdown functionality to work for logged-in users but fail for logged-out/incognito visitors.
    5. What caching and optimisation configuration Brizy recommends when using WP Rocket together with SiteGround Speed Optimizer.

    Our goal is to retain website caching and performance optimisation without risking the Brizy submenu dropdowns becoming unavailable to website visitors.

    We would appreciate Brizy's recommended configuration or exclusion rules so we can resolve this permanently rather than simply disabling optimisation features.

    Regards,
    Ardy




    0
  • Ariel H.

    Hi Ardy,

    Please add the following Brizy JS and CSS files to the exclusion list in WP Rocket or the asset optimization settings and see if this fixes the issue.

    JavaScript Exclusions:
    /wp-content/plugins/brizy/public/editor-build/prod/editor/js/main.base.min.js
    /wp-content/plugins/brizy-pro/public/editor-build/prod/js/main.base.pro.min.js

    CSS Exclusion:
    /wp-content/plugins/brizy/public/editor-build/prod/editor/css/preview.css

    Best regards,
    Ariel H.

    0
  • Ardy Lingatong

    Hi Ariel,

    I’ve adjusted the WP Rocket settings based on your recommendation, and everything is functioning properly now. I’ll continue monitoring to ensure the current frontend experience remains stable and will check later to see if the issue reoccurs.

    Best, 
    Ardy

    0

Please sign in to leave a comment.