WordPress.org

31. figaro
    Member
    Posted 5 months ago #

    @glennhall144: If you have a db backup you can. If not, you may be able to export all your content using the export feature in the WP admin. Install a clean copy of 2.7 and then import...I haven't tried this, so am just assuming it will work. As always...backup, backup, backup, before trying anything like this.

32. mondolizzie
    Member
    Posted 5 months ago #

    Yes, you can go back to 2.7. I did it and all is finally well with my blog now.

    Follow the instructions here:

    http://codex.wordpress.org/Upgrading_WordPress

    Where it says upgrade to the latest version, don't click that. Click here to get the 2.7 files in the Release Archives:

    http://wordpress.org/download/release-archive/

    Hope this helps!

33. glennhall144
    Member
    Posted 5 months ago #

    Right. Thanks. I did make a backup before I upgraded, but given the time to restore, I think I will probably leave it for now. Had you noticed that problem I am having regarding Word documents?

34. glennhall144
    Member
    Posted 5 months ago #

    Thanks, mondolizzie. I think I am going to leave mine with 2.8 unless I start having other problems. I really don't want to mess with it now, but if I have to, I know where to look!

35. figaro
    Member
    Posted 5 months ago #

    Had you noticed that problem I am having regarding Word documents?

    There have always been problems with copying/pasting from Word documents...sometimes it works, other times it will completely destroy the layout, push the sidebar to the bottom, etc. This isn't limited to WP...Word has some really ugly html that can cause all kinds of problems in web apps. The general advice is to copy from Word, past into something like notepad, then copy the plain text from there into WP and reformat.

36. MileHighFan
    Member
    Posted 5 months ago #

    Just curious if anyone has found that WP has released any type of 'Official' comment regarding 2.8. There seems to be a 'head in the sand' approach from WP. I know it's still a little early since the initial release, but I would think something should have been said/announced by now. Thanks.

37. onnaholl
    Member
    Posted 5 months ago #

    Help!! I upgraded two of my blogs one was fine (the one I had a back up of -lol) the other -I got this message Fatal error: Call to undefined function: _weak_escape() in /home/makin36/public_html/blog/wp-includes/wp-db.php on line 487 - it says it upgraded fine- then every where I click I get that message. says it when you load my site too!! AHHHH-wish I hadn't upgraded!! Any suggestions? I can't get into to anything to reload the 2.71?

38. figaro
    Member
    Posted 5 months ago #

    @onnaholl: If you didn't disable your plugins before upgrading, then try that first. See below for how to do it when you can't login:

    http://educhalk.org/blog/?p=38

    If that doesn't help, then you may need to reupload the source code manually.

39. mrmist
    Member
    Posted 5 months ago #

    Elsewhere on t'internet it says that the weak_escape issue is caused by an out of date version of the redirect plugin. So either update or remove that plugin and you should be sweet.

40. jgbutler
    Member
    Posted 5 months ago #

    MichaelH writes:

    Next update, it might be wiser for users with lots of plugin installed, to read and follow Upgrading WordPress instead of doing the automatic upgrade.

    Well, next update, it might be wiser for Automattic to not release an upgrade with such destructive capacity that it can delete directories of files OUTSIDE a WordPress installation. How could a user anticipate that?

    P.S. Advice that sounds a lot like RTFM does not make someone whose Website has been deleted feel any better.

41. chit chat administrator
    Member
    Posted 5 months ago #

    I am laughing as I read these because I too am beyond frustrated. I can only agree on so many of the items above.

    1. Disable the automatic upgrade immediately.
    2. Send out a notice to warn people about the issues.
    3. Automate a reverse back for 2.7.
    4. Don't assume we should have to disable every plugin prior to upgrading since nothing else seems to work this way or at least in future put that on the instructions with the Upgrade button so we know to do this before pressing this button.
    5. Have a link next to this button re: any plugin problems.

    I have had widget problems, dashboard is completely now broken, image load does not work, etc.

    I have tried ftp'ing my site to previous version and it is a disaster now. I am asking them again to restore back. Last restore still had a 2.8 version (they only normally go back 3 days) but now I am asking if there is any way to look for a system backup beyond that day hoping to get to the 2.7 version. I can't attempt the manual upgrade suggested again as it completely broke my system.

    I concur this should never have been released like this.

    Darlene

42. zzb
    Member
    Posted 5 months ago #

    To moderators: Why not sticky post this link so folks have quick access to previous versions without driving you guys nuts? What's the big deal about reverting back to 2.7.1 ? Did everyone forget how to FTP files ?

    http://wordpress.org/download/release-archive/

    Its clear this is not one of the WP team's finest moments. I am sure there are some lessons being learned that should translate into a better testing protocol for future releases leveraging the super user population first that run a large number of the most common plugins. I suspect this does occur but it can't be very large sampling. Not with this level of pain in the user community !!

