Skip to main content

Brizy Update breaks site

Heather Ferguson

Brizy did an update this morning and the site went down. It is listed as a critical error, I am unable to access the admin page. Below is what wordpress is saying - I need Brizy to fix it. I put in a request, got a message back almost immediately and haven't heard another word in 5 hours. I am assuming that their response is really just a bot. I have Brizy & Brizy Pro but neither are helpful if my site is down and visitors can see a message that the site has a critical error. I need a resolution!

 

Version 1.0.118 | By Brizy.io | View details
 This plugin failed to load properly and is paused during recovery mode.

An error of type E_ERROR was caused in line 114 of the file /home4/fergust1/public_html/wp-content/plugins/brizy/admin/settings.php. Error message: Uncaught Error: Call to private method BrizyPro_Admin_WhiteLabel::getEnabled() from context 'Brizy_Admin_Settings' in /home4/fergust1/public_html/wp-content/plugins/brizy/admin/settings.php:114 Stack trace: #0 /home4/fergust1/public_html/wp-includes/class-wp-hook.php(288): Brizy_Admin_Settings->actionRegisterSubMenuGetHelpLink('') #1 /home4/fergust1/public_html/wp-includes/class-wp-hook.php(312): WP_Hook->apply_filters(NULL, Array) #2 /home4/fergust1/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array) #3 /home4/fergust1/public_html/wp-admin/includes/menu.php(155): do_action('admin_menu', '') #4 /home4/fergust1/public_html/wp-admin/menu.php(326): require_once('/home4/fergust1...') #5 /home4/fergust1/public_html/wp-admin/admin.php(153): require('/home4/fergust1...') #6 /home4/fergust1/public_html/wp-admin/index.php(10): require_once('/home4/fergust1...') #7 {main} thrown

1

Comments

10 comments

Date Votes
  • Alex
    • Edited

    Hi Heather,

    I checked your discussion with my colleague Natalia. She helped you with your problem, even though it was 1 a.m. at her. This is really an effort on her part. You should appreciate this :)

     

    Now I will give you some general ideas that could help you in such critical times.

    1) Make a complete backup of your website, before updating. The update should go without problems, but in case something goes wrong it is good to have a backup.

    2) If your plugins are automatically updated, I recommend disabling this: https://www.wpbeginner.com/wp-tutorials/how-to-disable-automatic-updates-in-wordpress/

    3) First, update the Free plugin and then the PRO version.

    4) If you got a fatal error and you cannot access the dashboard, all you have to do is delete the plugin folder from the File Manager. You can log in via cPanel or FTP. 

    5) After you have deleted the folder, install the latest version of the plugin manually. This will solve the problem and you will not lose anything because all the configurations and settings are saved in the database.

    Hope this helps.

     
    0
  • Mateusz Ryszka

    Hello,
    I have the same issue with Brizy Pro plugin. Brizy Free works fine when Brizy Pro is inactive, but after active it back I get the same error as described by Heather Ferguson. Already tried to remove Brizy Free plugin folder and install it again, but it didn't help because its Brizy Pro problem. Can you give me some informations how to solve this problem?

    0
  • Alex

    Hi Mateusz,

    do you have the latest Brizy PRO version? Try to delete it and then download it from your Brizy account and re-install the PRO plugin.

    0
  • Mateusz Ryszka

    Hi Alex,

    I have Brizy PRO in version Brizy PRO 0.0.28 and Brizy Free in version Brizy 1.0.122. After many attempts yesterday I was able to solve the problem myself. The reason is some conflict between Brizy Free in version 1.0.122 and Brizy Pro in version 0.028, so after downgrading Brizy Free to version 1.0.117 everything started to work correctly.

    1
  • Alex

    Well yes.

    The latest Brizy Free version is not compatible with an old version of PRO. Plugins must always be updated both. If you cannot upgrade Brizy PRO because you do not have a license, you must keep Brizy Free on an older version. 

    So to make sure everything is always working well, you must have the latest version of Brizy Free and the latest version of Brizy PRO.

    0
  • La'tisha Bandele

    Hi alex can someone send me the downgraded free version I have to put my site back up asap i deactivated my lifetime pro version 0.0.39 but still not working

    0
  • Mateusz Ryszka

    La'tisha Bandele you can create backup of your Brizy Free plugin files (just to make sure that you can restore in case of some other problems) and then remove them (configuration is in database) and then install Brizy Free in again in proper version for example by CLI "plugin install brizy --version=1.0.117". That solution worked for me. 

    Alex if you have information that newest PRO version is not compatible with older FREE you should handle it with some readable exception to make debugging problem easier, because right now it is really hard to find the cause of error.

    0
  • Alex

    Hi,

    @La'tisha Bandele - All FREE version can be found here: https://wordpress.org/plugins/brizy/advanced/ at the bottom of the page you can download one of the previous versions. But, I would not recommend downgrading the plugin. If you install Brizy Free 1.0.122 and PRO 0.0.39 everything will work fine.

    @Mateusz Ryszka - I will talk to my colleagues and we will probably publish this information somewhere. Sorry for the created inconvenience.

    0
  • Mateusz Ryszka

    @Alex thank you for the answer and I hope that there will be relevant information or correct error handling so that other people who encounter this problem can solve it faster.

    0
  • Erol Oner

    Hi Guys,

    Just in case it helps anyone I just wanted to share my experience.

    I use Brizy Pro on a Centos7+NGINX and OPCACHE activated.

     

    If I update Brizy it WILL break the site.

    OPCACHE MUST BE FLUSHED after each update of Brizy for the site to be back on track.

     

    The hard way:
    sudo service php-fpm reload && echo "OPCACHE FLUSHED" || echo "OPCACHE NOT FLUSHED"

     

    The nice way with cachetool located in /tmp/cachetool.phar for this example:

    sudo php /tmp/cachetool.phar opcache:reset --fcgi=/var/run/php-fpm/php-fpm.sock

     

    It took me a while to find this so I thought I would share it.

    0

Please sign in to leave a comment.

Didn't find what you were looking for?

Ask a Question