Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Version 2.19.6 #1984

Merged
merged 59 commits into from
Feb 8, 2024
Merged

Version 2.19.6 #1984

merged 59 commits into from
Feb 8, 2024

Conversation

zackkatz
Copy link
Member

@zackkatz zackkatz commented Feb 8, 2024

= 2.19.6 on February 7, 2024 =

This update introduces the ability to send notifications using Gravity Forms when an entry is deleted, improves sorting and survey field ratings, and updates key components for better performance and compatibility.

🚀 Added

  • Ability to send notifications using Gravity Forms when an entry is deleted by selecting the "GravityView - Entry is deleted" event from the event dropdown in Gravity Forms notifications settings.

🔧 Updated

  • Foundation and TrustedLogin to versions 1.2.8 and 1.7.0, respectively.
    • Transients are now set and retrieved correctly when using object cache plugins.
    • Fixed a JavaScript warning that occurred when deactivating license keys and when viewing products without the necessary permissions.
    • Resolved PHP warning messages on the Plugins page.

🐛 Fixed

  • Sorting the View by entry ID in ascending and descending order would yield the same result.
  • Survey fields without a rating would show a 1-star rating.
  • Editing Gravity Forms Custom Post Fields with a Field Type set to "File Uploads" inside in Edit Entry.

Developer Updates:

  • Added: GravityView_Notifications class as a wrapper for Gravity Forms notifications.
  • Modified: Added the current \GV\View object as a second parameter for the gravityview/search-all-split-words and gravityview/search-trim-input filters.
  • Modified: Attach listeners in the View editor to $( document.body ) instead of $('body') for speed improvements.

dependabot bot and others added 30 commits July 8, 2023 00:16
Bumps [tough-cookie](https://github.com/salesforce/tough-cookie) from 4.1.2 to 4.1.3.
- [Release notes](https://github.com/salesforce/tough-cookie/releases)
- [Changelog](https://github.com/salesforce/tough-cookie/blob/master/CHANGELOG.md)
- [Commits](salesforce/tough-cookie@v4.1.2...v4.1.3)

---
updated-dependencies:
- dependency-name: tough-cookie
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [word-wrap](https://github.com/jonschlinkert/word-wrap) from 1.2.3 to 1.2.4.
- [Release notes](https://github.com/jonschlinkert/word-wrap/releases)
- [Commits](jonschlinkert/word-wrap@1.2.3...1.2.4)

---
updated-dependencies:
- dependency-name: word-wrap
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
See https://stackoverflow.com/a/49449955/480856

I confirmed that `$( 'body' )` listeners will still work when triggers are sent to `$( document.body )`, so this is back-compatible.
Bumps [postcss](https://github.com/postcss/postcss) from 8.4.5 to 8.4.31.
- [Release notes](https://github.com/postcss/postcss/releases)
- [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md)
- [Commits](postcss/postcss@8.4.5...8.4.31)

---
updated-dependencies:
- dependency-name: postcss
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [postcss](https://github.com/postcss/postcss) from 8.4.21 to 8.4.32.
- [Release notes](https://github.com/postcss/postcss/releases)
- [Changelog](https://github.com/postcss/postcss/blob/main/CHANGELOG.md)
- [Commits](postcss/postcss@8.4.21...8.4.32)

---
updated-dependencies:
- dependency-name: postcss
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Bumps [@babel/traverse](https://github.com/babel/babel/tree/HEAD/packages/babel-traverse) from 7.20.12 to 7.23.6.
- [Release notes](https://github.com/babel/babel/releases)
- [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md)
- [Commits](https://github.com/babel/babel/commits/v7.23.6/packages/babel-traverse)

---
updated-dependencies:
- dependency-name: "@babel/traverse"
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
…1959)

This fixes #1938.

If sorting only by ID, both primary and secondary field sort directions
need to be the same.
First, handle comments that have punctuation marks:

```
@(filter|action) `(.*)` (.*?)([!?])(\n\s+\*)
```

Replace with:
```
$3$4$5
```

Then handle comments that do or don't end with periods:

```
@(filter|action) `(.*)` (.*?)([.]?)(\n\s+\*)
```

Replace with:
```
$3.$5
```
mrcasual and others added 29 commits January 10, 2024 20:07
This PR Closes #1906. 

There was no strict checking, so `false` was evaluated as `0` (`+ 1 =
1`).
I wasn't able to install using `npm i` because the node-sass package failed at

```
npm WARN deprecated [email protected]: This SVGO version is no longer supported. Upgrade to v2.x.x.
```
I fixed all (most?) issues that could be resolved automatically.
Bringing the entire codebase to 100% compliance will take quite an
effort, but it can be done incrementally as we commit changes.

To prevent `phpcs` from running during the pre-commit stage, use the
`--no-verify` flag with the `git commit` command.

Make sure to run `npm i && composer install`.
This PR closes #1819 

I moved the notification logic to a separate service class. To avoid
issues when people switch mode from `delete` to `trash` the hook listens
to both.

Added unit tests to confirm inner workings.

Todo: 

- [x] Trigger event on a removal of entry in gravity forms

@zackkatz Should that be a separate event? It feels kind of weird
triggering the `GravityView - Entry is deleted` event when you delete an
entry in Gravity Forms.
…1971)

This PR Closes #1317 

The type checking for upload fields excluded custom fields by default by
not using `get_input_type()`. That already provides the right type for
the custom post fields.

And because files are not provides by an input field during updating a
different field, I skip the `get_value_save_entry()` method, as it has
no value, and removes the image completely.
@zackkatz zackkatz merged commit 12dfdfe into main Feb 8, 2024
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants