I have to wonder if you have some taxonomies that are visually listed as “Categories” and “Tags” but the taxonomy slugs are actually different.
We don’t do anything intended for duplication like that in that spot.
Here is what I found. The duplicate Category and Tags entries per the above are coming from the Download Monitor plugin: DLM
Here is what your form is showing on the cptui_manage_post_types page:
<td><fieldset><input type="checkbox" id="category" name="cpt_addon_taxes[]" value="category"><label for="category">Categories</label><a href="#" class="cptui-help dashicons-before dashicons-editor-help" title="Adds Categories support"></a><br><input type="checkbox" id="post_tag" name="cpt_addon_taxes[]" value="post_tag"><label for="post_tag">Tags</label><a href="#" class="cptui-help dashicons-before dashicons-editor-help" title="Adds Tags support"></a><br><input type="checkbox" id="dlm_download_category" name="cpt_addon_taxes[]" value="dlm_download_category"><label for="dlm_download_category">Categories</label><a href="#" class="cptui-help dashicons-before dashicons-editor-help" title="Adds Categories support"></a><br><input type="checkbox" id="dlm_download_tag" name="cpt_addon_taxes[]" value="dlm_download_tag"><label for="dlm_download_tag">Tags</label><a href="#" class="cptui-help dashicons-before dashicons-editor-help" title="Adds Tags support"></a><br></fieldset></td>
It looks like your plugin is not creating a unique name in the UI for the DLM Category and Tag.
What are your thoughts here?
Thanks.
Well, I can confirm that the taxonomy slugs are different, so that’s good. They are getting unique names when it comes to saving and associating with the post type.
However, all I do in those spots is output the taxonomy label. In your case, the first "Categories" and "Tags" set are from WordPress core, and the second set are from the DLM plugin. It just happens to use the generic "Categories" and "Tags" for their "dlm_download_category" and "dlm_download_tag" taxonomies. Thus it looks duplicated.
Not really much we can do specifically here. At least nothing I can think of. All the issue is is visual with the text.
… yea, just confusing I guess. Maybe add some type of further descriptor as to the specific slug in the event this comes up again in the future with other plugins? Not everyone can/will be diving into the form fields to research.
Food for thought …
I’ll keep it in mind and see if I can think up any decent solution.
