Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • May 8, 2019 at 1:54 pm #1098450
    conflock

    After WordPress auto upade to Version 5.2 we are getting an automated email that Enfold is no longer compatible with WP:

    _____
    Howdy!

    Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.

    In this case, WordPress caught an error with your theme, Enfold.

    First, visit your website (MYDOMAIN) and check for any visible issues. Next, visit the page where the error was caught (MYDOMAIN/wp-login.php) and check for any visible issues.

    Please contact your host for assistance with investigating this issue further.

    If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further.

    ******TOKEN LINK

    To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires.

    Error Details
    =============
    An error of type E_ERROR was caused in line 361 of the file /var/www/clients/client20/web70/web/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/template-builder.class.php. Error message: Uncaught Error: Class ‘ShortcodeHelper’ not found in /var/www/clients/client20/web70/web/wp-content/themes/enfold/config-templatebuilder/avia-template-builder/php/template-builder.class.php:361
    Stack trace:
    #0 /var/www/clients/client20/web70/web/wp-includes/class-wp-hook.php(286): AviaBuilder->handler_wp_head(”)
    #1 /var/www/clients/client20/web70/web/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array)
    #2 /var/www/clients/client20/web70/web/wp-includes/plugin.php(465): WP_Hook->do_action(Array)
    #3 /var/www/clients/client20/web70/web/wp-includes/general-template.php(2746): do_action(‘wp_head’)
    #4 /var/www/clients/client20/web70/web/wp-content/themes/enfold/header.php(77): wp_head()
    #5 /var/www/clients/client20/web70/web/wp-includes/template.php(722): require_once(‘/var/www/client…’)
    #6 /var/www/clients/client20/web70/web/wp-includes/template.php(671): load_template(‘/var/www/client…’, true)
    #7 /var/www/clients/client20/web70/web/wp-includes/general-template.php(41): locate_template(Arra
    _____

    Are you aware of this errors?

    May 9, 2019 at 5:50 am #1098744
    Rikard

    Hey conflock,

    No we are not, it’s running just fine on my local installation. Which version of the theme and PHP are you running?

    Best regards,
    Rikard

    May 9, 2019 at 11:24 am #1098863
    conflock

    We’re running PHP Version 7.3.1 and Enfold Version 4.5.6.

    Best regards

    Julian

    • This reply was modified 5 years, 7 months ago by conflock.
    May 13, 2019 at 12:06 pm #1100018
    Günter

    Hi,

    Thank you for reporting this.

    I checked it on my test server PHP 7.3.3 and Enfold Version 4.5.6.

    I do not get the error. I added a check if class ShortcodeHelper exists at this point and it returns true.

    And also from point of program flow – the class is loaded in the init hook and the error is reported in wp_head hook, which is called later. And if this class is missing, the whole output would be broken.

    Do you still recieve this message ?
    Could you try to disable all plugins and check with only WP and Enfold, if this still occurs (frontend or backend)?

    Best regards,
    Günter

    May 13, 2019 at 12:39 pm #1100026
    conflock

    Hi Günter,

    we do still get errors in the WP log on all of our Enfold websites. Even with all PlugIns deactivated:
    ——-
    Notice: avia_post_nav_settings is deprecated since version 4.5.6! Use avf_post_nav_settings instead. Return values handling has changed in /var/www/clients/client20/web70/web/wp-includes/functions.php on line 4711
    ——-

    Best Regards, Julian

    May 13, 2019 at 1:58 pm #1100050
    Günter

    Hi,

    So you only get the last Notice: deprecated since version 4.5.6 ?

    This is something you can ignore – it is only a notice that this filter will be removed in one of the next versions and you should use the new filter.

    Best regards,
    Günter

    May 13, 2019 at 2:30 pm #1100056
    conflock

    In the WP log it seems to be the only message at the moment. After updating to WP 4.5.6 we do still get this email from my first post for all our Enfold websites. I have no idea if these errors still exist. At the moment Ii can’t find anything in the log, so maybe it was just a WP bug.

    Thanks for the quick reply!

    Best Regards, Julian

    May 13, 2019 at 3:16 pm #1100096
    Günter

    Hi,

    Thanks for feedback.

    Could be that when updating WP tried to load something and this caused the error ?

    If everything is running as expected I would say we can ignore this.

    Feel free to come back when you need further assistance. I will close the topic for now.
    Enjoy the theme and have a nice day.

    Best regards,
    Günter

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • The topic ‘WordPress 5.2 upade Enfold fatal errors’ is closed to new replies.