• Hi all, I have encountered this message when editing posts on my website:

    `Fatal error: Uncaught Error: Call to undefined function et_pb_ab_get_refresh_interval() in /home/customer/www/wisefigjewellery.com/public_html/wp-content/themes/Divi/includes/builder/functions.php:4553 Stack trace: #0 /home/customer/www/wisefigjewellery.com/public_html/wp-includes/class-wp-hook.php(307): et_pb_before_main_editor(Object(WP_Post)) #1 /home/customer/www/wisefigjewellery.com/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters(NULL, Array) #2 /home/customer/www/wisefigjewellery.com/public_html/wp-includes/plugin.php(474): WP_Hook->do_action(Array) #3 /home/customer/www/wisefigjewellery.com/public_html/wp-admin/edit-form-advanced.php(581): do_action(‘edit_form_after…’, Object(WP_Post)) #4 /home/customer/www/wisefigjewellery.com/public_html/wp-admin/post.php(206): require(‘/home/customer/…’) #5 {main} thrown in /home/customer/www/wisefigjewellery.com/public_html/wp-content/themes/Divi/includes/builder/functions.php on line 4553
    There has been a critical error on this website.

    Is there anyone who can point me in the right direction to overcome this? WordPress, my themes and plugins are up to date, I haven’t made any very recent changes, and I haven’t come across this before.

    Thanks for any advice!
    Fiona

Viewing 14 replies - 1 through 14 (of 14 total)
  • lisa

    (@contentiskey)

    looks like something to start on by asking at DIVI theme’s support
    https://www.elegantthemes.com/members-area/login/

    Thread Starter fionah77

    (@fionah77)

    Thanks Lisa, I’ll do that

    I had the same error – after restoring from a backup that I knew was working. I discovered the plugin that gave that error is this,

    WooCommerce Wholesale Prices
    WooCommerce Extension to Provide Wholesale Prices Functionality
    Version 2.1.1 | By Rymera Web Co

    If you update to the wholesale prices to version 2.1.2 it will break the divi and not allow me to edit pages.

    So if you have that plugin try disabling it or revert back to version 2.1.1

    Thread Starter fionah77

    (@fionah77)

    Thank you, that’s really helpful!

    @fionah77 are you using divi & the wholesale prices plugin?

    Thread Starter fionah77

    (@fionah77)

    @emcwebdesign yes I am. I accessed divi support and came to the conclusion it was that plug-in, and disabling it solved the problem. I really liked the plug-in though so have followed your advice and rolled it back to the previous version and so far so good, so thank you!

    Great! so it sounds the plugin newest version 2.1.2 is not compatible with divi. I contacted the plugins developers. If I have any news I’ll post back here. @fionah77

    • This reply was modified 2 years, 6 months ago by emcwebdesign.
    Thread Starter fionah77

    (@fionah77)

    @emcwebdesign brilliant, thank you. I’ve also spotted another post with the same problem that the developer has commented on so I’ve left a message there too ??

    @fionah77 excellent. thanks for the update. I might install a test site to allow the developer troubleshoot. I hope to find the fix – the plugin seems right for this client site I was using it on. enjoy the day!

    Thanks for reporting. We had the same issue and deactivating the WooCommerce Wholesale Prices plugin v2.1.2 by Rymera Web Co got the Divi Builder working again. It’s still a Divi crash, but the Wholesale plugin triggers it. I’ve seen this sometimes with Elementor as well. These builders that render previews can have trouble with other plugins. Then you get finger pointing between the vendors!

    WooCommerce Wholesale Prices has just released v2.1.4 – this update appears to have fixed the fatal error.

    Thread Starter fionah77

    (@fionah77)

    @duckbell oh thank you for letting me know, I’ll have a look ??

    @fionah77 @duckbell Yes! the developers of wholesale prices plugin did troubleshooting on one of my test sites. Went to ver 2.1.3 after it still threw an error they went to ver 2.1.4 Its working good on my live site now.

    Thread Starter fionah77

    (@fionah77)

    @emcwebdesign brilliant, thank you for working through that with them ??

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘Critical error’ is closed to new replies.