• Resolved redorav

    (@redorav)


    I’m getting a “There has been a critical error on this website.” after updating the plugin, I’ve deactivated for now, just thought you’d want to know

Viewing 13 replies - 1 through 13 (of 13 total)
  • Same.

    same issue – WordPress white screen of death after updating – resolved on deactivating the plugin

    Getting the same on two client sites as well…. ugh

    My blg has crashed with version 1.7.4.

    Where can I find previous versions (1.6.1 for example) ?

    same problem for me. I turned off auto-update and will wait to see if another revision comes out.

    @jean-pierre-martel

    You can either install the Rollback plugin on your site and click the Rollback link to reinstall the previous version, or you can go to the main page of this plugin here and click Development -> Advanced View and scroll down to where you can download the previous version.

    Same error on the latest WordPress install.

    Jason Ryan, thank you for explanation of previous version installation.

    Same. Please fix ASAP!!

    There seems to be a dependency on the elementor plugin. If it is not installed, the site crashes with a fatal error:

    Fatal error: Uncaught Error: Class "Elementor\Plugin" not found in /home/.sites/web/wp-content/plugins/twenty20/inc/enqueue.php:15 Stack trace: #0 /home/.sites/web/wp-includes/class-wp-hook.php(324): twenty20_zb_enqueue_script('') #1
    Plugin Author Zayed Baloch

    (@zayedbaloch)

    Thank you for bringing this to our attention, and we sincerely apologize for the inconvenience caused. We’ve identified the issue and have released a new version 1.7.5 that fixes the unintended dependency on Elementor for users who do not have it installed.

    Please update to version 1.7.5, and the error should be resolved. We appreciate your patience and understanding and thank you for your continued support.

    Thanks Zayed – all sorted

    Success in my website as well. I updated to the latest version and the website is operating as expected. Thank you.

    Thread Starter redorav

    (@redorav)

    Can confirm this is fixed on my end as well, many thanks for the quick turnaround

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