tesscorinne

After doing some poking around in the backend, it seems like the problem only happens once I try to activate Comet Cache. I had my webhost reset the file ownership to “mydomain”, and everything worked fine and regenerated correctly until I reinstalled Comet Cache. After reinstalling Comet Cache and clearing the AO cache, the owner of the files and directories within wp-content/cache/autoptimize/ got reset to the “apache” user. I have to contact my webhost and ask them to change the file ownership again, but I suspect there may be some conflict.

That being said, I will be happy to leave a review! Thank you for being such a dedicated developer and so committed to your community.

I will ask around there. Thank you for all of your help!

Is there another way that I could change the uid that AO retrieves to create its directories?

I checked the name listed for the UID and it just says “apache”

The user is mydomain@localhost, and it’s the same user that owns wp-content/cache/ and wp-content/cache/autoptimize/. Those folders both have permissions set to 755. The site is on a shared host and behind a load-balancer, if that makes any difference.

I did also just notice that the owner listed for wp-content/cache/autoptimize/css/, and wp-content/cache/autoptimize/js/, and the .htaccess within wp-content/cache/autoptimize/ have a different owner than the rest of the site.

The user is mydomain@localhost, and it’s the same user that owns wp-content/cache/ and wp-content/cache/autoptimize/. Those folders both have permissions set to 755. The site is on a shared host and behind a load-balancer, if that makes any difference.

I did also just notice that the owner listed for wp-content/cache/autoptimize/css/, wp-content/cache/autoptimize/js/, and the .htaccess within wp-content/cache/autoptimize/ have a different owner than the rest of the site.