HOW CAN WE HELP?

You can choose to enable or disable the revisit consent widget from the plugin settings.

1. From the WordPress dashboard, go to GDPR Cookie Consent.
2. Open Settings > Customise Cookie Bar > Revisit consent
3. Then, enable/disable the Revisit cookie consent widget.

Refer Guide

If you are using version 2.3.4 or below and have got a new license after renewal, you might be getting the error ‘Invalid API License Key. Log in to your My Account page to find a valid API License Key: No matching API license key exists. Activation error.”

This happens because of the recent changes in the API manager which makes the new keys work only in version 2.3.5 or above. If you have already updated to 2.3.5 before license expiry, you won’t be facing any errors and you can directly activate the keys.

Workaround: To activate the new license, please download the latest version of the plugin from the Webtoffee My Account > Downloads section and install it first. You won’t lose any of your current settings by doing so.

You can choose to set the default button state to enabled/disabled according to your requirement. Please refer to our article with the detailed instructions.
Refer Guide

By default, the consent is set for a period of 1 year. You can alter it by using a filter to set any custom number of days. Please refer to the guide to get the code snippet.
Refer Guide

You can use the custom script blocker filter to add more items to the blocker. This will come handy in case if you want to block a script from a different plugin or of customer service.
View Doc

Go to GDPR Cookie Consent menu > Settings > General > Others and set “YES” for the option, Enable consent logging.

IP in consent is anonymized for GDPR reasons. To unmask the IP address, copy below code snippet to your active theme’s functions.php.
// For disabling ip masking
add_filter( 'wt_cli_enable_ip_masking', '__return_false');

Our GDPR Cookie Consent plugin does not collect any data on its own. It just enables you to block the scripts/cookies and run them based on consent. For example, if there is google analytics tracking on the site, the plugin will run the script of the analytics based on user consent. However, even after the user consent, the data tracked by the script will still be handled by the google analytics dashboard itself.

Kindly ensure that the plugin’s license key is active with your valid email address. If not, deactivate and activate again with same the API key and a valid email address. Preferably the billing email address used during plugin purchase.

Please check the following:

• Ensure that the cookies are present and set on your site from an incognito/private window. This is because the scanner accesses the site from a private window.
  Open the site in a private window. Also, open the developer console and check for cookies.
• Make sure you have created all the below-mentioned database tables.

            wp_cli_cookie_scan_url

            wp_cli_cookie_scan_cookies

            wp_cli_cookie_scan

            wp_cli_cookie_scan_categories

• Make sure that the user has database table write permission.
• Ensure that your site is publicly accessible without any htaccess protection.
• If you are using any maintenance mode or coming soon mode plugins, please disable them while scanning.

Enable the accept-all feature for the accept button under GDPR Cookie Consent > Settings > Customise button > Accept button > Enable accept-all feature. This action will automatically add a Save & Accept button into the settings pop-up.

You can use the cookie audit short code to list the cookies in the popup once you added them to the back end. Please refer to the guide for more info.
View Doc

While there isn’t such an option within the plugin, you can achieve it via code snippet. You may please refer to the documentation link to know how to hide banner on selected pages.

You can add the Cookie Settings link in 2 ways, either via shortcode which comes with its style, or by directly inserting using the associated class. Please refer to the guide.
View Doc

If you are using any third-party plugin to create custom data fields, then it will be stored as metadata. When importing custom fields, the import file must have the data in the same format as required by those plugins. The easiest way to identify the format is by exporting the sample existing data/product on the site using the plugin. Make sure you have enabled the option of Hidden metadata on the export mapping screen. Use the exported file as a template to import the data back.

If you are using any third-party plugin to create custom data fields, then it will be stored as metadata. You may please export the CSV with the option of Hidden meta checked in the export mapping. This action will include the custom metadata fields in the exported CSV.

