Dang, I was hoping it wasn’t this plugin that was the issue. I’m having the same problem. I believe it’s related to the 6.3.2 ACF update. They have refactored A LOT about how AJAX fields work in ACF, and I’m pretty sure this plugin just hasn’t been updated to support the changes.
I may end up needing to fork this, and will try to reply here if I find a workaround.
My apologies, I have been away from WordPress for a while and did not realize the changes that needed to be addressed were in the ACF. I will try to fix it as soon as possible. However, I have to work now, so please wait a day or so.
@gameryo, no problem.
I’ve just submitted a pull request that fixes the issue. If anyone is in an emergency situation, I’ve forked the plugin and you can use my fork here. I’ve set the main
branch to version 1.0.6.1. If a 1.0.7 is published, it should automatically overwrite mine. I will plan to remove my fork as soon as the main plugin is updated.
The relevant code that actually fixes the issue change can be found here, in my PR. The entirety of the code is pulled from ACF’s own advanced-custom-fields-pro/includes/fields/class-acf-field-select.php
file, in the ajax_query()
method.
Thank you both for your help. Nothing urgent, but an official update of the plugin would be welcome, thanks for the fork and for the existence of this plugin 🙂
I just updated ACF: Multiple Taxonomy to version 1.0.7.
>> signelazer
Thank you for finding and reporting the problem. I would still be unaware of the situation if you had not started the topic.
>> justinmaurerdotdev.
Thank you for resolving the issue so precisely. Your code and pull request helped me to fix the problem quickly.
Please let me know if there are any more problems.
Once again, thank you both.
thank you, the update is good for me 🙂
Awesome. Great work all around! 🥂