Hey @brandohui,
It sounds like a permissions issue is getting in the way of enabling the WP_CACHE constant in your wp-config.php. No worries, let’s tackle this together.
First off, since your wp-config.php file permissions are set to 640, that might be a little restrictive for WP-Optimize to make changes. You could try adjusting the file permissions temporarily. Setting it to 644 or even 660 might do the trick. This way, it’s readable and writable by the owner and readable by others. If you’re using an FTP client or a hosting file manager, just make a quick adjustment to:
chmod 644 /path/to/wp-config.php
After changing the permissions, open up your wp-config.php file. You can manually add the WP_CACHE constant by placing this line near the top, right after the <?php tag:
define('WP_CACHE', true); // WP-Optimize Cache
Save the file and upload it back to your server if you edited it locally. This should help WP-Optimize recognize that caching is enabled.
*Optional: One more thing—make sure the web server user (like www-data or apache) has write access to wp-config.php. If not, WP-Optimize won’t be able to edit the file itself, which could be why you’re seeing that error. And here’s a little extra tip: if permissions are still causing issues, you can add:
define('FS_METHOD', 'direct');
This line bypasses some of the file checks and should give WP-Optimize a smoother path for enabling caching.
Try these out and let me know how it goes : ) Thanks!
