Update readme for v6.21.1#2365
Conversation
|
Warning Rate limit exceeded@Crabcyborg has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 14 minutes and 43 seconds before requesting another review. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the 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. 📒 Files selected for processing (3)
""" WalkthroughVersion 6.21.1 introduces a new global spam setting for denylist-based spam validation, which is disabled by default. Detected spam keywords are now stored transiently and displayed for easier exception management. Denylist checks exclude radio buttons, checkboxes, dropdowns, signature, password, and CAPTCHA fields to reduce false positives, while still validating "Other" inputs. All spam checks are disabled during form imports. The honeypot field ID determination method was updated to avoid conflicts. Documentation and changelog were updated accordingly. Changes
Sequence Diagram(s)sequenceDiagram
participant Admin
participant SettingsUI
participant SpamValidator
participant Storage
Admin->>SettingsUI: Enable "Check denylist data to validate for spam"
SettingsUI->>SpamValidator: Update spam validation logic
SpamValidator->>Storage: Store detected spam keywords transiently
Storage->>SettingsUI: Display keywords under "Custom allowed words"
Note over SpamValidator: Exclude radio, checkbox, dropdown, signature, password, CAPTCHA fields from denylist checks
Admin->>SettingsUI: Import form
SettingsUI->>SpamValidator: Disable all spam checks during import
SpamValidator->>SettingsUI: Use updated honeypot field ID method to prevent conflicts
Possibly related PRs
Suggested labels
✨ Finishing Touches
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. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed 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)
Other keywords and placeholders
CodeRabbit Configuration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (5)
changelog.txt (5)
2-2: Maintain consistent blank line before version entry.Other version headings (e.g.
= 6.21 =) are preceded by a blank line for readability. Add a blank line before= 6.21.1 =to match the pattern.
3-3: Refine wording to avoid redundancy.The entry begins
* New: A new setting…which repeats “new.” Consider simplifying to:* New: Setting "Check denylist data to validate for spam" added to Global spam settings and disabled by default due to false positives.
4-4: Clarify use of WordPress transients.If readers are developers, specifying “stored in a WordPress transient” rather than just “a transient” will make the implementation detail clearer.
5-5: Ensure consistent listing of field types.For readability and consistency with other entries, use an Oxford comma in the list:
radio buttons, checkboxes, dropdowns, signature, and CAPTCHA fields
6-6: Add specificity to import behavior.Consider clarifying the context of “importing forms,” e.g., “during XML or CSV form imports,” so it’s clear which import mechanism is affected.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
changelog.txt(1 hunks)readme.txt(2 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (6)
- GitHub Check: PHP 7.4 tests in WP trunk
- GitHub Check: PHP 8 tests in WP trunk
- GitHub Check: Cypress
- GitHub Check: Cypress
- GitHub Check: PHP 8 tests in WP trunk
- GitHub Check: PHP 7.4 tests in WP trunk
🔇 Additional comments (2)
readme.txt (2)
8-8: Stable tag bumped to 6.21.1
TheStable taghas been correctly updated to6.21.1for this release. Please verify that the plugin’s main PHP header (Version:field) matches this value and that the corresponding SVN tag (tags/6.21.1) has been created on WordPress.org.
375-379: Changelog entries for v6.21.1 are in place
The new version header= 6.21.1 =and bullet points succinctly document the denylist‐based spam enhancements. Ensure these descriptions mirror those inchangelog.txtand maintain consistency in grammar and punctuation with existing entries.
1 participant
No description provided.