Critical Error

  • Resolved TheBusinessCat

    (@thebusinesscat)


    3 years, 6 months ago

    Hi there,

    When I try to access my themes or add a WooCommerce product, I get the message “There has been a critical error on this website.”

    I installed the WP Debugging plugin (https://wordpress.org/plugins/wp-debugging/) and below is a link to a screenshot I took. It refers to Forminator, and when I deactivate Forminator, I can access the themes page and add new WooCommerce products.

    View Screenshot

    Please could you advise?

    Thank you.

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Support Imran – WPMU DEV Support

    (@wpmudev-support9)

    3 years, 6 months ago

    Hello @thebusinesscat !

    I’m sorry to hear that you’re experiencing this issue!

    From the screenshot it looks like the messages are actually just deprecation notices which wouldn’t cause any issues, unless you have debugging enabled and error display set to true as this will cause the messages to appear in some additional places.

    Please try the following:
    – in wp-config.php remove all defines related to debugging, such as:

    define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', true );

    Replace them with those:

    define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
@error_reporting(0);
@ini_set('display_errors', 0);

    And see if that helps.

    I do think it’s not actually related to Forminator (as mentioned above, the deprecation messages don’t cause a Critical Error with that message). After performing the steps above, if the issue is still there, please check in wp-content/debug.log if there are any other messages about a “Fatal Error”.

    Best regards,
    Pawel

    Thread Starter TheBusinessCat

    (@thebusinesscat)

    3 years, 6 months ago

    Hi Pawel,

    Thank you for your message.

    I don’t mind seeing the deprecated message, and can just deactivate the debugging plugin to hide the messages.

    As mentioned it must have something to do with Forminator, because when I deactivate Forminator then everything works as usual. When I re-activate Forminator, then I have the issues mentioned in my first message. I’m trying to find out why this would be.

    I checked the debug.log file as you suggested but only see deprecated messages. I did a search and could not find any fatal errors.

    Thank you.

    Plugin Support Laura – WPMU DEV Support

    (@wpmudev-support8)

    3 years, 6 months ago

    Hi @thebusinesscat

    Thank you for response!

    The thing with “deprecation” is that despite the messages everything “should” work fine, because “deprecated” means more of “better avoid using this, it will soon be disabled/removed but for now you have time to make changes and it’s working as it used to“. At least in theory…

    It might, however, be a bit “misleading” error log (and we don’t really see “everything”) ro there might be some additional “conflict” there.

    I’m assuming that your WordPress core and all the themes/plugins are up to date, right?

    What theme are you using?
    What is the PHP version of the site?
    Could you please go to the (with deactivated Forminator so you would be able to use the site) “Tools -> Site Health -> Info” page, use “copy site info to clipboard” option and paste it below?

    Note: preferably mark it as “code” when sharing and feel free to edit/mask any paths or URLs if you prefer to.

    Kind regards,
    Adam

    Thread Starter TheBusinessCat

    (@thebusinesscat)

    3 years, 5 months ago

    Hi Adam,

    Thanks for your message.

    For some strange reason, everything seems to be working this morning, so not sure what happened.

    Everything was updated when I tried yesterday, so not sure what is up.

    Thanks so much for assisting. I appreciate it.

    Thread Starter TheBusinessCat

    (@thebusinesscat)

    3 years, 5 months ago

    Hi there,

    Sorry for re-opening this thread, but I am having the same issue again.

    Here is a video link to show what is happening:

    https://www.loom.com/share/95d1a417360b4b2eb7993014b15cbac5

    Just to answer the questions posted previously:

    WordPress core and all the themes/plugins are up to date.

    I am using the Divi theme.

    The PHP version of the site is 8.1.

    ### wp-core ###

version: 6.1.1
site_language: en_US
user_language: en_US
timezone: Africa/Johannesburg
permalink: /%postname%/
https_status: true
multisite: false
user_registration: 0
blog_public: 0
default_comment_status: open
environment_type: production
user_count: 2
dotorg_communication: true

### wp-paths-sizes ###

wordpress_path: /home/poweralot/public_html
wordpress_size: 370.91 MB (388928502 bytes)
uploads_path: /home/poweralot/public_html/wp-content/uploads
uploads_size: 22.29 MB (23368747 bytes)
themes_path: /home/poweralot/public_html/wp-content/themes
themes_size: 53.94 MB (56555753 bytes)
plugins_path: /home/poweralot/public_html/wp-content/plugins
plugins_size: 136.04 MB (142643060 bytes)
database_size: 19.72 MB (20679220 bytes)
total_size: 602.89 MB (632175282 bytes)

### wp-active-theme ###

name: Poweralot Theme (Poweralot Theme)
version: 1.0.0
author: Web Consultant Geek
author_website: https://webconsultantgeek.com
parent_theme: Divi (Divi)
theme_features: core-block-patterns, block-templates, widgets-block-editor, post-thumbnails, custom-background, automatic-feed-links, menus, title-tag, post-formats, woocommerce, wc-product-gallery-zoom, wc-product-gallery-lightbox, wc-product-gallery-slider, customize-selective-refresh-widgets, wp-block-styles, editor-style, widgets
theme_path: /home/poweralot/public_html/wp-content/themes/Poweralot Theme
auto_update: Disabled

### wp-parent-theme ###

name: Divi (Divi)
version: 4.19.2
author: Elegant Themes
author_website: http://www.elegantthemes.com
theme_path: /home/poweralot/public_html/wp-content/themes/Divi
auto_update: Disabled

### wp-plugins-active (9) ###

All-in-One WP Migration: version: 7.68, author: ServMask, Auto-updates disabled
Custom field finder: version: 0.3, author: Team Yoast, Auto-updates disabled
The Courier Guy Shipping for WooCommerce: version: 5.0.8, author: The Courier Guy, Auto-updates disabled
Ultimate Member: version: 2.5.1, author: Ultimate Member, Auto-updates disabled
WooCommerce: version: 7.1.1, author: Automattic, Auto-updates disabled
WooCommerce PayFast Gateway: version: 1.5.0, author: WooCommerce, Auto-updates disabled
WooCommerce Wholesale Prices: version: 2.1.5.1, author: Rymera Web Co, Auto-updates disabled
WOOF - WooCommerce Products Filter: version: 1.3.0, author: realmag777, Auto-updates disabled
Wordfence Security: version: 7.8.0, author: Wordfence, Auto-updates disabled

### wp-plugins-inactive (2) ###

Facebook for WooCommerce: version: 3.0.5, author: Facebook, Auto-updates disabled
Forminator: version: 1.21.0, author: WPMU DEV, Auto-updates disabled

### wp-media ###

image_editor: WP_Image_Editor_GD
imagick_module_version: Not available
imagemagick_version: Not available
imagick_version: Not available
file_uploads: File uploads is turned off
post_max_size: 64M
upload_max_filesize: 64M
max_effective_size: 64 MB
max_file_uploads: 20
gd_version: 2.3.3
gd_formats: GIF, JPEG, PNG, WebP, BMP, AVIF, XPM
ghostscript_version: 9.25

### wp-server ###

server_architecture: Linux 3.10.0-962.3.2.lve1.5.67.el7.x86_64 x86_64
httpd_software: Apache
php_version: 8.1.13 64bit
php_sapi: litespeed
max_input_variables: 1000
time_limit: 120
memory_limit: 128M
admin_memory_limit: 256M
max_input_time: 60
upload_max_filesize: 64M
php_post_max_size: 64M
curl_version: 7.84.0 OpenSSL/1.1.1p
suhosin: false
imagick_availability: false
pretty_permalinks: true
htaccess_extra_rules: true

### wp-database ###

extension: mysqli
server_version: 10.2.44-MariaDB
client_version: mysqlnd 8.1.13
max_allowed_packet: 1073741824
max_connections: 750

### wp-constants ###

WP_HOME: undefined
WP_SITEURL: undefined
WP_CONTENT_DIR: /home/poweralot/public_html/wp-content
WP_PLUGIN_DIR: /home/poweralot/public_html/wp-content/plugins
WP_MEMORY_LIMIT: 40M
WP_MAX_MEMORY_LIMIT: 256M
WP_DEBUG: false
WP_DEBUG_DISPLAY: true
WP_DEBUG_LOG: false
SCRIPT_DEBUG: false
WP_CACHE: false
CONCATENATE_SCRIPTS: undefined
COMPRESS_SCRIPTS: undefined
COMPRESS_CSS: undefined
WP_ENVIRONMENT_TYPE: Undefined
DB_CHARSET: utf8mb4
DB_COLLATE: undefined

### wp-filesystem ###

wordpress: writable
wp-content: writable
uploads: writable
plugins: writable
themes: writable
mu-plugins: writable
    Plugin Support Nebu John – WPMU DEV Support

    (@wpmudevsupport14)

    3 years, 5 months ago

    Hi @thebusinesscat,

    Sorry to know that the issue re-appeared.

    Just to make sure it’s not any plugin or the theme conflicting with Formiantor and causing the issue, can you please try a complete conflict test?

    That is – deactivate all the plugins except Forminator and check if that resolves the issue. If yes, reactivate all the plugins, one at a time and check at which point the issue re-appears.

    I hope the following flowchart comes in handy: https://wpmudev.com/wp-content/uploads/2015/09/Support-Process-Support-Process.gif

    If this is a live website with traffic, please create a staging website and perform the test without disturbing the live traffic. A staging website is an exact copy of your live website in a new directory on the same server with a separate database.

    Please let us know the results.

    Kind Regards,
    Nebu John

    Thread Starter TheBusinessCat

    (@thebusinesscat)

    3 years, 5 months ago

    Hi @wpmudevsupport14,

    Thank you for your response.

    I make a clone of the website and actually tried it on a different hosting account, and everything works as it should, even with all the other plugins activated.

    Could this then be an issue with the current hosting? And if so, how would I know what is causing this issue and how would I explain it to the hosting company?

    I noticed under Site Health => Status the SQL server is outdated. Could this be the cause?

    Thank you.

    Plugin Support Patrick – WPMU DEV Support

    (@wpmudevsupport12)

    3 years, 4 months ago

    Hi @thebusinesscat

    This could be the case, yes but it is not possible to confirm without the log, I see you said that no fatal error is visible on debug.log, could you try to render it on frontend 

    define( 'WP_DEBUG', true ); 
define( 'WP_DEBUG_LOG', true ); 
define( 'WP_DEBUG_DISPLAY', 1 ); 
@error_reporting(1); 
@ini_set('display_errors', 1);

    Let us know the result you got with forcing the error on the front end.

    Even the outdated SQL version is not the cause if the issue we always suggest using an updated version.

    Let us know the result you got.
    Best Regards
    Patrick Freitas

    Thread Starter TheBusinessCat

    (@thebusinesscat)

    3 years, 4 months ago

    Hi @wpmudevsupport12,

    Thank you for the advise.

    I got the following fatal error when rendering on the frontend:

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 131072 bytes)

    I increased the PHP memory limit to 256MB, and it seems to have resolved the issue.

    Thanks once again.

    All the best.

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘Critical Error’ is closed to new replies.