Upgrade 1.5 > 1.5.1

  • Please read the whole thread – many people have added useful information !

    This applies ONLY to an upgrade from 1.5 to 1.5.1 – it is not the method to use if upgrading from an earlier version.

    It may look complicated – it isn’t!

    1. BACKUP your database
    2. Download 1.5.1. Unzip it.
    3. Open the unzipped folder, and DELETE wp-images. (You have no need for these in an upgrade)
    4. Now open your ftp program and go to your blog directories
    5. On the server, delete the directories wp-admin and wp-includes. Note: If you have “languages” directory in your wp-includes folder (with .mo files) you may want to save/backup those before deleting the wp-includes directory. Upload the new ones.
    6. The Classic and Default themes have been changed slightly so if you wish to, you can upload those to your wp-content folder.

      7. (See the post below this)

    7. On the server and at blog root, delete the old WordPress files and upload new ones. I recommend you do this one by one if you are not sure. Do not delete wp-config.php.
    8. Now run “www.example.com/wp-admin/upgrade.php”

    That’s it.
    You don’t go near your wp-content folder so your themes and plugins are perfectly safe. this is a very easy upgrade – probably the easiest one yet for WordPress.

    Please use a proper ftp client.

    Please don’t think it’s easier to overwrite and not bother deleting files first – you will get errors, you’ll post here for help, we’ll tell you to do it properly, you will and the errors will go away. Far easier to cut that middle stuff out ??

    If you wish, you can delete the following files:
    install*.php
    upgrade*.php
    import*.php

