1. PROMO Get 60% OFF Lifetime Pro Membership & access all our Pro Divi Extensions, Divi Layouts, Divi AI Generator, Divi Block, etc.VIEW PRICING
Dismiss Notice
UPDATE Custom Color Scheme + Premade Divi Layouts - A perfect combination to boost productivity. New 'Gadget Repair' layout added.Try our Custom Color Layouts
BEST Divi Block - A revolutionary drag & drop tool to easily mix & match 960+ premade blocks (Light & Dark) to kick start your Divi site design. Special module designs are included as well.
Learn More About Divi BlockFree Version ~ 340+ Free Blocks

Critical Error Wordpress with Divi Theme

Discussion in 'Free Divi Community Forum' started by StephenKilbreath, Jul 3, 2024.

  1. StephenKilbreath

    StephenKilbreath New Member

    I keep getting this message:

    There has been a critical error on this website. Please check your site admin email inbox for instructions. Learn more about troubleshooting WordPress.

    When I attempt to update a page. WordPress says it is a critical error with Divi. How can this problem be solved?
     
    1. PRO MEMBER PERKS Divi Block Pro - 30+ premade custom header designs for you to choose from:View Demo
  2. Divi Booster

    Divi Booster Divi Expert

    Hey Stephen,

    This indicates that an error has occurred in the site's PHP code. There can be various causes, such as hosting memory limits being reached or an error in a plugin.

    You should have been sent an email to the admin email address configured on the site. If you check this email it should have the full error message (including affected file and line number) associated with the error. If you share that here we should be able to point you in the direction of a solution. If you can't find the email / error message, you can also get the error message by enabling the WordPress debug.log:

    https://wp-staging.com/docs/enable-wordpress-debug-log-mode/

    Once enabled, trigger the error and check for the error message in the /wp-content/debug.log file. Again share it here for interpretation.

    An alternative approach would be to disable unnecessary plugins (which might get you back below any memory limit being hit) and if the issue persists, disable plugins one at a time to find the one with the issue. Then work with the plugin author to get a fix (note that they'll likely want to get the error message as described above).