WordPress.org

Ready to get started?Download WordPress

Forums

After 3.3 upgrade, all sites have crashed (9 posts)

  1. doncobb
    Member
    Posted 2 years ago #

    I recently upgraded 5 sites that I have hosted on WordPress to 3.3. Now the only page I can get from my sites is "500 Internal Server Error". I've tried rolling back to 3.2.1 and now I get a message saying "WordPress Update Required". Really? All of my WP sites are down now. Anyone know how to fix this? Thanks.

  2. Tara
    Member
    Posted 2 years ago #

    -Check if your theme is compatible with WP 3.3. To check, you may try switching to the default theme (twentyeleven) for a moment by renaming your current theme's folder in wp-content/themes. The idea is to force WordPress to fall back to the default theme to rule out any theme-specific issue.

    -also, make sure all your plugins are uptodate and compatible with the 3.3. deactivating ALL plugins temporarily to narrow down the problem. If the problem goes away, activate them individually (one-by-one) to find the problematic plugin.

    -Ipstenu has put togather an extensive 3.3 troubleshooting guide. Please review it as well.

    - also try Hotfix - a plugin for bugs to be fixed before the next WordPress release.

  3. doncobb
    Member
    Posted 2 years ago #

    You've got to be kidding me, right? Does WP think we're all techies? Surely they realize that WE'RE NOT and that's why we use WordPress? When WP tells me it's time to upgrade, I upgrade. Now you want me to investigate whether or not my plugins and my themes are all compatible with 3.3?!? It would be easier for me to set up my blogs elsewhere. Just being honest. BTW, now I can access my sites again, but I cannot upload any media. It tells me "no temporary folder" whenever I try to upload a jpg. Will that go away one day? Or do I have to figure out how to create a temporary folder for any photos I want to upload now?

  4. RichardWPG
    Member
    Posted 2 years ago #

    Does your hosting provider provide support?

  5. doncobb
    Member
    Posted 2 years ago #

    Some. They took me in and had me change the name of a file that was something like htaccess something-or-other. I think that enabled one of my sites to become accessible again. Then they had me migrate my entire setup to a more recent version. Maybe THAT is why I have access to all of my sites now. All I know is that all *I* did was upgrade to 3.3 and then my problems began. You can probably see why it's difficult for me to solve my own problems here. I relied on WP to provide me with a solid foundation that I could make minor modifications to and end up with a professional looking product. Problem solving is not within my grasp, however. I know next to nothing about any of this. I'm a writer...and a musician. Neither of which help me here. Thanks.

  6. Tara
    Member
    Posted 2 years ago #

    You've got to be kidding me, right?

    No, i am not kidding.

    Just trying help you (free!).

    Try working through the solutions listed in http://wordpress.org/support/topic/troubleshooting-wordpress-33-master-list

    Of course you do have the option of engaging a professional to assist you if you feel that this is beyond your capabilities (I am not a consultant, I do this just for fun!).
    See http://jobs.wordpress.net/ if you want to follow that option.

  7. doncobb
    Member
    Posted 2 years ago #

    I'm sorry if I sounded ungrateful. I guess a lot of you are all edjumacated an' stuff. I'm not. I write. I sing. I record. I blog. I don't do html or css. And I don't pay professionals for what I can get relatively inexpensively and then modify myself. This whole thing was a first for me. I'll either figure it out or move on to someplace more accomodating of newbies. Thanks for your help.

  8. doncobb
    Member
    Posted 2 years ago #

    “SonomaCountyPolitics.gif” has failed to upload due to an error
    Missing a temporary folder. That's what I get on all of my sites now. I cannot upload photos. I'll try your master list. Thanks.
    *************************************
    Just read through it. Nothing about problems uploading photos. Whatever. I'm a little astonished at how many issues the article lists, however. Maybe the beta could have been experimented with for another few months before it was made a mandatory upgrade to avoid all of this. I deactivated all of my plugins and tried to upload a photo. No go. I'll just keep waiting for someone to figure it out and post about it. I'm really trying to promote a new local political discussion message board, so it will make all the difference in the world to upload a graphic. Oh well. Thanks again.

  9. Nikki Blight
    Member
    Posted 2 years ago #

    "Maybe the beta could have been experimented with for another few months before it was made a mandatory upgrade to avoid all of this."

    There's no such thing as a "mandatory upgrade". Heck, there's nothing preventing you from using WordPress 2.0 if you really wanted to.

    Beta testing is all well and good, but you'll never see every bug in a beta test. There just aren't enough people with enough differences in their configurations to catch everything.

    As to your specific problem, a temporary folder generally refers to the folder a file is transferred to by PHP before it is moved into it's final location in the wp-content/uploads folder. You said your host had you migrate your site... was it to a whole new server, or what?

    Because USUALLY the cause of that specific error message is an improperly set upload_tmp_dir in your server's php.ini file... which is something your host would have to have screwed up when they moved you. If PHP doesn't have a temporary upload directory specified, it can't upload a file. If PHP can't upload, neither can WordPress.

    It sounds like it's not WordPress that can't upload... it's PHP. If that's the case, your host needs to fix it for you.

    Your original 500 error was likely caused by your site's .htaccess file, as your host suspected. Renaming it, and then generating a new one by re-saving your site's Permalink settings once you have backend access again, ought to fix it.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags

No tags yet.