Security fix: server-side validation is now enforced for REST API \/ block editor publishing, closing a gap where required fields could be bypassed.<\/p>","1.4.6":"
Documentation fix: Classic Editor support was always present but incorrectly described as Gutenberg-only. No functional changes.<\/p>","1.4.3":"
Fix: scheduled posts now validated, Gutenberg empty-content check improved, warning banner visible above all modals.<\/p>","1.4.2":"
Important fixes: publish blocking now uses the official lockPostSaving API, server-side category validation added, and documentation corrected.<\/p>","1.3.0":"
Major rewrite: Gutenberg validation now uses React hooks (registerPlugin). Fixes subscribe loops and false publish errors. Classic editor validation simplified.<\/p>","1.1.1":"
Critical fix: Gutenberg validation now works correctly for pages and when updating published posts. WPCS compliant. Tested with WordPress 6.9.<\/p>","1.0.8":"
Important update: All users (including admins) now require validation. Improved translation support for multilingual sites.<\/p>","1.0.7":"
Recommended update for better WordPress.org compliance and security improvements.<\/p>"},"ratings":[],"assets_icons":[],"assets_banners":[],"assets_blueprints":{},"all_blocks":[],"tagged_versions":["1.4.7"],"block_files":[],"assets_screenshots":[],"screenshots":{"1":"Warning banner showing missing required fields in Gutenberg editor","2":"Disabled Publish button when required fields are missing","3":"Validation error message in Classic Editor","4":"All required fields completed - ready to publish"}},"plugin_section":[],"plugin_tags":[89,1795,166,266794,1460],"plugin_category":[50],"plugin_contributors":[241557],"plugin_business_model":[],"class_list":["post-334285","plugin","type-plugin","status-publish","hentry","plugin_tags-category","plugin_tags-featured-image","plugin_tags-posts","plugin_tags-required-fields","plugin_tags-title","plugin_category-media","plugin_contributors-domclic","plugin_committers-domclic"],"banners":[],"icons":{"svg":false,"icon":"https:\/\/s.w.org\/plugins\/geopattern-icon\/effortless-required-fields-validator.svg","icon_2x":false,"generated":true},"screenshots":[],"raw_content":"\n
Effortless Required Fields Validator<\/strong> ensures content quality by requiring all users to complete essential fields before publishing posts. It works with both the block editor (Gutenberg) and the Classic Editor.<\/p>\n\n In the block editor (Gutenberg):<\/strong><\/p>\n\n In the Classic Editor:<\/strong><\/p>\n\n Server-side validation runs for both editors, so the check cannot be bypassed.<\/p>\n\n Currently, the plugin doesn't provide filters for customization, but this may be added in future versions based on community feedback.<\/p>\n\n To translate this plugin:<\/p>\n\n For support, please use the WordPress.org support forums or visit the plugin's GitHub repository (if available).<\/p>\n\n This plugin does not collect, store, or transmit any user data. It only validates post fields in the WordPress editor.<\/p>\n\n Developed by domclic with \u2764\ufe0f for the WordPress community.<\/p>\n\n\n The plugin works immediately after activation. No configuration needed!<\/p>\n\n Simply try to publish a post without filling all required fields, and you'll see the validation in action.<\/p>\n\n\n Yes! The plugin includes validation for both Gutenberg and the Classic Editor.<\/p><\/dd>\n Currently, the plugin requires Title, Content, Featured Image, and Category (for posts). Customization options may be added in future versions based on user feedback.<\/p><\/dd>\n Currently, the plugin only validates the 'post' post type. Support for pages and custom post types may be added in future versions.<\/p><\/dd>\n No. As of version 1.0.8, all users (including administrators) must complete all required fields before publishing. This ensures consistent content quality across your entire site.<\/p><\/dd>\n No. The validation only applies when publishing new posts or updating existing ones. Your existing published posts remain unaffected.<\/p><\/dd>\n Yes! The plugin is fully compatible with the Gutenberg block editor and all standard blocks.<\/p><\/dd>\n In Gutenberg, the Publish button will be disabled and a warning banner will show which fields are missing. In the Classic Editor, you'll see an error message with a link to return to editing.<\/p><\/dd>\n Yes! The plugin is fully translatable and includes French translation. You can add your own translations using the provided .pot file.<\/p><\/dd>\n No. The plugin only loads its assets on post edit screens and has minimal performance impact.<\/p><\/dd>\n\n<\/dl>\n\n\nRequired Fields<\/h4>\n\n
\n
Features<\/h4>\n\n
\n
How It Works<\/h4>\n\n
\n
\n
Use Cases<\/h4>\n\n
\n
Translations<\/h4>\n\n
\n
Developer Notes<\/h3>\n\n
Filters Available<\/h4>\n\n
Translation<\/h4>\n\n
\n
.pot<\/code> file in the \/languages<\/code> folder<\/li>\nSupport<\/h4>\n\n
Privacy Policy<\/h3>\n\n
Credits<\/h3>\n\n
Automatic Installation<\/h4>\n\n
\n
Manual Installation<\/h4>\n\n
\n
After Activation<\/h4>\n\n
\n
Does this work with the Classic Editor?<\/h3><\/dt>\n
Can I customize which fields are required?<\/h3><\/dt>\n
Does it work for custom post types?<\/h3><\/dt>\n
Can admins bypass the validation?<\/h3><\/dt>\n
Will this affect my existing posts?<\/h3><\/dt>\n
Does it work with Gutenberg blocks?<\/h3><\/dt>\n
What happens if I try to publish without required fields?<\/h3><\/dt>\n
Is it translation ready?<\/h3><\/dt>\n
Does it impact site performance?<\/h3><\/dt>\n
1.4.7<\/h4>\n\n
\n
rest_pre_insert_post<\/code> validation that enforces the same required fields for REST-submitted posts.<\/li>\n$_POST<\/code> data, which could incorrectly block programmatic post publishing (WP-CLI, cron, imports, other plugins) that doesn't submit the classic editor's form fields. The check is now scoped to genuine classic-editor form submissions, with a safe fallback for programmatic saves of existing posts.<\/li>\n<\/ul>\n\n1.4.6<\/h4>\n\n
\n
1.4.5<\/h4>\n\n
\n
1.4.4<\/h4>\n\n
\n
1.4.3<\/h4>\n\n
\n
future<\/code> was not being caught<\/li>\nmax-width: 90vw<\/code> and centered text for narrow viewports<\/li>\nerfv-missing-fields<\/code> body class no longer toggled in JS<\/li>\nwp-edit-post<\/code> script dependency<\/li>\nPost\/page<\/code> copy corrected to Post<\/code> throughout<\/li>\n1.4.2<\/h4>\n\n
\n
lockPostSaving<\/code>\/unlockPostSaving<\/code> API \u2014 replaces CSS-only approach that could be bypassed<\/li>\nERFV_VERSION<\/code> constant \u2014 replaces hardcoded version strings in asset enqueue calls<\/li>\n1.3.0<\/h4>\n\n
\n
registerPlugin<\/code> with React hooks (useSelect<\/code>, useEffect<\/code>) \u2014 eliminates subscribe loop<\/li>\n$_POST['_thumbnail_id']<\/code><\/li>\nwp_die()<\/code> output sanitized with wp_kses()<\/code>, back link uses wp_get_referer()<\/code><\/li>\nRequires at least<\/code> and Requires PHP<\/code> headers in main plugin file<\/li>\n1.1.1<\/h4>\n\n
\n
rest_pre_insert_page<\/code> filter)<\/li>\n1.0.8<\/h4>\n\n
\n
1.0.7<\/h4>\n\n
\n
1.0.6<\/h4>\n\n
\n
1.0.5<\/h4>\n\n
\n
1.0.4<\/h4>\n\n
\n
1.0.0<\/h4>\n\n
\n