• Resolved peter8nss

    (@peter8nss)


    Somewhere between version 2.1.0 and 2.4.0 the code for get_post_type_tax_rules has been modified to include:

    // Skip taxonomies that are not public.
    $should_skip_private_tax = ! plugin()->get_option( 'includePrivateTaxonomies', false );

    As a result any rules previously defined using private taxonomies stop working.

    The setting ‘includePrivateTaxonomies’ does not appear to be exposed on the Settings UI.

    To avoid breaking existing installations this setting should probably default to true rather than false.

    It looks like I can workaround the problem by setting ‘includePrivateTaxonomies’ in ‘content_control_settings’ option to true.

Viewing 1 replies (of 1 total)
  • Plugin Support Kim L

    (@kimmyx)

    Hi @peter8nss,

    Thanks for the post!

    We forwarded your question to our dev team and this is their response:

    Yes, we protect content that is rendered in various ways via built-in WordPress mechanisms.?There are no mechanisms in WordPress that would show those types to users on the front end, rest api, etc, when they are private.?This removing them from our lists is a simple performance enhancement.

    We hope that helps! Let us know if you have other questions. ??

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.