See my other topic about this (which was closed, so I can't add a reply to it). I just updated Gravity Forms to 220.127.116.11 and the issue wasn't fixed.
The Form Editor is still working exactly as I described in the other topic.
I'm running Firefox 4 on OSX and encountering no problems what so ever editing form fields and creating fields in Gravity Forms v18.104.22.168.
Here is a screencast that shows me creating a form and editing a form using Gravity Forms v22.214.171.124 and FireFox 4 on OSX without any issues: http://screenr.com/TVy
I already mentioned it did work with new fields, but I can't edit already existing fields (I only get the remove/edit links when I add a new field). And with already existing fields I mean fields from forms existing prior to the WP3.2 update.
But I'll try clearing cache again.
Clearing the cache again didn't work. Btw, I've also tested with all other plugins disabled (except for the Campaign Monitor add-on & ofcourse GF itself) and the default theme, but the issue was still there.
So when you create New Forms with this version you can edit them fine but when you edit forms that existed prior to the upgrade it doesn't work?
Yes, exactly. And only when I add a new field to the already existing form I get the edit/remove links. Older fields can be removed after that, but not edited.
I have been able to replicate this issue locally now, it's only when editing existing fields and not when adding new fields or creating a new form (also new fields). We will look into the issue and get this fixed in an update. The odd thing is I wasn't encountering this issue when testing this release, the only thing that changed on my end was updating the nightly build of WordPress 3.2 which I think caused the issue to start happening for me, it may be the same with you. We'll get it fixed.
The issue is related to changes made to the nightly WordPress 3.2 builds. It was corrected, and then they made additional changes in the 3.2 beta build that broke it again. We have reproduced it and will be correcting the issue in the next release.
Just a reply to confirm the issue has been resolved. Using the latest GF & WP3.2beta2 :)
Thanks for confirming, Hiranthi. :)