Crash dashboard

Same here:

Fehler-Details
==============
Ein Fehler vom Typ E_ERROR wurde in der Zeile 12 der Datei wordpress/wp-content/plugins/apcu-manager/includes/libraries/decalog-sdk/EventsLogger.php verursacht. Fehlermeldung: Uncaught Error: Undefined constant “DecaLog\DECALOG_VERSION” in /webseiten/wordpress/wp-content/plugins/apcu-manager/includes/libraries/decalog-sdk/EventsLogger.php:12
Stack trace:
#0 /webseiten/wordpress/wp-content/plugins/apcu-manager/includes/libraries/autoload.php(28): include_once()
#1 /webseiten/wordpress/wp-content/plugins/apcu-manager/includes/libraries/decalog-sdk/Engine.php(197): {closure}()
#2 /webseiten/wordpress/wp-content/plugins/apcu-manager/apcu-manager.php(137): DecaLog\Engine::eventsLogger()
#3 /webseiten/wordpress/wp-content/plugins/apcu-manager/apcu-manager.php(155): apcm_run()
#4 /webseiten/wordpress/wp-settings.php(517): include_once(‘…’)
#5 /webseiten/wordpress/wp-config.php(89): require_once(‘…’)
#6 /webseiten/wordpress/wp-load.php(50): require_once(‘…’)
#7 /webseiten/wordpress/wp-admin/admin-ajax.php(22): require_once(‘…’)
#8 {main}
?thrown

I’m having the same problem with the site crashing and going into recovery mode:

An error of type?E_ERROR?was caused in line?12?of the file?/home4/pipbujmy/public_html/zanshin/wp-content/plugins/apcu-manager/includes/libraries/decalog-sdk/EventsLogger.php. Error message:?Uncaught Error: Undefined constant "DecaLog\DECALOG_VERSION" in /home4/pipbujmy/public_html/zanshin/wp-content/plugins/apcu-manager/includes/libraries/decalog-sdk/EventsLogger.php:12 Stack trace: #0 /home4/pipbujmy/public_html/zanshin/wp-content/plugins/apcu-manager/includes/libraries/autoload.php(28): include_once() #1 /home4/pipbujmy/public_html/zanshin/wp-content/plugins/apcu-manager/includes/libraries/decalog-sdk/Engine.php(197): {closure}('DecaLog\\EventsL...') #2 /home4/pipbujmy/public_html/zanshin/wp-content/plugins/apcu-manager/apcu-manager.php(137): DecaLog\Engine::eventsLogger('apcu-manager') #3 /home4/pipbujmy/public_html/zanshin/wp-content/plugins/apcu-manager/apcu-manager.php(155): apcm_run() #4 /home4/pipbujmy/public_html/zanshin/wp-settings.php(517): include_once('/home4/pipbujmy...') #5 /home4/pipbujmy/public_html/zanshin/wp-config.php(90): require_once('/home4/pipbujmy...') #6 /home4/pipbujmy/public_html/zanshin/wp-load.php(50): require_once('/home4/pipbujmy...') #7 /home4/pipbujmy/public_html/zanshin/wp-login.php(12): require('/home4/pipbujmy...') #8 {main} thrown

Same here. Here’s how I was able to disable the plugin.

Edit the file /wp-content/plugins/apcu-manager/includes/libraries/decalog-sdk/EventsLogger.php

