possible plugin conflict with acert plugin?
I attempted to extend tags and categories to our project pages and we suspect a plugin conflict. With the current ACERT plugin I am able to add categories/tags to projects on our wat1 test site. So far I have been unable to reproduce the issue from our live site on our wat1 test site. Is there any way we can run a test like you did last time?
#2 Updated by David dos Santos about 3 years ago
Hi Boone, sorry for the confusion. I was able to get this to work on our local test site but not the live site on the commons. Gina suggested that it may have been a plugin issue. I was referring to Feature #5314 when you discovered which plugin conflicted with our ACERT plugin.
#3 Updated by Boone Gorges about 3 years ago
Ah, OK. Can you please give specific details to reproduce the problem on the production site, so I have a better sense of what to debug? Is it precisely the same issue you were having in #5314? I'm not sure which steps to take to verify that you "attempted to extend tags and categories to our project pages". Thanks in advance.
#4 Updated by David dos Santos about 3 years ago
This is a separate issue from #5314.
In my ACERT plugin (which can be seen in #5614) on lines 70-83, I have extended the post category and post tags taxonomies to woo projects. I tested the plugin on our wat1.hunter.cuny.edu test site (only accessible on 68th st campus) and it works.
However, on our live site when I go to add project, I do not see categories or tags extended.
#5 Updated by Boone Gorges about 3 years ago
- Status changed from New to Reporter Feedback
Thanks for the additional details, David.
On a lark, I bumped the priority of your `register_taxonomy_for_object_type()` calls, from
add_action('init', 'cac_acert_tags_support_all'); add_action('init', 'cac_acert_category_support_all');
add_action('init', 'cac_acert_tags_support_all', 100); add_action('init', 'cac_acert_category_support_all', 100);
(When the third argument is absent, the default priority 10 is used.) This appears to have done the trick. It suggests that another plugin is interfering between priority 10 and 100 of the 'init' action, and overwriting the object-type-taxonomies. Bumping the priority means that your customizations run last, and are not overridden. I glanced through your active plugins to see if I could find the culprit, but I didn't see anything obvious; I'm not sure it's worth digging into much more, given that it's now working.
Could you please verify?
#7 Updated by Boone Gorges about 3 years ago
- Category name set to WordPress Plugins
- Status changed from Reporter Feedback to Resolved
- Target version set to 1.9.18
Great! The change has been applied to the repo at https://github.com/cuny-academic-commons/cac/commit/09d6ea7c6bfcc92295ee907035d8adca1977851c