Posted 4 years ago #
Long time wordpress user here. Upgraded to the latest 2.6 like all good wordpressers should and for some reason now when I log in all I get is the "You do not have sufficient permissions to access this page."
I have logged in as admin and other users, all see the same thing. There appears to be a major bug with 2.6, I need to get some posts made does anyone have any ideas here?
Note that the blog itself still shows fine so I am pretty sure that this isnt a DB conenction issue.
Posted 4 years ago #
Can someone please help me? I've tried pretty much everything I can think of short of blowing away my whole blog.
ok so just making sure, you have tried logging in on other networks and computers, other bowsers and so on?
and can you ask others to try to log in?
Posted 4 years ago #
Tried from IE, firefox, and safari. Tried several users. Cleared cache and cookies. Windows, mac, etc.
I have deleted all plugins. I have remove everything except for wp-content and wp-config and unzipped everything fresh several times. I have read through the forums and actually found other people with the same issues, alas, no fix as of yet.
yeah unlike all wordpress users i have not updated any of my blogs to wp6 waiting till these bugs are all cleared :)
Posted 4 years ago #
I am wishing I had not upgraded myself. Especially since it appears like no fix is in sight.
Posted 4 years ago #
Does anyone know when a new version is set to be released? I am handcuffed, my blog is serving content fine, but I am locked out and cannot add/edit/delete any content.
Maybe someone knows a way that I can back up my posts and I will just start again from scratch?
Posted 4 years ago #
Is anyone willing to help em save my blog? What say you mods?
Posted 4 years ago #
Is there any way that I can at least save the content?
Posted 4 years ago #
Have you tried:
It's a really old fix but did the job for me with 2.6.
Posted 4 years ago #
Having this issue now with my 2.6 upgrade and haven't fixed it. I tried the force-upgrade.php script to no avail. Any thoughts?
Posted 4 years ago #
@Ziyphr: yep tried the force-upgrade to no avail. At this point I just want to get a dump of my data that I can dump into a fresh install. But it would be nice just to fix the problem too.
Posted 4 years ago #
I am trying to go to: http://www.domain.com/wp-admin/export.php and I am getting the same errors. This is starting to piss me off. Anyone out there know how I can at least get a WXR?
Posted 4 years ago #
FYI - Even the xmlrpc interface wont let me interact with the blog via scribefire (a last ditch effort to inform my blog readers of the dilemma). It throws "Sorry, you must be able to edit posts on this blog in order to view categories."
In the DB that user has a login level of 10, what gives???
Posted 4 years ago #
OK so I need to start all over, but I am very reluctant to go with wordpress this time around. Mainly bummed that all the mods have blatantly ignored this thread and refused even a suggestion. How would they feel if it were their blog and their users left in the lurch?
Posted 4 years ago #
Did a completely fresh install of wordpress, brand new DB, etc. And I STILL get "You do not have sufficient permissions to access this page" I am so exhausted here...
Posted 4 years ago #
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
Posted 4 years ago #
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.
Posted 4 years ago #
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...
Posted 4 years ago #
Deleting secret key worked.
Posted 4 years ago #
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?
Posted 4 years ago #
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.
Posted 4 years ago #
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...
Posted 4 years ago #
It was also in my original post. Second line from the top.
Posted 4 years ago #
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??
Posted 4 years ago #
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.
Posted 4 years ago #
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.
This topic has been closed to new replies.
