[Kurt Gilek]

I tested the W3 Total Cache for the purpose of database caching only (no page caching)
First everything looked good, but then problems occurred in other plugins because of wp cron problems.
With the help of the support of these plugins, we narrowed the problem down to Op Code caching.
I had to turn off W3 Total Cache – and everything worked fine again.
I only need db caching and nothing else from W3 Total Cache,
but it seems I cannot turn off the Op Code caching, there is no option to do so.

Any suggestions ?

[Marko Vasiljevic]

Hello Kurt,

Thank you for reaching out, and I am happy to help!
In W3 Total Cache, the Opcode is read-only, meaning if the W3 Total Cache detects the opcode is enabled on the server, it will show enabled there, and you can purge the Opcode via the W3 Total Cache.
The question is if the Opcode is used by other plugins?
What you can try is to disable the OP code entirely:
Using php.ini or .user.ini for system-wide settings
1. Locate your php.ini file:
This file contains the main configuration for your PHP installation.
2. Edit the opcache.enable setting:
Find the line opcache.enable=1 (or a similar value) and change it to opcache.enable=0.
3. Alternatively, use .user.ini:
For domain-specific settings in environments like Plesk, you can use a .user.ini file instead of php.ini.
4. Restart your web server or PHP-FPM:
After saving the file, restart the web server (e.g., Apache, Nginx) or the PHP-FPM process for the changes to take effect.
Using .htaccess (for Apache users)
Create or edit .htaccess: If your PHP is running as an Apache module, you can use an .htaccess file.
Add the directive: Include the line php_flag opcache.enable Off in the file.
Save the file: The change will be applied immediately for that directory and its subdirectories.

Let me know if this helps!

Thanks!

[Author]

Posts