• Resolved bredchic

    (@bredchic)


    Hi. Multiple wordpress installations work in front end and crash in back end. All have Polylang 3.3.1 and restart working with the plugin is disabled.

Viewing 8 replies - 1 through 8 (of 8 total)
  • I have the same issue! Did you solve it?

    Thread Starter bredchic

    (@bredchic)

    Hi. Not Jet. I guess we need to wait for an update.

    If you have automatic updates activated, just wait for the next update.

    If you do not have automatic updates activated and you’ve updated it manually, rename the plugin folder of Polylang in order to deactivate it (or deactivate via softaculous if you have it), and reactivate after the plugin will be fixed with a new version.

    Good luck!

    Thanks! Hope they make an update soon.. I cant upload blog posts in the meantime ??

    Plugin Author Chouby

    (@chouby)

    Hello,

    Did you make a search on the forum? Other people had this issue: https://www.ads-software.com/support/topic/polylang-fatal-error-since-09-01-23/.
    Maybe the same as you. Difficult to know as you don’t provide the error message.

    When you The error is : There has been a critical error on this website. Please check your site admin email inbox for instructions.(see screenshot below)
    https://ibb.co/X4m8xmg

    i also received an email stating :

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

    I am receiving error to. Can we downgrade to an earlier version?

    Edit: delete and re-install Polylang solved the issue for me.

    I have the same issue, had to disable polylang to stay online.

    Here is the output of wp_debug.

    Fatal error: Uncaught Error: Class "PLL_Lingotek" not found in /home/wicked1q/public_html/wp-content/plugins/polylang/modules/lingotek/load.php:13 Stack trace: #0 /home/wicked1q/public_html/wp-content/plugins/polylang/include/class-polylang.php(247): require_once() #1 /home/wicked1q/public_html/wp-includes/class-wp-hook.php(308): Polylang->init() #2 /home/wicked1q/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters() #3 /home/wicked1q/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #4 /home/wicked1q/public_html/wp-settings.php(480): do_action() #5 /home/wicked1q/public_html/wp-config.php(95): require_once('/home/wicked1q/...') #6 /home/wicked1q/public_html/wp-load.php(50): require_once('/home/wicked1q/...') #7 /home/wicked1q/public_html/wp-admin/admin.php(34): require_once('/home/wicked1q/...') #8 /home/wicked1q/public_html/wp-admin/plugins.php(10): require_once('/home/wicked1q/...') #9 {main} thrown in /home/wicked1q/public_html/wp-content/plugins/polylang/modules/lingotek/load.php on line 13
    
    Notice: Function is_embed was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/wicked1q/public_html/wp-includes/functions.php on line 5835
    
    Notice: Function is_search was called incorrectly. Conditional query tags do not work before the query is run. Before then, they always return false. Please see Debugging in WordPress for more information. (This message was added in version 3.1.0.) in /home/wicked1q/public_html/wp-includes/functions.php on line 5835
    
    There has been a critical error on this website. Please check your site admin email inbox for instructions.
    

    Some say “check your e-mail” but I receive none for this error.

    • This reply was modified 1 year, 10 months ago by progonkpa.
    • This reply was modified 1 year, 10 months ago by progonkpa.
    Thread Starter bredchic

    (@bredchic)

    Thank you @progonkpa !

    • This reply was modified 1 year, 10 months ago by bredchic.
Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘version 3.3.1 is crashing wp-admin’ is closed to new replies.