Answers.Body: <p>I use Google ReCaptcha on our User Login and Contribution pages. Problem solved, No more Spam Registrations. It has been working for several months. Plus it is much simpler for the users to check <em>I am not a robot</em> then to do the pictures, letters, numbers mess. </p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-18T03:57:13.180Z
Answers.Text: I will try that and see if it works better than the other Captcha plug in. Thanks
Answers.UserDisplayName: Mike Ubell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-17T03:12:51.843Z
Answers.LastActivityDate: 2017-04-17T03:12:51.843Z
Answers.UserDisplayName: Iowa Boy
Answers.Body: <p>To be clear, the article that you linked to says why it's irresponsible to remove the default jQuery in WordPress. Are you sure that CiviCRM is doing that? My understanding (possibly incorrect) was that Civi just uses its own.</p>
  
  <p>Do you have the console errors that SpamShield was throwing that proves that this is what the error is? This may be a namespacing issue.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-16T22:29:52.493Z
Answers.Text: 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.
Answers.UserDisplayName: Mike Ubell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-17T17:50:58.620Z
Answers.Text: 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.
Answers.UserDisplayName: Coleman
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-17T21:21:39.647Z
Answers.Text: 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.
Answers.UserDisplayName: Mike Ubell
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-18T14:30:03.737Z
Answers.Text: @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?
Answers.UserDisplayName: JohnFF
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2017-04-15T19:16:17.890Z
Answers.LastActivityDate: 2017-04-15T19:16:17.890Z
Answers.UserDisplayName: JohnFF
Body: <p>I am running Civi on WordPress.  I was getting spam registrations.  I installed WP-SpamShield which worked great until someone tried to register for an event.  This fails saying that cookies and javascript need to be enabled. I backed off to just used SI Captcha Anti-Spam.  This work ok for a month or so but then the spam registrations started again.  The SpamShield support folks figured out that the problem is that Civi loads its own version of jQuery.  They say this is know to be a bad thing to do: <a href="https://pippinsplugins.com/why-loading-your-own-jquery-is-irresponsible/" rel="nofollow noreferrer">https://pippinsplugins.com/why-loading-your-own-jquery-is-irresponsible/</a></p>
  
  <p>Any one know why Civi does this or how to disable it?</p>
  
Tags: <wordpress><civievent><spam>
Title: CiviCRM loads its own copy of jquery. This interferes with WP plugins
ThreadText: # CiviCRM loads its own copy of jquery. This interferes with WP plugins
  
  (Asked by: username_0 on 2017-04-15)
  
  I am running Civi on WordPress. I was getting spam registrations. I installed WP-SpamShield which worked great until someone tried to register for an event. This fails saying that cookies and javascript need to be enabled. I backed off to just used SI Captcha Anti-Spam. This work ok for a month or so but then the spam registrations started again. The SpamShield support folks figured out that the problem is that Civi loads its own version of jQuery. They say this is know to be a bad thing to do: <https://pippinsplugins.com/why-loading-your-own-jquery-is-irresponsible/>
  
  Any one know why Civi does this or how to disable it?
  
  **Tags:** wordpress, civievent, spam
  
  
  ---
  
  ## 2 answers
  
  ### Answer by username_1 on 2017-04-17. Score: 1
  
  I use Google ReCaptcha on our User Login and Contribution pages. Problem solved, No more Spam Registrations. It has been working for several months. Plus it is much simpler for the users to check *I am not a robot* then to do the pictures, letters, numbers mess.
  
  > **Comments:**
  > **username_0**: I will try that and see if it works better than the other Captcha plug in. Thanks  
  
  ---
  
  ### Answer by username_2 on 2017-04-15. Score: 1
  
  To be clear, the article that you linked to says why it's irresponsible to remove the default jQuery in WordPress. Are you sure that CiviCRM is doing that? My understanding (possibly incorrect) was that Civi just uses its own.
  
  Do you have the console errors that SpamShield was throwing that proves that this is what the error is? This may be a namespacing issue.
  
  > **Comments:**
  > **username_0**: 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.  
  > **username_3**: username_2 is right, CIvi does not remove WP's copy of jQuery or to the best of my knowledge do anything to interfere with it.  
  > **username_0**: 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.  
  > **username_2**: @username_0 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?  
  
  ---
  
  