pressidium

Hey, @ashishtiwari27!

There’s no option to customize the font through the plugin’s UI as of now.

However, it’s possible to specify a font using the --cc-font-family CSS custom property.

You’ll need to create a child theme (or, you could use a third-party WordPress plugin that allows you to include CSS rules into your site), with the following CSS:

:root {
  --cc-font-family: Helvetica, sans-serif;
}

Substitute Helvetica with the font you’d like to use.

We’ll leave this topic’s status as “not resolved” to look into including an option to customize the font via the plugin’s settings.

If you have any more questions, let us know!

Hey, @pieterbakker!

Thank you for your kind words and for highlighting the issue with the plugin’s functionality when used with Autoptimize, along with suggesting a workaround by unchecking the “Optimize JavaScript Code?” option.

I wonder if it is possible to export the configuration data so that it can be used (imported) for other websites using this plugin.

Yes, you can export your configuration to a JSON file, and import it on another website.

1. Log in to your website
2. Navigate to the WordPress dashboard (wp-admin)
3. Select the Cookie Consent menu item
4. Scroll to the down and click Export Settings to export your configuration as a JSON file

Likewise, on the other website, click Import Settings and choose the JSON file you exported earlier to import your configuration.

I also note that when using Autoptimize in “JavaScript Options” the “Optimize JavaScript Code?” should be left unchecked because otherwise blocking cookies will not work

We’ve opened an issue on the plugin’s GitHub repository (#48) to track and look into this further.

Hey, @marbe!

Short answer:

The issue is likely fixed in the latest version. Please update to version 1.1.1 and let us know if that resolves the issue 🙂

Long answer:

It’s likely that you’re running WordPress on a MySQL database with the utf8 character set (an alias of utf8mb3), which stores up to three bytes per character, instead of utf8mb4 which can store up to four bytes. We need that fourth byte to support storing emoji characters.

By default, the plugin contains the loudspeaker (📢) emoji (“Cookie usage 📢”, under Translations → English → Settings modal → Cookie usage heading). As a result, you were unable to save the settings until you deleted the preset language strings, effectively removing the emoji.

This was addressed in issue #15, by converting any emoji characters into their equivalent HTML entities and storing them in the database instead. So, as of version 1.1.0, the plugin supports emoji characters even when running on a database using the utf8/utf8mb3 charset.

If the problem persists after updating to the latest version, please navigate to Cookie Consent → Logs, click on “Copy to clipboard” and share your logs here as a reply. This will help us in further investigating the issue.