Legacy markup is a term we use to identify the markup code and practices that existed in Gravity Forms before version 2.5 of our core product.
Gravity Forms 2.5 was a major transition to more modern markup, and we overhauled the existing methods and styles to accommodate many accessibility enhancements, abandon some bad habits we have had for years, and to provide us with a more flexible and nimble methodology that can support upcoming features.
The legacy markup Form Setting was automatically enabled for existing forms on upgrade to Gravity Forms 2.5 and later. It was designed to allow backward compatibility with that release for the many millions of forms already in existence. New forms are created with the newer “modern markup” (legacy markup setting disabled), but legacy markup can be enabled for a newly created form if circumstances require it.
For more information on what changes in 2.5, refer to this summary article.
Legacy Markup Toggle
The use of legacy markup is toggled within the Form Settings. Therefore finding out if your form is using Legacy Markup is as easy as checking if your form has this setting enabled.
This article shows you where to find the setting.
Note: The Legacy Markup Toggle will only be available when you have a form on this particular installation with Legacy Markup enabled. For new installations or installations where there are no forms with Legacy Markup Enabled, the Legacy Markup Toggle will not display. Importing a form with Legacy Markup will allow the toggle to be enabled or disabled and you can manually enable Legacy Markup using the gform_enable_legacy_markup filter.
A new warning is also added to the Legacy Markup Toggle to advise incompatibility with the Orbital Theme:
Although we recognize and support the need for backward compatibility, it is important to note that this does not imply forward compatibility.
Legacy markup will not be updated to support future functionality.
As such, forms continuing to use the legacy markup option will not have complete access to new features. Some features will require the newer markup to function. You may also be presented with the following admin notice to warn you of this when legacy markup is enabled.
For example, the following features cannot be used while the legacy markup mode is set to on.
- The column feature of the Form Editor, where a user can drag content into columns.
- Some Submit button settings will not function. The Appearance settings of Submit Button Width and Submit Button Location will work in the editor but will not display as expected on the front end
- Conversational Forms created through the Conversational Forms Add-On do not support Legacy Markup.
What Can You Do?
We recommend that all new forms use modern markup wherever possible.
We also recommend that any time you need to make a major update to an existing form that uses legacy markup, seriously evaluate whether legacy markup can be switched off. Do this on a sandbox or test environment, then any normal testing you had planned for the form updates can also test the changes made to markup, confirming no negative effects in layout or theme support. Once completed, this ensures the most flexibility and ongoing support for your form.