No cache directory no caching files exists

Are any notices shown in the WordPress dashboard or Cache Enabler settings page? Can you please provide a direct URL to your website so I can take a look? If you do no want to share this publicly feel free to use our contact form while referencing this support thread. It’d be helpful to receive a screenshot of your Cache Enabler settings as well.

no notices, no conflicts in server logfie. no cache directory in: web/wp-content/cache/cache-enabler/
Cache directory has no /cache-enabler/ dir – so it can’t deliver caches while is not existing.

Maybe this info is important for you:
Woocoommerce is with subscribtion and membership plugins etc. active!

• This reply was modified 3 years, 6 months ago by agenciesFirst.

Thanks for the additional information. The cache directory is only created by Cache Enabler if it caches a page and that directory does not already exist. Just so you’re aware, when the plugin is updated the complete cache will be cleared. New pages will then have to be created again.

To troubleshoot this further, can you please provide a direct URL to your website and a screenshot of your Cache Enabler settings?

Thanks, not needed screenshot. Cache-Enabler dir was created in ‘/web/wp-content/settings/’ not in ‘/web/wp-content/cache/’ as expected. So that’s wrong and the onliest problem. Chache dir not expected in /cache/ its in /settings/ with my domain. dir are chmod 755 that must enough. Thanks I’ll look deeper and reporting you

Sounds good. The settings directory is not the cache directory. By default, Cache Enabler will store the settings files in wp-content/settings/cache-enabler and the cache files in wp-content/cache/cache-enabler. These can be manually overridden as of version 1.8.0 through constants.

The settings file is required to cache the page. That means if it does not exist the first page request will create the settings file, the second will cache the page, and the third will receive the cached page.

