Conversation
supportHi, Thank you for this cool plugin. Here is a suggestion: it would be great if the plugin could also detect custom fields. Thanks! https://wordpress.org/plugins/post-type-requirements-checklist/
Jean-Phillippe, I am working on this feature for the next major release. Its pretty tricky to auto-detect custom fields, based on the number of available field types (text, wysiwyg, dropdown…). As soon as I can provide a simple UX around custom fields, this feature will be available. I’m close to releasing v. 2.2, which allows for both minimum and maximum limits for Categories, Tags and Custom Taxonomies. Thanks for the suggestion! Dave
v2.2 has been released, as promised. Look for custom field requirements to drop in the next month. Dave
Hi Dave, Just updated your plugin, works great. Looking forward to seeing the custom field requirements option. Thanks!
Glad you like it… contact me through my website to inquire about beta testing future releases of this plugin. I haven’t started this feature, but when I do, you can be the first to know. 😉
Jean-Philippe, I’m beginning to work on the custom fields requirements for this plugin. I’m running into some logistical roadblocks, though. WordPress doesn’t really handle custom fields in a consistent way across field types and 3rd party plugins that add custom fields are not consistent in how those fields are handled. My question to you… how do you add custom fields? And, which types of fields should this plugin support? I’m having to rethink this implementation quite a bit – and I’m trying to keep the settings pages consistent and minimal. Proving to be a tricky task. 🙂 Dave
Hi Dave, I mainly add and manage custom fields thanks to ‘Advanced Custom Fields’ plugin, which actually includes an option to make a field a requirement or not. ACF can manage lots of different type fields. So my suggestion to make ‘Requirements Checklist’ compatible with custom fields is essentially a way to manage all those required post fields within the same place: your plugin.
Jean-Philippe, I use ACF, too. But, I’m afraid making it fully compatible with my plugin just isn’t going to happen. Both ACF and the “Types” plugin (which I see used a lot) have options to make a field required for a single post only , as well as for all post in a type and everywhere. Without recreating those settings in my plugin, I can’t accommodate some of those options. I’ll continue to look into it, but I’m trying to keep my settings pages as clean as possible. Perhaps I could hook into the ACF plugin and have mine auto-detect required fields from ACF. Then, it would look the same to the user. But, don’t see my plugin controlling which custom fields can be required (at least, not those created by ACF). The only way I could do this would be to have my plugin save data to the ACF database values — that’s really messy and I hate when other plugins try to do that. If ACF ever changes the way its data is stored, everything will break. I’ll keep looking for a clean solution, though.
Hi Dave, Thank you for your answer. Indeed, I suppose it’s a hard task to auto-detect required fields from ACF. No worries, it was just a suggestion. By the way, I encountered an issue while using ‘Drag & Drop Featured Image’ plugin. I’m going to open a new topic for this. Cheers!
Jean-Phillippe, I am working on this feature for the next major release. Its pretty tricky to auto-detect custom fields, based on the number of available field types (text, wysiwyg, dropdown…). As soon as I can provide a simple UX around custom fields, this feature will be available. I’m close to releasing v. 2.2, which allows for both minimum and maximum limits for Categories, Tags and Custom Taxonomies. Thanks for the suggestion! Dave
v2.2 has been released, as promised. Look for custom field requirements to drop in the next month. Dave
Hi Dave, Just updated your plugin, works great. Looking forward to seeing the custom field requirements option. Thanks!
Glad you like it… contact me through my website to inquire about beta testing future releases of this plugin. I haven’t started this feature, but when I do, you can be the first to know. 😉
Jean-Philippe, I’m beginning to work on the custom fields requirements for this plugin. I’m running into some logistical roadblocks, though. WordPress doesn’t really handle custom fields in a consistent way across field types and 3rd party plugins that add custom fields are not consistent in how those fields are handled. My question to you… how do you add custom fields? And, which types of fields should this plugin support? I’m having to rethink this implementation quite a bit – and I’m trying to keep the settings pages consistent and minimal. Proving to be a tricky task. 🙂 Dave
Hi Dave, I mainly add and manage custom fields thanks to ‘Advanced Custom Fields’ plugin, which actually includes an option to make a field a requirement or not. ACF can manage lots of different type fields. So my suggestion to make ‘Requirements Checklist’ compatible with custom fields is essentially a way to manage all those required post fields within the same place: your plugin.
Jean-Philippe, I use ACF, too. But, I’m afraid making it fully compatible with my plugin just isn’t going to happen. Both ACF and the “Types” plugin (which I see used a lot) have options to make a field required for a single post only , as well as for all post in a type and everywhere. Without recreating those settings in my plugin, I can’t accommodate some of those options. I’ll continue to look into it, but I’m trying to keep my settings pages as clean as possible. Perhaps I could hook into the ACF plugin and have mine auto-detect required fields from ACF. Then, it would look the same to the user. But, don’t see my plugin controlling which custom fields can be required (at least, not those created by ACF). The only way I could do this would be to have my plugin save data to the ACF database values — that’s really messy and I hate when other plugins try to do that. If ACF ever changes the way its data is stored, everything will break. I’ll keep looking for a clean solution, though.
Hi Dave, Thank you for your answer. Indeed, I suppose it’s a hard task to auto-detect required fields from ACF. No worries, it was just a suggestion. By the way, I encountered an issue while using ‘Drag & Drop Featured Image’ plugin. I’m going to open a new topic for this. Cheers!