Prepare for 6.22.1

[Crabcyborg]

No description provided.

[coderabbitai]

Walkthrough

This update increments the plugin version from 6.22 to 6.22.1 across relevant files, updates changelog and readme documentation to include a fix for name fields with minimize=1, adjusts PHPDoc @since annotations to reflect the new version, and updates translation template metadata and entries.

Changes

Files/Paths	Change Summary
changelog.txt, readme.txt	Added 6.22.1 changelog entry for name field minimize=1 fix.
classes/controllers/FrmSettingsController.php	Updated PHPDoc @since annotations from x.x to 6.22.1 for private static members.
classes/helpers/FrmAppHelper.php, formidable.php	Updated plugin version from 6.22 to 6.22.1 in code and plugin header.
languages/formidable.pot	Updated POT version, creation date, line references, added/removed "Payments" translation entries, and updated metadata.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant Plugin
    Note over Plugin: On plugin update to 6.22.1
    Plugin->Plugin: Update internal version to 6.22.1
    Plugin->Plugin: Apply fix for name fields with minimize=1
    Plugin->Plugin: Update translation template metadata
    Plugin->User: Provide updated changelog and documentation

Loading

Possibly related PRs

• Strategy11/formidable-forms#2409: Updates changelog and readme for version 6.22.1 with the same fixes and documentation changes.
• Strategy11/formidable-forms#2219: Updates plugin version in FrmAppHelper.php for a prior version increment, involving similar version update procedures.
• Strategy11/formidable-forms#2391: Updates version metadata and @since annotations for a previous version, similar to changes in this PR.

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 PHPStan (2.1.15)

Note: Using configuration file /phpstan.neon.
Invalid configuration:
Unexpected item 'parameters › strictRules'.

---

📜 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 3a5a43e and c7ec4e3.

📒 Files selected for processing (6)

• changelog.txt (1 hunks)
• classes/controllers/FrmSettingsController.php (3 hunks)
• classes/helpers/FrmAppHelper.php (1 hunks)
• formidable.php (1 hunks)
• languages/formidable.pot (9 hunks)
• readme.txt (1 hunks)

⏰ 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). (15)

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

🔇 Additional comments (13)

classes/controllers/FrmSettingsController.php (3)

11-12: DocBlock version annotation looks correct
The @since 6.22.1 tag now reflects the patch release and keeps docs in sync with the codebase versioning.

---

191-192: Annotation update acknowledged
remove_payments_sections() now carries the correct version marker. No functional impact.

---

212-213: Annotation update acknowledged
payment_sections_sort_callback() PHPDoc is in sync with 6.22.1.

formidable.php (1)

5-5: Version constant alignment verified
The $plug_version constant in classes/helpers/FrmAppHelper.php (line 32) is correctly set to '6.22.1', matching the plugin header. No further updates are needed.

readme.txt (1)

375-381: Changelog entry added – LGTM
The new Payments-section note and minimize fix are clear and properly scoped under 6.22.1.

classes/helpers/FrmAppHelper.php (1)

32-32: Patch version bump acknowledged

The constant bump to 6.22.1 matches the PR objective and should correctly propagate via plugin_version() uses for cache-busting and update checks. No further action needed here.

changelog.txt (1)

2-9: Verify ancillary version bumps & docs sync

👍 The 6.22.1 section looks fine.
Double-check that:

1. FrmAppHelper::plugin_version (or equivalent) is already set to 6.22.1.
2. The header in formidable.php and readme.txt lists the same version/date.
3. The POT/translation meta was regenerated so translators see the new string.

Helps avoid mismatched version reports in WP admin and on wp.org.

languages/formidable.pot (6)

5-5: Version number update is consistent.

The version has been properly updated from 6.22 to 6.22.1 in the Project-Id-Version header.

---

12-12: POT creation date updated appropriately.

The POT-Creation-Date has been updated to reflect the new build timestamp, which is standard practice for translation template updates.

---

1245-1251: New payment-related translation entry added correctly.

A new "Payments" translation string has been added with proper source file references including:

• classes/controllers/FrmSettingsController.php:80
• Multiple Stripe-related files
• Payment list and helper files

The entry follows the correct POT format with msgid and msgstr "" structure.

---

1794-1796: Payment settings description added.

A new translation entry for payment settings page description has been added with the appropriate source file reference. This complements the payment functionality additions.

---

492-492: Line number references updated systematically.

Multiple source file line number references have been updated throughout the file. This is expected when code is added or modified in the source files. The updates appear systematic and maintain proper POT file structure.

Also applies to: 664-688

---

2696-2696: Consistent line number maintenance.

Additional line number updates in helper files and JavaScript error handling maintain consistency with the source code changes. All updates follow the proper #: filename:linenumber format.

Also applies to: 7719-7721

✨ 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.