By PaulWood on

Is is safe to only overwrite with newer files when upgrading?

For example, the most recent file date in ver 5.10 is 08/03/2008. In ver 5.11 there are only 48 files with a date stamp more recent than 08/03/2008. Can I just overwrite those 48 files? I intend on using the following steps:

  1. Login as user1
  2. Take site off-line
  3. Switch to Garland
  4. Disable all non-core modules
  5. Overwrite with only the newer files
  6. Run update.php
  7. Re-enable non-core modules
  8. Bring site back on-line

Should I re-enable the non-core modules before running update.php or after as listed here?

Thanks for your comments.

⋅ Categories: Drupal 5.x

Comments

PaulWood’s picture

PaulWood commented

Oops. The date for the most recent file in ver 5.10 is 08/13/2008. My question remains the same.

cog.rusty’s picture

cog.rusty commented

For a minor update like 5.10->5.11 which has the same files, it is ok to overwrite with the newer files.

You must run update.php after uploading the new core files, to do their database updates and make them work reliably. Then you must run it again after uploading and enabling any additional modules, to do their database updates as well.

Running update.php is harmless because it keeps track of the database updates which it has already done.

PaulWood’s picture

PaulWood commented

Thanks for your insight. So, to recap:

  1. Backup database
  2. Login as user1
  3. Take site off-line
  4. Switch to Garland
  5. Disable all non-core modules
  6. Overwrite with only the newer files
  7. Run update.php
  8. Re-enable non-core modules
  9. Run update.php again
  10. Bring site back on-line
  11. Switch back to preferred theme
JamesKB’s picture

JamesKB commented

Would this also apply for updating from 6.3 to 6.6???

cog.rusty’s picture

cog.rusty commented

Same thing. It is an upgrade between minor releases. In such cases it is not even necessary to disable any modules. Just make sure that update.php runs and completes successfully at the end.