How do you migrate from 7.x-2.x-dev back to 7.x-1.x?

I don't know why I was using the 7.x-2.x-dev branch but I wanted to migrate to the 7.x-1.x version.

The database schema and the contents of the 'data' column look similar so on my test environment I simply replaced the 7.x-2.x-dev code with the 7.x-1.x code. This seemed to work ok (i.e. fieldsets in content types still worked ok).

Having said that, the only feature in use was fieldsets, so I was not faced with migrating any 7.x-2.x-dev specific, and therefore potentially more complex, issues.

If anyone is aware of anything I've missed please let me know and hope this helps.

I have just "downgraded" myself, and did encounter some problems. Fieldsets and divs were ok, but a form which used the Multipage option threw some errors:

Notice: Undefined index: formatter in field_group_pre_render_multipage() (line 807 of mysite/sites/all/modules/field_group/field_group.module).
Notice: Undefined property: stdClass::$collapsible in field_group_pre_render_multipage() (line 811 of mysite/sites/all/modules/field_group/field_group.module).
Notice: Undefined property: stdClass::$collapsed in field_group_pre_render_multipage() (line 812 of mysite/sites/all/modules/field_group/field_group.module).

I tried resaving the form, and switching the field-group type to something else and switching back again, but no luck. So I had to delete all the field-groups and start again from scratch on the form which used Multipage.

Hope this is useful info (or warning) for anyone needing to do the same.

I am unable to uninstall 7.x-2.x-dev. Even though I selected the uninstall option.
When I attempt to install 7.x-1.x-dev, I am told that field_group is still installed.

I noticed that the entry in the system table contains the version, so simply replacing the code could be problematic.

I would have thought that uninstall would have deleted the field_group from the system table.

Any suggestions besides manually deleting the field_group entry from the system table?

I also have this issue and I think it is time for a solution.

Can anyone help us, pls?

Is 7.x-2 no longer being developed? If so I also need to migrate to 7.x-1

Hey all,

First of all, as said in the description that explained 7.x-2.x branch on the project page, 7.x-2.x was never a "better" version only a different set-up (without horizontal tabs) since horizontals would be better of in another module.
So, differences between 1.x and 2.x:
- horizontal tab element is not available in 2.x (using this, you should have the elements module with a patch)
- another approach for people wanting to hook into the form altering and preprocessing of forms. The code was merged from 2.x to 1.x so this would be the same.
- 2.x does not have all the upgrade hooks as it was not longer supported.

Upgrade path should not be necessary, I don't know why you would have a WSOD.
The only think I can imagine is that the old 7.x-1.x update script did not run for some reason (maybe because drupal thinks the version 2.x was higher ...)
To know for sure, try resetting the version in the system table to a lower number ... that should fix it.

Special for trainingcity: don't use another branch if you don't know the difference. I also think in your case, you just need a cache clear.
Can you be so kind to elaborate on the "memory leak" think. I never came across such a think, I think this can be very informative for everyone.

For people still having problems, you can check the patch that merged 2.x into 1.x: http://drupalcode.org/project/field_group.git/patch/61fc57ebe83a6304caf3...

thx.
that's the problem, there shouldn't be any upgrade path, it's just fields nested in groups. no db changes or whatever.
As mentioned before, the only think I can imagine is that some update hooks which were in the 7.x branch did not run. So the only thing fieldgroup can do is advice to run them again. Or by invoking them manually in a custom module or reset the version number to the 7.x version of the time when you installed field_group the first time.

If the site goes into a loop, and the module to blame is fieldgroup, then this can only happen when a groupA is parent of groupB and GroupB has parent groupC and then groupC has parent GroupA again... things like that.

I was never able to reproduce this. if someone can provide steps to do so ... or a secure db dump on a normal drupal install, I will try.

It looks like part of the problem here is there is no hook_uninstall(). Is it safe to simply uninstall the module and delete the field_group table?

Hello,

I have the exact same problem here. I need to get ride off this 7.x-2.x-dev version but after exploring db and removed field_group I'm always not able to install the 7.x-1.5 version. Is someone else succeed in it?

Thanks in advance
François

Hello Traningcity,

I finally succeeded in by removing all what I sw in database and then by copy paste database code in phpMyAdmin. This work fine for now. Thank you for your proposal :)