WordPress could not write during an update or install.
WHAT IT MEANS
The file system refused a write.
THE COMMON CAUSES
Directory permissions wrong Ownership wrong, frequently after a restore or an unusual upload method Disk quota full Inode limit reached
CHECK DISK AND INODES FIRST
The cPanel statistics panel shows both.
A full account, or one at its inode limit, produces this. Inodes are hit more often than people expect.
PERMISSIONS
wp-content and its subdirectories need to be writable: 755 with correct ownership.
Not 777. If the application cannot write with correct ownership, the ownership is wrong rather than the permissions being too strict.
OWNERSHIP
Files should be owned by your cPanel user. After a restore or a transfer by an unusual route, they may not be.
Open a ticket and we will correct ownership from the server side.
IF IT AFFECTS ONLY UPDATES
WordPress may be trying to use FTP because it cannot write directly. Correcting ownership resolves that.