43. Elpie
    Member
    Posted 5 months ago #

    I'm not part of WordPress, just a 3rd party hacker, but even so I think a couple of points should be made...

    1. WordPress Codex says, "deactivate plugins before upgrading" (http://codex.wordpress.org/Upgrading_WordPress) and people who don't are really asking for trouble. Plugins are mini-applications that hook into WordPress and either change or build on WordPress core functionality. It is only logical that when the underlying core code changes then plugins can cause problems.

    2. WordPress tells everyone to take backups before upgrading. These backups are important as many things can go wrong with an upgrade - even things that are outside of WordPress itself. Restoring from backup is relatively easy, as long as the backups exist.

    3. WordPress, like all open source projects, relies on its community to test code. WP 2.8 had beta releases and a release candidate before it was finally released. Most of the issues that were raised during the testing phase were fixed before WordPress 2.8 was released but obviously everyone uses different server setups with different versions of PHP and MySQL so the few people who did test could not test on all platforms.

    Which brings me to my final point - if everyone was prepared to test the beta's and release candidates and provide feedback to the developers, a lot of these problems would not occur.

    Even opening or adding to tickets on the tracker is helpful. http://core.trac.wordpress.org/

    All open source depends on users to feed information back to the developers. I share the frustration of everyone in this thread (perhaps even more frustration since I spent time testing the betas and RC1, with no problems until I put this onto live blogs) but, really, venting in the forum doesn't help. If we report the issues in the tracker and they don't get fixed, THEN we really have grounds for complaint ;)

44. MadHag
    Member
    Posted 5 months ago #

    I upgraded from 2.7.1 or so, I was a bit nervous but did everything manually by the book and it worked perfect. Well happy with 2.8

    David

45. The Debil
    Member
    Posted 5 months ago #

    I’m stunned by how many people are making such fundamental errors.

    Seems simple enough.

    1. Read upgrade support docs.
    2. Back up all files and database.
    3. Turn off all plugins.
    4. Run upgrade.

    Alternatively.

    1. Do not read support docs.
    2. Do not back up files and database.
    3. Leave all plugins turned on.
    4. Screw up completely.
    5. Blame everything except the user.

    Analogy.

    1. Go to gun store.
    2. Buy gun and bullets.
    3. Shoot self in foot.
    4. Blame the gun.
    5. Ball and cry and the gun store owner.

46. figaro
    Member
    Posted 5 months ago #

    @Elpie:

    I agree with much of what you said, but let me make a couple counter-points :-)

    1. WordPress Codex says, "deactivate plugins before upgrading"

    That is very true and it should be done. BUT, failure to disable a plugins should not, for example, result in a person's Joomla site being deleted...their WordPress site being broken, okay, but no reasonable person would expect virtually everything in their public_html directory to be wiped clean due to a wordpress upgrade.

    2. WordPress tells everyone to take backups before upgrading.

    That is true, but this advice doesn't assume you need to backup your entire webhosting account before upgrading WordPress. How many people here really backup their entire hosting account (other than their normal backups) before upgrading WordPress? I don't. When I upgrade a WP install (for myself or a client) I backup the WP source code and the WP database...it never occurred to me that during a WP upgrade, I could completely wipe out my (or a clients) entire public_html directory content. That's the disturbing part here...not that the upgrade could destroy WP (your backup should allow you to recover from that), but that a WP upgrade (if what is being reported is fact) could wipe out all content in your public_html directory.

    Again, I think this reported problem deserves some sort of "official" comment.

    PS...Either way I (still) love WordPress and think it's by the far best blogging software (free or commercial) our there :-)

47. Mogandi
    Member
    Posted 5 months ago #

    I was able to get my page online again, after installing automatically 2.8 and "wiping" out my site.

    Maybe i was lucky, but it didnt wiped out anything it seems.
    So i went into my files via ftp and discovered the .maintainance file which i renamed.

    My site is now available again and it seems working fine without beeing updated.

    http://www.mogandi.de is the page.

    Didnt need any reinstalling or something complicated. Lucky me?

48. jdembowski
    Member
    Posted 5 months ago #

    That's the disturbing part here...not that the upgrade could destroy WP (your backup should allow you to recover from that), but that a WP upgrade (if what is being reported is fact) could wipe out all content in your public_html directory.

    Huh?? I don't use automatic upgrade, being an SVN fan, but where in the automatic upgrade code does this effect non-WP directories? I'm not saying that it's not there but having the PHP equivalent of "rm -rf *" seems hard to believe. If that's there (and I doubt it is) I honestly would like to see that.

    Anyone have a good walk through of what the automatic upgrade does specifically? I can't find it in the codex. I could hunt through the code but my PHP-fu may not be up to the task.

49. MichaelH
    moderator
    Posted 5 months ago #

    Interesting comment here:
    https://core.trac.wordpress.org/ticket/10140#comment:4

50. jdembowski
    Member
    Posted 5 months ago #

    Much thanks Michael. I had started looking at wp-admin/update-core.php on 2.7.1 and left colorize syntax on in vim.

    Soon I expect to get my color vision back...

51. chit chat administrator
    Member
    Posted 5 months ago #

    I have restored both database and site files. I disconnected a Gixax Chat plugin and my Dashboard now seems to work. Keep fingers crossed.

    I have wasted approx. 4 days on this.

