WordPress Development Stack Exchange is a question and answer site for WordPress developers and administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The issue appeared immediately after upgrade. The only part of the application impacted is the sub-menu items under settings where it relates to a plug-in. The core application settings work, just not the plug-ins. All plug-ins are up to date and impacted.


share|improve this question
Title should be "INsufficient permissions...." – markratledge Dec 11 '10 at 19:13

Try visiting the list of users, and re-change your role to administrator. WP may have messed up the permissions array during the upgrade.

share|improve this answer

Probably it changed the permissions of the wp-content directory itself, or one of its subdirectories, in this case, maybe the plugins folder. You can check that with a ftp client (like FileZilla) or ssh.

Comparing with my installations, the wp-content folder has 0755 permissions, which means it has read, write and execution access for the owner, and read and execution access to the group and others, the files inside wp-content has 0644 permissions (read, write and no execution access for the owner, and only read permissions for the group and others).

An easy way to make sure all the permissions are correctly is run through ssh:

 chmod -R a-x+X wp-content/

That takes out the the execution permission (-x) for every user (a) and file inside the folder and its children(-R) and only add it for the directories (+X; that need execution permission to be browsed).

If the permissions are all messed up (let's suppose that files doesn't have the 0644 permissions), you can do it by hand or by doing:

 chmod -R 0755 wp-content/

Which will make every file have execution permission (I think is a security issue, but will last for a few seconds ;)). And then use the first command, that way all permissions would be "reset"; not very elegant solution, but works.

share|improve this answer
This isn't a filesystem permission issue, it's down to WordPress user capablities – TheDeadMedic Dec 11 '10 at 13:58
@thedead Sorry, I had a similar issue =P – pablox Dec 13 '10 at 12:37

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.