This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
August 18, 2010 7:46pm
Subscribe [3]#1 / Aug 18, 2010 7:46pm
I’m sure this has been covered, but Google and the search here are not helping me today.
I have a few sites that use Gypsy. Not a lot, but enough to break things if I didn’t have gypsy. It is one of the biggest reasons I don’t upgrade all our 1.x installations (3).
Has anyone done this? Do I need to recreate a field for each field group? Can I use the 2.0 version of the gypsy like add on I just saw on devot-ee?
#2 / Aug 18, 2010 7:49pm
You might want to ask the author. 😊
#3 / Aug 18, 2010 8:04pm
You might want to ask the author. 😊
Perhaps, but I figured he may not want to take the time to tell me how to not use his (free) product.
I’m sure some people here have been in this situation and frankly I’d rather get the input of average joe’s than developers who know things inside and out.
#4 / Aug 18, 2010 8:31pm
Brandon actually just published a very interesting blog post on a possible solution using the Publish Layouts feature. This is something that could be used.
http://brandon-kelly.com/blog/custom-fields
Since neither Gypsy nor Field General is EE2 compatible, and it seems that Gypsy isn’t likely to be (Brandon has specifically said that he’s not doing it, not to mention that the hook it requires is missing in EE2, anyhow), then the Publish Layouts option might be the best bet, even though it would mean assigning virtually all of your custom fields to every channel and then selectively hiding or showing them.
Personally, I like the way MODx handles this with Template Variables, and it would be nice to see something similar in EE.
Anyhow, Brandon’s post should at least give you an idea of what you could do now if you wanted to move to EE2 sooner rather than later.