return array (
‘version’ => ‘1.8.1’,
‘use_trailing_slashes’ => 1,
‘permalink_structure’ => ‘has_trailing_slash’,
‘cache_expires’ => 1,
‘cache_expiry_time’ => 0,
‘clear_site_cache_on_saved_post’ => 0,
‘clear_site_cache_on_saved_comment’ => 0,
‘clear_site_cache_on_saved_term’ => 1,
‘clear_site_cache_on_saved_user’ => 0,
‘clear_site_cache_on_changed_plugin’ => 0,
‘convert_image_urls_to_webp’ => 1,
‘mobile_cache’ => 0,
‘compress_cache’ => 1,
‘minify_html’ => 1,
‘minify_inline_css_js’ => 1,
‘excluded_post_ids’ => ”,
‘excluded_page_paths’ => ”,
‘excluded_query_strings’ => ”,
‘excluded_cookies’ => ”,

Thanks. That shows your settings file exists. If your pages are not being cached when logged out even after clearing your browser cache and cookies then that indicates something is causing the Cache Enabler cache to be bypassed. To confirm, you’re not using any of the Cache Enabler hooks, right?

If yes, then there are several ways to continue troubleshooting this depending on your preference. One would be temporarily deactivating one plugin at a time, testing if a page can be cached afterwards (when logged out and with the browser cache disabled). If you don’t want to start with that I’d be happy to take a look at your plugins first to see if I can identify where the issue may be at.

To do this, please either share a screenshot of your plugins installed or your Site Health Info. If required, our contact form previously mentioned can be used to share this privately.

• This reply was modified 3 years, 6 months ago by Anonymous User 16850768. Reason: clarity

same problem on an apache server. after the update nothing is cached anymore.

• This reply was modified 3 years, 6 months ago by René.

Hi, also not working, no “cache” folder in /wp-content/, nothing is cached, 1.7.2 worked fine. Also no errors in logs.

Hi Corey, yesterday evening I tied following steps on other server:
was a old one debian 8 with Apache and php 7.2, also fpm and WP 5.7.x (last one before 5.8).
I logged me completly out from backend, logged into again. Than I load webpage from second browser and just after these action will CacheEnabler creates the cache directory in the correct place. But! First I have to load the website from second browser after login otherwise not cached. If you stayed login and use Google Pagespeed Insight to checking the page this causes a pre-loading all cache from there, than stayed the cache empty. And when I make changes in pages, CacheEnabler does not updating the cache. Than I have to do the first steps from above again. I using warm cache plugin to drive CacheEnabler preloaded automatically from extern cornjob, but has no effect anymore. In the last version was the cache ‘dir’ everytime present and was only removed when I deactivating CacheEnabler, when I purging or clearing the cache, only the files are gone not the direcoty too. That is a new behavior or incorrect? I have no idea what’s going on. Hope you get the right way for fixing that. Thanks for attention

Same error here, nothing cached after update

Seems wp-config file is touched by last update

define(‘WP_CACHE’, true); // Added by Cache Enabler

this code has disappeared

I think the error could be related to wp-config.php modification, some security settings or configurations may not work, in my case it seems that plugin update just deleted the sentence and did not write other things.

Maybe there are some missing logic at the config.php edit function?

if ( $set && ! $found_wp_cache_constant ) {
            $ce_wp_config_lines  = '/** Enables page caching for Cache Enabler. */' . PHP_EOL;
            $ce_wp_config_lines .= "if ( ! defined( 'WP_CACHE' ) ) {" . PHP_EOL;
            $ce_wp_config_lines .= "\tdefine( 'WP_CACHE', true );" . PHP_EOL;
            $ce_wp_config_lines .= '}' . PHP_EOL;
            $ce_wp_config_lines .= PHP_EOL;
            $wp_config_file_contents = preg_replace( '/(\/\*\* Sets up WordPress vars and included files\. \*\/)/', $ce_wp_config_lines . '$1', $wp_config_file_contents );
        }

        if ( ! $set ) {
            $wp_config_file_contents = preg_replace( '/.+Added by Cache Enabler\r\n/', '', $wp_config_file_contents ); // < 1.5.0
            $wp_config_file_contents = preg_replace( '/\/\*\* Enables page caching for Cache Enabler\. \*\/' . PHP_EOL . '.+' . PHP_EOL . '.+' . PHP_EOL . '\}' . PHP_EOL . PHP_EOL . '/', '', $wp_config_file_contents );
        }

        file_put_contents( $wp_config_file, $wp_config_file_contents, LOCK_EX );

@agenciesfirst, thanks for the additional information. I still can’t say exactly what’s occurring as I don’t have enough data. I will need the following information to continue troubleshooting this issue:

1. Direct URL to your website.
2. List of plugins installed on your website. Either a screenshot of the plugins page or copy the Site Health Info.

This can all be shared privately through our contact form while referencing this support thread if you don’t want to share it here.

@mobiflip and @jordiniubo, are any notices shown in the WordPress dashboard or Cache Enabler settings page? If no, do you have any custom extensions added to Cache Enabler through any hooks? Can you also provide the information requested above?

@javierdemuga, Cache Enabler touching the wp-config.php file on an update is not new. Without checking specifically, I think this has been occurring since version 1.5.0. The snippet you’ve shared, define(‘WP_CACHE’, true); // Added by Cache Enabler, is from versions 1.4.9 and below. This and what Cache Enabler currently sets will be removed when the disk is cleaned, which can occur when the plugin is updated or deactivated. In an update, the disk is setup after being cleaned, which will proceed with creating the advanced-cache.php drop-in and then setting the WP_CACHE constant. It will only do this if Cache Enabler thinks the file is the default config, which is considered true if the /** Sets up WordPress vars and included files. */ line exists (and has the correct permissions.) If this line is not found Cache Enabler will not set the WP_CACHE constant. In that case it would have to be set manually. Are you receiving the WP_CACHE related notice in your Cache Enabler settings? If yes, I’d try deactivating and then activating the plugin again. If it is still not set then that means you will have to do it manually.

• This reply was modified 3 years, 6 months ago by Anonymous User 16850768. Reason: clarity

@mobiflip and @jordiniubo, to add to your reply. I forgot to mention that you may want to first try deactivating and then activating Cache Enabler again before proceeding with the next steps.

Thank you @coreyk for your detailed answer, you are right.

After deactivating and reactivating and checking more thoroughly I believe I am aligned with the same problem as @agenciesfirst , /cache-enabler folder is not created.

Maybe it is related with get_cache_dir function? Also tried to create manually cache-enabler folder in /wp-content/cache/ but that did not help so it is not only about the folder creation.

Using PHP 8 and my website is on a shared hosting