Unexpected Behavior in Taxonomy Input Field on Post Form v4.1.8

[kabirbd89]

I am experiencing unexpected behavior with the taxonomy input field in the post form of the WordPress User Frontend plugin.

The taxonomy field offers several input types:

• Select
• Multi Select
• Checkbox
• Text Input
• Ajax

There is also a Selection Type setting with the following options:

• Exclude
• Include
• Child of

All input types seem to behave the same way, and the advanced Selection Type options (Exclude, Include, Child of) do not appear to have any effect.

Expected Behavior
For example, when I select the Ajax input type and set Child of to a specific parent category (e.g., parent C), the form should only display terms that are children of that parent category (parent C). However, this filtering does not work as expected — the full list of terms is still shown.

Steps to Reproduce
Go to the post form.
Choose the taxonomy field and set the input type to Ajax.
Set the Selection Type to Child of and specify a parent term (e.g., parent C).
Submit the form and observe the taxonomy field.

Actual Behavior
The taxonomy field shows all terms instead of filtering by the specified child of the parent term.

[kabirbd89]

Additionally, there is another issue: no matter what I select when creating the taxonomy field initially, I cannot update the field settings afterward. It seems like I have to remove the field and add it again every time I want to change its settings.

Please check all possible (15 Combinations) combinations of the following settings to identify which ones are working and which are not:

[anik-fahmid]

We are looking into this. Are you using the latest versions?

[kabirbd89]

We are looking into this. Are you using the latest versions?

Version 4.1.8

[anik-fahmid]

We are releasing a version today that should fix these issues.

@Rubaiyat-E-Mohammad vai, please post an update about the mentioned issues here after release is done.

[kabirbd89]

@anik-fahmid

The Custom Taxonomy field is now in Pro mode. I understand you reserve the right to control features, but generally, it’s a norm that features which were free should remain free. After spending a lot of time building a site with this feature, it’s frustrating to see it suddenly moved to Pro. It feels unreliable and painful to rework everything.

Of course, it’s your product and you have full control over how it evolves but such changes can cause many sites to break or require significant rework.

[anik-fahmid]

Hello @kabirbd89, which custom taxonomy are you referring to? We didn't move anything to pro. Please post a screenshot.

[kabirbd89]

Hello @kabirbd89, which custom taxonomy are you referring to? We didn't move anything to pro. Please post a screenshot.

After updating Frontend, I noticed that the custom taxonomies I had created for my forms using ACF were removed. A popup appeared with a warning/notice, and now those fields are showing as PRO features and have been deactivated.

Previously, I was using these fields on the frontend of my nonprofit site without any issue, and I never purchased the PRO version of the plugin. Since I never had PRO, it seems something may have changed unexpectedly during the update. Could you please look into this?

[anik-fahmid]

If ACF taxonomies should be in the builder, they will be back. Let us check if this is because of an issue or business logic. Please wait till the next 1/2 releases.