I created a custom taxonomy (event year), then a custom field (taxonomy advanced) to add a value to CPTs (give a year to each event). But the value is not registering in the backend when creating a new value ("add new event year"). It saves it somehow because if I reload the page then the new year will show in the taxonomy advanced dropdown menu, BUT IT DOESN'T SHOW while editing the CPT until refresh. But this is not usable since the field "event year" is set to "Required", the post will then not save with new year. I cannot deliver this to my client if they don't understand why adding a new year doesn't work, and I can't just tell them to "pre-create" years in the taxonomy's admin menu bar to then fetch it while editing the CPT, it makes no sense. Please help.
There is an issue in this case. Please don't mark this field as required if you allow the user to create new terms when editing the post. I've escalated this issue to the development team to find a way to fix it.
Please let me give you access to the website in private because there is a problem with the way Taxonomies are working at the moment. I do not understand how a user can add taxonomy values (whether in frontend or backend, adding values doesn't work), they just do not register anywhere. I am confused as to whether the user should be adding taxonomy values in a custom field (Taxonomy Advanced) linked to an custom Taxonomy, or if they should be adding the value in the edit page Meta Box (WP native Meta Box, not the MB plugin) on the right side. Either way, this is way too confusing...
You could also look into this issue that I have never been back to you about (you asked for access) :
Please send your site info via the ticket system, I will help you to check the issue.
Taxonomy behaviour seems to have changed. Can you confirm there has been a fix to the Taxonomy not registering mentioned above ?
There is no change of the field type
taxonomy_advanced. The feature that supports creating a new term when creating/editing the post still works as well. It is possible that there was an issue on your site in a while.