Critical error when activate Page Cache

No one can help me?

Fatal error: Uncaught Error: Call to undefined function atec_nonce()
in?/****/wp-content/plugins/atec-cache-apcu/includes/atec-cache-apcu-page-cache-admin-tools.php?on line?33

same for me

Error details

An E_ERROR error was caused on line 53 of the /home/xxxx/web/xxxx/public_html/wp-content/plugins/atec-cache-apcu/atec-cache-apcu.php file. Error message: Uncaught Error: Failed opening required ‘/home/xxxx/web/xxxx/public_html/wp-content/plugins/atec-cache-apcu/includes/atec-wpca-install.php’ (include_path=’.: /usr/share/php’) in /home/xxxx/web/xxxx/public_html/wp-content/plugins/atec-cache-apcu/atec-cache-apcu.php:53
Stacktrace: 0 /home/xxxx/web/xxxx/public_html/wp-settings.php(517): include_once() 1 /home/xxxx/web/xxxx/public_html/wp-config.php(90): require_once(‘…’) 2 /home/xxxx/web/xxxx/public_html/wp-load.php(50): require_once(‘…’) 3 /home/xxxx/web/xxxx/public_html/wp-admin/admin.php(34): require_once(‘…’) 4 /home/xxxx/web/xxxx/public_html/wp-admin/plugins.php(10): require_once(‘…’) 5 {main}

thrown

Hello,
sorry for the inconvenience.
I have updated the plugin.
Please deactivate und remove the plugin.
If you have access to /wp-content, please remove object-cache.php.
After that reinstall and activate the new version 1.4.6 from the WP plugin library.
The plugin has a new install routine and should clean up the old object-cache.php in case it exists.

The object-cache is the brand new version 1.2 and I have tested the plugin on different machines, but it is not all that simple. Some files were not in sync in the repository, and that was part of the problem.

Please report if it works.
Regards, Chris

Hello,
sorry for the inconvenience.
Please install the new version 1.4.6.
Regards, Chris.

Many thanks for your reply and your help. I just tried to an other website, and it works ??

Question, in the site health, it seems that I don’t have page cache, do I need another plugin to add with yours to get the page cache? I already activated on your plugin.

Thank you for your help

glad to hear that.

good point, i have added “x-cache-enabled” in v1.4.8 if you update, warning should disappear.
did you manage to activate plugin on first site “dreadlocksnation” too?

please leave a review when you are happy.

Greetings docjojo,

Many thanks for your help, and YES, it works well, on my 2 websites! ??

Perfect.

glad it works.

C.

Thank you for the review!
C.

Sorry to bother you but, I’m facing a problem with the 2 websites, on the site health. Never get this warning about performance with other plugins…

“1 critical issue

Critical anomalies are items that can have a significant impact on the performance or security of your site, and resolving these issues should be a priority.

Page caching is detected but server response time is still slow
Performance
Using page caching improves the speed and performance of your site by serving static pages instead of generating each page from scratch each time a user visits.

The page cache is detected by looking for a possible active cache extension on the site, and also by making three requests to the home page and looking for one or more of the following HTTP client caching response headers :

cache-control, expires, age, last-modified, etag, x-cache-enabled, x-cache-disabled, x-srcache-store-status, x-srcache-fetch-status.
The median server response time was 833 milliseconds. It should be below the recommended threshold of 600 milliseconds.
1 client cache response header was detected: x-cache-enabled.”

Many thanks for your help.

Thanks for your quick reply. The only thing I have in the debug is

Deprecated: Hook pll_after_languages_cache is deprecated since version 3.4 with no alternative available. in /volume1/web/dreadlocksnation/wp-includes/functions.php on line 6078

So nothing about this. I think it’s because my websites are self hosted.

Many thanks

atec_cache_apcu does not use any pll_ polylang functions.
so yes, i think it’s a performance issue on the server.
should be possible to solve.
what do you mean “self hosted”?
you can install atec-cache-info and atec-system-info plugin and send me screenshots.
so that i can help you narrow down the issue.

https://www.ads-software.com/plugins/atec-cache-info/
https://atec-systems.com/WP-Plugins/atec-system-info.zip

@docjojo If you access any forum user’s site, you risk getting banned and having your plugin removed. You need to reply that you understand this in this topic. I have archived your login ask.

While I know you have the best of intentions, it’s forum policy that you not ask users for admin or server access. Users on the forums aren’t your customers, they’re your open source collaborators, and requesting that kind of access can put you and them at high risk.

If they are paying customers (such as people who bought a premium service/product from you) then by all means, direct them to your official customer support system. But in all other cases, you need to help them here on the forums.

Thankfully are other ways to get information you need:

• Ask the user to install the Health Check plugin and get the data that way.
• Ask for a link to the https://pastebin.com/ or https://gist.github.com log of the user’s web server error log.
• Ask the user to create and post a link to their phpinfo(); output.
• Walk the user through enabling WP_DEBUG and how to log that output to a file and how to share that file.
• Walk the user through basic troubleshooting steps such and disabling all other plugins, clear their cache and cookies and try again (the Health Check plugin can do this without impacting any site vistors).
• Ask the user for the step-by-step directions on how they can reproduce the problem.

You get the idea.

We know volunteer support is not easy, and this guideline can feel needlessly restrictive. It’s actually there to protect you as much as end users. Should their site be hacked or have any issues after you accessed it, you could be held legally liable for damages. In addition, it’s difficult for end users to know the difference between helpful developers and people with malicious intentions. Because of that, we rely on plugin developers and long-standing volunteers (like you) to help us and uphold this particular guideline.

When you help users here and in public, you also help the next person with the same problem. They’ll be able to read the debugging and solution and educate themselves. That’s how we get the next generation of developers.

I understand.