Hello there,
Can you share more deatils of the issue and the step you took to find it. Also, if possible, can you please attach a screenshot to your next reply? It could be helpful to understand the issue better. If you don’t know how to make a screenshot, here’s a quick explanation:
https://en.support.wordpress.com/make-a-screenshot/
That said, it seems you’ve already taken significant steps to address the caching issue. Please ensure that the WP_CACHE line in your wp-config.php is correctly set as define( 'WP_CACHE', true ); and placed above the "That's all, stop editing! Happy publishing." line. Also, check if the wp-config.php file is writable, as write protection can prevent changes from taking effect.
If the issue persists, verify that no other caching systems are active, including plugins or server-level caching. If your hosting provider has a built-in caching system, you may need to contact them for further assistance.
On a side note, I can see an issue with the connection between your site and Jetpack. Jetpack needs this connection to function correctly for most of its features. To correct the issue you’ll need an user-authenticated connection to WordPress.com. Jetpack is a plugin that allows you to use features we developed on WordPress.com on your self-hosted website through the Jetpack plugin. Since these features were built for WordPress.com sites, we need to connect your site via the Jetpack plugin to a WordPress.com account. You can find more details about this here:
https://jetpack.com/support/why-the-wordpress-com-connection-is-important-for-jetpack/
Please follow these steps to connect:
- Go to the Jetpack menu in your WP Admin dashboard
- Access your Jetpack → My Jetpack
- Scroll down to find the Connection area
- Click Connect your WordPress.com account to connect Jetpack to your WordPress.com account
Let us know when you have done this, and we can take another look at your Jetpack connection.
Cheers
Hey @subhansafdars !
I was taking another look and seems like the cache is working now. So I think you figured it out. For future reference, sometimes this issue can be due opcache caching. If that happens, the easy solution is to restart the php process. e.g. restarting httpd or php-fpm whichever is applicable to your setup.
And, as @chatoxz suggested, I highly recommend you fix the Jetpack connection issue for other Jetpack features to work smoothly.
