2.6 upgrade complete: You do not have sufficient permissions to access this page

Did you happen to solve this yet? I just upgraded from 2.51 to 2.61 on windows 2003 server and I am getting the same error. I have my backups but really didn’t want to roll it all back.

Thoughts? Solutions?

Thanks,
Jeremy

I had the same problem upgrading from 2.3.3 to 2.6.1. The access issues disappeared when I deleted the secretkey line from wp-config.php (step 12 of the upgrade procedure). After reading a bit more on this site, I modified the sample wp-config file from 2.6.1 with the data from my old wp-config file and uploaded this new version. That solved the problem.

Hey, just delete the SECRET KEY there in ur wp-config.
I have luck with that!

SECRET KEY function should be improved…how can this happen…

Deleting secret key worked.

Tried force upgrade: No success.
Tried deleting secret key: No success.

Where I’m at now:
I can log in as admin, but I have no admin privs.
I can view Dashboard, but can’t create new posts, edit comments, or do any of my admin functions.

Any other ideas?

And what about the ideas posted right above?

Yes, I’ve tried those things. Would you like a more complete list?

– Upgraded to latest version of WordPress
– Received “You do not have sufficient permissions” message
– Tried force upgrade
– Got into Dashboard, although no admin privs
– Cleared cache, cookies and history
– Got into Dashboard, although no admin privs
– Tried different browsers: IE, Firefox, Safari, Chrome
– Got into Dashboard, although no admin privs
– Tried another computer
– Cleared cache, cookies and history on all browsers on the new computer
– Got into Dashboard on all browsers, although no admin privs
– Tried deleting secret key
– Cleared cache, cookies and history
– Got into Dashboard, although no admin privs
– Deleted plugins folder
– Cleared cache, cookies and history
– Got into Dashboard, although no admin privs

Not to be snippy, but I wouldn’t waste anyone’s time posting here unless I’d already tried the suggested solutions.

One thing is missing from that list: clicking on the link in my post and trying what is described in that post.

Your link takes me to the suggestion about deleting the secret key. I’ve done that.

Sorry, I didn’t see it in the list…

It was also in my original post. Second line from the top.

Hey all –

I just upgraded from 2.3.1 to 2.6.5 and I got the exact same error after going to the /wp-admin. I entered my correct credentials and the error popped-up. The commenting out of the secret keys in my wp-config.php seemed to solve the issue. What’s the point of the secret key anyway??

just upgraded to 2.6.5 and got the same error. deleted the secret key and I can get in now.

I was able to get in right after the download (with the secret key still in the config file) but after about a half hour it wouldn’t let me in. This happened on 2 different blogs.

Hey there – I went through this error for a full day.

Note: I wasn’t upgrading, I was moving the site to another box. Importing the files through XML were leaving 300 posts behind… and duplicating comments every time I retried to import. So to go around this, I had to go into MySQL and take care of it manually.

Once I did – I came across the same error message. I tried all the suggestions you guys had. Nothing worked.

Here’s what caused my problem, hopefully it will help someone.

The moron that installed the first version here, actually gave the secret key… not ignoring it – shocked me. So moving the entire DB over – and changing the options table to refer to the new URL – didn’t work.

Deleted the DB and started over. I moved all tables except for the options table. Same message. Furious.

So, my fix came down to these conditions:
– Create the brand new site, with the table prefix to match (my server guy picked a “wpUS_” prefix, our windows version wasn’t case sensitive, but the new Linux version… was.
– Move the old wp_config file over, after changing the host/user/db fields in it for the new box.
– Move all the tables, except for the options table.
– Go into options table, and fix the fields that referenced the old site.

Then my uploads would work. CHMOD 777, didn’t work. It changed the permission to 777, but the upload still didn’t work. Furious.

Luckily I have root access to the box. I SSH’d to it, and noticed that my apache user wasn’t the owner. The FTP account was, because I moved the files through it. I made the Apache account the owner for it, and then went back to 755, and it worked. And it’s secure again.

Like I said, not exactly what you’re going through, but the step I would go through if I were you – were to backup my data to SQL, initialize with a clean installation, and then move the posts, comments, taxonomy and meta data manually. I don’t trust upgrades for beans. With any software.

As a side note – I wouldn’t ever rely on the dumps. I had two people do a dump, the file was different each time. I did a dump, and got a 5MB file, a 6MB file, a 560KB file, and a 2.3MB file.

Use one, it’s incomplete, use all, dups… and the real odd thing – I never got Decembers posts in any of these scenarios. Real mess.