How to Change the Gravity Forms License on a Site

How to Change the Gravity Forms License on a Site

SummaryPre-RequisitesUpdating the KeyNotes

Summary

There is a chance you may need to replace the Gravity Forms license key in use on one of your websites with a different Gravity Forms license key.

For example, your license may have expired and you have purchased a new one, or you can no longer contact the developer who originally set-up your website and you want to replace their Gravity Forms license key with one you can control and manage yourself.

Pre-Requisites

Administrator access to a WordPress website that has an existing Gravity Forms license key installed and registered on it.A new Gravity Forms license key. See this article for information on how to find your key within your Gravity Forms account. You can purchase from the Gravity Forms pricing page.

Updating the Key

It really is as easy as pasting the new key over the hold one (though note that the old one is a hidden field, and represented only by asterisks).

Simply:

Navigate to Forms > Settings.Under General Settings, paste your new license key into the Support License Key field.Click the Save Settings button at the bottom of the page.A green check mark should be displayed next to the field if your license key has been successfully activated.

Image: A successfully validated Gravity Forms license key

Notes

Make sure the new license key has the same capabilities as the installed license you are replacing (or exceeds them). Otherwise you may lose access to needed add-on updates, have an insufficient site allowance, or lose your Priority Support status. See this article for a summary of license types and their benefits.Changing your license key does not disrupt any of your form functionality, and will not cause the loss of any existing form data. You can make this change without disruption. If your key does not validate, check this table for a list of possible validation errors you may encounter.

Gravity Forms 2.2: Changes to Entry IP Detection

Gravity Forms 2.2: Changes to Entry IP Detection

With the release of Gravity Forms version 2.2, changes have been made to the IP displayed when a form entry is generated.
Previously, Gravity Forms would check for the X-Forwarded-For header, and use that IP. This would allow for proxied connections such as Cloudflare to report the user』s IP, instead of showing the IP of the server making the request (such as Cloudflare).
To more accurately report IP addresses, this functionality has been removed. Entries will now show the IP address of the server physically making the request.
Of course, this can cause issues for some sites that are behind a reverse proxy. To solve this problem, we』ve placed a hook that will allow the the X-Forwarded-For header to be used. It can be found at the following:
gform_ip_address filter

Changes to Stripe Checkout with Stripe Add-On v3.0

Changes to Stripe Checkout with Stripe Add-On v3.0

IntroductionBest PracticesChanges to the Stripe Checkout processRemoval of the Modal WindowCheckout StylingChanges to FiltersRemoved FiltersModified FiltersScreenshots

Introduction
Version 3 of the official Gravity Forms Stripe Add-On made a number of changes to bring our add-on into line with Stripe』s updates around Strong Customer Authentication and their new API. Please review this document carefully, as your existing flow using Stripe Checkout or Stripe filters may have been affected.
Best Practices
The payment gateway add-on is a vital cog in any website, and as such you should never run updates without testing in a sandbox first. We always recommend that you:
– make a complete backup that can be used as a restore point
– switch to sandbox payment environment, and test the update first
– once satisfied, don』t forget to switch back to your production environment before you start collecting live payments.
Be cautious. Be prepared.
Changes to the Stripe Checkout process
Removal of the Modal Window
If you use the Stripe Checkout method, then Stripe Add-On 3.0 will modify your payment flow. With their recent API updates, Stripe have replaced the modal window with a full page display for the final portion of the checkout process. See screenshots at bottom for examples.
Checkout Styling
All styling options for this new window now take place in Stripe under your Branding section. All styling options that previously existed within the Stripe Add-On Feed Settings area have been removed in version 3.
Changes to Filters
We have added some new filters with this update (see the Change Log), but also removed and modified some existing hooks to orient with Stripe』s API updates.
Removed Filters

gform_stripe_currency (added in 2.7)
gform_stripe_checkout_options (added in 2.6)
gform_stripe_checkout_supported_cards

Modified Filters

gform_stripe_charge_pre_create no longer works with Stripe Checkout. Use gform_stripe_session_data to replace it.

Screenshots
Screenshot A: Deprecated Stripe Checkout Modal Window

Screenshot B: New Stripe Checkout Page

Screenshot C: New Stripe Checkout Page, with billing address

Changes to markup in Gravity Forms 2.5

Changes to markup in Gravity Forms 2.5

IntroductionMarkup Changes in 2.5Sample

Introduction

Gravity Forms 2.5 introduced significant updates to the markup used. Changes were made to modernize and improve the markup for better standardization and accessibility, as well as simplifying the styles used. These can create breaking changes on existing forms. Note that all existing forms will default to Enable Legacy Markup on, meaning that the new markup changes listed here will not be in effect for those forms. If you do choose to turn that off and use the new markup, review and test first!

To test your existing forms and their presentation under the new markup (if needed), we suggest you install 2.5 on one of your sandboxes, turn off legacy markup on your existing forms, and start checking under all your normal user conditions. There is no substitute for grunt-work QA in this scenario.

Markup Changes in 2.5

This list is a good starting point for changes that have been made. It may not be exhaustive, with possible changes as we progress through the Beta releases.

All fields are now wrapped with either a

or a

. We no longer wrap fields in

  • .All multi-input fields (such as Address, Name, Checkboxes, etc) are now wrapped in a
    (previously were

    ) for improved accessibility.Field labels inside a

    use

    (previously were