Version 1.22 #919
Merged
Version 1.22 #919
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
Green build contingent on latests master + gravityforms/gravityforms#96
Make sure that \GravityView_Cache::delete clears the object cache as well, otherwise a call to \GravityView_Cache::get will grab the result from it even once we've deleted it via the database. Delete it via the API to make sure the object cache does not serve us with stale data. Tests included.
Forms that make up a cache key will now be invalidated regardless of their position in the key. If a key contains a form that has been invalidated - the cache will be cleared. Tests included.
Some fields will have empty values when not set, for example the product field. An array of empty values would need to be detected as empty here.
Wrong variable name, eek
The tests will fail, because of some fixes (like escaping issues) between 2.1 and 2.2
2.2.1.14 introduced a remote call during the upgrade/install process. Meh it out.
Change detail table to meta table, lead to entry. Remove deprecated cache bust method call.
lead_meta -> entry_meta lead_notes -> entry_notes
This will help styling single entry pages, as well as fix issues with the Inline Edit and Featured Entries plugins. Fixes GravityKit/GravityEdit#81 Closes #885 Fixes #741
- Always use the license when defined in `GRAVITYVIEW_LICENSE_KEY ` - When defined, set the input type to "password" instead of "text" - Disable updating the license key setting when it's defined in the code - And if `$field['disabled']` is false, unset the key so Gravity Forms knows what to do with it. Fixes #917
The plugin compat is loaded very early and tries to detect functions, classes to compat with when they haven't even been loaded yet. Offload the checks to after all plugins and themes have been loaded.
Divi and other Elegant Themes products try to load the widgets in an admin context when editing a post with a sidebar block in it. Prevent the sidebar block to be rendered. Attempts to fix #914
Only supported in PHP 5.5 and above.
# Conflicts: # readme.txt
|
Changes Unknown when pulling 235e9c4 on develop into ** on master**. |
I'm not thrilled with the consistency of our template CSS selectors, but we definitely shouldn't break stuff! Reviewed for backward compatibility with our CSS Guide, updated accordingly.
|
Changes Unknown when pulling 740101a on develop into ** on master**. |
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.
┆Issue is synchronized with this Asana task