52. jdembowski
    Member
    Posted 5 months ago #

    Good job! Now not to be cheeky, but can you get a new file and database backup of your blog if you haven't already?

    I know it's been beaten to death, but you having the capability to backup and restore your blog yourself is your best safety net going forward.

53. planetmagazin
    Member
    Posted 5 months ago #

    i have had similar problems:

    1. cannot save tags
    2. toooo slow opening
    3. sometimes Error at opening of site
    4. problems / erorrs with editing of comments
    5. users cannot opened comments

    now i have made downgrade at 2.7.1. and those problems gone

54. jordy1
    Member
    Posted 5 months ago #

    My dashboard is really messed up after making the 2.8 upgrade.

    This statement is on the wordpress.org front page just above the link for getting the 2.8 version.

    "More simply, WordPress is what you use when you want to work with your blogging software, not fight it.

    New to blogging? Learn more about WordPress, then follow the three easy steps below to start blogging in minutes."

    Lol...ha, that's funny ...three easy steps!

    I started using Wordpress to write articles and enjoy blogging. By the looks of many of these comments, I am now being expected to be a wordpress code expert.

    To say the least, I am very dissapointed.

55. The Debil
    Member
    Posted 5 months ago #

    jordy1

    You do not have to be a code expert to read the upgrade instructions:

    http://codex.wordpress.org/Upgrading_WordPress_Extended

    1. Backup database
    2. Back up your files
    4. Deactivate plug ins

    My questions to you are: Did you read this and did you actually do it?

    If your answer is yes and yes... then why not just install your back up?

56. vegasrenie
    Member
    Posted 5 months ago #

    I haven't seen this problem yet, but it seems to fit in. Sort of.

    I did everything by the book. Disabled plug-ins, did a backup, yadda yadda yadda.

    Did the upgrade (manual, not automatic). Logged into site when login screen popped up and found everything there. Although this is a site that I do not regularly maintain, there were no problems. I reactivated the plug-ins, rearranged the widgets (great widget functionality!) and happily saved everything. I clicked the Visit Site button only to discover that there's no site. Nothin'.

    I know everything is there. It's just that the rest of the world can't see it. This verifies something I've found out since the upgrade to 2.5. NEVER EVER upgrade the at the first release. Every single time I've done it, I've had some sort of disaster.

    Fortunately, (as I mentioned), this is a tertiary site, few ordinary widgets, that's also my guinea pig. If this had been my primary site, I would have been completely panicked!

    Irene
    http://blackjewishwineaux.com (disappeared!)
    http://vegaswineaux.com (primary site)

57. figaro
    Member
    Posted 5 months ago #

    You may try to login on the site that disappeared and try changing themes to see if that helps.

    http://blackjewishwineaux.com/wp-admin

58. jordy1
    Member
    Posted 5 months ago #

    Finally, my dashboard is fixed. Here's a link to a good WP list of related problems and possible solutions. http://wordpress.org/support/topic/279132

    I used this one: "7. Some people also reported success redoing the upgrade via Tools->Upgrade->Re-install automatically, then clearing the browser cache."

    Although things seem to be running smoothly now, since this glitch occurred my average traffic to my blog was cut in half daily. Ahhh, grrr... a lot of revenue was lost along with time wasted.

59. whooami
    Member
    Posted 5 months ago #

    upgraded countless blogs and helped fix 2 bad upgrades in the last few days -- have seen ONE problem, ok 2:

    the first one was caused by the theme.

    the second issue was with the googleanalyticator (sp) plugin breaking the widget page. Upgrading that plugin (new rls yesterday) fixed that.

    the upgrades that I did went perfectly.

    And to make a comment on a comment from the previous page of this thread regarding "wordpress" doing something with how plugins are released or some uninformed language like that:

    B as in B -- S as in S. The ONLY person responsible for wordpress plugins is the person that adds to them to their site. To even think that WP **could** exert any more control than they is already leveraged via the plugins repository is ludicrous. That, my friend, is how open source works.

60. sustainorder
    Member
    Posted 5 months ago #

    Hi, it is really unproductive if you blame a large number of people experiencing similar problems on improper installation/upgrade practices. Doesn't fly INHO.

    I report the following with my blog-
    after a couple of days running WP 2.8 the host would redirect the home page to WP installation page (as if the site didn't exist), to install it once again, which alarmed me. Then they said what was wrong were database permissions which they changed, but then none of the links worked on the site.
    So I was told something was wrong in the .htaccess file, and a tech person corrected this error and everything started to work again.
    This scenario has happened a few months ago, and it happened again with the new installation of WP 2.8.
    But this time they keep redirecting the home page to the installation page as if automatically. They are able to reverse it to the normal home page url with a stroke of a button, but they don't do this because I am being told their server CPU keeps increasing when the site is in use.
    Which causes the reversal all over again to stop the CPU server increase.
    I am told they can't give me more server space because it is a shared server.

    Someone else above noted the same problem- increased CPU server usage with WP 2.8. Which may mean the new PHP code is to blame.
    Unless I am wrong, I just don't know, and I don't know how to go back to the previous version without damaging the site.

Reply »

You must log in to post.