• Resolved digitalbeetle

    (@digitalbeetle)


    Getting this message when i exit safe mode

    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 one of your plugins, Polylang.

    First, visit your website (https://www.digitalbeetle.in/) and check for any visible issues. Next, visit the page where the error was caught (https://www.digitalbeetle.in/wp-admin/plugins.php?activate=true&plugin_status=all&paged=1&s=) 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.

    https://www.digitalbeetle.in/wp-login.php?action=enter_recovery_mode&rm_token=dErx4RBLCGjQjkvMJ6V4h9&rm_key=3PwpX3jgFrHh3zXGtcfxQr

    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.

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 5.4
    Current theme: Hueman (version 3.5.3)
    Current plugin: Polylang (version 2.7)
    PHP version 7.2.29

    Error Details
    =============
    An error of type E_ERROR was caused in line 59 of the file /home/u453518311/domains/digitalbeetle.in/public_html/wp-content/plugins/polylang/admin/admin-base.php. Error message: Uncaught Error: Class ‘PLL_Wizard’ not found in /home/u453518311/domains/digitalbeetle.in/public_html/wp-content/plugins/polylang/admin/admin-base.php:59
    Stack trace:
    #0 /home/u453518311/domains/digitalbeetle.in/public_html/wp-content/plugins/polylang/admin/admin.php(61): PLL_Admin_Base->init()
    #1 /home/u453518311/domains/digitalbeetle.in/public_html/wp-content/plugins/polylang/include/class-polylang.php(290): PLL_Admin->init()
    #2 /home/u453518311/domains/digitalbeetle.in/public_html/wp-includes/class-wp-hook.php(287): Polylang->init(”)
    #3 /home/u453518311/domains/digitalbeetle.in/public_html/wp-includes/class-wp-hook.php(311): WP_Hook->apply_filters(NULL, Array)
    #4 /home/u453518311/domains/digitalbeetle.in/public_html/wp-includes/plugin.php(478): WP_Hook->do_action(Array)
    #5 /home/u453518311/domains/digitalbeetle.in/public_html/wp-settings.php(409): do_action(‘plugins_loaded’)
    #6 /home/u453518311/domains/digitalbeetle.in/public_html/wp-config.php(79): require_once(‘/home/u45351831…’)
    #7 /home/u453518311/d

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

Viewing 10 replies - 1 through 10 (of 10 total)
  • I have the same problem. I tried to upgrade from 2.6.10 version. PHP version 7.3. WordPress 5.3.

    Same issue here.. any updates?

    I have exactly the same problem.

    Is it possible to downgrade to the previous version, at least while they fix the problem with the new one?

    same problem.

    Last WP version.
    PHP 7.2

    I don’t think so.. if you have some other website with older version installed, you could try to manually copy that to plugins folder, but still I’m not sure if this can work.
    From what I know, downgrade is not possible

    temporally fix from @rafaelcalero :
    To solve it while taking out an update is as easy as commenting the following line:

    /wp-content/plugins/polylang/admin/admin-base.php line 59:

    This line:
    $this->wizard = new PLL_Wizard( $this );

    Replace with this:
    //$this->wizard = new PLL_Wizard( $this );

    Plugin Author Chouby

    (@chouby)

    Hello,

    Sorry for the mess. I made a mistake with the svn manipulation while sending the update of the version 2.7 to www.remarpro.com.

    Hopefully, it is now fixed with the version 2.7.0.1. At least, I don’t have the fatal error with a version downloaded from www.remarpro.com.

    Thanks razzner, this solves my problem.

    Yes, apparently this also solved my problem. Thank you

    After crashing the site a couple of times, contacting NameCheap support and not being able to restore an old version of the plugin, all I did was deleting the plugin (not updating) and installing the latest version. Problem solved.

Viewing 10 replies - 1 through 10 (of 10 total)
  • The topic ‘Site crash after update plugin’ is closed to new replies.