Documentation/GDPR Cookie Consent/Troubleshooting methods for Cookie Scanner

Troubleshooting methods for Cookie Scanner

Error 1 : Unable to load cookie scanner. Scanning will not work on local servers

Kindly make sure that you are not checking from localhost as the scanner does not work in the localhost environment.

In case if you are getting this error message from a publicly hosted site, please save the below-given code snippet in .php file format (for eg: ipinfo.php) and host it in your site root directory.

Then enter the URL your domain/ipinfo.php in the browser and check what IP it’s returning (for eg:

Error 2 : Unable to load cookie scanner

  1. Please make sure below database tables are created on the site. Go to phpmyadmin and verify the same.
    • wp_cli_cookie_scan_url
    • wp_cli_cookie_scan_cookies
    • wp_cli_cookie_scan
    • wp_cli_cookie_scan_categories
  2. Alternatively, you can check in the error logs to find if any table creation errors are logged. To check,
    1. Add below line to wp-config.php.
      define( ‘WP_DEBUG’, true );
      define( ‘WP_DEBUG_LOG’, true )
    2. Deactivate and activate the plugin once.
    3. Look for any database table creation error messages logged in to wp-content/debug.log within your site’s filesystem.
       If not created, please make sure that the user has table creation permissions.

Error 3 : 0 cookies found as result

Since the scanner accesses the site from a private window/incognito window, make sure that the cookies are present and set in your site from an incognito window. Open the site in private window and open developer console and check the following:

  1. Make sure that all the database tables mentioned below are created.
    • wp_cli_cookie_scan_url
    • wp_cli_cookie_scan_cookies
    • wp_cli_cookie_scan
    • wp_cli_cookie_scan_categories
  2. Ensure that your site is publicly accessible without any htaccess protection.
  3. If you are using any maintenance mode or coming soon mode plugins, please disable while scanning.
  4. Make sure that the user has database table write permission.
  • Was this article helpful?
  • YesNo