error after update

ok, can you;

1. check if wp-content/plugins/async-javascript/assets/lib/chosen_v1.4.2/chosen.jquery.min.js is available on the server (it should)
2. check if you can load [yourdomain]/wp-content/plugins/async-javascript/assets/lib/chosen_v1.4.2/chosen.jquery.min.js in a webbrowser (it should)
3. go to Async JS settings while keeping an eye on the network tab in your developer tools; is it requested (it should) and do you see a 200 (or 304) HTTP response code or something else?

frank

I have a file chosen.jquery.min.js
It is loaded – status 200

also when on the async js page? in that case there’s no reason why you’d get that error message really as it’s that file that defines the jQuery .choosen function …

so …
1. what browser are you using?
2. are there any other errors on the console?
3. are you running any other plugin that is changing the way JS is loaded in the backend?

(going to get me some sleep now, but I’ll make sure to follow up on this tomorrow)

I have Safari for Mac 11.0.3
There is only one mistake, the other is not. https://joxi.ru/82QBKzji1XZGBA
Other plugins do not use

OK, so _maybe_ it’s a problem that is specific to Safari, could you test in Chrome or Firefox for MacOSX?

In Chrome, everything is working fine

OK, can you try https://harvesthq.github.io/chosen/ (the Chosen demo page) in Safari to see if that works?

Everything is working

OK, so an issue with the Chosen implementation on Safari … I’ll have a look at the code and try to find someone on MacOS so I can test myself.

Could you make a screenshot of what you mean when writing “I lost the button in the “add entry” section.”?

I recorded a video https://www.dropbox.com/s/aaleu6o42ta7g5j/java.mov?dl=0

OK, so the problem is not (only) on the AsyncJS settings-page, that’s ugly. I’ll get working on a fix right away!

OK, I have committed a fix on Github, could you try applying those changes (or replacing the contents of asyncjsBackendClass.php or downloading and installing the full zip-file from Github) and test?

[edit] this commit should limit the impact of the JS error to the AsyncJS page, I have a 2nd fix prepared for that as well but want to make sure that whatever goes wrogn only does so on AsyncJS own settings page.

frank

Thanks, now everything has worked

Great! I guess the async-js settings page itself might still not work, or does that work too now?

There is a problem when you click the save button nothing happens and nothing is saved