Support » Fixing WordPress » Upgrade to V3.2 and my site is f**ked

Viewing 15 replies - 16 through 30 (of 38 total)
  • If someone were to publish a list of worst support nightmares due to entitlement-mentality impaired people who completely disrespect the volunteers attempting to help them, this thread would be near the top of such list.

    To the OP: you can wait until the cows come home, but you’re not going to get any different, or better, advice or instruction than what Ipstenu has already given you.

    If you can’t be bothered to follow the official instructions for resolving the issues you’re experienced, if you are unable to use basic web-hosting tools such as FTP and MyPHPAdmin, then perhaps you would be better off using a hosted blogging service such as wordpress.com, so that you don’t have to worry about such matters.

    Christine Rondeau

    (@crondeau)


    Volunteer Forum Moderator


    I think that perhaps some of the blame falls on WordPress.

    They’ve done such amazing marketing that everyone thinks that it’s super easy, when in fact, theming a site, modifying css and understanding servers is quite difficult. I really wish people would realize that you don’t become a web developer after just a few clicks.

    OK WTF,
    Deactivated all plugins VIA ftp and DATABASE, still BLANK PAGE, tried php error reporting and nothing

    OH THIS IS F***** up
    my theme is no working now i had to disable theme and stylesheet database option id 45
    then now i need to RE-DO A THEME wth

    It’s always easy to sit back and pontificate Mr. Bennett but the harsh reality is that my site doesn’t work, yours does. Our perspectives are a little different.

    The official response trotted out in this thread is about as helpful as a chocolate tea pot when (and this is where I lose the will to live repeating myself), I have no access to either the front end or the back end of my site. I get a blank page for both.

    This fault is due to the upgrade (free or otherwise) and as a result, 6 months of hard work has gone out the window. The prospect of routing around in my FTP to reset something is beyond my understanding.

    So 3.2 has been tested for months Andrea_r? (Forgive me but you don’t look like a pirate) Not long enough mate. If I was developing an update for a world famous blogging platform, I definitely wouldn’t release it if there was a possibility that the upgrade would cause someone’s site to crash due to the resulting conflict between it and a plugin. And here’s the problem. We don’t even know if it even the fault of the plugin.

    The resulting restore is going to cost me 25 quid. Not the end of the world but irritating enough. So if anyone has anyone non self-righteous advice they can offer, (which hasn’t already been added to this site) feel free.

    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.

    We don’t even know if it even the fault of the plugin.

    That’s true, it might be because of the theme.

    If I was developing an update for a world famous blogging platform, I definitely wouldn’t release it if there was a possibility that the upgrade would cause someone’s site to crash due to the resulting conflict between it and a plugin.

    Impossible. Because anyone who wants to can write a plugin, and anyone who wants to can write a theme. These can be used in any combination, which is exactly what makes the platform so powerful.

    fonglh: Well it is impossible for them to test every plugin to see if it works, the whole system should not shut down to a white screen whenever a plugin is bad. It should give an error message “plugin x is not compatible and has been disabled.” It should not just dump out with no errors.

    I am currently trying to deal with a blank admin page too, but it’s very hard to move forward with zero information to go on. I did all the standard disable plugins and themes via ftp. Did not work.

    Tomorrow I will start a clean install and start restoring my data.

    It just seems that these errors could be handled more gracefully than a blank screen.

    Moderator Dion Hulse

    (@dd32)


    Despite me reading the initial part of this thread making me not even want to attempt to help for the fear of being flamed over it..

    If you’re recieving a White page even after disabling plugins, and accessing the admin directly (not the front of the site) doesnt help, I’d suggest enabling the Debug Mode, It’s primarily for developers, but it may also result in a error message being shown which someone can help you with troubleshooting from the result of it.

    In your wp-config.php file, You need to define WP_DEBUG to true, newer config files will include this already defined to false.

    The code you need to add to wp-config.php before the final “stop editing here” text is this:
    define('WP_DEBUG', true);
    if you see this line: define('WP_DEBUG', false); in there, you’ll just need to change the falseto true.

    If you post the error message that shows (if it shows anything, it sometimes doesn’t depending on the server configuration – out of WordPress’s hands) I, or one of the other volunteers may be able to help you.

    Moderator keesiemeijer

    (@keesiemeijer)


    moderator


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

    Hey kids,

    I’ve just updated my wordpress site and suddenly can’t access anything. This is the error message I am getting: Warning: require_once(/home3/viendama/public_html/wp-includes/class-json.php) [function.require-once]: failed to open stream: No such file or directory in /home3/viendama/public_html/wp-content/plugins/tweet-this/tweet-this.php on line 145

    Fatal error: require_once() [function.require]: Failed opening required ‘/home3/viendama/public_html/wp-includes/class-json.php’ (include_path=’.:/usr/lib64/php:/usr/lib/php’) in /home3/viendama/public_html/wp-content/plugins/tweet-this/tweet-this.php on line 145

    Help please!!!! Please please please!

    Moderator Dion Hulse

    (@dd32)


    Vienda: Fatal error: require_once() [function.require]: Failed opening required ‘/home3/viendama/public_html/wp-includes/class-json.php’

    The Tweet This plugin you’re running is not compatible with 3.2, Please disable the plugin by deleting the folder via FTP, see this post i just made related to it: http://wordpress.org/support/topic/troubleshooting-wordpress-32-master-list?replies=15#post-2201677

    Thanks Dion!
    I can’t access my dashboard so how do I disable the plugin?

    Moderator Dion Hulse

    (@dd32)


    I can’t access my dashboard so how do I disable the plugin?

    Follow the link mentioned in my previous post: http://codex.wordpress.org/FAQ_Troubleshooting#How_to_deactivate_all_plugins_when_not_able_to_access_the_administrative_menus.3F

    Put simply, You need to delete the ‘tweet-this’ folder in your plugins directory manually via FTP, or by your hosts control panel file manager.

    Holy crap…

    LMFAO. I really cannot believe how people expect free assistance when they are so rude and insulting. Don’t you consider that no one but you gives a hoot about your site so if you want help – be nice.

Viewing 15 replies - 16 through 30 (of 38 total)
  • The topic ‘Upgrade to V3.2 and my site is f**ked’ is closed to new replies.