With custom fields created using third-party plugins, it is important for the import file to have data in the same format as required by those plugins. The easiest way to identify the format is by exporting the sample existing data/product in the site using the plugin. Make sure you have enabled the option of Hidden metadata on the export mapping screen. Use the exported file as a template to import the data back.

Our Product import export plugin can import products via CSV files. The Shopify export CSV may not exactly be compatible with the WooCommerce or the plugin supported format. Thus, you will have to make the modifications in the CSV file to import the variable products accordingly so that the import process will be compatible with our plugin.

 Sample CSV of variable products supported by the plugin.

Please enable the option Update even if empty values to import blank data from the CSV file and remove the existing value. 

The import speed depends on the amount of data present in the CSV, including attributes, taxonomies, image URL, network speed, server, etc. For CSVs with images, the import speed also depends on the time taken to download the images as well.

Import speed varies for each server and CSV file. During import, each CSV row and column import is accessing different tables in the database and entering data into each table. This will increase the import time as the data needs to be written to each field in the database and continuous database hits can slow down the server.

You can also import large CSVs in batches of 5000-10,000 per CSV so that import will not get stuck since the CSV is containing a large number of data.

We can suggest some methods to increase the import speed:
1. On import, map only the necessary columns.
2. If you are having the product images already in the WP media library, you may please specify the image name only.
3. Import large CSV in batches of 5000-10,000 products per CSV.

Our Product import export plugin can import products via CSV files. The Shopify export CSV may not exactly be compatible with the WooCommerce or the plugin supported format. Thus, you will have to make the modifications in the CSV file to import the variable products accordingly so that the import process will be compatible with our plugin.

 Sample CSV of variable products supported by the plugin.

We have developed a code snippet for this requirement. Please add this code snippet in the active theme’s functions.php file.

If you are using any third-party plugin to create custom data fields, then it will be stored as metadata. When importing custom fields, the import file must have the data in the same format as required by those plugins. The easiest way to identify the format is by exporting the sample existing data/product on the site using the plugin. Make sure you have enabled the option of Hidden metadata on the export mapping screen. Use the exported file as a template to import the data back.

If you are using any third-party plugin to create custom data fields, then it will be stored as metadata. You may please export the CSV with the option of Hidden meta checked in the export mapping. This action will include the custom metadata fields in the exported CSV.

With custom fields created using third-party plugins, it is important for the import file to have data in the same format as required by those plugins. The easiest way to identify the format is by exporting the sample existing data/product in the site using the plugin. Make sure you have enabled the option of Hidden metadata on the export mapping screen. Use the exported file as a template to import the data back.

Please enable the option Update even if empty values to import blank data from the CSV file and remove the existing value. 

WordPress encrypts passwords and stores them as a hashed value in the database. On reaching step 4 of the import process:

• Select Yes for the option Retain user passwords if you are importing hashed passwords that were exported from another WordPress site.
• Select No for the option Retain user passwords if you are importing a plaintext/custom password using a CSV.

We have developed a code snippet for this requirement. Please add this code snippet in the active theme’s functions.php file.

Kindly ensure the following:

1. Provide the email address of the users in the CSV column and is mapped to the field “user_email” during import.
2. All the users have unique email addresses.

The reason why the imported users do not show up under Woocommerce > Customers is that:

• Users who have placed at least one order will only show up in this section. Newly imported users will be having zero orders. That is, the database (DB view wp_customer_lookup) contains zero records resulting in an empty view.
• Therefore, once an imported user places his/her first order, this view will be populated. Then, users will be displayed under Woocommerce > Customers.

Please copy the snippet in the below article to make the plugin compatible with BuddyPress fields. Once the snippet is copied, you can export the BuddyPress fields to the CSV file. Later on, you can use the same CSV file as a template to import data back.

How to export and import BuddyPress data

The import speed depends on the amount of data present in the CSV, including attributes, taxonomies, image URL, network speed, server, etc. For CSVs with images, the import speed also depends on the time taken to download the images as well.

