@suziekh Thanks for the reply.
That seems very likely and we can certainly try to narrow it down to find the conflict.
I think the problem here still is that if the plugin can’t access what it needs it should catch that error and log it but not let it bubble up.
In other words, totally understandable that it can run into a jQuery conflict but not okay that it breaks otherwise working scripts.
I think a big reason for that is that jQuery conflicts can be common since so many libraries use it.
I will reply later if I can narrow down what else may be conflicting.
-
This reply was modified 6 years ago by mlummus.