Uncaught Reference Error: tippy is not defined - ccers.min.js

Fixed Bugs
1

Hi there,

I tried to see if others report the issue - but can’t find any way to fix this
I keep getting this error is my console when inspecting a page
Could you perhaps please advise how to resolve?

Uncaught ReferenceError: tippy is not defined
    at cc_tooltip (ccers.min.js?ver=1.2.8.7.3:1:5242)
    at ccers.min.js?ver=1.2.8.7.3:1:6462
    at NodeList.forEach (<anonymous>)
    at ccers.min.js?ver=1.2.8.7.3:1:6442
    at c ((index):5:32865)```

I'm using only CWICLY theme & plugin (no other theme)

* WordPress version: 	6.1.1
* Gutenberg Plugin version: - Not Installed
* Cwicly Plugin version: 1.2.8.7.3
* Cwicly Theme version: 1.0.3
2

Hi there @Oelof,

I’m sorry to hear this.
Could you possibly tell me if you are using tooltips on the culprit pages, or is this happening on every single one?

Thanks in advance.

3

Hi @Louis

Thank you for the swift reply. I’m not using any tooltips on any of the pages.

4

Hi @Oelof,

Thanks for the precision.
Would you know if you have any type of attribute like: data-tooltip?

Cheers,

5

Hi @Louis

I viewed the page source based on your suspicion and searched for “data-tooltip”
And the good news is that it was the Cookie Plugin (which loads on every page) which caused the conflict. I’ve deactivated the plugin, and then the error cleared - FYI Plugin is CookieYes | GDPR Cookie Consent

Now with the source identified, is there a way around it that I can implement to avoid “conflict”.
I will see if I can make any changes to the Cookie Plugin with the Plugin Editor (as its only for compliance :slight_smile: )

Thanks once again for your swift reply and nudge in the right direction!

1 Like
6

Hi @Oelof,

Thanks for letting me know, good to know what’s causing this.
There should be a check on our side as the error shouldn’t happen in any case, so apologies for the trouble here.

Do you need a quick fix or can this wait a couple of days for our next update?

Cheers,

7

Hi @Louis

No rush on my side, you were a great help thank you - I can wait for a future update.
I’m sure there are higher priorities - it’s not causing any major conflicts/disruptions on my end

Thanks in advance,

1 Like
8

Hi @Oelof,

Thanks for your patience on this one.
We have put a safeguard to make sure this function exists in 1.2.9.

If you still experience trouble with this, I’d be grateful if you could let me know.

Cheers,

9

Hi @Louis,

Thank you, I can confirm that the new update resolved it.
Much appreciated