Skip to main content

Many, Many sites have Single Page Posts CSS/layouts damaged, and full site CSS damage (Down!) if Global Block Edit trick attempted

Barry Lippold

We have had many sites go down many times in our history with Brizy and Brizy Pro, but nothing as maddening as this time.  Most of our sites suddenly lost the Single Page Post formatting (with no changes to the template on our part). The usual tricks with editing a global block's padding to get the CSS to recompile is not working; in fact, when we try, the entire site's CSS is damaged, on the latest versions of Brizy and Brizy Pro (2.8.9 and 2.8.4, respectively). Prior to updating Brizy and Brizy Pro, the Single Page Templates seemed to get auto-damaged at some point during recent updates, but updating to the latest version and changing just the padding on the title in the Single Page Template does not fix the issue, even after updating Brizy+BP.  Worse, as mentioned above, if we try editing any global blocks padding or spacing, the entire site gets damaged and we have to revert to a backup.  We have tried for 3 hours to troubleshoot, turning off and on Siteground Speed Optimizer before editing, turning it off completely after a restore then updating Brizy and editing...In all cases, with or without plugin caching, the site gets damaged with any global edit, and the posts in some sites (11 and counting) are also damaged in addition to this global issue.  Please explain how to fix these issues since we're having them on many sites. I'm sending access and a screencast recording of the site.  You can see the messed up post page CSS here: https://jpmanagementcorp.com/how-to-vet-a-financial-professional/, and the global edits damaging the entire site's CSS in the video link sent to support.

0

Comments

5 comments

Date Votes
  • KC George

    Hello Barry,

    To fix the above issue, kindly upload these files to the respective folders using an FTP client like FileZilla or using the File Manager plugin

    • Download the CSS file at https://jmp.sh/XSTZzOUo and uplod it to the folder /wp-content/plugins/brizy/public/editor-build/prod/editor
    • Download the two CSS files at https://jmp.sh/ufDJvmM6 and upload it to the folder /wp-content/plugins/brizy-pro/public/editor-build/prod

    If you need help with uploading these files, kindly give us access to your WordPress dashboard. Please add a new user to your WordPress Dashboard and send the following details to our email: communitysupport@brizy.io 

    Your email must include a link to this thread's URL, otherwise we will be unable to locate your support ticket. Please notify us in this thread when you send us the email.

    0
  • Barry Lippold

    Had sent email with the info above to Support@ but now forwarded it to the communitysupport address. However, I need to know what is causing this since it's happening on many sites, and therefore, how to avoid it from happening on all sites. It seems strange to have to upload CSS files manually after Brizy or WP updates. Please advise. Thank you.

    0
  • KC George

    Hello Barry,

    I have uploaded the required CSS files and the blog posts are now working. Please check https://jpmanagementcorp.com/how-to-vet-a-financial-professional/

    Kindly download the Brizy version at https://jmp.sh/KCSY9BJZ, upload it to other websites with the same issue and check if it helps to fix the CSS issues.

    0
  • Barry Lippold

    Hi KC George,

    Yes...It was a painful process to do many sites (getting the logins/etc.), but the Beta version fixed it, thank you.  However, there were some sites that appeared ok without the Beta version, and some of them were even based on the same template/same client design, so we didn't update those to the Beta, but why??  And should we update them to Beta?  And, with that beta plugin uploaded on all of the broken sites, will the normal auto or manual updates still work when the official .10 version is released?  How does the beta upload impact that?  And I guess this was another bug in a Brizy update, but what was it exactly, and did it only affect certain sites?  When things like this happen, and you're getting a large number of reports, I would really like to see proactive communications from Brizy instead of finding the issues via clients or after days or weeks of damaged sites, where we just don't know.  

    0
  • KC George

    Hello Barry,

    Let me go over your questions.

    • The websites that are functioning properly don't require you to upload the beta version.
    • It might not be necessary for websites using the 2.8.10 beta to update to the official 2.8.10. We will confirm this with you on Monday after consulting with the development team. (On weekends, we are closed.)
    • The problem was caused by a global block compilation bug in Brizy, which has been fixed in the beta version of Brizy 2.8.10.
    • Communicating this bug to our customers was not an option since we did not anticipate it.
    0

Please sign in to leave a comment.

Didn't find what you were looking for?

Ask a Question