Thread

I have a lot of custom fields that rely on FieldFrame. I realize that extension has been integrated within EE in version 2.

Several of my custom fields rely on RI States Select, VZ URL, and SI Countries Select which (I assume) are no longer available/valid for EE2. There are others that rely on FF Radio Group and FF Checkbox.

What are my options moving forward from 1.6.8 to 2.0.x with these fields?

Should I convert these fields to something more basic (Text Input)?

Seems like a pretty simple question that’s keeping me from shelling out the $$ to upgrade to EE2…

EllisLab-ers, any takers? Not asking for a walkthrough, just some guidance (even if it’s: you’re SOL).

This forum is for community support, which is why you’re not getting any staff responses.

As per the docs, you should make sure that any add-ons you’re using have 2.0 compatible versions.  If you want to update and don’t have those available, I’d recommend experimenting on a development installation, so as not to affect your live site.

And moved from the Core forums to the General forum.

Makes sense. I’ve done my research and I’m feeling good about my “add-on” situation.

My core question is: If FieldFrame has been “integrated” into EE2, what is the recommended best practice for getting existing 1.6.8 FieldFrame fields ready for prime-time?

You would be best to talk to each fieldtype author about an upgrade path for their fieldtype.