Import speed varies for each server and CSV file. During import, each CSV row and column import is accessing different tables in the database and entering data into each table. This will increase the import time as the data needs to be written to each field in the database and continuous database hits can slow down the server.

You can also import large CSVs in batches of 5000-10,000 per CSV so that import will not get stuck since the CSV is containing a large number of data.

We can suggest some methods to increase the import speed:
1. On import, map only the necessary columns.
2. If you are having the product images already in the WP media library, you may please specify the image name only.
3. Import large CSV in batches of 5000-10,000 products per CSV.

Yes, you can migrate user passwords between 2 WordPress sites. On reaching step 4 of the import process:

• Select Yes for the option Retain user passwords if you are importing hashed passwords that were exported from another WordPress site.
• Select No for the option Retain user passwords if you are importing a plaintext/custom password using a CSV.

WordPress encrypts passwords and stores them as a hashed value in the database. On reaching step 4 of the import process:

• Select Yes for the option Retain user passwords if you are importing hashed passwords that were exported from another WordPress site.
• Select No for the option Retain user passwords if you are importing a plaintext/custom password using a CSV.

Yes, you can migrate user passwords between 2 WordPress sites. On reaching step 4 of the import process:

• Select Yes for the option Retain user passwords if you are importing hashed passwords that were exported from another WordPress site.
• Select No for the option Retain user passwords if you are importing a plaintext/custom password using a CSV.

If you are using any third-party plugin to create custom data fields, then it will be stored as metadata. You may please export the CSV with the option of Hidden meta checked in the export mapping. This action will include the custom metadata fields in the exported CSV.

With custom fields created using third-party plugins, it is important for the import file to have data in the same format as required by those plugins. The easiest way to identify the format is by exporting the sample existing data/product in the site using the plugin. Make sure you have enabled the option of Hidden metadata on the export mapping screen. Use the exported file as a template to import the data back.

Please enable the option Update even if empty values to import blank data from the CSV file and remove the existing value. 

First of all, please make sure that the users are already present on the importing site prior to importing orders. That is, always import the users first before importing orders.

Within the plugin, the orders and users are linked using the user’s email address. So, in order to link them please ensure the following:

1. Add the correct user email address in the importing CSV file.
2. On reaching the import mapping screen, map the field customer_email properly.

If you are using any third-party plugin to create custom data fields, then it will be stored as metadata. When importing custom fields, the import file must have the data in the same format as required by those plugins. The easiest way to identify the format is by exporting the sample existing data/product on the site using the plugin. Make sure you have enabled the option of Hidden metadata on the export mapping screen. Use the exported file as a template to import the data back.

If you are using any third-party plugin to create custom data fields, then it will be stored as metadata. You may please export the CSV with the option of Hidden meta checked in the export mapping. This action will include the custom metadata fields in the exported CSV.

With custom fields created using third-party plugins, it is important for the import file to have data in the same format as required by those plugins. The easiest way to identify the format is by exporting the sample existing data/product in the site using the plugin. Make sure you have enabled the option of Hidden metadata on the export mapping screen. Use the exported file as a template to import the data back.

Please enable the option Update even if empty values to import blank data from the CSV file and remove the existing value. 

We have developed a code snippet for this requirement. Please add this code snippet in the active theme’s functions.php file.

If you are using any third-party plugin to create custom data fields, then it will be stored as metadata. When importing custom fields, the import file must have the data in the same format as required by those plugins. The easiest way to identify the format is by exporting the sample existing data/product on the site using the plugin. Make sure you have enabled the option of Hidden metadata on the export mapping screen. Use the exported file as a template to import the data back.

If you are using any third-party plugin to create custom data fields, then it will be stored as metadata. You may please export the CSV with the option of Hidden meta checked in the export mapping. This action will include the custom metadata fields in the exported CSV.

