Home Forums Community Forum Updated to 5.5.2 resulted in this fatal error

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • designbrei
    Participant
    Post count: 2

    …wp-content/themes/Avada/includes/upgrade/class-avada-upgrade-552.php on line 143

    Is this something I can fix?

    Thanks!

    Michael C
    Keymaster
    Post count: 489

    Hi @designbrei,

    This sounds like a compatibility issue with a specific version of Avada. To resolve please disable Fusion Builder, then run the update. That way the update should work fine. Once that has run you should then be able to update and activate the new builder without issues.

    designbrei
    Participant
    Post count: 2

    Thanks for the help! All fixed. Thank you thank you thank you.

    lipinsky
    Participant
    Post count: 1

    So how did I get my site back after the update? I can’t disable Fusion Builder due to the error.

    The update should not have run if Fusion Builder is active or it should have disabled Fusion Builder.

    This is just plain poor programming.

    Michael
    Keymaster
    Post count: 505

    Hi @lipinsky

    This has nothing to do with programming. When it does come to updating, be sure to follow our update instructions. These are our detailed update instructions:

    Updating from an old version of Avada? -> http://bit.ly/2pPNngZ

    Important Update Info -> http://bit.ly/1FAmQpu

    How to Update -> http://bit.ly/1H8JGzo

    Fusion Patcher -> http://bit.ly/1QSd8Ol

    Avada Change log -> http://bit.ly/1EK5mAg

    Something else that is important is to also ensure any patches that our team releases between update cycles are applied as part of ongoing maintenance for your install and always clear your cache plugins post update

    Patches are applied at the click of a button as explained in this help file -> http://bit.ly/1NAWVwM

    Thank you kindly

    Michael C
    Keymaster
    Post count: 489

    Hi @lipinsky,

    You can still disable the plugin via FTP by renaming the plugin folder or by disabling prior to updating. Also, please note, this is specifically for updating from previously unstable versions of the theme (5.1 > 5.1.4), not a general updating issue.

Viewing 6 posts - 1 through 6 (of 6 total)
  • You must be logged in to reply to this topic.