Closed jamieburchell closed 6 months ago
@jamieburchell This issue appears to be a configuration issue in the hosting environment. We see that your post includes "wp-content: not writable" and a WordPress installation path that most likely is owned by "root" and your PHP running user is not "root". We recommend reviewing your server configuration. You can also ask us for help by going to our Premium support page ("wp-admin/admin.php?page=w3tc_support"). Our GitHub issues section is for bugs and enhancements.
It has nothing to do with the wp-content
directory not being writable @cssjoe. It's set like that for security reasons as per Roots Bedrock and WordPress hardening best practice. The folders that need to be writable within it are in fact writable. That includes the W3TC directories and uploads. It's an occasional occurrence (as stated) which further invalidates your reasoning.
I still believe it's a race condition of some sort and I continue to run in to it occasionally.
Your dismissive response and immediate closure of this issue as invalid is frustrating.
Occasionally I am seeing references in my HTML to stylesheets that produce this output:
This results in broken/missing styles on the website.
When this happens, the file in question - in this case
6e7bc.css
doesn't exist in the cache directory. Clearing all W3TC caches does not rectify the issue. To solve it, I had to regenerate Elementor's CSS then clear the W3TC caches.Thinking that something was wrong with the generated CSS from Elementor, I compared the files it generated the first time around with the files that it generated the second time around and they were actually identical.