Thanks. I think I'll try without disabling modules.

Daniel.

Steve Kessler wrote:

Different users have different theories on this. I have found that disabling modules is more of a pain than its worth for updates within 5.X and within 6.X. You should not lose any data by disabling a module but always back up before upgrading both your site and your database.

Hope this helps.

-Steve

Steve Kessler Denver DataMan 303-587-4428 Sign up for the Denver DataMan Free eNewsletter

-----Original Message----- From: Daniel Carrera [mailto:daniel.carrera@zmsl.com] Sent: Friday, December 19, 2008 5:36 AM To: support@drupal.org Subject: [support] Upgrading Drupal

Hello,

If I am upgrading Drupal 5.9 to 5.14 do I still have to disable the modules before the upgrade?

Should I be worried that data might get lost if I disable a module?

Cheers, Daniel.

Hello,

I always backup the database before to upgrade. In case of problem it is very useful and it take a few time. We use also a test site to test all upgrades. That is just a copy of the site. With a test site you can try on your own configuration and with your own modules what you want without risks.

Best regards, Geneviève Romier www.projet-plume.org

Victor Kane wrote:

My policy is not to disable contributed modules for minor upgrades (ie. 5.x to 5.x+1).

I have never encountered a problem as a result of following this policy.

But in case you decide to do so, just disabling them (as opposed to then clicking on the uninstall tab and actually uninstalling the modules, which will run the module uninstall script, if it has one, and destroy all database tables) should not destroy any of your actual content associated with those modules.

Victor Kane http://awebfactory.com.ar

On Fri, Dec 19, 2008 at 10:36 AM, Daniel Carrera daniel.carrera@zmsl.comwrote:

...

Hello,

If I am upgrading Drupal 5.9 to 5.14 do I still have to disable the modules before the upgrade?

Should I be worried that data might get lost if I disable a module?

Cheers, Daniel. -- [ Drupal support list | http://lists.drupal.org/ ]

Yeah, I'll use a test site. Thanks.

Genevieve Romier wrote:

Hello,

I always backup the database before to upgrade. In case of problem it is very useful and it take a few time. We use also a test site to test all upgrades. That is just a copy of the site. With a test site you can try on your own configuration and with your own modules what you want without risks.

Best regards, Geneviève Romier www.projet-plume.org

Victor Kane wrote:

...

My policy is not to disable contributed modules for minor upgrades (ie. 5.x to 5.x+1).

I have never encountered a problem as a result of following this policy.

But in case you decide to do so, just disabling them (as opposed to then clicking on the uninstall tab and actually uninstalling the modules, which will run the module uninstall script, if it has one, and destroy all database tables) should not destroy any of your actual content associated with those modules.

Victor Kane http://awebfactory.com.ar

On Fri, Dec 19, 2008 at 10:36 AM, Daniel Carrera daniel.carrera@zmsl.comwrote:

...

Hello,

If I am upgrading Drupal 5.9 to 5.14 do I still have to disable the modules before the upgrade?

Should I be worried that data might get lost if I disable a module?

Cheers, Daniel. -- [ Drupal support list | http://lists.drupal.org/ ]

In this discussion, I am a little concerned that people might be confusing a major upgrade (Drupal 4.7 to Drupal 5.x, Drupal 5.x to Drupal 6.x) with a minor upgrade (Drupal 5.12 to Drupal 5.14).

Is this the case?

Victor

On Fri, Dec 19, 2008 at 11:42 AM, Emmanuel Seyman < emmanuel.seyman@club-internet.fr> wrote:

• Daniel Carrera [19/12/2008 13:46] :

...

If I am upgrading Drupal 5.9 to 5.14 do I still have to disable the modules before the upgrade?

That's what the documentation says but it's a lot of work for little gain. My procedure is :

When upgrading the core modules, do not disable nor upgrade the contributed modules you are using.

Once you have upgraded Drupal and given your site a quick test run to make sure it's still up and running, disable the contributed modules you are using, update them and re-enable them.

Go through another test run and you're done.

...

Should I be worried that data might get lost if I disable a module?

Hasn't happened to me, so far. Always make a backup of your data, just in case.

Emmanuel

[ Drupal support list | http://lists.drupal.org/ ]

Just thought I'd add my tuppence worth on one point: CCK had a bug in it till pretty recently (late summer '08 if i recall) that lost DB data when you disactivated it for drupal upgrades. I found out on a test site before launch so it was no biggie...and as many have said, you should always do a backup anyway in case something like that happens.

for the record, I don't both disactivating modules anymore and have never had a problem.

Neil

• Daniel Carrera [19/12/2008 13:46] :

...

If I am upgrading Drupal 5.9 to 5.14 do I still have to disable the modules before the upgrade?

That's what the documentation says but it's a lot of work for little gain. My procedure is :

When upgrading the core modules, do not disable nor upgrade the contributed modules you are using.

Once you have upgraded Drupal and given your site a quick test run to make sure it's still up and running, disable the contributed modules you are using, update them and re-enable them.

Go through another test run and you're done.

...

Should I be worried that data might get lost if I disable a module?

Hasn't happened to me, so far. Always make a backup of your data, just in case.

Emmanuel

[ Drupal support list | http://lists.drupal.org/ ]