fortunerice

I figured it out. I had to first extend the custom post type job_listing, and also enable the REST API.

Hi, when I do
[pods]{@custom_taxonomy_name}[/pods]

The custom_taxonomy_name is referring to the Pod Name with type ‘Custom Taxonomy’.

I’ve only tried using the shortcode and the pod template. Where should I put the php code that you posted?

Also, I notice from https://docs.pods.io/displaying-pods/magic-tags/using-magic-tags/ that there’s a note saying: “NOTE: You can only display the Taxonomy content if you have Extended it with Pods. This especially applies to the built-in category or post_tag ; they will not show up in your magic tags if you have not extended the taxonomies.” In my case, my Custom Taxonomy was created as a pod. The post I’ve associated the custom taxonomy with is a custom post type job_listing of WP Job Manager (using the Listify theme). Any special considerations with this set up?

I’m facing a very similar problem. I have defined a custom taxonomy and associated it to a custom post type (from the Connections tab).

I’ve tried to add the following shortcodes to a block editor.

If I do:
[pods]{@custom_taxonomy_name}[/pods]
I get an empty output.

If I do:
[pods name="custom_taxonomy_name"]{@name}[/pods]
I get a list of ALL items names of this custom taxonomy, regardless of whether or not they are associated with the particular post (i.e. NOT filtered by the current post ID)

Any ideas why this might be happening? Any help greatly appreciated.

Issue fixed in version 0.81

I’m getting the same issue.

Hey John, really appreciate the time you took to make the video. It does reaffirm how it works.

I found out why it didn’t work for me. Let me explain my set-up in a way analogous to your demo:
I had TestPostA belonging to both categories CatA and CatB.
I had TestPostB belonging to just category CatB.

When I ran the shortcode [taxonomy=’CatA, CatB’ must_include_categories=’true’] I still got both TestPostA and TestPostB being pulled, contrary to the expected behaviour of just getting TestPostA.

And now here’s what I found: For TestPostB, not only did it belong to a category named “CatB”, but it also had a tag with the identical name, i.e. a TAG called “CatB”.

So to revise the original understanding:
I had TestPostA belonging to both categories CatA and CatB.
I had TestPostB belonging to just category ‘CatB’ BUT also having a TAG ‘CatB’

And this somehow caused the plugin to include TestPostB in the results, despite TestPostB not associated to neither a category nor a tag named ‘CatA’.

To reproduce this in your demo, I suspect that if you add a “Novels” TAG to your Test Post B, it would show up in the results despite the must_include_categories=”true” flag that’s supposed to exclude it.

To avoid the problem now, I’ve simply removed all tags that had identical names to categories, since they were redundant info in my case anyways.

I would be interested to know if this is reproducible on your side, but for now I don’t have any further issues.

Eagerly awaiting your update! Thanks so much.

Hi thanks for the quick response. I have tried listing out both categories using the taxonomy param, and then setting must_include_categories=’true’, but what I’m getting is OR logic output rather than AND logic output. So I’m getting posts that just belong to 1 of the 2 categories. Using plugin version 7.1.9. Any ideas?