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.
