• i did a fresh install of 3.1.2 and a new database through Godaddy hosting. i can’t create any posts or pages without getting this error:

    You are not allowed to edit this post.

    i also tried to trash some existing posts and got similar errors about how i can’t move to trash.

    i’m the only user set up and i’m an administrator – it shows me logged in as well. i also disabled all plugins and reverted to the base theme – same story.

    the only thing i really did that was extraordinary is import some posts from an older version of the blog and map the users to the one user account.

    if anyone can help i’d appreciate it – pulling my hair out over here.

Viewing 10 replies - 16 through 25 (of 25 total)
  • Just just tried a fresh install of 3.1.2 locally on my computer with XAMPP, imported the old database and restored wp-content/ – and still get the same problems.

    So it must not to do with anything with the server.

    I also think there is something corrupted with the datatabase.

    I know I use to have wordpress working with a XAMPP local install.

    Just to confirm, I also did another fresh install locally, with brand new database and all, and I can post all okay.

    Thread Starter kiess

    (@kiess)

    yeah i can do a fresh install as well even on my hosting server and it works fine — it’s when you import old posts that everything seems to corrupt and fall apart. i don’t get it. but i need old posts so we have to figure this out one way or another.

    Same for me KIESS . wordpress upgrades are not much good for me if I can’t keep my old messages . Surely this isn’t a problem that just we three have . Any developers out there that want a challenge . It looks like a nice little challenge for some one .

    I have solved my problem! It turns out it was something that I did.

    The DB user and password I had in wp-config.php did not have INSERT privileges to the database.

    I had some time in the past, accidentally disabled INSERT for the user.

    Re-enabling the command and checking the user had full access to the DB, then fixed this issue.

    When I was testing locally, I had messed the editing of wp-config.php and my local XAMPP setup was actually accessing the external DB with the bad privileges.

    I only discovered this when I completely deleted my live install, and re-installed it from scratch, when it come to the wizard setup to create the DB, it said that all INSERT commands had failed which I thought was a little odd, because it created the tables and everything fine, and the db user/pass all fine. Further checking in my web hosting config page showed the problem.

    Thread Starter kiess

    (@kiess)

    i don’t think this is the same issue for me/the rest of us. my server (godaddy) sets up the database and user automatically to work with wordpress, and i’m not sure i even see a place in their control panel to change the privileges of a database user (there is only one, after all). on top of that, the whole thing works on a fresh install before you try to import old posts — if it was a user privilege issue i feel like nothing would work on a fresh install either.

    anyway, curious if anyone else tries this and if it works for them.

    Thread Starter kiess

    (@kiess)

    so i have a positive update — i think i finally figured it out.

    i did another fresh install (4 of them, actually) because i was hellbent on figuring out exactly what caused the errors.

    i did an import of old posts from a Blogger blog and everything worked fine and it still let me add posts.

    i did an import of old posts from another WordPress and that also worked fine and let me add posts as well. so far so good.

    then i tried Tumblr, and guess what? it broke again — instantly. every post says “submit for review” instead of “publish” and i can’t do anything.

    i started thinking maybe the export tool that i used for Tumblr somehow corrupted the .xml file i was importing. so i found and used a different export tool, which is here: https://www.tumblr2wp.com/ it generates a wordpress compatible xml file from your tumblr blog and you import it using the wordpress importer.

    guess what? it works.

    all my old posts are now onsite and i still seem to have admin privileges somehow. so i don’t really know what happened or why it’s working, but maybe some Tumblr exporters corrupt the file and thus corrupt your install somehow. either way it seems to be working now — knock on wood.

    hope this works for someone else.

    HELP!!.. I have been working on this issues for so many hours no with no luck. I am logged in as Admin but I cannot create new posts, upload new images or change any plugin settings. I have checked this forum for any solutions and have found none that work. I have done fresh installs, re uploaded database files, checked and rechecked all tables.. I know there has to be a fix but I am at an impasse. If someone has dealt with this before and had successful results please contact me asap. I am willing to pay $ for any help that works. Thanks –

    I was able to resolve this by editing wp-includes/post.php.

    There is a line that reads:

    $post_date_gmt = '0000-00-00 00:00:00';

    I replaced it with:

    $post_date_gmt = current_time('mysql');

    and I did not have any further issues.

    I case that anyone still should have trouble with this, I found a solution that worked for me.

    My setup was moving a blog from one to another using the export/import function. But after importing on the new site i got the message “You are not allowed to edit this post” when I tried to do a new post.

    The solution was to, instead of creating the user from the old database in the wizard, I created them before I started the import and all had admin rights.

    I hope this can help ??

    After a few hours looking into this problem, I found out that the import of the pre-production database onto the real production site, didn’t restore the table structure properly! It missed the auto increment flags (which is the thing that causes this error), and it didn’t restore the proper collation setting.

    I made the settings equal for all 11 tables to the pre-production database that I’d still running on my local NAS and problem solved :)!

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘You are not allowed to edit this post.’ is closed to new replies.