Update readme for v6.16.3#2176
Conversation
WalkthroughThe pull request updates the Formidable Forms plugin to version 6.16.3, introducing new features such as duplicate entry validation for iOS form resubmissions, updated timestamp formatting in the sidebar, and a new database index for performance improvements. It also includes several fixes related to input validation, error handling, and compatibility with WordPress 6.7+. Additionally, deprecated elements and settings have been removed or relocated to streamline the plugin's functionality and reduce file size. Changes
Possibly related PRs
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? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
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
🧹 Outside diff range and nitpick comments (4)
readme.txt (3)
374-377: Important security improvement for duplicate entry validationThe extended duplicate entry validation window (from 60s to 1 month) helps prevent duplicate form submissions on iOS devices, significantly improving form reliability and data integrity.
Consider adding a configurable timeframe setting to allow admins to customize the duplicate entry window based on their needs.
378-379: Database performance optimizationThe addition of a new database index for entry count queries is a significant performance improvement that should speed up entry listing and reporting features.
Consider adding documentation about the new index for users upgrading from older versions who may need to manually add it if the upgrade process fails.
🧰 Tools
🪛 LanguageTool
[misspelling] ~378-~378: This word is normally spelled as one.
Context: ... a proper aria-invalid value, and error auto-focusing wouldn't work as expected for name fiel...(EN_COMPOUNDS_AUTO_FOCUSING)
385-389: Code cleanup and deprecation improvementsGood cleanup of legacy code and assets:
- Removed old form button settings section
- Removed deprecated CSS
- Deprecated global JS functions
- Removed unused asset file (s11-fp.svg)
This helps reduce the plugin's footprint and maintenance burden.
Consider adding migration code to handle any custom code that may have been relying on the removed functionality.
🧰 Tools
🪛 LanguageTool
[style] ~385-~385: Consider removing “of” to be more concise
Context: ...orm button settings has been removed as all of the settings had been moved. * Some old dep...(ALL_OF_THE)
changelog.txt (1)
13-16: Cleanup and deprecation updatesA few cleanup items:
- Removed form button settings section (settings have been relocated)
- Removed deprecated CSS to reduce frontend file size
- Deprecated global JS functions frmFrontForm.invisible and frmFrontForm.visible
- Removed s11-fp.svg asset file to reduce plugin size
Consider documenting where the form button settings were relocated to help users find them in the new location.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (2)
changelog.txt(1 hunks)readme.txt(2 hunks)
🧰 Additional context used
🪛 LanguageTool
readme.txt
[misspelling] ~378-~378: This word is normally spelled as one.
Context: ... a proper aria-invalid value, and error auto-focusing wouldn't work as expected for name fiel...
(EN_COMPOUNDS_AUTO_FOCUSING)
[grammar] ~384-~384: Did you mean “I”?
Context: ...nberg Form blocks were disabled. * Fix: A cannot access offset of type string on ...
(A_MD_VB)
[style] ~385-~385: Consider removing “of” to be more concise
Context: ...orm button settings has been removed as all of the settings had been moved. * Some old dep...
(ALL_OF_THE)
🔇 Additional comments (3)
readme.txt (1)
377-378: Improved timestamp formatting consistency
The timestamp display now properly respects WordPress format settings, providing better consistency across the application.
🧰 Tools
🪛 LanguageTool
[misspelling] ~378-~378: This word is normally spelled as one.
Context: ... a proper aria-invalid value, and error auto-focusing wouldn't work as expected for name fiel...
(EN_COMPOUNDS_AUTO_FOCUSING)
changelog.txt (2)
2-4: Notable performance and validation improvements in v6.16.3
The latest version includes important changes:
- Extended duplicate entry validation from 60 seconds to 1 month for iOS form resubmissions, which helps prevent duplicate submissions
- Added database index to form entries table to optimize entry count queries
- Updated timestamp display in sidebar to use WordPress format settings
6-12: Several bug fixes and validation improvements
Multiple fixes have been implemented:
- Fixed aria-invalid value and error auto-focusing for name fields
- Fixed fatal error related to unsupported operand types
- Fixed translation loading hook for WP 6.7+ compatibility
- Fixed deprecated strpos() message
- Added validation for non-existent payments/subscriptions
- Fixed form titles/descriptions visibility in Gutenberg blocks
1 participant
No description provided.