[support] upgrading to 5.8. One question.

[Neil: esl-lounge.com]

I will do some testing too on a test site. I began this thread because I'd 
read in the upgrade.txt in 5.8 that "officially", you should disactivated 
all contributed modules before upgrading and I raised an eyebrow, 
remembering I'd had some issues with CCK by disactivating it and having 
content_type_X tables disappear.

It is possible I'm remembering badly but I've heard CCK mentioned by others 
in this thread and seeing as it's almost a core module in itself, it's vital 
we track this problem down, should it exist.

Neil


----- Original Message ----- 
From: "KOBA | Hans Rossel" <info at koba.be>
To: <support at drupal.org>
Sent: Monday, July 14, 2008 10:14 PM
Subject: Re: [support] upgrading to 5.8. One question.


> Interesting discussion.
>
> I also never disable modules when upgrading. I have never lost data
> when I disabled them originally, but as far as I remember some
> configurations of CCK were lost. But that was in the early days of cck
> and Drupal 4.7. Since then I never disabled modules and never had
> problems (always with backup ready). Its also quite annoying when you
> have more modules uploaded than enabled to have to write down which
> modules are needed for each installation.
>
> it could be good to hear from somebody who always does it right and
> disables all modules before upgrading that it has never caused
> problems, just to add some counterweight to this thread.
>
> Hans
> www.koba.be
>
> 2008/7/14, Earnie Boyd <earnie at users.sourceforge.net>:
>> Quoting Brian Choc <bchoc at t4tcolorado.org>:
>>
>>> I found that disabling modules during minor upgrades causes data loss
>>> consistently under specific circumstances, during earlier updates (e.g.
>>> 5.2,
>>> 5.3).  I observed that any module-supplied node type would drop all the
>>> data
>>> in any assigned CCK fields when disabling & upgrading.  For example, if
>>> one
>>> had a simplenews node with an "editor" cck field attached to it, one 
>>> would
>>> lose all "editor" information.  However, the basic simplenews node data
>>> would be kept, as would any cck fields attached to standard nodes.  Only
>>> the
>>> combo of cck + module-supplied-node-type seemed to cause problems.
>>>
>>
>> So what you're indicating is that modules implementing hook_node_info
>> will loose the node_type row and thusly the nodes of that type.  This
>> would then be a critical bug in the core base system.  Or perhaps your
>> incident is related to only one of the CCK fields modules and then the
>> critical bug would lie with that module.  Disabling a module should not
>> under any circumstance cause data to be removed.
>>
>> That said, I do not disable modules either when upgrading from Drupal
>> version 5.x to Drupal version 5.y.  However, that isn't the documented
>> method and the documented method needs to work.
>>
>> Earnie -- http://for-my-kids.com/
>> -- http://give-me-an-offer.com/
>>
>> --
>> [ Drupal support list | http://lists.drupal.org/ ]
>>
>
>
> -- 
> Hans Rossel
> KOBA Webdevelopment
> Kerkstraat 228
> 9050 Gent
> 09-334.52.60
> 0472-79.32.16
> www.koba.be
> info at koba.be
> -- 
> [ Drupal support list | http://lists.drupal.org/ ]
>