ResolvedFew errors in chrome dev tools
- This topic has 9 replies, 2 voices, and was last updated 3 years, 3 months ago by
typ.
- AuthorPosts
- February 5, 2020 at 10:00 am #21132
typ
ParticipantHi,
Please let me know how to fix this errors and warnings. Content imported from main template and changed to my own.
On each page there are errors in chrome dev tools mode:
– pinterest error
– zas-libs-config.min.js error
– 42 warnings about cookiesI have no pinterest address (links) set in theme settings.
February 5, 2020 at 11:05 am #21144Althemist
KeymasterHi typ,
I am afraid we can’t help with screenshots of errors out of the context. In order to try finding what could be wrong there we’d need to see the problem “live”. Please, provide a working link where we can check the problem.
So far, we can only tell there are JS errors on your site.
As for the cookies – I am afraid that’s not theme related, so we can’t really help here.
February 5, 2020 at 12:22 pm #21148typ
ParticipantThis reply has been marked as private.February 6, 2020 at 3:18 pm #21175Althemist
KeymasterYes, it’s a private reply and it’s absolutely safe, but we don’t need passwords. Just a working link to your site.
February 7, 2020 at 1:20 am #21186typ
ParticipantThis reply has been marked as private.February 11, 2020 at 1:06 am #21215typ
ParticipantDid you checked it?
February 11, 2020 at 3:21 pm #21242Althemist
KeymasterHi typ,
I have just checked and it looks like your site doesn’t load some of the theme’s JS files. It looks like some security problem with your hosting settings. Could you, please give us temporary admin access, so we can check further?
February 11, 2020 at 3:27 pm #21244typ
ParticipantThis reply has been marked as private.February 12, 2020 at 2:00 pm #21274Althemist
KeymasterHello typ,
Unfortunately, this is not theme related. You’d probably need to check your pinterest related plugin settings and also your hosting security settings, as it looks your site can’t communicate with pinterest properly.
Regards,
DimitarFebruary 15, 2020 at 8:36 pm #21357typ
ParticipantIndeed, it was problem with another plugin . I fixed this up. Thanks for fixed “zass-libs-config” problem.
- AuthorPosts
You must be logged in and have valid license to reply to this topic.