They promised to check that out and fix (if necessary) in the next module version
We care about your privacy.Use the list below to configure your privacy settings
These cookies are necessary for the website to function and cannot be switched off in our systems. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
You can set your browser to block or alert you about these cookies, but some parts of the site will not then work. These cookies do not store any personally identifiable information. Read more about cookies in our Privacy Policy
The collection of information about your use of the website used to measure, understand, and report on your usage of the service, only in case of some error appearing. All collected information will be automatically removed from our server every month or immediately after your request.
Allow us to collect details to access your server and your website admin panel. This information will be requested from you only if it will be really necessary to provide requested by you an action like fix a bug or configure website. All provided information will be removed from our server by your request.
Please take a moment...
to read about the Privacy Policy we use with this website. Click "Privacy Options" to configure how we can interact with you and your device or computer.
Comments
How it’s related to the theme?
I see an errors caused by google analytics and Facebook modules
both analytic and facebook module is deactivated.
I followed doc… → 16. How to add Google Analytics/Tag Manager’s Code
Get your code from Google
but there is still alot of errors
But I don’t see an error caused by the theme’s scripts
so step 16. in doc is wrong or what are you saying ?
this error seams to be cause of theme facebook widget, as you can see it onlys shows this errors on home page.
Yes, maybe. I can only ask creative module developers. but from my experience they will not reply fast
yes please ask them
They promised to check that out and fix (if necessary) in the next module version