This has been reported before, but I am unable to find the cause of the issue. The best I can recommend is to make sure that JavaScript is enabled, jQuery is included on the page, and then try disabling either/both the Category and/or Tag fields and try again. Please let me know if you discover any clues, as I am still in the process of trying to resolve this issue.
Hi, Jeff,
Thanks for your answer.
I am going to test and let you know.
Hi Jeff,
I kept enabled Category and Tag fields, but disabled the option “use existing tags” and that error was gone, the page loads fine and the form works smoothly.
Your plugin is awesome, by the way!
It is a shame not be able to select from existing tags though. If possible to fix it would be perfect.
best,
-LH
Hey thanks, glad you got it all sorted out.
For using existing tags, you can enable the option “Use Existing Tags”.
Cheers
I know, Jeff, but if I enable it the jquery error we are talking about comes back.
Which version of the plugin are you using?
Versão 20200320
as well as WordPress most recent one, v 5.4.2
Thanks. It definitely looks like a bug with the fancy tag field. Can you try a test, add the following code snippet to the plugin setting, “Custom Content”:
<script>var usp_disable_chosen = true;</script>
Then save changes and try the fancy select tag field again.
Hi, Jeff,
that did it, the errors are gone while using the form with the the option “Use Existing Tags” enabled.
By the way, does the plugin use functionality not present on newer versions of jQuery?
Because the console also shows:
JQMIGRATE: Migrate is installed with logging active, version 1.4.1
Searching the web I found that “WordPress uses the jQuery migrate script to ensure backwards compatibility for any plugins using functionality removed from newer versions of jQuery”
Thanks again for your attention!
-LH
Great, glad to hear you got it sorted.
For this:
“does the plugin use functionality not present on newer versions of jQuery?”
No not that I know of.
Jeff, thank you very much for your kind attention.
And once again, the plugin is just awesome!
Just to follow up with this. The reported bug with “Uncaught TypeError: $(…).chosen is not a function” is resolved in the next version of USP (20200817). Should be available within a couple of days.