If I were to upgrade from 6.x-1.3 to 6.x-2.x (either the -dev or -beta version), I know I would need to install the Features module. Is that all I would need to do?

Is there anything else anyone should know when upgrading from 1.x to 2.x? I'm going live with a site that uses Views Gallery very soon and I wanted to be sure that an upgrade from 1.x to 2.x would be possible later (or now) and that all the images and galleries will remain in place and not be affected by the upgrade. A list of steps to follow would be great, or just some reassurance that all will upgrade smoothly if Features is installed first. ;)

Thanks very much for your help... and for this great module. :)

Comments

KarenS’s picture

KarenS CreditAttribution: KarenS commented

Yes, install the features module (along with Strongarm and CTools). If you visit the modules page after doing that you will see that the module is still installed. Then go to the Features page to enable the feature.

Everything should work fine with no other changes, but as always when making changes like this do a database backup first so you have something to go back to.

aanjaneyam’s picture

aanjaneyam CreditAttribution: aanjaneyam commented

KarenS
I also have views gallery 6.13 on my site with lots of galleries and pictures. Your explanation is not clear. Am I right if I followed the following upgrade steps:

1. Backup site database.
2. Upload and enable/install Features, Strongarm and CTools modules.
3. Upload the replacement views_gallery (ver. 6.2.x) folder to the /sites/all/modules thereby replacing 6.13.
4. Run update.php
5. Go to Features page and enable the module.

Do I need to do anything else. Hopefully my images and gallery are intact and remain unaffected.

aanjaneyam’s picture

aanjaneyam CreditAttribution: aanjaneyam commented

Anybody please?

dmetzcher’s picture

dmetzcher CreditAttribution: dmetzcher commented

amsri: Your steps look correct. I just updated today from v.1.3 to v.2.0-beta1.

A few notes...

  1. Your step 5 wasn't necessary for me. It was already enabled on the Features page and was in the Overridden state.
  2. After updating, I noticed that the Gallery field on the Image content type no longer had a view selected under the "Advanced - Nodes that can be referenced (View)" section for the "View used to select the nodes" dropdown menu. If you don't have anything in there, no worries. I, however, had a view selected so that my users are only able to select galleries that they have created. I just had to reselect it and save the field again.
  3. Permissions will need to be fixed a little after upgrading. Be sure to go over the Drupal Permissions page and look for the create, edit any, edit own, delete any, and delete own permissions for both the gallery and image content types.
  4. Upgrading to v.2.0-beta1 fixed this issue: Non-Admin User Unable to Change Gallery on Existing Image
  5. I noticed that the "File Path" text field on the field_gallery_image field on the Image content type was changed after the upgrade. Prior to this, it was set to "images". After the upgrade, it was set to "photos". I changed it back, but not before a user uploaded a new image, so I had to clean that up a little. (Note that you will find the "File Path" text field under "Path Settings" on the field_gallery_image field. Click to expand it and the first field is "File Path".)
  6. The "Display Fields" setting for field_gallery_image on the Image content type was changed after the upgrade. Previously, it was set to "Lightbox2: reg->original", but it was set to "reg image linked to node" after the upgrade (Im about 90% positive that this is the case, and I confirmed with another user that the behavior had changed after the upgrade). I changed it back to "Lightbox2: reg->original" to correct this.

It doesn't really matter, but I installed/updated the modules in the following order:

  1. Strongarm (installed)
  2. Features (installed)
  3. Views Gallery (upgraded)
  4. Spaces (see my next comment below)

Hope all that helps.

dmetzcher’s picture

dmetzcher CreditAttribution: dmetzcher commented

I disabled an unrelated module today and Views Gallery was suddenly also disabled. I noticed that it said I was missing Spaces (another module). I do not see this listed under the requirements on the Views Gallery project page.

So I installed Spaces and reactivated Views Gallery.
Now, when I try to view either a Gallery or an Image node, I get page not found.
I have no idea what happened.

And, it seems that all aliases (and menus) on my site are suddenly ruined. It's like they go nowhere now. Why did this happen?
I tried deleting one of the aliases and I let pathauto recreate it. It still doesn't work. The alias is there, but I get page not found when I view it.
This happened AFTER I added Spaces and re-activated Views Gallery. Prior to this, everything was fine.
This also affects menus. Custom menus that I created now go to a page not found as well.

My whole site... basically down. It's completely unusable.

dmetzcher’s picture

dmetzcher CreditAttribution: dmetzcher commented

Disabled Views Gallery... issue with path aliases is still there.
Disabled Spaces next... issue with path aliases went away.

So... it's something with Spaces. Looks like Spaces uses the Context module... I'm thinking about upgrading that one, re-enabling Spaces, and seeing what happens. I'll continue to report back here using this comment all day.

Update: Found the issue that Spaces was causing with path aliases. It was one of the modules that comes with Spaces, called "Spaces Custom Text". I disabled it and it corrected the issue with the path aliases.

archer007’s picture

archer007 CreditAttribution: archer007 commented

Upgrade notes in the main description on the project page would be very helpful. Has anyone seen issues other than those mentioned already?

KarenS’s picture

KarenS CreditAttribution: KarenS commented

There was not supposed to be a dependency on spaces. That has been fixed. The code was intended only to work right if spaces is enabled.

I'm going to do a few upgrades and confirm if there are any other issues and document this on the project page.

KarenS’s picture

KarenS CreditAttribution: KarenS commented

Per the comments in #4 (really late, sorry):

#2 - Both the old and new code have no view selected. You altered that. So any custom changes you made to your fields will be lost and need to be added back.

#5 - Again, both the old and new code use the 'photos' path for the imagefield, so you apparently altered that.

#6 - Yeah, looks like the new code did not set the formatter up the same way, I should fix that.

I think the remaining possible problem is if someone changed the content type names for the gallery and/or image because Features requires a known content type name, and it is using 'gallery' and 'gallery_image' and nothing else will work.

KarenS’s picture

KarenS CreditAttribution: KarenS commented
Status: Active » Fixed

I added info in the README.txt about how to upgrade and also added a link on the project page to that.

The formatter was set up the same as the original code, so formatter settings also must have been changed later. I added info in the README to say that you will have to re-apply and custom changes you made to field settings.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

k_and_j’s picture

k_and_j CreditAttribution: k_and_j commented

I'm wary of upgrading to a beta as I'm not a power user. It's been a year and a half and the 2.0 version has not moved past beta. Looking through closed issues, the fix always seems to be to upgrade.

What can I do to get this moving again (and/or to get D7 versions running)?