Viewing 15 replies - 166 through 180 (of 203 total)
  • Thread Starter Mark (podz)

    (@podz)

    wp-admin should have permissions of 755
    everything IN it should be 644

    Please … I said a screenshot of the issue. I will mod that chunk of code.

    Thanks! Sorry for the output, didn’t think anyone would mind(I changed the post a bit more to look better).

    On the subject, that is how the permissons are, I should be all right now then? (in other words, the update script does not change anything else which I would have to do manually?)

    Smooth upgrade with one anamoly. After the upgrade, comments and trackback options were all set to ‘on’ in Options. These are options I had set to ‘off’ in 1.5 since I don’t use them in my site.

    Many thanks to the dev team.

    My previous image dissapear from the home page
    https://photo.e-roro.net
    in the archives the previous link and image works fine.

    @kay 9
    I have described the process of backing up and restoring the database in my post – https://blog.taragana.com/index.php/archive/note-to-self-backup-restore-procedure-for-mysql-database-for-wordpress-etc/

    phpmyadmin doesn’t work for database size over 2MB.

    @vkaryl
    Would the simpler dashboard be from me ??
    Good to know it is still working on 1.5.1

    I know quite some people use my Admin Dashboard hack (link above) which replaces wp-admin/index.php file. I believe the same procedure should also work in this bug fix version 1.5.1. Let me know if you face any problems in my comments (link above).

    Hope that helps…

    Ah ha! Yes, Angsuman, it IS yours! I am more than occasionally senior AND blond at the same time, and while I saved the zip file to its own folder, I did NOT label where it came from. Idiocy incarnate! And the file once unzipped doesn’t include any info about the author etc. for some reason.

    If you would like to send me the author info, I’ll paste it into the php file. Email sylvermoon*at*gmail*dot*com.

    And yes – I did not make any changes to the file itself, simply replaced the wp-admin/index.php file with it. Works fine.

    Angsuman, hello! I am also using your Dashboard trim ver 2, and I really love it. Absolutely love it. I did not upgrade to 1.5.1 (and have no plans to at this time), but instead used a patch (thanks again Shelley) just for the security bug, which is fantastic. So I am not backing up anything right now. (Your instructions on the db backup are beyond me, anyway, and not critical right this minute for me because, as I said, I’m not upgrading from 1.5. When I do backup, I will just ask my hosting service people, who are not only friendly, but quick to respond! I’m lucky.) But THANKS very much for taking the time to read/reply. Very nice of you.

    @vkaryl Thanks. Its no big deal. I didn’t include author info initially because it wasn’t really a plugin, just a drop-in-replacement. However I took your advice and updated the code.

    Please download the updated hack from my website. It adds few usability enhancements (without wasting bandwidth).

    To anyone else interested, as Vkaryl and myself have tested, it works with 1.5.1 too.

    I have just upgraded two 1.5 sites to 1.5.1. On one site, I received an error about upgrade-functions.php:

    // Rewrite the theme header.
    $stylelines = explode("n", implode('', file("$site_dir/style.css")));
    if ($stylelines) {
    $f = fopen("$site_dir/style.css", 'w');

    It couldn’t find the file to open…

    On the second site, I didn’t have this error and the upgrade seemed to go successfully. I noted that a whole new folder appeared in my themes dir called /my-site/.

    Do I need to de-activate my current theme and then ACTIVATE this new theme created by the upgrade?

    If yes, any ideas about how I can clear up the fopen error in upgrade-functions.php so that I can successfully upgrade my first site?

    TIA!
    JF ??

    Angsuman – thanks, will grab and update immediately! [Edit: did so, and its working perfectly – I like the new stuff in the sidebar too!]

    jfriesen: are these on the same or different hosts?

    @kay9 I am happy to know you found it useful.

    > Your instructions on the db backup are beyond me, anyway, and not critical right this minute for me because, as I said, I’m not upgrading from 1.5.

    All you need to do is run the following command from shell script:
    mysqldump a€“opt wordpress | gzip -9 > wordpress.sql.gz

    What I didn’t mention was that your have to use <b>-u username -p password</b> after mysqldump (with the values suitably substituted).

    I think it is a good idea to back up the database at some intervals, even if you don’t upgrade.
    In fact recently I faced an interesting situation with phpMyAdmin and I was really happy to have a backup ??

    Let me know if you face any problems in my post comments.

    BTW: I have also decided not to upgrade to 1.5.1, at least not until the reported problems are sorted out. I am waiting for Shelly to reply me with her patch. However I have a feeling that might not be the main issue. I took a look at the defects filed and there are more critical bugs like non-checking of login/passwords strings and low level users can modify config file etc. I will know for sure when I get the patch.

    It would have been very helpful to get the patch from Matt himself, however I haven’t heard back from him yet.

    Hi vkaryl, thanks for the reply.

    The sites are hosted by the same host, though they are on different virtual servers that I manage. I know of no differences between the servers though.

    After the error occurred, I had a peek inside the themes folder and found a folder called /my-site/ but unlike the successfully upgraded site, this one had only an empty /images/ folder and style.css.

    The upgrade (when successful) seems to create a revised theme based on your activated theme. Do we need to activate this new theme to complete the upgrade?

    thanks!
    JF ??

    I am reading several posts by members here complaining of problems with 1.5.1 upgrade. Check out MacManx blog for some details too. Some like Tom Raftery feels it is ok, but when I went to comment on a post on his site, I found that it is broken. So people feeling ok may just haven’t explored enough to know, specially non-visible like trackbacks or pings.

    Is 1.5.1 still a recommended upgrade? Matt?

    I was wondering if Matt and his team could just roll out a patch for the security vulnerabilities.

    Personally I will hold of any upgrade till WP goes to a more stable debugged release.

    jfriesen: not as far as I know. In fact, I simply delete the extraneous “mysite” or whatever folders. There seems no real need for them, all 4 of my installations are humming right along with the same theme folders I’ve had since inception. If these “new” theme folders are a necessary part of the install, then someone needs to say so. I can’t see the point, myself.

    As to your issue: if they are on the same host, then the php etc. specs should be the same. So that leaves me without anything to offer except perhaps to begin again with the problem one: reupload the upgrade files, and run the upgrade.php again…. I know I saw a couple of posts over the last week where someone did that and it worked the second time. Can’t hurt I guess.

    Angsuman, thanks for your kind reply. I found an easier (for me) way to backup the db, since I’m not at all familiar with shells or any of that. I was surfing around my hosting site; I went to CPanel, which had (surprise!) a big button labeled “Backups.” Ha! Then I chose the aptly-named “Download a MySQL Database Backup” option. Click. All done. Now that’s “db Backup for Dummies”! ?? Thanks again, though, for trying to assist me.

    I’m posting this not only to say thanks, but also just in case it can help someone else who comes along reading this thread and can use this option. Best wishes. ??

Viewing 15 replies - 166 through 180 (of 203 total)
  • The topic ‘Upgrade 1.5 > 1.5.1’ is closed to new replies.

Tags