Support » Installation » WordPress 3.5 upgrade proving to be a problem

WordPress 3.5 upgrade proving to be a problem

  • I have now upgraded 4 sites with WordPress 3.5. Every single one of them have viewed totally blank and I’ve had to delete the WordPress files and re upload them manually.

    I’ve made sure that plugins are updated and I’ve made sure the sites are backed up. I don’t understand why the upgrade has done the same thing to each site I’ve done so far.

    I’m dreading doing any more. I have over 20 more sites to upgrade and really don’t want to be doing any more manual updates. It’s extremely time wasting and for most of these sites it’s not like I can charge someone for my time.

    Think I’ll hold off doing any further upgrades till I know that it’s working properly.

    The themes I’m using are varied, some paid for, some not.

Viewing 4 replies - 1 through 4 (of 4 total)
  • One thing you can do is disable all your plugins and switch to the default theme twentyeleven before you do the upgrade.

    When you re enable your plugins they won’t activate if there are any PHP fatal errors.

    Ok, thanks for that. Looks like I’ll have to change the order I do things in. But all the same, think I’ll hold off doing any further updates for now.

    I’m having a similar problem with one of my sites;
    using the ‘automatic update’ ends in a 404 at this url:

    I’ve tried reverting to the twentyeleven theme and disabling all plugins, but the same thing is happening.

    I’ve successfully upgraded several others to 3.5, some of which are on the same hosting provider, so can’t figure out what’s the problem with this site.
    I too have many other WP sites to upgrade, so any help would be greatly appreciated.



    Forum Moderator

    As per the Forum Welcome, please post your own topic. Posting in an existing topic prevents us from being able to track issues by topic. Added to which, your problem – despite any similarity in symptoms – is likely to be completely different.

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘WordPress 3.5 upgrade proving to be a problem’ is closed to new replies.