January 25th, 2009

Some Nagging WordPress Issues I’ll Help You Solve

The funny thing about WordPress is the way it behaves differently across my different webhosts – Dreamhost, Media Temple and A Small Orange.

My food blog is hosted on MT. Before I manually upgraded it to WordPress 2.7, it was languishing in the old 2.3 version. Back then when 2.3 was the “in thing” it was already having issues with WP’s AJAX features. But I learned to live with it. Yesterday, while I was making a new post about an Indian Restaurant, the autosave feature was acting like its usual crazy self. It displays an error message “You do not have permission to do that”. Ok, so who does? Like before, I’m not allowed to make new categories. I was forced to create them in phphmyadmin. I don’t care for WP’s AJAX capabilities other than autosave. Otherwise I can totally do away with them.

I was determined to see what was causing the problem. It turns out that it had to do with permissions inside the wp-includes file. But I wonder why it *only* happens on my food blog, and not on my photo blog. Anyway, if nothing else has worked for you, open up your FTP client and connect to your web server. Chmod the wp-includes folder and everything in it to 644. I have tried all combinations of permissions and in this is the only that worked for me. If you can provide alternative solutions, please let me know by leaving a comment below.

Another bug I encountered on my food blog is the news on the dashboard aren’t showing up (solution still up in the air).

UPDATE: I looked into the second bug further and discovered that it is intertwined with the first bug. If I set the wp-includes folder to 644, the problems with autosave and adding categories go away, but as a result, the dashboard news fails to load. To fix it, I set the permissions of the wp-includes -> js -> jquery folder to 744. Still scratching my head over this.

Posted in Announcements


  1. 8 Comments

  2. Ajay said...

    Another problem could be that you got logged off. I’ve kept the post open and then open a new window and login and everything would be fine.

    Jan 25, 2009

  3. jehzlau said...

    CHMOD everything inside your WP folder to 777 and it should work just fine 😀 hehe…

    Jan 26, 2009

  4. Andrew said...

    @Ajay: I’m logged in when I was testing it.

    @Jehz: Yeah tried that too. No luck!

    Jan 26, 2009

  5. Blogie said...

    chmod 777 is dangerous, and on most servers there are protective measures against this, and that’s probably why that didn’t solve the issue.

    Aside from chmod, check your user/group permissions.

    Jan 28, 2009

  6. semidoppel said...

    I can’t get it, I’m not familiar with that. OP me. Anyway, is it ok if we exchange links? Please add me to your blogroll http://www.semidoppel.com, and please visit my site, you can leave comments and exchange thoughts with me.

    Jan 31, 2009

  7. WAYSMAKEMONEY said...

    so its not safe?

    Feb 4, 2009

  8. Rahul said...

    No, its not safe at all. Permissions higher than 755 to your directories is not safe. 777 will give reade/write/execute permissions to the world, and this is really dangerous.

    Feb 25, 2009

  9. emre said...

    so its not safe?

    Jun 6, 2009

Post a Comment