Prepare for 6.22.2

[Crabcyborg]

No description provided.

[coderabbitai]

Walkthrough

This update increments the plugin version from 6.22.1 to 6.22.2 across metadata, code, and documentation files. It adds a changelog entry describing a fix for a fatal error related to incorrect cached data types. Additionally, a test assertion was updated to include a new valid tip info message on the entries page. No functional code changes are included.

Changes

Files/Paths	Change Summary
changelog.txt, readme.txt	Added changelog entry for 6.22.2 noting a fix for a fatal error; updated stable tag version.
classes/helpers/FrmAppHelper.php, formidable.php	Updated plugin version from '6.22.1' to '6.22.2'.
languages/formidable.pot	Updated Project-Id-Version and POT-Creation-Date metadata to reflect version 6.22.2.
tests/cypress/e2e/Entries/EntriesPageDataValidations.cy.js	Added a new expected tip info message to test assertions on entries page.

Possibly related PRs

• Strategy11/formidable-forms#1939: Updates the plugin version number in the FrmAppHelper class and related files without changing functionality.
• Strategy11/formidable-forms#2349: Modifies expected tip info and tip CTA messages in the same test file, related to tip message validation.
• Strategy11/formidable-forms#1917: Introduces the entries page validation test file that this PR modifies by adding an additional expected tip info message.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 20fe172 and dacd695.

📒 Files selected for processing (1)

• tests/cypress/e2e/Entries/EntriesPageDataValidations.cy.js (1 hunks)

✅ Files skipped from review due to trivial changes (1)

• tests/cypress/e2e/Entries/EntriesPageDataValidations.cy.js

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (9)

• GitHub Check: Psalm
• GitHub Check: Cypress
• GitHub Check: Run PHP Syntax inspection (8.3)
• GitHub Check: Run PHP Syntax inspection (7)
• GitHub Check: PHP 8 tests in WP trunk
• GitHub Check: Run PHPCS inspection
• GitHub Check: Run ESLint
• GitHub Check: PHP 7.4 tests in WP trunk
• GitHub Check: PHPStan

✨ Finishing Touches

• 📝 Generate Docstrings

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 2

🧹 Nitpick comments (3)

changelog.txt (1)

2-3: Consider replacing “would occur” with “could occur” for a crisper, more typical changelog tone.

Most entries already use “would”, so feel free to keep it for consistency—but if you aim for succinctness, “could occur” reads cleaner.

readme.txt (1)

375-377: Nit: tighten wording & remove extra spacing flagged by linter

LanguageTool reports a double-space before the next version header and the sentence can be clearer.

-= 6.22.2 =
-* Fix: A fatal error on some websites would occur because of an issue with incorrect cached data types.
+ = 6.22.2 =
+* Fix: Fixed a fatal error on some websites caused by incorrect cached data types.

languages/formidable.pot (1)

5-12: *Consider marking .pot as generated to keep PR noise down

Only two header lines change, yet the full 7 k-line file appears in the diff.
Adding an entry like the following to .gitattributes keeps future PRs cleaner:

# treat POT as generated-binary to suppress huge diffs
languages/*.pot linguist-generated

Or commit via git add -p to stage only the header hunk.
Purely optional, but it makes code-review easier.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f1077e7 and 20fe172.

📒 Files selected for processing (5)

• changelog.txt (1 hunks)
• classes/helpers/FrmAppHelper.php (1 hunks)
• formidable.php (1 hunks)
• languages/formidable.pot (1 hunks)
• readme.txt (2 hunks)

🧰 Additional context used

🪛 LanguageTool

readme.txt

[grammar] ~376-~376: Use correct spacing
Context: ... of an issue with incorrect cached data types. = 6.22.1 = * New: Stripe, Square, PayPa...

(QB_NEW_EN_OTHER_ERROR_IDS_5)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (3)

• GitHub Check: Cypress
• GitHub Check: Cypress
• GitHub Check: Cypress

🔇 Additional comments (3)

formidable.php (1)

5-5: Version bump looks good
Header correctly reflects 6.22.2.

readme.txt (1)

8-8: All version strings have been updated to 6.22.2

Confirmed occurrences in the codebase:
• README (readme.txt lines 8 and 375)
• Changelog (changelog.txt line 2)
• Plugin header (formidable.php line 5)
• FrmAppHelper (classes/helpers/FrmAppHelper.php line 32)
• POT file header (languages/formidable.pot line 5)

languages/formidable.pot (1)

5-5: Header bump looks good

Project-Id-Version and POT-Creation-Date are correctly updated to 6.22.2 / current timestamp.
Nothing else is touched, so translators won’t be forced to re-fuzzy every string. 👍

Also applies to: 12-12