Critical Error with last MLS update
-
Hello,
With the last Multisite Language Switcher update on my site (25th of August) the site crashed and I got the WordPress “Critical Error” message and no more access to wp-admin.
I deactivated the plugin after connecting by FTP, and now the site is active again, but without the flag or Switcher function.
I will now update to WordPress 5.5.1, but can I enable the Multisite Language Switcher plug-in again? Or do I need a patch — or new version of MLS?
Theme : Uncode
Thank-you for your help.
Catherine
-
For info :
The MLS version actually installed but deactivated : 2.4.7The minimum for PHP version is 7 since 2.4.0 … please, what version is installed on your webserver!
Let me know,
DennisHello,
The Global PHP version is 7.2.
Catherine
OK, very good. Do you have more detailed information coming from the error.log of your webserver?
I saw through the Jetpack log that a few minutes after the auto-update of MLS on the 25th August, the site went down. In the OVH error logs for the 25th of August, I don’t see anything, but then again I know nothing about this! They seem pretty much the same for the 24th and 26th :
[Tue Aug 25 00:47:02 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 01:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 02:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 03:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 04:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 06:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 07:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 08:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 09:47:02 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 10:47:02 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 11:47:02 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 12:00:00 2020] [error] [client 78.85.221.126] [host http://www.horus-finance.com] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace.
[Tue Aug 25 12:47:02 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 13:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 14:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 15:47:02 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 16:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 17:47:02 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 18:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 19:47:02 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 20:47:02 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 21:47:02 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 22:29:24 2020] [error] [client 91.185.70.60] [host http://www.horus-finance.com] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use ‘LimitInternalRecursion’ to increase the limit if necessary. Use ‘LogLevel debug’ to get a backtrace.
[Tue Aug 25 22:47:02 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.
[Tue Aug 25 23:47:01 2020] [warn] [client 127.0.0.1] [host horusfin.cluster003.ovh.net] (22)Invalid argument: Cannot fix environment variables for container, continue anyway.I’m sorry but these lines don’t help much. They are just warnings and no error-messages.
BTW Version 2.4.8 is the last one. Please try to update to that version.
- This reply was modified 3 years, 7 months ago by Dennis Ploetner.
So after updating to WordPress 5.5.1, I updated MLS to 2.4.8 and then reactivated the plug-in — it works again!
Not sure what happened… Thanks for your help!
Best
CatherineI’m glad it helped!
- The topic ‘Critical Error with last MLS update’ is closed to new replies.