Loading Profile...
Twitter,
Facebook, or email.
As Gypsy is not going to be available for 2.0 for a while I've been reviewing if I can manage without it and so be able to upgrade. I plan to put all the custom fields into one field group.
Am I right think the only way to do it is to edit the database directly in something like phpMyAdmin?
I think I just need to change the field group in exp_weblog_fields to my chosen one.
But, do I change 'field_is_gypsy' to 'n' and 'gypsy_weblogs' to empty at the same time or change them in the EE control panel before I edit the database?
I don't want to loose any of the existing data.
I’m
unsure
Official
Response
-
You are correct – changing the group_id column within your exp_weblog_fields table is all that is required to move a field from one group to another.
You can delete the field_is_gypsy and gypsy_weblogs columns entirely.
I’d recommend you backup your database first, just to be safe (especially because you’re upgrading to EE2).
EMPLOYEE
-
You are correct – changing the group_id column within your exp_weblog_fields table is all that is required to move a field from one group to another.
You can delete the field_is_gypsy and gypsy_weblogs columns entirely.
I’d recommend you backup your database first, just to be safe (especially because you’re upgrading to EE2).Comment -
-
I’m
unsure
Everything seems to have gone OK.
I have disabled the extension and removed the files from the server but notice that in the exp_extensions table there are still 6 entries for Gypsy.
Could these confuse anything in the future and so should I delete those entries?
Or will it mess up the extension_id table if there entries after them? -
-
Good to hear.
You can go ahead and delete those rows in exp_extensions. -
-
Thanks Paul for pointing me to this thread. I'll explain what I have tried in case I've misunderstood, or if I haven't in case it's of help to others.
I have a 3-site MSM system on EE1. For site_id 1, we have weblogs 1, 3, 4, 22, 23, 34, 36, 41, 42, 50 which share gypsy fields; these fields being defined in field groups 1 and 4 (some of group 1's fields are used in 1, 22, 23, 34, 41, 42, 50; and some of group 4's fields in 1, 3, 4, 22, 23, and 36). Don't ask.
Having upgraded the database to EE2, I did as follows.
First I created a new ‘Generic’ field group, field group 42.
Then I changed the channel fields to put all the fields in the new field group:
UPDATE exp_channel_fields SET group_id = 42 WHERE site_id = 1 AND group_id IN (1, 4);
Finally I updated the channel table to use the new field group for the relevant channels:
UPDATE exp_channels SET field_group = 42 WHERE site_id = 1 AND channel_id IN (1, 3, 4, 22, 23, 34, 36, 41, 42, 50);
So far this seems to work, although I haven't dared edit anything...
All that remains is to use Publish Layout to hide the unwanted fields in each channel in turn.
If I have this wrong please let me know!
Cheers
Brian -
