gw-cache-buster.php: Fixed an issue with Cache Buster and Expired Forms.
#1007
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
⛑️ Ticket(s): https://secure.helpscout.net/conversation/2827184964/77017
Summary
When using Cache Buster with a form that has a schedule, if the form is expired, the following PHP warning is being thrown, and the form expiration message does not show:
PHP Warning: Undefined array key "page_number" in ...\plugins\gravityforms\form_display.php on line 727As Gravity Forms does it here to check for form expiration, we have added the logic on the required spot at Cache Buster. Since, an expired form won't have a page number set.
Post Update:
