Gravity Forms Conversational Forms Update Proudly Announces Forms Will Now Occasionally Continue Being Forms
Gravity Forms released Conversational Forms Add-On v1.8.0 this week, delivering a sweeping package of enhancements designed to ensure website visitors can once again perform advanced tasks such as clicking “Next.”
Among the landmark improvements:
• Draft submissions will now resume where the user actually left off, rather than transporting them back to the beginning as punishment for their lack of commitment.
• The “Save & Continue” Send Link button has reportedly entered its long-awaited “sends link” era.
• Phone number dropdowns and phone number fields are now the same height, ending a visual crisis that had brought several front-end developers to the brink.
• The word null will no longer mysteriously appear above form labels, depriving website visitors of the opportunity to wonder whether they’ve accidentally entered the Matrix.
• Conditional logic applied to a “Next” button will now also be respected by the other buttons whose entire purpose is also to go next.
• Duplicating a conversational form will no longer randomly increment its permalink, because apparently the URL had been participating in the conversation too.
• Three-digit hex colors will no longer return NaN, marking another decisive victory in humanity’s centuries-long struggle to make computers understand colors.
• A fatal error affecting Gravity Forms 2.9+ has also been fixed, tucked quietly between button markup support and a phone-field height adjustment like someone mentioning during lunch that the building had previously been on fire.
The update additionally adds support for Gravity Forms 3.0’s new Repeater field and button markup, while updating components to “the latest version,” a technical term meaning everyone involved has agreed not to discuss what version they were on before.
Developers praised the release.
“This is huge,” said one WordPress administrator while staring emotionlessly at 47 available plugin updates. “Yesterday my form could display null, forget where you were, ignore its own conditional logic, break its Save & Continue button, throw JavaScript errors, generate PHP warnings, and occasionally die.”
“Today,” he added, “the phone fields line up.”