Urgent! CE recursively chmodding ALL directories and files to 755

Yes, there’s something seriously wrong with the latest update. I have several sites and after updating, all of them have been completely broken.

On my sites I had “There has been a critical error on your website” error message after updating. I tried uploading old cache enabler plugin files and restored database from a backup file but that didn’t help. I had to do complete site restores from cPanel backup files to get the sites working again.

• This reply was modified 3 years, 2 months ago by HarriL.

Hi, what I observing is NGINX produce more 500 or site not reachable results than before withou kowing reason and without markable log entrees. Use with care!

I’d recommend just rolling back to 1.7.2 for now

after the last 2 updates hosting crashes, and if i disable the plugin via FTP somehow it empties my wp-config.php file :)))

i have to recover it from the backup

i never exprienced this before… having a empty wp-config.php file from a plugin update

Fixed in version 1.8.4.

This is happening again, people upgrading to 1.8.5 are experiencing it, killlinnggg ussssss

PHP Warning: chmod(): Operation not permitted in /home/nginx/domains/domain.com/public/wp-admin/includes/class-wp-filesystem-direct.php on line 173

| cache-enabler | active | none | 1.8.5 |

@justin-bigscoots, in version 1.8.5 the only place Cache Enabler will potentially change a mode for the access permissions through the WordPress filesystem is when creating the cache and settings directories. Unless overridden by a constant, these are in the following locations:

1. /path/to/wp-content/cache/cache-enabler
2. /path/to/wp-content/settings/cache-enabler

Do you not allow that?

I experienced the same thing when the first new post was published after installing Cache Enabler. It was a catastrophic failure and knocked PHP-FPM offline entirely, taking other non-WordPress apps with it.

Restarting PHP-FPM and Nginx fixed the issue. I am using the advanced configuration with the custom Nginx configuration settings. As with Justin’s issue, the only clues were the PHP error log filled with tens of thousands of these lines while the site was offline:

PHP Warning: chmod(): Operation not permitted in /home/nginx/domains/domain.com/public/wp-admin/includes/class-wp-filesystem-direct.php on line 173

The /path/to/wp-content/cache/cache-enabler directory is owned by the PHP-FPM user (nginx) and permissions are set to 777. It has a lot of cached pages as expected inside it, so the plugin does appear to be mostly working as expected.

The /path/to/wp-content/settings/cache-enabler directory is also owned by the PHP-FPM user (nginx) with 755 permissions and the www.domain.com.php configuration file itself has permissions of 644. (I never modified that myself, it was just the default.)

I have manually defined these constants in wp-config.php

define('WP_CACHE', TRUE);
define('FS_METHOD', 'direct');

I defined FS_METHOD based upon @coreyk’s advice given here in this forum. Not sure if it’s relevant or not.

??

# du -sh php_error.log
4.1G    php_error.log

https://share.bigscoots.com/S5TB5jUarq5n9We77Je5Uo5xww84FeIT/Cs9Qq6DtNP.png

Your trying to chmod my entire file system, its not good..

write(7, "[07-Jan-2022 21:39:39 UTC] PHP Warning:  chmod(): Operation not permitted in /home/nginx/domains/domain.com/public/wp-admin/includes/class-wp-filesystem-direct.php on line 173\n", 177) = 177
close(7)                                = 0
stat("/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/self/task/23823/cwd/proc/23823/task/23823/root/proc/18742/task/18742/root/usr/src/kernels/3.10.0-1160.49.1.el7.x86_64/include/linux/platform_data/spi-omap2-mcspi.h", {st_mode=S_IFREG|0644, st_size=559, ...}) = 0