- πͺπΈSpain oriolroger
Hi. We're having the same problem here. We're migrating a site from Drupal 7 to Backdrop, and when we run the module unfeaturize to move all data from the features to the database, it seems that the field groups and the order of the fields are not saved, once we migrate that content into Backdrop. Could it be anything we're missing?
Thanks for your help!
- π¦πΊAustralia klonos 90% Melbourne, Australia - 10% Larissa, Greece
Here's a feature module to help those that want to test/reproduce/troubleshoot this. I've named the fields and groups according to the order they are meant to be, but here's what the order should look like:
- πΊπΈUnited States jenlampton
Hi Everyone, thanks for reporting this issue!
Can you check to see if the field group information is still present on the Drupal 7 site after the features have been removed? If so, the problem is probably in the upgrade path for fieldgroup on Backdrop, but if not, the problem is definitely in unfeaturize :)
Thanks!
- πͺπΈSpain oriolroger
Hi both, and thanks for helping on this.
I've run the test to unfeaturize and disable one feature with a content type on it. The content type has five field_groups in the Manage fields section.
When it finishes to unfeaturize, the DB table "field_group" is still empty (I've supposed that this is the table where the field groups should be saved), and all the field groups in the Manage fields section have disappeared. We've also lost the order of the fields.
I'm using version Unfeaturize 7.x-2.0, and Features 7.x-2.14, if it helps. And I can't see any strange watchdog log message, other than the notice one: "Disable completed for test_feature / node."
We'll keep looking at this, thanks again for your support.