Replace line 12 if ( ! defined( 'DECALOG_VERSION' ) && version_compare(DECALOG_VERSION, '4.0.0', '<') ) { with if (true) {

Then, on the command line, I ran wp plugin deactivate apcu-manager which disabled the plugin.

Hope that’s of some use to people.

For my part, I added a . to the folder in the ftp to deactivate it and then removed its installation. I reinstalled version 3.7.2 while waiting for a patch.

Dear all!
I am deeply, deeply sorry for what has just happened: a wrong development version has been pushed on the WordPress directory (due to an error on my part) and, consequently, deployed on your sites.
A new version is now available and should fix this issue.
Please, accept my sincere apologies.
Pierre

The newly pushed version solved the problem, thanks! I’ve re-activated the plugin and everything seems to be working correctly.

@pierrelannoy Thank you !
Don’t worry, these things can happen. Thanks again for the quick fix.

All right, a little more information from what I can see in my case…

I’ve got a client hosting on Bluehost. The errors I get are quite similar to what @zanduino posted, so I won’t repeat them.

There are just two sites there, both of them using APCu Manager, both also set to auto-upgrade (for almost all, if not all plugins).

As soon as the auto-upgrade facility kicked in (not necessarily at the same time, mind you) — around 04-May-2024, 18:13:57 to 18:23:30 UTC — the site(s) started throwing the error as reported. Note that in my case it didn’t merely affect the Dashboard; the whole site was knocked down, with a message being displayed saying that there had been a critical error.

Fortunately, Bluehost includes the CLI utility wp, so I proceeded to deactivate and then delete APCu Manager:

wp plugin deactivate apcu-manager --skip-plugins
wp plugin delete apcu-manager --skip-plugins
wp cache flush --skip-plugins

Note the need to include the --skip-plugins option, or else APCu Manager’s fatal error will also affect the CLI, and it won’t work.

Also note that merely deactivating the plugin was not enough. This is because apparently APCu Manager adds a few extra hooks to clean the cache, a few wp-cron entries, etc., and these need to be removed as well. Of course, if the plugin crashes with a fatal error, it is not able to clean up after itself. Forcing its deletion is the only way of getting it to work again.

Obviously, this also means that everything will become a tad slower…

I’m not quite sure what exactly is happening. The error being thrown is Uncaught Error: Undefined constant "DecaLog\DECALOG_VERSION". A quick search on Google showed that DecaLog is one facility used by WordPress itself to do some of its own logging as well.

My theory, therefore, was if I placed a ‘fake’ entry on wp-config.php like this:

define( 'DECALOG_VERSION', '1.0' );

then at least I would avoid a fatal error — I’d still get other errors for sure (e.g., ‘wrong version’), but I might at least try to understand things better.

No such luck — creating a ‘fake’ DecaLog version just gets a new fatal error:

PHP Fatal error:  Declaration of DecaLog\EventsLogger::emergency(Stringable|string $message, array $context = []): void must be compatible with Psr\Log\LoggerInterface::emergency($message, array $context = []) in /[PATH-REDACTED]/wp-content/plugins/apcu-manager/includes/libraries/decalog-sdk/EventsLogger.php on line 325

At this point, it was clear to me that further debugging would require much more time than I have available ??

But, who knows, maybe this can give the APCu Manager plugin developers some clues on what’s wrong…

I’ll gladly submit a more detailed list of my configuration on both these sites, if needed for debugging. But from the earlier comments it seems that a vast variety of different setups are giving the same error as well, so I would think that the environment itself is very likely not the culprit (for what’s worth, that server is running PHP 8.3.6 on Apache).

Thank you so much for this report @gwynethllewelyn !

A fix is available for some minutes now. You can update to 3.8.3…

Whoops… that’s what happens when taking too much time to answer hehe…

@pierrelannoy thanks so much for the almost-instant-reply!

I can also confirm that 3.8.3 is working again on both websites I mentioned a bit ago.

However….

Interestingly, I cannot seem to be able to activate them from the CLI!

$ wp plugin activate apcu-manager --skip-plugins
Fatal error: Declaration of DecaLog\EventsLogger::emergency(Stringable|string $message, array $context = []): void must be compatible with Psr\Log\LoggerInterface::emergency($message, array $context = []) in [...REDACTED PATH...]/wp-content/plugins/apcu-manager/includes/libraries/decalog-sdk/EventsLogger.php on line 325

(Plugin remains inactive)

But there is no problem whatsoever activating it from the WP Dashboard, so I guess it’s fine!

• This reply was modified 6 months, 3 weeks ago by Gwyneth Llewelyn. Reason: typos!

Hi. I have five websites running APCu Manager and, of course, all of them stopped working because of version 3.8.2. The five websites are running on the same Linode VPS (and therefore have the same version of PHP 8.2, Debian Linux 12.5, etc.)

I have just upgraded the five installations to version 3.8.3 and, interestingly, three of the websites are working fine with 3.8.3 while two of them are throwing PHP fatal errors:

PHP Fatal error: Declaration of DecaLog\EventsLogger::emergency(Stringable|string $message, array $context = []): void must be compatible with Psr\Log\LoggerInterface::emergency($message, array $context = []) in /wp-content/plugins/apcu-manager/includes/libraries/decalog-sdk/EventsLogger.php on line 325

I have disabled APCu Manager in the meantime for those two websites and they are working again.

Any idea of what is happening and how the solve the issue?

Hello, for me version 3.8.3 continues to cause problems, I deactivated it again. I am running PHP 8.2 on all my site. I see “APCU “Dependencies check failed”

• This reply was modified 6 months, 3 weeks ago by antoniomanco.
• This reply was modified 6 months, 3 weeks ago by antoniomanco.

@gwynethllewelyn & @avinashm : sorry to hear that… This is strange behavior I must admit and I’m not sure what’s going on. It’s like upgrade is not complete or some files are in cache. Do you experiment the same issue after some hours? If yes, do you have an “agressive” code caching strategy (like OPcache with special settings)?

@antoniomanco : could you tell me where you see “APCU Dependencies check failed” message? It’s not coming from APCu Manager and I would like to understand what is generating it…

I see the exactly the same error like @avinashm when trying to activate the new version here. Let me know if I can help with more debugging / testing.

Hello @m0urs

I suggest you to delete the plugin (from WP admin, while plugin is already deactivated), then fully reinstall it.
If you do like that, what is the error?