FYI this has actually been an issue since the first beta but just kept forgetting to bring it up. The forms integration lists Gravity Forms as an integration but doesn’t work at all with GF 2.5. It does recognize the form > lets me select it > but displays nothing.
Form works perfectly using the “Classic Gravity Forms” element but not the new Form Integration Element
Thanks! Fixed for next patch.
This doesn’t appear to be fixed for me … at least not when the Form Integration element is in the footer. It makes the entire footer disappear in the editor. (It shows up just fine on the front end.)
In addition, this element doesn’t seem to respect all of the settings. For example, I have it set to Base Width of 500px and Maximum width of 90%. It works OK on desktop, where it is 500px wide. However, on mobile, it exceeds the 90% width of the screen (and actually bleeds off the right edge of the phone).
Thanks @dannikb,
I found another issue in the preview rendering system after testing again with a bunch of different form controls. We’re shooting to push another RC tomorrow so let me know if that resolves the issue for you.
I’m also seeing this issue in RC1. The form displays on the live site but not in the builder. I’ve seen this issue in both the content and the global block builders.
Fixed for next patch.
I tested this on RC2 with Gravity Forms. It’s fixed for newly created forms but the sample forms they provide which can be imported are still not displaying in the builders. This is true for forms imported both before and after the installation of Pro RC2.
I did more testing, and process of elimination, I discovered the drop down field was the issue. There are two drop downs in the advanced contact form they provide. Deleting the ordinary drop down did not allow the view in the builder to work, but when I deleted the one with conditional logic dependent on it, I was able to see the form in the builder.
This may not be the only problematic field type.
I imported their Multi Page Form Sample and it too fails to display in the builder. I have not had time to narrow down what field in this form causes the issue, but with a quick look at a few fields, I didn’t notice conditional logic tied to a drop down.
Hope all this helps.
Hi @Sheri17,
Thanks for the followup. Makes sense that specific types might introduce additional conflicts depending on what javascript is run there. Maybe I’m looking right past it… but I can’t seem to find the sample form you’re referring to.
Would you mind just exporting the form you’re working with and emailing me a copy? Thanks!
Ok, I think I’ve reproduced this - at least I’ve triggered another error. I’ll get this sorted for the next patch and we can see if that makes a difference with what you’re observing.