Make it possible to determine resource in get_ancestors()

[filosofo]

In case there exists a conflict between taxonomy and post_type names, allow it to be resolved explicitly when calling get_ancestors().

[filosofo]

Please ignore the first patch with its logic flaw.

[demetris]

There is a typo in the @param doc line for the new parameter: resorce. :-)

[filosofo]

Well, time to get some coffee.

[scribu]

I think we should prevent conflicts between post_type and taxonomy names at the registration step, not later.

[scribu]

On second thought, nevermind. I was thinking about query_var, which doesn't have to corespond to the taxonomy name.

[scribu]

By the way, shouldn't we also check if the post type is hierarchical, like we do for taxonomies?

[filosofo]

Replying to scribu:

By the way, shouldn't we also check if the post type is hierarchical, like we do for taxonomies?

Agreed; I don't think is_post_type_hierarchical existed when I wrote the original patch.

I also agree that checking query_var and maybe rewrite slug are good ideas.

[scribu]

Enhancement, no patch, punting.

[boonebgorges]

15029.patch​ refreshes the patch for the modern age.

[boonebgorges]

In 30141:

Allow resource_type to be specified in get_ancestors().

Being explicit about resource type (taxonomy vs post_type) allows for the
proper resolution of conflicts when a taxonomy and post_type share a slug.

Props filosofo.
Fixes #15029.