Update readme 6.15

[Crabcyborg]

No description provided.

[coderabbitai]

Warning

Rate limit exceeded

@Crabcyborg has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 19 minutes and 49 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Files that changed from the base of the PR and between 2d0c1f0 and a80bc24.

Walkthrough

The update from version 6.14.1 to 6.15 of the Formidable Forms plugin includes a redesign of the add-ons page, new email actions using shortcodes, and modifications to confirmation field validation. Additionally, various fixes were made to enhance JavaScript error handling, styling, and security measures against XSS vulnerabilities. The changes aim to improve user experience and streamline functionality across the platform.

Changes

File	Change Summary
src/FrmProAppHelper.php	- Method frm_after_generate_csv() added. - Method frm_show_entry() signature updated.
src/FrmFieldType.php	- Method frm_get_select_attributes() signature updated.
src/FrmField.php	- Method frm_field_value() signature updated.
changelog.txt, readme.txt	- Redesigned add-ons page with toggles and filtering. - New email actions introduced. - Confirmation field validation changes.

Possibly related PRs

• Start working on readme/changelog for v6.14 #1969: The changes in the main PR regarding the redesign of the add-ons page and improvements to form validation are related to the updates in the visual styler and form handling optimizations mentioned in this PR.

Suggested labels

run analysis, run tests

---

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>, please review it.
  • 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 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 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 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 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: 0

🧹 Outside diff range and nitpick comments (3)

readme.txt (3)

374-380: Changelog for version 6.15 looks good, but consider adding more details.

The changelog for version 6.15 provides a good overview of the new features and fixes. However, consider the following suggestions to improve clarity:

1. For the add-ons page redesign, it might be helpful to mention any benefits this brings to users (e.g., easier management of plugins).
2. Regarding the confirmation field validation change, it would be useful to explain why this change was made and how it improves user experience.
3. For the new email actions, consider providing an example of how to use the new shortcodes or linking to documentation.
4. The fixes are well-described, but it might be helpful to mention if these were reported issues by users.

Consider expanding on these points to provide more context and guidance for users updating to this version.

---

Line range hint 382-394: Security fix is crucial, but consider providing more guidance.

The changelog for version 6.14.1 includes a critical security fix for an XSS vulnerability. This is well-highlighted at the top of the changelog, which is good practice. However, consider the following suggestions:

1. Add a note encouraging users to update immediately due to the security fix.
2. Provide a link to a security advisory or documentation with more details about the vulnerability and its potential impact (without revealing exploitable information).
3. Consider adding a brief explanation of what XSS is for less technical users.

Adding this information can help users understand the importance of the update and take appropriate action.

---

Line range hint 1-373: README structure is comprehensive, but consider some updates.

The readme file provides a wealth of information about the Formidable Forms plugin, which is excellent. However, here are some suggestions for improvement:

1. Update the "Tested up to" WordPress version (currently 6.6.2) to the latest stable version if possible.
2. Consider adding a "Changelog" section header before the version changelogs for better organization.
3. The FAQ section is extensive, which is great. However, consider adding a table of contents at the beginning of the FAQ for easier navigation.
4. In the "Installation" section, consider adding a step for configuring the plugin after activation.
5. The "Screenshots" section mentions 6 screenshots, but no actual screenshot descriptions are provided. Consider adding these or removing the section if it's not needed.

These updates could improve the overall user experience when reading the plugin information and make it easier for users to find the information they need.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between b8af986 and 2d0c1f0.

📒 Files selected for processing (2)

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

🔇 Additional comments (6)

changelog.txt (6)

2-7: New redesign of add-ons page with improved functionality

The add-ons page has been redesigned with several improvements:

• Plugins can now be enabled/disabled using toggles instead of buttons
• A new category filter has been added for plugins
• These changes should improve user experience and make managing add-ons easier

---

4-5: Improved validation behavior for confirmation fields

Confirmation fields will no longer validate immediately when the main field loses focus. Instead, validation occurs only on form submit and when the confirmation field itself is changed. This change should reduce premature error messages and improve user experience.

---

5-6: New email shortcodes for default settings

New shortcodes [default-email] and [default-from-email] have been added for email actions. These use email settings defined during onboarding, with a fallback to the admin email. This improvement should make email configuration more flexible and easier to manage.

---

6-7: Fixed validation issues with confirmation fields

A bug has been fixed where confirmation fields would not validate with JavaScript when empty, allowing form submission with a blank confirmation when the main field had a value. This fix improves form validation and data integrity.

---

7-8: Fixed issue with backslashes in field format settings

A bug where backslashes in field format settings would get stripped in some cases has been resolved. This fix is particularly important for regex statements, which often use backslashes. It should prevent unexpected behavior in field formatting and validation.

---

1-3: Formidable Forms shows consistent improvement and active maintenance

The changelog demonstrates that Formidable Forms is actively developed and maintained. Regular updates include new features, improvements to existing functionality, and bug fixes. This ongoing development suggests a commitment to enhancing the plugin and addressing user needs, which is a positive indicator for current and potential users.