Simplify Your Editing Life
Requires your various post types — as specified in a simple options page — to have a featured image set before they can be published. If a lack of featured images causes your layout to break, or just look less-than-optimal, this is the plugin for you.
Rather than forcing you to manually enforce your editorial standards of including a featured image in every post, if your contributors fail to add a featured image to a post before publishing it they’ll simply find it impossible to publish.
Setting up the Plugin
By default it works on the “Post” content type only, but you can specify other content types, or turn it off for Posts in the new options page in your left sidebar: Settings > Req Featured Image. Simply check and uncheck the appropriate types, set a minimum image size if you desire, hit save and you’re all set. Happy publishing!
Don’t forget to check out the plugins page on our website, and don’t hesitate to browse and fork on GitHub. Have a unique WordPress project you need help on? Get in touch with Press Up to set yourself up for success.
Imagens de tela
Activate the plugin. No other steps are necessary to require featured images on Posts only.
If you want to require featured images on a different content type, or allow Posts to be published without them simply go to the settings page in your left sidebar: Settings > Req Featured Image. Check and uncheck the appropriate types, set a minimum image size if you desire, hit “Save”, and you’re all set. Happy publishing!
- What post (content) types does this plugin work for?
Every “custom post type” — or variety of content — is now supported. Before 0.5.0, this plugin could only be used to force people include featured images on Posts, not Pages or any custom post type. Now all of them are a simple few clicks on the options page away.
- How does it prevent people from publishing a post without featured images?
- I’m not seeing one of my content types on the settings page. Why?
To simplify the settings page, and avoid confusion, only content types that support Featured Images will appear on the page. It wouldn’t make sense for us to try to enforce that a content type that can’t have a featured image set can’t be published without it. If you want to require that a content type has a featured image but it doesn’t currently support it, get in touch with your developer, fiddle with the
register_post_type()call creating the content type yourself, or get in touch with us at Press Up, we love to help!
- Why would I use this plugin?
Because you want it to be required that your posts have featured images before they be published. If you’d like that your posts have featured images, but it’s not a show-stopper for your editorial standards, this plugin may not be for you.
- Are there any options?
Yep, just for different “custom post types.” In your left sidebar under Settings, you should see “Req Featured Image”. There are options. You can choose which Post Types you want check as well as setting a minimum size for the featured image. Happy publishing!
- Support for other languages?
Yes. We’re currently (early 2016) hoping that these can start being done on traslate.wordpress.org, so if you’d like to contribute one and are familiar with the process, go ahead and do it there.
As the dust is still settling on that process, we will continue supporting other languages via contributions of translations which will be rolled into the next point release of the plugin, as we’ve done historically.
Colaboradores e desenvolvedores
“Exigir Imagem de Destaque” é um software com código aberto. As seguintes pessoas contribuíram para este plugin.Colaboradores
“Exigir Imagem de Destaque” foi traduzido para 10 localizações. Agradecemos aos tradutores por suas contribuições.
Traduzir “Exigir Imagem de Destaque” para o seu idioma.
Interessado no desenvolvimento?
Navegue pelo código, dê uma olhada no repositório SVN ou assine o registro de desenvolvimento via RSS.
Registro de alterações
- It was impossible to publish a post (which was never saved as a “Draft”) because of the server-side check. It is no longer.
- Fix to crude Gutenberg compatibility in JS
- Crude-and-quick Gutenberg compatibility
- Fixing an issue where the PHP didn’t stop the post from publishing, if it were invoked
- Fixing an issue where the size warning banner would flash on in Chrome erroneously
- Fixing an issue that would make the plugin seem not to work when newly installed.
- Adding composer.json and Japanese translation.
- Lots of code style changes for better readability and comprehensibility.
- Smattering of small changes to make code more readable and standardized in formatting.
- Addressed and issue where a translation function was being used in the wrong place at the wrong time.
- Adding the ability to declare, check for, and enforce a minimum featured image size. Big props to @cjk508 for making that happen.
- Adding Finnish translation. This commit might/should also unlock language packs on .org, so it could be the last one!
- Added support for WordPress v4.4
- Improving support for WP4.3 by getting right of h1/h2 targetting issue in jQuery. Thanks Jamie.
- Added Danish translation. Thanks Jess!
- Added support for WordPress v4.3+
- Fixed an logic error that made it nearly impossible to publish posts. Apologies to all affected.
- Version bump because we finally resolved the issue people started complaining about in 1.0, where you were able to publish with an image and then go remove the image. The change was made in 1.0 to allow for people with old content without featured images to edit posts easily, which was an issue in pre-1.0. The solution, turned out to be to store an option on plugin activation, and then only start enforcing from that time forward. People with the plugin already activated will be auto-set to two weeks before when they upgrade.
- Adding Portuguese (Portugal) translation.
- Adding Dutch translation.
- Bumping WP version tested number.
- Brazilian Portuguese translation from matheusmb.
- VCS games…
- Adding translation to Serbian by from Andrijana Nikolic of WebHostingGeeks. Thanks Andrijana!
- Adding translation to Norwegian by Alf Otto Fagermo.
- Adding translation to German by Wolfgang Tischer.
- Fixing typo in .pot file that was causing a string to not come through translated.
- Cleaned up settings page a fair bit.
- Made as mistake during VCS games, bumping again was easiest.
- Realized that JS check to allow for edit of featured-image-less unpublished posts would not work in non-English installs. Found a markup-based way to discover the same thing.
- Big JS Refactoring so the final action statements are quite obvious.
- Made it so that when a post is published without a featured image, the plugin doesn’t block you from changing it (say to fix a typo).
- Big version bump! This is too widely used to not be at 1.*, and should have been sooner.
- Adding Greek translations.
- Readme changes (4.1 support).
- Adding Arabic translation.
- Readme changes (4.0 support).
- Readme changes (3.9 support rev, some copy changes).
- Adding Spanish translation from Andrew Kurtis of WebHostingHub. Thanks Andrew!
- Updating readme so the live version will change, and removing a .mo file I didn’t mean to commit.
- Big changes: Added support for languages localization. I think. I’m new at this.
- Changed it under the hood to use a proper hook rather than a terrible hack system I’d devised before.
- Big changes: now supports all your custom post types out of the box. This can be accessed through the options page (recommended and preferred) or through a filter called ‘rfi_post_types’.
- Created an options page to make it easier to update your custom post types and set them within the admin.
- Some small improvements to internal code structure to increase readability and comprehensibility. This plugin may finally be big enough to benefit from some object-based design, but not for 0.5.0.
- Improved conditional fall-back PHP test of publishing because it was stopping saves.
- Fixed some minor documentation errors
- Fixing typo in JS file name.
- Fixed wp_die() to only be triggered if post_type is post.
- Updating documentation after seeing it in repository.
- First release