Add changelog for v6.11.1

[Crabcyborg]

No description provided.

[coderabbitai]

Walkthrough

Version 6.11.1 of the Formidable plugin includes accessibility improvements to screen reader text, enhanced hover styling for modal close icons, and a fix for missing reCaptcha settings name. It also bumps the minimum supported version of Formidable Pro to 6.0 and deprecates the FrmAddonsController::is_license_expiring function.

Changes

Files/Paths	Change Summary
changelog.txt, readme.txt	Updated summaries to reflect the changes in version 6.11.1, including improvements and deprecations.
src/controllers/FrmAddonsController.php	Deprecated the function FrmAddonsController::is_license_expiring.
Various files	Updates to screen reader text for accessibility.
Various files	Enhanced hover styling for modal close icons.
reCaptcha settings files	Fixed the missing reCaptcha settings name.

---

Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 8b80860 and 2fef3af.

Files selected for processing (2)

• changelog.txt (1 hunks)
• readme.txt (1 hunks)

Additional comments not posted (1)

readme.txt (1)

374-380: Update Changelog Entry: Version 6.11.1

The changelog entry for version 6.11.1 includes several updates and fixes:

• Accessibility Improvement: Screen reader text updates.
• UI Improvement: Hover styling for modal close icons.
• Critical Fix: reCaptcha settings name correction.
• Version Bump: Minimum supported version of Formidable Pro increased to 6.0.
• Deprecation Notice: The function FrmAddonsController::is_license_expiring is deprecated.

These updates are well-documented and provide clear information on the changes made.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
  • Generate unit testing code for this file.
  • 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 generate unit testing code for this file.
  • @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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @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.

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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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: 0

Outside diff range and nitpick comments (5)

changelog.txt (5)

3-3: Clarify the scope of the update.

The description "Screen reader text has been updated on some admin pages" could be more specific. Consider specifying which admin pages were updated for better clarity.

- * New: Screen reader text has been updated on some admin pages to improve accessibility.
+ * New: Screen reader text has been updated on admin pages such as [specific pages] to improve accessibility.

---

4-4: Clarify the scope of the update.

The description "Hover styling has been updated for modal close icons" could be more specific. Consider specifying which modals were updated for better clarity.

- * New: Hover styling has been updated for modal close icons to improve user experience.
+ * New: Hover styling has been updated for modal close icons in [specific modals] to improve user experience.

---

5-5: Specify the affected area.

The description "The reCaptcha settings name was missing in a global settings string" could be more specific. Mention where this issue was fixed.

- * Fix: The reCaptcha settings name was missing in a global settings string.
+ * Fix: The reCaptcha settings name was missing in a global settings string on the [specific settings page].

---

6-6: Clarify the reason for the update.

The description "The minimum supported version of Formidable Pro has been bumped to version 6.0" should include the reason for this change.

- * The minimum supported version of Formidable Pro has been bumped to version 6.0.
+ * The minimum supported version of Formidable Pro has been bumped to version 6.0 to ensure compatibility with the latest features.

---

7-7: Clarify the implication of the deprecation.

The description "The function FrmAddonsController::is_license_expiring has been deprecated" should include what users should do as a result of this deprecation.

- * The function FrmAddonsController::is_license_expiring has been deprecated.
+ * The function FrmAddonsController::is_license_expiring has been deprecated. Users should update their code to use [new function] instead.