Apache Error Log: “PHP message: Asset CleanUp: Could not write to … //cache

  • Resolved tiger1i1y

    (@tiger1i1y)


    5 years, 9 months ago

    Hello Asset CleanUp,

    Thank you for such an incredible plugin! It does wonders for my site speed and performance scores.

    I just switched from host Bluehost to Cloudways and noticed this error coming up in my Apache Error Log. I believe it has been there all along before I switched hosts, but just wasn’t being alerted.

    Here is some of the error log output:

    [Sun Sep 13 16:19:38.909349 2020] [proxy_fcgi:error] [pid 3096] [client 71.19.145.96:34094] AH01071: Got error 'PHP message: Asset CleanUp: Could not write to /home/471900.cloudwaysapps.com/wdxfhdczwv/public_html//cache/asset-cleanup/css/item/generateblocks-v1f630b052fee13c58a7aea3b827300c88a2d6cc3.css', referer: https://wordpress-471900-1481155.cloudwaysapps.com/

    [Sun Sep 13 16:19:37.690726 2020] [proxy_fcgi:error] [pid 3095] [client 71.19.145.97:34090] AH01071: Got error 'PHP message: Asset CleanUp: Could not write to /home/471900.cloudwaysapps.com/wdxfhdczwv/public_html//cache/asset-cleanup/css/item/generateblocks-v1f630b052fee13c58a7aea3b827300c88a2d6cc3.css', referer: https://wordpress-471900-1481155.cloudwaysapps.com/

    [Sun Sep 13 09:27:20.400399 2020] [proxy_fcgi:error] [pid 27481] [client 195.54.160.21:51284] AH01071: Got error 'PHP message: Asset CleanUp: Could not write to /home/471900.cloudwaysapps.com/wdxfhdczwv/public_html//cache/asset-cleanup/css/item/generateblocks-v1f630b052fee13c58a7aea3b827300c88a2d6cc3.css'

    [Sat Sep 12 20:56:18.105481 2020] [proxy_fcgi:error] [pid 10368] [client 45.148.10.28:58908] AH01071: Got error 'PHP message: Asset CleanUp: Could not write to /home/471900.cloudwaysapps.com/wdxfhdczwv/public_html//cache/asset-cleanup/js/item/superpwa-register-sw-v9ff550eba45d41f2ee70fc8d7916853936557cad.jsPHP message: Asset CleanUp: Could not write to /home/471900.cloudwaysapps.com/wdxfhdczwv/public_html//cache/asset-cleanup/js/item/smush-lazy-load-vda585b65c7726a84036fa1f91ac77565d67c14e1.jsPHP message: Asset CleanUp: Could not write to /home/471900.cloudwaysapps.com/wdxfhdczwv/public_html//cache/asset-cleanup/css/item/generate-child-v66f549c0133c9d7653f1276fd8b271dca02d7fad.css', referer: http://144.202.105.139:80/admin/login.asp

    [Sat Sep 12 20:48:37.340151 2020] [proxy_fcgi:error] [pid 10229] [client 116.75.106.125:58692] AH01071: Got error 'PHP message: Asset CleanUp: Could not write to /home/471900.cloudwaysapps.com/wdxfhdczwv/public_html//cache/asset-cleanup/js/item/superpwa-register-sw-v9ff550eba45d41f2ee70fc8d7916853936557cad.jsPHP message: Asset CleanUp: Could not write to /home/471900.cloudwaysapps.com/wdxfhdczwv/public_html//cache/asset-cleanup/js/item/smush-lazy-load-vda585b65c7726a84036fa1f91ac77565d67c14e1.jsPHP message: Asset CleanUp: Could not write to /home/471900.cloudwaysapps.com/wdxfhdczwv/public_html//cache/asset-cleanup/css/item/generate-child-v66f549c0133c9d7653f1276fd8b271dca02d7fad.css

    I have a directory in public_html (root directory) called “wp-content” where I believe this plugin is trying to write to. I also have a static subdomain to serve cookie-free static assets, but I don’t believe this error log is from the static subdomain, but instead from my main domain.

    How do I get Asset CleanUp to write to /public_html/wp-content/cache/ instead of to /public_html//cache/?

    Thank you so much for your time and help!

    Cheers,
    tiger1i1y

    • This topic was modified 5 years, 9 months ago by tiger1i1y.

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author Gabe Livan

    (@gabelivan)

    5 years, 8 months ago

    @tiger1i1y I’ve checked the error as well as the plugin once again and it relies on WP_CONTENT_DIR constant. If this one is altered in any way by a plugin or if it was set to something else in wp-config.php, then it will trigger such an error. Frankly, this is the first time I hear about it since the plugin has been developed and it strongly suggests something is going on on your end.

    Can you try to edit wp-config.php from the root of your WordPress installation and locate the following code:
    /** Absolute path to the WordPress directory. */
    if ( !defined('ABSPATH') )
    define('ABSPATH', dirname(__FILE__) . '/');

    AFTER this code, please add:

    if ( ! defined( 'WP_CONTENT_DIR' ) ) {
	define( 'WP_CONTENT_DIR', ABSPATH . 'wp-content' ); // No trailing slash, full paths only - WP_CONTENT_URL is defined further down.
}

    It will set the WP_CONTENT_DIR sooner and it might work. Let me know how it goes! Please be sure that the “wp-content” directory exists in the root of your WordPress installation, the same way wp-config.php is 😉

Viewing 1 replies (of 1 total)

The topic ‘Apache Error Log: “PHP message: Asset CleanUp: Could not write to … //cache’ is closed to new replies.