Cannot write to file

  • Resolved slhctech

    (@slhctech)


    4 years, 2 months ago

    Hi Gabriel

    I’ve been checking the various log files on our server and I noticed the file php_errorlog is getting steadily larger. The first entry was on the 18th September when I moved our site to a different host (Siteground) and it now has 1300 entries all similar to the one below. As far as I can tell wp-content is writable and the directory wp-content/cache/asset-cleanup/css/item/ has actually got the file mentioned in it. Any ideas?

    [21-Sep-2020 13:34:47 UTC] Asset CleanUp: Could not write to /home/customer/www/rivergippingtrust.org.uk/public_html/wp-content/cache/asset-cleanup/css/item/widgetopts-styles-vd3564ed18d1ecb0e6afc71936d6a84c3bccba6e7.css

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter slhctech

    (@slhctech)

    Hi Gabe

    Any movement on this?

    Spencer

    Thread Starter slhctech

    (@slhctech)

    Gabe

    Just checked the log file again and the problem seems to have gone away. At least there have been no more entries since the 21st September so I’ll mark this as resolved.

    Plugin Author Gabe Livan

    (@gabelivan)

    @slhctech thanks for letting me know! This is one of those odd things when something is getting fixed by itself and it should not have happened in the first place. If /home/customer/www/rivergippingtrust.org.uk/public_html/wp-content/cache/asset-cleanup/css/item/ was writable, there shouldn’t have been any errors like the one you mentioned. At least, the errors were printed to the visitors, which is good. Perhaps, someone or something (e.g. a PHP script) changed the writing permissions and it made it work as it should have been.

    I checked your website and there are files there that were created so writing permissions are fine now. We’ll consider this topic as resolved in this case ??

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Cannot write to file’ is closed to new replies.