WordPress.org

Ready to get started?Download WordPress

Forums

NEW: Upgrade to 1.5.2 (95 posts)

  1. vkaryl
    Member
    Posted 8 years ago #

    Um. Yeah, I do a "beel" mostly too.... so far I've been "safe", but I'm bound to have problems eventually....

  2. Beel
    Member
    Posted 8 years ago #

    So what "breaks" for others? I mean the plugins are listed in one option in the database - so the contents of that option gets "fried" - no biggie, just empty it and start over. What am I missing?

  3. vkaryl
    Member
    Posted 8 years ago #

    I dunno - I've not "broken" anything as yet.... well, at least by upgrading without disabling plugins, that is.

  4. James
    Happiness Engineer
    Posted 8 years ago #

    I forgot to disable my plugins when I upgraded from v1.5 to v1.5.1, and a conflict between Kafkaesquí's Entity2NCR plugin and a new feature in WordPress v1.5.1, that was basically exactly the same as Entity2NCR, turned my blog into one big parse error. The only way to fix it was to either delete the plugin file, or edit the plugin file so that it only had the header in it and "safely" deactivate it via the plugin interface.

    While this happened because I forgot to disable the plugin before upgrading, the same would have happened if I had disabled it and then enabled it after upgrading.

    I always expect something to break when I upgrade. That way, I'm prepared if something does break, and pleasantly surprised when it doesn't.

  5. vkaryl
    Member
    Posted 8 years ago #

    *laughing* macmanx, you just stated my "theory of living life" exactly.... I always expect and plan for the worst, and then I can be pleasantly surprised if the worst does not come to pass.

    I've lived nearly 58 years by that attitude, and I've found it works quite well.

  6. dedge
    Member
    Posted 8 years ago #

    I've customized a couple of the 1.5.2-affected files. Even with the hacks and without disabling my 14 plugins, I was able to upgrade easily. But disabling first (and backing up!) is always a good idea.

    Back in 1.5.0 I learned the hard way to carefully document every home-grown tweak I make to the WP core. It adds some work, but upgrades are much easier and safer.

  7. lokrin
    Member
    Posted 8 years ago #

    Just did the minor upgrade also. At first I thought everything was fine, but then I noticed that all the internal links were giving 404 errors. I finally replaced the .htaccess file created on the new install with the old file. Now everything is back to working. So I'm guessing that something was wrong with the rewrite rules, but I'm not that great with the coding. I'll look it over a bit more later.

  8. pcmt
    Member
    Posted 8 years ago #

    Thanks to everyone involved in producing the new version. I too forgot to disable plugins, but the upgrades were successful.

    In contravention to the advice, I didn't delete the old .htaccess file because I couldn't see why this was necessary. It would be helpful to know why this is recommended.

  9. Mark (podz)
    Support Maven
    Posted 8 years ago #

    I didn't delete my .htaccess either.

    If we say "Delete your .htaccess then redo your permalinks" we end up with people posting that their .htaccess is full of custom stuff and why can't WP work round it and WP is just SOOOO bad at all this upgrading and why can't we have it done with a single click like [insert product of choice] and I won't upgrade because of this and so my blog will be at risk and it's all YOUR fault. *sob* *whinge* *boooo*

    Or

    If we say to NOT delete your .htccess, then we will sometimes have people posting here with "HELP I CANT SEE MY BLOGGGG!!!!11!!!1!!!!!!!" and all they need to do is delete the .htaccess and do another one.

    So either way, we can't please all of the people all of the time.
    I'll try and address this in the new upgrade guides.

    Note: artistic licence taken with the above two descriptions :)

  10. pcmt
    Member
    Posted 8 years ago #

    Thanks for the reply, but I'm still not clear why leaving the .htaccess file as it is would cause a problem on an upgrade such as this one. If the database remains untouched, why is it an issue?

  11. Beel
    Member
    Posted 8 years ago #

    May not be... with this release.

  12. James
    Happiness Engineer
    Posted 8 years ago #

    Just clarify what I think Beel is saying,

    It may not be an issue with going from v1.5.1.3 to v1.5.2, but it may be an issue with going from v1.5.x.x to v1.5.2.

  13. Beel
    Member
    Posted 8 years ago #

    In the short time it was up, I came to rely on the "latest reply" link up top... any chance it will be fixed?? Sure was handy, especially for long threads like this.

    Yep, I meant any update, past or future, may be an issue or may not - it just depends on what changes from the version you happen to be using to the version to which you are upgrading.

  14. anthonymcg
    Member
    Posted 8 years ago #

    Just changed the files and ran upgrade.php now. Worked a charm.

  15. 46664
    Member
    Posted 8 years ago #

    im just wondering how come theres always updates and vulnerblties? i feel like this is owned by b gates. but dnt take me wrong..i really love wp but why such thing?

  16. skippy
    Member
    Posted 8 years ago #

    Updates are necessary for three basic reasons:
    * to fix exploits that can lead to a compromise
    * to fix things that don't work as they should
    * to add new features

    Yes, it can be aggravating to upgrade several times in quick succession. Of course, it's more aggravating to recover from a compromised blog. I've helped people do it privately, as well as in the forums here. It's not fun. Given the choice, I'd rather take a few minutes of hassle to upgrade every couple of months.

  17. Mark (podz)
    Support Maven
    Posted 8 years ago #

    " i feel like this is owned by b gates"

    All the Linux distros also update - every system updates.
    If the market shares of Windows and Linux were switched, not only would the hackers refocus their attention to Linux, but you'd hear very very little about Windows problems.
    Go drop 'linux critical updates' into Google - there are a couple of million hits.

    (This is not to start a Windows / Linux argument, I'm just illustrating a point).

  18. Beel
    Member
    Posted 8 years ago #

    And no one says you have to upgrade, I've stopped updating many of my shareware programs - too dang expensive.

  19. tommygeorge
    Member
    Posted 8 years ago #

    Call me a noob, if you must, but I have a question... I upgraded, as per the instructions in the first post of this thread, and upon the first log-in, I noticed that my Write Post screen was no longer "broken" in Opera. [by Broken, I mean that my category list was left aligned, but my actual Post box was positioned below it, instead of next to it.].
    I noticed, now, that the category box was aligned to the RIGHT of my POST box, and there were no breaking or styling errors.

    However, I recently logged in again, to see things back the way they were!

    Did I do something wrong, should I install from scratch, am I crazy, has this happened to someone else, etc., are my questions. Hopefully they will be answered shortly. Thanks much. = )

  20. stewy
    Member
    Posted 8 years ago #

    Wow, I thought I had broken WP for sure.

    I tried the unoffical method first, that broke my WP, probably because I did not run upgrade.php (am I supposed to do this when using the unofficial method? the instructions just say NOT to use it for the official method)

    So then I tried the offical method, did everything perfectly, but still somehow got database connection errors (even though I kept my original wp-config file) seems to be working right now, even though I have not changed anything, all I did was hit F5 a bunch of times. I think I'm in the clear.

    TommyGeorge
    the first thing i would do is empty out your browsers cache to make sure you're not loading the page from the cache rather than the newest version.

  21. PetLvr
    Member
    Posted 8 years ago #

    ut-oh .. disable plugins?? Hmm .. I just converted my 1.5.1.2. version to 1.5.2. using the "unofficial" suggestion, on Page 1 of this forum. I first deleted the files, then copied over the new ones. So far, everything appears to be fine. But, now that I think of it, I remember some of my early plug-ins suggested I modify files besides the template design and plug-in directories.. but i never marked it down. I hope it's okay. But, I can post. I can see my blog. I think I'm okay. Am I? Are there tell tale signs to look for to indicate it wasn't a clean upgrade?

  22. Beel
    Member
    Posted 8 years ago #

    Are you? We certainly don't know which plugins required you to edit which files. If you overwrote those files, then those plugins more than likely won't work properly. Are you OK? Only you can tell.

  23. ionic
    Member
    Posted 8 years ago #

    Just as little warning to all those now installing 1.5.2

    WordPress 1.5.2 does not fix the remote code execution vulnerability. It just renders the published exploit useless.

    After inserting 10 magic characters into the exploit it will still work against 1.5.2

  24. Mark (podz)
    Support Maven
    Posted 8 years ago #

    I've asked for advice on this.

  25. Michael Adams (mdawaffe)
    Member
    Posted 8 years ago #

    ionic: I assume you have already contacted security@wordpress.org.
    No need to reply if you have (though if you haven't, please do so).

    EDIT: (didn't want to bump the thread) After seeing your response below: Thanks!

  26. ionic
    Member
    Posted 8 years ago #

    Yes I did and it is fixed for 2 days in the Subversion tree.

  27. PetLvr
    Member
    Posted 8 years ago #

    Beel: I stand corrected, I did not edit any files in the wp-admin directory, but have added to the folder.. // I have now converted two blogs .. both are unique and I guess share the same database. http://PetLvr.com/blog/ and http://1800HART.com/blog/ .. In both, a plug-in used is "UserOnline" v.1.5 by GaMerz ... it seemed to work fine in the first conversion .. In the second conversion, well - I'm getting a bad error that I don't understand. .

    "WordPress Database Error: You have an error in your SQL Syntax. Check the Manual that corresponds to your MySql server version for the right syntax to use near 'Set timestamp=1124271908",ip='142.161.171.143', .,. blah blah blah" ... Those two numbers are recurring in my sidebar. The second, is my IP address, but don't know what the first represents. I was as careful on the 2nd conversion and I was on the 1st conversion.

    Any thoughts?

  28. henchster
    Member
    Posted 8 years ago #

    Thanks for that download, link sure help me out and upgraded my exisiting board to 1.5.2 within second nice work.

    http://henchstersp.xstorm.co.uk/

    Cheers

  29. kjarrett
    Member
    Posted 8 years ago #

    Just upgraded four blogs in ~ 10 minutes.

    Longest part was the file upload.

    Great work everyone. Thanks!

    -kj-

  30. masquerade
    Member
    Posted 8 years ago #

    ionic, this was already fixed in 1.5.2, I suggest you go download the packages before you start throwing up secirty advisories on the public forums and creating FUD in unknowing users.

Topic Closed

This topic has been closed to new replies.

About this Topic

Tags