With custom fields created using third-party plugins, it is important for the import file to have data in the same format as required by those plugins. The easiest way to identify the format is by exporting the sample existing data/product in the site using the plugin. Make sure you have enabled the option of Hidden metadata on the export mapping screen. Use the exported file as a template to import the data back.

Please enable the option Update even if empty values to import blank data from the CSV file and remove the existing value. 

First of all, please make sure that the users are already present on the importing site prior to importing orders. That is, always import the users first before importing orders.

Within the plugin, the orders and users are linked using the user’s email address. So, in order to link them please ensure the following:

1. Add the correct user email address in the importing CSV file.
2. On reaching the import mapping screen, map the field customer_email properly.

The import speed depends on the amount of data present in the CSV, including attributes, taxonomies, image URL, network speed, server, etc. For CSVs with images, the import speed also depends on the time taken to download the images as well.

Import speed varies for each server and CSV file. During import, each CSV row and column import is accessing different tables in the database and entering data into each table. This will increase the import time as the data needs to be written to each field in the database and continuous database hits can slow down the server.

You can also import large CSVs in batches of 5000-10,000 per CSV so that import will not get stuck since the CSV is containing a large number of data.

We can suggest some methods to increase the import speed:
1. On import, map only the necessary columns.
2. If you are having the product images already in the WP media library, you may please specify the image name only.
3. Import large CSV in batches of 5000-10,000 products per CSV.

The error, “Importing order(ID) conflicts with an existing post” occurs when a post already exists in the importing site with the same ID as in the CSV file. In WordPress, posts include: product, images, pages, media, orders, coupons etc.

You may please try importing the orders by selecting “Import as new item” for the option “If conflict with an existing Post ID” or by unmapping the Order ID column during mapping or deleting the Order ID field from the file. WordPress will automatically assign a new ID to the imported orders.

Please note that importing orders with a new ID will assign a new order number.

By default in WooCommerce, orders and products are linked using either ID or SKU. Kindly make sure that the product ID present in the line_item column of the order CSV file is the same as the product ID on the importing site.

If you are using SKU to link the products, then please make sure that you enable the Link products using SKU instead of Product ID option while importing the orders.

Our plugin development is exclusively based on Woocommmerce and is not compatible with other non-Woocommerce platforms. The data exported from the non-Woocommerce platform will not be compatible with Woocomerce by default and you will have to make modifications to the CSV file in order to import them to the Woocommerce site.
You will have to include all the item details in a single column(line_item_1,line_item_2,..) like in the sample CSV file.

We have developed a code snippet for this requirement. Please add this code snippet in the active theme’s functions.php file.

First of all, please make sure that the users are already present on the importing site prior to importing orders. That is, always import the users first before importing orders.

Within the plugin, the orders and users are linked using the user’s email address. So, in order to link them please ensure the following:

1. Add the correct user email address in the importing CSV file.
2. On reaching the import mapping screen, map the field customer_email properly.

By default in WooCommerce, orders and products are linked using either ID or SKU. Kindly make sure that the product ID present in the line_item column of the order CSV file is the same as the product ID on the importing site.

If you are using SKU to link the products, then please make sure that you enable the Link products using SKU instead of Product ID option while importing the orders.

Our plugin development is exclusively based on Woocommmerce and is not compatible with other non-Woocommerce platforms. The data exported from the non-Woocommerce platform will not be compatible with Woocomerce by default and you will have to make modifications to the CSV file in order to import them to the Woocommerce site.
You will have to include all the item details in a single column(line_item_1,line_item_2,..) like in the sample CSV file.

The Apple pay button will show up only if the following pre-requisites are met:

1. Ensure that the site domain verification is complete in the stripe account.
2. Also, make sure that the site is SSL certified(HTTPS).

It will show up only if checked from a compatible browser which is Google Chrome. Also, ensure the following:

1. You have saved cards in a supporting browser or on your device.
2. The site is SSL certified(HTTPS).