Tag field: only one tag visible when limited to a specific tag group

[jrgong]

@angus

So now we need to know the difference between the old tag group and this new one.

As far as any admin settings in each of the individual tag groups, there are no differences and they all have exact same settings. What’s odd is that in some of the settings

Could the issue be how each individual category is currently using the tag group settings?

Since the diy tag is being displayed, maybe some settings there that the others don’t have (or vice versa) could be the cause?

UPDATE: @angus could the issue be that some of the tags are assigned to multiple tag groups?

[jrgong]

Quick update:

In y test, for the field with “Location” tag group, only the outdoor tag was being displayed. The outdoor tag was part of 2 tag groups: “Location” (assigned in CW) and a second tag group (not assigned) that I just deleted.

After that, the outdoor tag is not being displayed in the field dropdown, despite now being assigned to only one single tag group which is set as filter in the CW field.

Update 2: I removed all tags from tag group “Beleuchtung” but one led tag. Still not being displayed in the CW field.

[jrgong]

Update 3, getting closer

Created a new tag group StrainsCW and added tags which are assigned to other legacy tag groups already and it works!

Could the issue then be tied to the legacy tag groups? Maybe they still inherited some old depracated settings that are still active?

[richard]

@jrgong

@richard can you install the presumed bugged version again so I can give it a shot?

The bugged version was installed (from the moment I made those videos)

@angus

Applying a “fix” without knowing the reason would not be a good idea

Exactly, that’s what I said, right?

@richard

It seems that this patch resolves the issue, but I have no idea what I am doing and whether this is causing unwanted side effects.

@richard

However, it leaves the :for_input parameter intact and passes it to super.

There are a few places in the core code where it acts on the mere presence of :for_input. But as I understand, the parameter has served its purpose, so removing it might be good.

Could you please elaborate a bit on how this works, i.e. why the parameter is not being removed. That would help me a lot in drilling down on issues like this.

@angus

What about the tags themselves. Are they restricted in any way? Do they all actually exist, i.e. those in the group?

I posted the relevant database contents above.

[angus]

@jrgong Could you perhaps just create a new tag group, put your locations tags in it and we can call it a day? We’ve verified that the functionality works. There may be diminishing returns here.

@richard I do understand where you’re coming from, I just feel like we might be too many cooks on what at the end of the day may not entirely be an actual issue. We could perhaps get to the bottom of this. But I’m not sure we need to.