Release 2.23 #2058
Merged
Release 2.23 #2058
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
…r-field-value-configured-to-use-a-comma-as-a-decimal-separator
…in case of decimals
…t commas and dots
Adds a filter for the link text (anchor text) in notification emails so that the text can be customized depending on the form. For some use cases, e.g., ”confirm” or ”accept” might be a better text than ”approve”.
Due to Foundation being a private repository and GravityView public, this allows all users to install GravityView dependencies without access to the private Foundation repo.
To be replaced with Playwright
Allow modifying entry approval link url, text and other parameters
Adds a filter for the link text (anchor text) in notification emails so that the text can be customized depending on the form. For some use cases, e.g., ”confirm” or ”accept” might be a better text than ”approve”.
$parms['format'] is always defined
…get-when-searched-value-contains-two-words [ci skip]
This PR addresses #2034 where the export link widget would cause a fatal error when searching on multiple words. The problem is that the space between the words is transformed into `%20`. And because the link is added to the `printf` function directly it reads that `%` as a placeholder. Fixed it by adding the link via a `%s` placeholder as well.
This PR addresses #1892. Basically everything asked for in that issue is solved. But to reference the parent in the merge tags you need to use: `{Parent:<field>}` So `{Parent:1.2}` or `{Parent:entry_id}` or `{Parent:form_id}`. And to be able to connect in the view search field you need to search for the key `gpnf_entry_parent` or `gpnf_entry_parent_form`. 💾 [Build file](https://www.dropbox.com/scl/fi/jgdhs9mnmju6uxqaji8o5/gravityview-2.22-7f95583e8.zip?rlkey=svggtxibwx92eulbdzg045bgs&dl=1) (7f95583).
This applies to settings with the "full_width" property set to true. Previouslty, the GravityView_Render_Settings::render_setting_row() method did not render the setting's description for those fields unlike for the checkbox field.
Fix formating Fixes #1872 Also related to GravityEdit: GravityKit/GravityEdit#236 💾 [Build file](https://www.dropbox.com/scl/fi/2vdgaoqe704yc5lmvwvnt/gravityview-2.22-cb786ea90.zip?rlkey=wfkvsf51b3jn0ng4580ghe284&dl=1) (cb786ea).
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.
This update adds support for Nested Forms' entry meta, addresses several bugs, including critical ones, and improves GravityKit's Settings and Manage Your Kit screens.
🚀 Added
✨ Improved
🐛 Fixed
🔧 Updated
💻 Developer Updates
gk/gravityview/entry/approval-link/paramsfilter to modify entry approval link parameters.💾 Build file (6a235f9).