Support » Fixing WordPress » Upgrade to V3.2 and my site is… V2.0

  • So it’s not wordpress that’s at fault, it’s the plugins?

    How do I protect myself against crappy plugins?

    Better question, how do I disable plugins from FTP?

    Also do I have to upgrade WP every time a new version comes out?

Viewing 8 replies - 1 through 8 (of 8 total)
  • fonglh
    Posted 13 hours ago #

    You do not need access to your site.
    What you need is access to your host’s control panel.
    If you let us know who your host is someone will be able to find a link to the login page for you.

    The fault is due to a plugin which conflicts with the upgrade. Plugin developers may not always follow best practices or keep their plugins updated.

    Rooting around in FTP is just like renaming folders in Windows.

    I can get into FTP but I don’t know what to look for… My Host is

    1. Usually it’s plugins or themes

    2. BY doing research. It’s usually a matter of knowing who writes good plugins, and reading the comments being posted about plugins.

    3. Delete the offending plugin from the wp-content -> plugins folder using ftp. That will deactivate it

    4. Yes. Almost all WP upgrades contain security enhancements

    Ah gotcha. Arras is a fairly stable and popular theme. If I rename the plugins one by one, will that effectively deactivate them?

    Say put an X at the end of each one? It’ll make it easier to work out which one has caused the problem so I can report it back here.

    Moderator keesiemeijer



    Ah, bwoose let’s keep it civil in this topic (before you make it cosed)
    a lot to learn here.

    – switching to the default theme by renaming your current theme’s folder in wp-content/themes using FTP or whatever file management application your host provides.

    resetting the plugins folder by using FTP or whatever file management application your host provides. Sometimes, an apparently inactive plugin can still cause problems.

    – renaming or deleting the .htaccess file by using FTP or whatever file management application your host provides. If you delete it make a backup first.

    – re-uploading all files & folders – except the wp-content folder from a fresh download of WordPress. by using FTP or whatever file management application your host provides. (essentially doing a manual upgrade)

    And read this for 3.2 troubleshooting: (there are known Arras theme problems)

    The theme Arras was my issue. There is a code issue in the functions.php

    you say you’ve managed to get FTP access and that you’re using the Arras theme.

    The Arras theme just got updated so that it’ll work with WordPress 3.2. Download it, unzip it, then upload the whole ‘arras’ folder by FTP to your wp-content/themes directory.
    Depending on where your FTP login puts you, it might be under a folder named public_html or htdocs.
    The download link to the new version of Arras is at

    Try that first and let us know how it goes.

    anyway, there’s a customer login link on the top right of your host’s homepage. that should bring you to the control panel.


    Yes, if you add X to the folder name of each plugin it will deactivate them.

    Alternatively, download them to your local hard drive and delete them from your web server. Install them back again using the built in WP plugin installer to ensure you have the most recent version and check to see that the recent version is compatible with 3.2 before moving forward to the next plugin.

    If the plugin doesn’t work or generates errors, contact the plugin author immediately. I just updated 10 of my plugins to ensure they work well with WordPress, it’s up to each plugin author to ensure they update their software to work with the new versions of WordPress.

    You can disable all plugins in one go by renaming wp-content/plugins to wp-content/pluginsX (or some other name) via FTP (using Filezilla, or your hosts File Manager feature).

    If you’ve not sorted the theme issue, then you could do a similar thing to that – rename all but the twentyeleven folder within the wp-content/themes folder so that WordPress falls back to using the TwentyEleven theme.

    At this point, you would hopefully find the site is no longer whitescreening, and that WP dashboard is back up for you to log into.

    It’s a fact of life, that when the user-friendly administration (WordPress) stuffs up, you might have to get down and dirty with the files, folder and code to fix it for your install. Or hire a web developer who understands the problem, and more importantly, fixes problems like this every day.

Viewing 8 replies - 1 through 8 (of 8 total)
  • The topic ‘Upgrade to V3.2 and my site is… V2.0’ is closed to new replies.