Will

Good afternoon,

I was able to resolve this by setting global_terms_enabled to 0 in the sitemeta table in the DB. Still curious as to why this issue was only present with the All in One Security Plugin enabled, however I am glad to have it resolved.

Thanks for looking into it.

Good afternoon @vupdraft,

We do not have the WPML plugin installed and are hoping not to have to add any additional plugins.

Thanks.

Good morning,

No, the slug is what is causing the problem. Here is some additional info that may help:

1) We are using the plugin with WPMU.
2) Here is what is returned by get_term for the same category both with and without this plugin enabled:

With the plugin enabled:
object(WP_Term)#2587 (10) { ["term_id"]=> int(6222) ["name"]=> string(15) "Review Magazine" ["slug"]=> string(15) "review-magazine" ["term_group"]=> int(0) ["term_taxonomy_id"]=> int(5) ["taxonomy"]=> string(8) "category" ["description"]=> string(0) "" ["parent"]=> int(0) ["count"]=> int(58) ["filter"]=> string(3) "raw" }

With the plugin disabled (this is the correct slug):
object(WP_Term)#2505 (10) { ["term_id"]=> int(6222) ["name"]=> string(15) "Review Magazine" ["slug"]=> string(10) "the-review" ["term_group"]=> int(0) ["term_taxonomy_id"]=> int(5) ["taxonomy"]=> string(8) "category" ["description"]=> string(0) "" ["parent"]=> int(0) ["count"]=> int(58) ["filter"]=> string(3) "raw" }

Thanks.

I do see a slight problem with this functionality. When you return to the “Exclude Objects” tab on the Settings page, the list of excluded custom fields no longer appears. So there is no way to re-include a custom field that has been excluded (without accessing the database I assume). Thanks.

Thanks Timm

Great, thanks again.

Thanks Ryan, works great!