Legacy markup options in Gravity Forms will be removed by the vendor in the future v3.1 release. Also, UW Theme 2.0 will not accommodate legacy markup styling. Users are encouraged to review existing forms and toggle off the legacy markup now, if possible (action steps included below).
Background
The legacy markup toggle allowed for continued use of Gravity Forms features that were made available prior to v2.5. Once v2.5 was released, all new forms had legacy markup toggled off by default. The update modernized the code and provided better standardization and accessibility.
Note: Version 3.1 has not yet been released. Based on previous release cadences, it is speculated that this version will be rolled out in fall of 2026 (related source).
Impacted features/functions
The following are a few of the features and/or functions provided using legacy markup that will not be available in v3.1. Please visit the vendor’s markup update documentation for more information about these and other changes.
Custom CSS selectors
Custom CSS that targeted pre-2.5 markup will no longer work. Example: Targeting elements within <li> tags or using <table> tags for layout.
CSS ready classes
The custom classes provided by the vendor will be removed. These helped influence and control layout of form fields/elements.In some cases, these options are now available without using legacy markup. Visit the vendor documentation on this topic to learn about alternatives.
UW Theme 2.0 styling
UW Theme 2.0 will not accommodate CSS styling for legacy markup forms. When you transition to UW Theme 2.0, you will need to verify that legacy markup is turned off to provide the best display of content and align with UW branding.
Action: Reviewing existing forms
We encourage site administrators to start reviewing their forms now and toggle off legacy markup, where possible. This will ensure that your forms display using branded styles in UW Theme 2.0.
- Navigate to the Forms link on the left menu
- Hover over the form title and select Settings > Form Settings
- Scroll down to the Form Options section and look to see if the “Enable legacy markup” option is enabled
- If not enabled, that form should be ready for the future change.
- If enabled, check the form for possible markup features/functions that will be removed in the future and transition to alternatives. Then, toggle off the legacy markup option and re-publish the form.
- Repeat these steps for each form on your site.
Questions
If you have questions regarding this shift, please connect with the WiscWeb team via the Customer Support Form on the WiscWeb website. Our team is happy to work through any questions that you might have.