Support » Installing WordPress » 2.7.1 Thanks for Nothing

  • Would have been nice if they would have told us that all of our mods would have been lost by upgrading from 2.7.

    Had no idea it was going to discard my CSS sheets and everything.


Viewing 13 replies - 1 through 13 (of 13 total)
  • Moderator Samuel Wood (Otto)

    (@otto42) Admin

    What mods are you talking about? What CSS? You need to be more specific.

    If you’ve modified any of the files included with WordPress itself, then yes, those will be overwritten. This is why you should never modify the core files.

    If you’ve made changes to the WordPress Default theme, then you will need to restore your files from your back as the automatic upgrade rewrites the files for the WordPress Default and Classic themes. If you don’t have a backup of your files, in particular the wp-content/themes/default folder then ask your host if they have a backup.

    Please review WordPress Backups to make sure it does not happen again in the future.


    Please quit dissing WP because you didn’t make yourself familiar with what needs to be done before you upgrade. One of those things would be the backing up of your files/database which you could have the used to restore any modifications you made to your theme/core files.

    Hang on a minute guys

    I’m with ajpn on this – a change from 2.7.0 to 2.7.1 is an UPDATE it should not have touched any files not shipped with the 2.7.0 package.

    If this had been an UPGRADE to 2.8.0 then fair enough – it would be a major revision and it could be expected to rewrite entire directories.

    An UPDATE should only rewrite individual files, not entire directory trees.

    AND there is a serious oversight in wp-settings.php

    It states that the default_secret_key from wp-config.php must be copied into the relevant position.
    There is NO DEFAULT_secret_key in wp-config.php – it means the AUTH_secret_key – that needs fixed for 2.7.2

    Moderator Jan Dembowski


    Brute Squad and Volunteer Moderator

    An UPDATE should only rewrite individual files, not entire directory trees.

    That would be nice if it were true but that’s not how it works. The whole distribution/package/euphemism-here get’s updated. You are running a self-hosted blog so you’d best acquaint yourself with doing full backups of your files and database.

    As MichaelH said updating/modding the distributed files is fine, even the Default theme. But it’s up to you to backup your mods and know what you’ve changed.

    Don’t modify those files. In the Default theme’s case, it’s trivial to copy that to your own themes/myblogtheme directory and modify the style.css with a different name. That way the next time an update comes in, your personalize default theme will not be impacted.

    Personally, I only ever modify imported themes, and use plug-ins. I also run a back-up of everything before an upgrade – it’s why it takes me 6 hours per site to do the full upgrade manually.

    However, I also use SMF Forums on some of my sites, and a core system “one click” upgrade only modifies files and/or ADDS directories and files – it does not delete them – nor does it delete existing files (even core system files) it simply parses them for where to insert the updated code, and in that manner it leaves any existing mods in place – with SMF, we don’t even touch the plug-ins when updating the core because the upgrade/update system is smart enough to know what code is not from SMF..

    That’s what WP should be doing – especially considering how many non-programmers and non-server-techs there are using the program.


    Moderator Jan Dembowski


    Brute Squad and Volunteer Moderator

    it’s why it takes me 6 hours per site to do the full upgrade manually.



    Gaz, pal, buddy, friend, I backup my blog every night and keep 30 days worth of files/database automatically via a scheduled job. I do check the backup on a regular basis but it’s generally fire and forget. It’s also saved me when I do bone headed things.

    Using SVN it takes me about 1 minute to upgrade each blog. I have not used the automatic upgrade so I can’t really speak to that. But just as a friendly suggestion, you may want to re-evaluate how you are maintaining your software…

    6 hours per site to do the full upgrade manually

    I’m with @jdembowski here. The most time-intensive part of an upgrade is FTPing the new source code to the server…if you have a control panel that allows you to upload and unzip files, then even that’s a 10 second process. You can backup your old source code in-place, dump the database, upload the new source code, create a new config file, move over the custom stuff and then upgrade…a 15 minute job tops.

    Moderator Samuel Wood (Otto)

    (@otto42) Admin

    That’s what WP should be doing – especially considering how many non-programmers and non-server-techs there are using the program.

    If you’re a non-programmer, then you should not be modifying the core files anyway.

    Plugins, additional themes, etc, these will NOT be overwritten or removed by an automatic upgrade. The upgrade only overwrites the files that are actually in the WordPress installation.

    Maybe this will help:

    How to Upgrade WordPress 2.7

    jdembowski & figaro – you’re both suffering from the blinkered “we live in a developed country with developed IT infrastructure so we’re OK” viewpoint.

    I’m 12,000 miles from my hosting server, in a country where the internet collapses every time it rains or the wind gets above 10mph (overhead lines and inept telco technicians).

    What starts at the exchange as 2MB broadband (fastest available in this country) reaches me at around 500K and regularly drops to 4K for extended periods, if the connection remains at all. Every time China or Singapore sneezes, this country loses all international internet for days. A few years back, we lost all international internet for nearly 3 months because a fishing boat dragged anchor in the South China Sea and broke THE (i.e. the only) cable.

    Add to that a country supposedly on stable 220volts 50Hz with a main electrical supply that yoyos between 0v and 350v and you start to get an idea of what we’re facing here. Just because we have a connection now, does not mean we’ll have it in 2 seconds time.

    This country is not exceptional – geographically, there’s more than 50% of the world in the same state.

    figaro – 10-second upload for the WP zip? I wish – see above.
    JD – SVN – what’s that then? And how do you use it?

    Thanks to a wild and random thought, last upgrade I simply copied the entire WP install on the server to another folder as an “instant” and temporary back-up solution – seems to have done the trick in terms of cutting job time drastically, though I’m now at risk of having my hosting account suspended for using the hosting space as a file store.

    Across hosting servers in several countries, I have many installs (not just one blog), and would welcome anything that drastically reduced upgrade admin (as well as back-up admin). Having also a portfolio of other ecommerce and community sites leaves me little time to do the required research and self-education (“can’t see the wood for the trees” syndrome).

    I do still stand by earlier comments though – an automatic upgrade from 2.7.0 to 2.7.1 should be parsing the changes, not overwriting the whole directory structure. Even just a file by file XML would save the deletion of non-core directories and files – at a developer level, that xml list could be templated so they can knock out files that are not changed during an upgrade, and only affect files with changes.


    Moderator Jan Dembowski


    Brute Squad and Volunteer Moderator


    SVN stands for Subversion. It’s a revision control system and I use it to upgrade my WordPress installations.

    If you have a UNIX/Linux/BSD system then there is probably a package for your system. The CLI interface is the command ‘svn’.

    Once you have SVN installed it’s pretty easy to use.

    See for instructions on new installations using the stable version.

    For example using to install the files for WordPress 2.7 in a directory named blog:

    cd blog
    svn co .

    The ‘co’ stands for checkout. You are checking out a copy from the repository.

    Then a new version comes out, version 2.7.1. You just run switch command like so

    cd blog
    svn sw .

    This will only download the copies in the 2.7.1 repository that have actually changed from 2.7 to 2.7.1. Given your line conditions and Internet speed issues, this might be an attractive option for you,

    This is for files only and will not effect your database. It overwrite any core files that you have modified including the default theme. This is why earlier it was stated that modifying the default theme (or any core files) is unwise.

    jd – thanks for that – I’ll have to revisit this over the weekend and have a play with a test install of an older version to see if I can get the hang of it.

    As I said – anything that saves time will be a great help.

    (but I still prefer SMF Forums’ upgrading system 😉 )

Viewing 13 replies - 1 through 13 (of 13 total)
  • The topic ‘2.7.1 Thanks for Nothing’ is closed to new replies.