Title: JavaScript function naming conflict
Last modified: January 24, 2024

---

# JavaScript function naming conflict

 *  Resolved [thewebtailors](https://wordpress.org/support/users/thewebtailors/)
 * (@thewebtailors)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/javascript-function-naming-conflict/)
 * Hello,
 * When “Use Anti-Spam by CleanTalk JavaScript library” is turned on (currently 
   turned off on my site), I am getting the following JavaScript error when the 
   page is also loading the autocomplete widget from kraaden ([https://github.com/kraaden/autocomplete](https://github.com/kraaden/autocomplete)).
   Apparently, there is an autocomplete function in [https://moderate.cleantalk.org/1.1.18/ct-bot-detector.min.js](https://moderate.cleantalk.org/1.1.18/ct-bot-detector.min.js)
   which is causing the conflict. Is there a chance you can rename the autocomplete
   function in your library?
 * Thank you for considering!
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fjavascript-function-naming-conflict%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 9 replies - 1 through 9 (of 9 total)

 *  Plugin Support [katereji](https://wordpress.org/support/users/katereji/)
 * (@katereji)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/javascript-function-naming-conflict/#post-17370515)
 * Hello.
 * We will try to reproduce it on our side. Please give us 3-4 business days.
 *  Thread Starter [thewebtailors](https://wordpress.org/support/users/thewebtailors/)
 * (@thewebtailors)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/javascript-function-naming-conflict/#post-17370657)
 * Sure thing. Sorry, I forgot to post the JavaScript error. Here it is in case 
   it is helpful:
 *     ```wp-block-code
       ct-bot-detector.min.js:1 Uncaught (in promise) TypeError: t.hasAttribute is not a function
           at autocomplete (ct-bot-detector.min.js:1:2559)
           at initApplicationAutocomplete (application_form.js?ver=1:24:5)
       ```
   
 *  Plugin Support [eugenecleantalk](https://wordpress.org/support/users/eugenecleantalk/)
 * (@eugenecleantalk)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/javascript-function-naming-conflict/#post-17371279)
 * Thank you
 *  [SergeM](https://wordpress.org/support/users/serge00/)
 * (@serge00)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/javascript-function-naming-conflict/#post-17380102)
 * Hello,
 * We will improve the code in the upcoming 2 weeks and inform you about it.
 * Please, wait.
 *  [SergeM](https://wordpress.org/support/users/serge00/)
 * (@serge00)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/javascript-function-naming-conflict/#post-17380109)
 * While this process goes, please disable the option “**Use CleanTalk JavaScript
   library**“:
   • WordPress Admin Page → Settings → Anti-Spam by CleanTalk → Advanced
   settings → set the option “Use CleanTalk JavaScript library” to “Off” → Save 
   Changes.
 * Then refresh your website cache. Make sure that the website cache is 24 hours
   or less.
 *  Thread Starter [thewebtailors](https://wordpress.org/support/users/thewebtailors/)
 * (@thewebtailors)
 * [2 years, 2 months ago](https://wordpress.org/support/topic/javascript-function-naming-conflict/#post-17381155)
 * Thank you!
 *  Plugin Support [amagsumov](https://wordpress.org/support/users/amagsumov/)
 * (@amagsumov)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/javascript-function-naming-conflict/#post-17436489)
 * Hello [@thewebtailors](https://wordpress.org/support/users/thewebtailors/),
 * We’ve fixed the issue.
 * Please turn the **Use Anti-Spam by CleanTalk JavaScript library **option on and
   check the result.
 * Please let us know about the result.
 * Thank you.
 *  Thread Starter [thewebtailors](https://wordpress.org/support/users/thewebtailors/)
 * (@thewebtailors)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/javascript-function-naming-conflict/#post-17436826)
 * This fixed it. Thank you!
 *  Plugin Support [amagsumov](https://wordpress.org/support/users/amagsumov/)
 * (@amagsumov)
 * [2 years, 1 month ago](https://wordpress.org/support/topic/javascript-function-naming-conflict/#post-17436900)
 * We are glad to know the issue is solved.
 * If you have a moment, could you please leave us some feedback? We would be very
   grateful.
 * Anti-Spam: [https://wordpress.org/support/plugin/cleantalk-spam-protect/reviews/](https://wordpress.org/support/plugin/cleantalk-spam-protect/reviews/)
 * Thank you.

Viewing 9 replies - 1 through 9 (of 9 total)

The topic ‘JavaScript function naming conflict’ is closed to new replies.

 * ![](https://ps.w.org/cleantalk-spam-protect/assets/icon-256x256.png?rev=1637702)
 * [Spam protection, Honeypot, Anti-Spam by CleanTalk](https://wordpress.org/plugins/cleantalk-spam-protect/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/cleantalk-spam-protect/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/cleantalk-spam-protect/)
 * [Active Topics](https://wordpress.org/support/plugin/cleantalk-spam-protect/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cleantalk-spam-protect/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cleantalk-spam-protect/reviews/)

 * 9 replies
 * 5 participants
 * Last reply from: [amagsumov](https://wordpress.org/support/users/amagsumov/)
 * Last activity: [2 years, 1 month ago](https://wordpress.org/support/topic/javascript-function-naming-conflict/#post-17436900)
 * Status: resolved