You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So you have selected the "HDD" backend, <subdir>/wp-content/cache/cachify exists, but is empty?
My installation is in a subfolder
/path/to/page is internally redirected to /<subdir>/index.php or transparent, i.e. /<subdir>/path/to/page is called directly?
folder permissions was 750, but modifying to 755 does not help
I would not expect a world-readable to make any difference on the cache-generation side. Cachify (i.e. the PHP process) should be able to write. But we would also expect some kind of error message in case of permission problems.
Now it is not empty anymore, but it was triggered at 14 h, although I tried in the morning to trigger the cache creation with a non-logged-in view of the site.
Maybe because of my usage of APCu?
/path/to/page is internally redirected to //index.php or transparent, i.e. //path/to/page is called directly?
Running Cachify 2.4.0 and WP 6.6.2, but my cache folder is completely empty.
Not sure why this happens. My installation is in a subfolder (folder permissions was 750, but modifying to 755 does not help).
No error in the error log.
The text was updated successfully, but these errors were encountered: