Cannot access Dashboard after 3.4.1 upgrade

Maybe .htaccess file was overwritten during upgrade? Or you might also wanna try disabling the plugins, by moving the plugin folders to another (because you can’t login to disable them from Admin Panel), try to login and move the plugins back.

Just make sure to backup the site and database before doing this.

Is there any way of contacting a damn WP person? I’m having this same issue with the update, and I cannot find where I can contact someone for help. They got so many links I don’t even know where to look.

WP is not suited for someone that has little knowledge about PC’s. I keep reading how I need to go to an FTP page or rearrange HTML or some other crap I can’t understand. All I want is for this thing to work.

@kenscheper

I can feel your pain, but unfortunately that is still far from reality, unless one day we will be having computer with AI to help us.

I haven’t had any problems upgrading to 3.4.1, so puzzled. If you can enable WP debug and see if there are any error messages displayed on the screen, copy and paste it here, might be able to give you tips.

You can find how to enable WP debug here:

https://www.ads-software.com/support/topic/plugin-wp-openid-how-to-enable-loggingdebugging?replies=5

Thank you startupcms! I’ll try that link and see what happens.

Try this steps

If you don’t have access to your admin panel, try manually resetting your plugins, using ftp rename plugins folder to plugins_hold and create a blank plugins folder If that resolves the issue, delete blank plugins folder and rename original back to plugins reactivate each one individually until you find the cause.

If that does not resolve the issue, try switching Twenty Eleven theme to rule-out a theme-specific issue. If you don’t have access to your admin panel, access your server via FTP or SFTP, navigate to /wp-content/themes/ and rename the directory of your currently active theme. This will force the Default theme Twenty Ten theme (WordPress 3.0 and higher) to activate and hopefully rule-out a theme-specific issue.

If that does not resolve the issue, it’s possible that a .htaccess rule could be the source of the problem. To check for this, access your server via FTP or SFTP and rename the .htaccess file. If you can’t find a .htaccess file, make sure that you have set your FTP or SFTP client to view invisible files.

If you weren’t able to resolve the issue by either resetting your plugins and theme or renaming your .htaccess file, we may be able to help, but we’ll need a more detailed error message. Internal server errors are usually described in more detail in the server error log. If you have access to your server error log, generate the error again, note the date and time, then immediately check your server error log for any errors that occurred during that time period. If you don’t have access to your server error log, ask your hosting provider to look for you.

Thanks for your responses govpatel. I tried renaming the plugins folder and renaming my theme folder and it did not work. Before looking for the .htaccess file, I logged into my Godaddy account saw there was an update to 3.4.1 for me to install, so I reinstall the update through GoDaddy.com and now I have the dashboard access once again.

hello klbulloch12030 & govpatel
Where did you go in your Godaddy account to find the update for 3.4.1 ?
I’m surfing all around my Domain Manager, Control Panel, etc. and cannot find such a function?
I cannot access my Admin Panel on my WP accounts since the 3.4.1 update via WP.

If you want to update manually you need download wordpress from this forum and unzip the folder you will have wordpress folder in there you will all folders and files.

using ftp connect to account and replace all files and folders except wp-content folder and wp-config.php file.

Everyone,

I managed to fix this issue and I am not the most computer savvy of people. Here’s what I did:

– Downloaded WordPress 3.4.1 and extracted the files to my desktop.

– Accessed my FTP file manager (which, for me, is provided by GoDaddy.com).

– With the FTP file manager I selected all of the 3.4.1 files EXCEPT FOR THE “wp-content” FILE. When you go to upload, remember to DESELECT that folder, or you will overwrite all of the content you’ve created on your site and all will be lost.

– Uploaded/overwrote the files (for me, there were 17 files).

– Check and see if you can access the wp-admin Dashboard (I could not).

– Next, in the FTP file manager, I opened up the “wp-admin” and “wp-includes” folders individually. I uploaded/overwrote ALL of the files in these folders with the freshly downloaded 3.4.1 ones on my desktop. I did this for both of the folders.

– After doing this, I was able to access the Dashboard. But before I could, there was a page that said something about having to update the database. With no other options, I clicked the update button and waited. Viola! I now have full access to my dashboard.

I hope this works for you guys. If you find that it does, please get on at least one forum and re-post what you did to solve it in easy-to-follow instructions. There are A LOT of people who are freaking out over this issue.

I resolved it directly from Godaddy.com.
– Login
– Select MY ACCOUNT
– Select WEB HOSTING > LAUNCH
– Under Applications (right side) Select WORDPRESS
– Under My Management (right side) Select MANAGE MY APPLICATIONS
– Updated to WordPress .3.4.1 from there.

I was having trouble accessing dashboard after the 3.4.1 update. I did what suggested about renaming the “plugins” folder and created a new blank one, and that worked; I was able to acccess dashboard using https://www.site.com/wp-admin/….HOWEVER; when replace the new blank “plugins” folder with the old one, I could only access dashboard using
https://www.site.com/wp-login.php. I would get a blank screen when trying to access with /wp-admin.

Any thoughts ?

And whenever I update or create a new post it redirect me to https://site.com/wp-admin/post.php, but the page is blank, its doesnt bring me back to my post edit page.

Any thoughts?

Fixed the problem…it was a plugin that messed it up.