By MYCON-1 on

Download & unzip the new folder, and simply replace the other one via ftp, and good to go? this is what I'm doing and no problems yet.
Or is it better practice to uninstall the module on the front-end and then replace the folder?

⋅ Categories: Drupal 6.x

Comments

vm’s picture

vm commented

you don't need to uninstall the module before updating when updating on the same major version. Matter of fact, uninstalling the module first can cause problems as when uninstalled all information related to the module is removed from the database.

Always the 1st step: Database Backup

after you are sure you have a working backup:

disable the module
remove the old folder
upload the new folder
reenable the module
run update.php
test site

profjk’s picture

profjk commented

If it is not creating any problems for you, that should be good enough. However, the "Good Practice" would be to uninstall the module and delete it, upload new module, install and enable it to safeguard against problems!

profjk’s picture

profjk commented

VeryMisunderstood sounds logical. As well as faster in typing out the response!!

vm’s picture

vm commented

uninstalling modules is not a best practice unless you want to loose settings and content that may be held by those modules. "DISABLING" and NOT UNINSTALLING is a best practice.

MYCON-1’s picture

MYCON-1 commented

thanks guys; I still need to get my language more defined in the drupal reality; I was equating 'disabling' with uninstalling. This makes sense. Uninstalling and losing tons of ties to the core/other modules is of course not a good look.

Running 'update.php' I don't think I knew about, and I definetely wasn't backing up the db. Funny enough I just downloaded that module 'Backup and Migrate', hopefully it works sufficiently; access to my server is pretty inconvenient right now.

Thanks though; going to make your advice the status quo