Timeline for CiviCRM loads its own copy of jquery. This interferes with WP plugins
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 18, 2017 at 14:30 | comment | added | JohnFF | @MikeUbell Then it becomes a trickier issue. Civi is far larger than your average plugin, and there is a major case for it to maintain its own jQuery - particularly that it works on 3 different Content Management Systems. Guaranteeing the same version across all three would not be possible. Why not politely suggest to the SpamShield team that they look at namespacing their jQuery a touch more precisely? | |
| Apr 17, 2017 at 21:21 | comment | added | Mike Ubell | I think the issue is that SpamSheild relies on using one version of Jquery within the system and having a second different copy breaks how it works. | |
| Apr 17, 2017 at 17:50 | comment | added | Coleman | JohnFF is right, CIvi does not remove WP's copy of jQuery or to the best of my knowledge do anything to interfere with it. | |
| Apr 16, 2017 at 22:29 | comment | added | Mike Ubell | The error that SpamSheild throws is: ERROR: Sorry, there was an error. Please be sure JavaScript and Cookies are enabled in your browser and try again. After sending diagnostics to the support folks at SpamShield they have concluded that the problem is in differences in the JavaScript version used by WP vs the one used by CiviCRM. | |
| Apr 15, 2017 at 19:16 | history | answered | JohnFF | CC BY-SA 3.0 |