May 18, 2022
This guide only applies when using up to v.2.8.3 of the Magento 2 Clerk extension.
In some setups, Require.js stops Clerk.js from loading, which means that no sliders or search results will be shown.
When this happens, the following error will be shown in your console:
Uncaught ReferenceError: Clerk is not defined
The Magento 2 extension already handles Require.js, but in some cases, its necessary to have it ignore Clerk.js.
You can do this in the following file:
...May 18, 2022
This guide only applies when using up to v.4.4.1 of the Prestashop Clerk extension.
In some setups, Require.js stops Clerk.js from loading, which means that no sliders or search results will be shown.
When this happens, the following error will be shown in your console:
Uncaught ReferenceError: Clerk is not defined
There are two ways to handle Require.js. Both approaches requires you to make changes to the tracking-script in this file:
modules->clerk->views->hook->visitor_tracking.tpl
...May 18, 2022
This guide only applies when using up to v.1.7.1 of the WooCommerce Clerk extension.
In some setups, Require.js stops Clerk.js from loading, which means that no sliders or search results will be shown.
When this happens, the following error will be shown in your console:
Uncaught ReferenceError: Clerk is not defined
There are two ways to handle Require.js. Both approaches require you to make changes to the tracking-script in this file:
wp-content -> plugins -> clerkio -> includes -> class-clerk-visitor-tracking.php
...May 18, 2022
Uncaught ReferenceError: Clerk is not defined
#
If you see this error message, it means Clerk is not being defined in the website.
The most common cause for this is the Clerk.io tracking Scripts not being implemented in the appropriate places.
Click here to view the implementation process for inserting both the Order Tracking and Visitor Tracking scripts.
API COOLDOWN Starting again in…
#
This message in the data sync logs is coming from the Lightspeed rate limit. Lightspeed has set a low rate limit by default to manage the volume of data transmitted from their services. Please note that this rate limit is not within Clerkâs control.
To address this, you have two options:
...May 18, 2022
Every now and then, Wordpress / Woocommerce plugins mess up with the Wordpress rewrite rule.
The rewrite rule is the set of configurations that makes sure that links like this
domain.com/?p=123
becomes beautiful and SEO-optimised links like
domain.com/product/my-beautiful-product/
and are actually reachable by you and your customers.
If your links do not work properly, do this:
1. Log in your Wordpress backend
2. Then go to: Dashboard –> Settings –> Permalink
...May 18, 2022
Often HTTP authentication is used on staging sites to avoid uninvited visitors.
This will block the Clerk importer as well and display a 401 Unauthorized error in the sync log.
You can easily verify the importer by inserting the authentication info in the import URL like below, in Data Sync at my.clerk.io:
https://USER:OASS@dandomain.clerk.io/api/6155349/28
May 18, 2022
Often HTTP authentication is used on staging sites to avoid uninvited visitors.
This will block the Clerk importer as well and display a 401 Unauthorized error in the sync log.
You can easily verify the importer by inserting the authentication info in the import URL like below, in Data Sync at my.clerk.io:
http://USER:PASS@magento2.clerk.io/
May 18, 2022
Often HTTP authentication is used on staging sites to avoid uninvited visitors.
This will block the Clerk importer as well and display a 401 Unauthorized error in the sync log.
You can easily verify the importer by inserting the authentication info in the import URL like below, in Data Sync at my.clerk.io:
https://USER:PASS@www.ewoksRus.com
May 18, 2022
Often HTTP authentication is used on staging sites to avoid uninvited visitors.
This will block the Clerk importer as well and display a 401 Unauthorized error in the sync log.
You can easily verify the importer by inserting the authentication info in the import URL like below, in Data Sync at my.clerk.io:
http://USER:PASS@www.ewoksRus.com
May 18, 2022
Often HTTP authentication is used on staging sites to avoid uninvited visitors.
This will block the Clerk importer as well and display a 401 Unauthorized error in the sync log.
You can easily verify the importer by inserting the authentication info in the import URL like below, in Data Sync at my.clerk.io:
https//USER:PASS@www.ewoksRus.com
