Browser: Version 137.0.7151.122 (Official Build) (arm64) OS: macOS
Update: There is a difference on how CPT and Taxonomy are set up and linked in ACF, which impacts Bricks. See updated info at the end of the post.
I’ve found an issue when a taxonomy is assigned to multiple CPTs via ACF Post Types & Taxonomies . As I just started with Bricks I cannot estimate if this is a bug, a limitation, or if I did something wrong.
Example:
Taxonomy: Vibe (vibe)
CPTs: Event & Venue
Vibe is linked to both CPTs in ACF (Post Type + Taxonomy settings).
Problem:
The terms appear fine in WP Admin for both CPTs.
In Bricks, the Taxonomy element only shows Vibe for the first CPT listed in the Post Types field.
If Event is first, Venue can’t access it in the builder — if Venue is first, then Event can’t.
So the order of assigned CPTs controls which CPT sees the taxonomy in Bricks.
Expected: The Taxonomy element should list the taxonomy for all assigned CPTs, not just the first.
Workaround: Re-ordering the CPTs in the ACF Taxonomy settings does switch which CPT can see it in Bricks — so the link clearly exists, but Bricks only shows the first match.
UPDATE
In ACF I can
v1. Go to Taxonomy and define Post Types where this taxonomy is used (screenshot)
v2. Go to Post Type and define Taxonomies this Post Type can use
This has impact on Bricks.
v1 → problematic as you can see in the screenshot
v2 → seems to work, it shows only “Vibes” and not “Vibes (Event)” or “(Vibes (Venue)”
v1+v2 → I tend to have the very same setting applied from both ends in ACF, maybe that’s not a good idea
What’s more odd now, if I resume with my initial approach (v1 / screenshot) “Vibes (Event)” will output in the end “Vibes (Venue)” on the frontend - I am not 100% sure if this was always the case or only now after trying many different attempts.
The label in brackets (Event or Venue) should not have any effect on the output in your case, as it is the same taxonomy. In other words, it should also make no difference which one you choose.
Would you be so kind as to provide a live link and a screencast using https://jam.dev showing and explaining what’s happening?
there is not much I can show in a screencast I did not already show in the screenshots. No problem to send you an additional screencast in private, but I prefer not to do it in public.
The problem though is that it’s very much misleading. I tried for hours to figure it out, and was not able to get the taxonomy of Vibes (Venue) as it only showed me Vibes (Event). Yes, it’s a shared taxonomy but in the end I am in the context of the venue single template here, thus of course looking for fields related to the venue and not the event.
It’s a bit strange in the end also how ACF handles this - as there are two places to link taxonomy to post type and those are not in sync.
Meanwhile, I know how I can workaround it as shown in my updated post (v2 in ACF setup). Dealing with custom fields and accessing those in different situations and different context can become quite complicated, and if the builder adds up on that by showing misleading information it can become frustrating in my opinion.
From my point of view it looked like a bug - even though it maybe isn’t.
Unfortunately, I can’t tell from the screenshot where exactly you are: in a loop, on a page, in a template, and if so, which one, etc. That’s why I asked for the screencast.
Alternatively, you can send us temporary login details and a link to this thread so we can take a closer look at your setup and resolve the issue if necessary.
But you agree that it works in the front end and it’s just the labeling that’s confusing, right?
Got it. I shared the screenrecording and access to the site in a private message.
The taxonomy element is inside the Venue single template, and therefore trying to access the taxonomy Vibe which is assigned to Venue and Event alike.
My tests now show that it’s only the labeling indeed.
Unfortunately I cannot recall 100%, if I tried to add the taxonomy “Vibe (Event)” to the venue single template. It could be that I tried it and it was not successful. Could be that I did not even try it as I was clearly looking for “Vibe (Venue)” and not “Vibe (Event)”. However, the results right now show it’s only the labeling.
Thanks and sorry for making it bigger than it actually is now. It simply looked as a bug to me at first, and I didn’t have comparison with previous versions of Bricks, so I was not sure at all.
