Hi,
Drupal 6.1
Image module 6.x-1.x-dev

Drupal informed me that there was a new image module available. from the module page it appears as though it's the same version as before, but I take it there has been a minor change, but the module hasn't been renamed?

I disabled and uninstalled the old module.
Uploaded and reneabled the latest module.
ran update.php - it didn't show any updates to the database!

*All my galleries have been wiped, even though the images still exist in the same place on the server.

So - I reversed the module back using my back up.
deleted the mysql database, and restored the whole database from the back up.

All galleries are there and the site is back to its previous state.

I have looked in the previous support requests, but there doesn't seem to be anything exactly the same. The nearest request had a response of a link to other q and A responses, which I'm afraid were too technical for me.

Please can you tell me how to ensure all previously created galleries are correctly showing following an upgrade of the Image module?

Many thanks
Mark

Comments

nancydru’s picture

Um, "uninstall" generally deletes all content - and the message said that before you said "Yes, I'm sure."

Rarely do I uninstall a module when upgrading. The most I may do is to delete the source before re-extracting.

I'd say this should be "by design."

markmason7’s picture

Nancy - Thanks for your response,
I had assumed that uninstalling a module was part of the upgrade procedure after having seen it on drupal as a demo video. OK I just replaced the module, with the latest (11th April - at the time of writing), ran update, and all is still fine.

However, I have another site running Drupal 5.7 with Image 5.x module, which I want to upgrade to Drupal 6 with latest 6.x Image module. Are you also recommending that I don't uninstall 5.x just disable and replace the module files, re-enable and update?

I would be grateful for some advice please, as I have about 20 galleries with many images.

Many thanks

Mark

markmason7’s picture

In addition to the above:

I have tested the upgrade on a test 5.7 site to 6.2.
I disabled the modules but not uninstalled them.
Upgraded the site.
Uploaded all new version 6 modules, including latest Image (11th April).
Enabled modules.

All galleries are there but the images are not showing as thumbs. Just listed as attachments.

All content is there, but again images are not showing as thumbs.

Mark

nancydru’s picture

Well, this is a more special case.

When upgrading a major release of Drupal, you must disable (but do not uninstall) all contributed modules before upgrading the core. Then you install the new versions of the contribs and enable them (preferably one by one).

To further complicate this, not that Image 6.x is still not an official release yet, and the release notes for 6.x specifically say there is no upgrade path yet. I have no idea why this is, but that's what it says and that's why I haven't installed Image 6.x yet.

I'm not sure why anyone would tell you to uninstall a module before upgrading. Typically the uninstall code will delete all content associated with a module as well as all settings. Uninstall is typically a one-way street used when you intend to abandon a module.

markmason7’s picture

Nancy - thanks.

Yes I was just reading that "no upgrade path" warning on the current Image 6.x dev version. At least my test site is not a live site.

I just checked my source for the uninstalling of modules, and yes, you're right, I misunderstood. the recommendation was to uninstall only modules you will never want to use again.

I shall await an upgrade path for the Image module before upgrading my 5.7 site to 6.

Thanks for you help.
Mark

markmason7’s picture

If I can be of any assistance in testing the drupal 6 release version when it includes an upgrade path please let me know.

markmason7’s picture

I see there is now a 6.x-1.0alpha1 version.
I can't see an upgrade path so I have created another issue with a request for support on it.

sun’s picture

Status: Active » Closed (duplicate)

I think this issue has been fixed in the meantime.