Excellent! This goes without saying, and should be underlined three times:<br><br>1. Work with a test site (if necessary copy your production site over). It can even be on your local development computer or laptop.<br>2. Backup the file system and a dump of the database all together as a single snapshot of the production state.<br>
3. Do the upgrade first on your test site. If all goes well, carry out the same procedure on your production site. For same release upgrades (5.x to 5.y) the procedure is very quick.<br><br>Victor Kane<br><a href="http://awebfactory.com.ar">http://awebfactory.com.ar</a><br>
<br><div class="gmail_quote">On Fri, Dec 19, 2008 at 11:04 AM, Genevieve Romier <span dir="ltr"><<a href="mailto:genevieve.romier@urec.cnrs.fr">genevieve.romier@urec.cnrs.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
I always backup the database before to upgrade. In case of problem it is very useful and it take a few time.<br>
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.<br>
<br>
Best regards,<br>
Geneviève Romier<br>
<a href="http://www.projet-plume.org" target="_blank">www.projet-plume.org</a><div><div></div><div class="Wj3C7c"><br>
<br>
Victor Kane wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
My policy is not to disable contributed modules for minor upgrades (ie. 5.x<br>
to 5.x+1).<br>
<br>
I have never encountered a problem as a result of following this policy.<br>
<br>
But in case you decide to do so, just disabling them (as opposed to then<br>
clicking on the uninstall tab and actually uninstalling the modules, which<br>
will run the module uninstall script, if it has one, and destroy all<br>
database tables) should not destroy any of your actual content associated<br>
with those modules.<br>
<br>
Victor Kane<br>
<a href="http://awebfactory.com.ar" target="_blank">http://awebfactory.com.ar</a><br>
<br>
On Fri, Dec 19, 2008 at 10:36 AM, Daniel Carrera <<a href="mailto:daniel.carrera@zmsl.com" target="_blank">daniel.carrera@zmsl.com</a>>wrote:<br>
<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hello,<br>
<br>
If I am upgrading Drupal 5.9 to 5.14 do I still have to disable the<br>
modules before the upgrade?<br>
<br>
Should I be worried that data might get lost if I disable a module?<br>
<br>
Cheers,<br>
Daniel.<br>
--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br>
<br>
</blockquote>
<br>
</blockquote>
<br>
</div></div><br>--<br>
[ Drupal support list | <a href="http://lists.drupal.org/" target="_blank">http://lists.drupal.org/</a> ]<br></blockquote></div><br>