• Settings are not saved when i make changes. The problem is that I want to add Greek and it is not impossible

    From my knowledge as a programmer i understand that this must be related to the database. and more specifically this has to be related to emojis

    Ιn short the database encoding needs to be converted to utf8mb4, which is a huge process and a lot of effort that is not even worth the effort.

    I’m trying to give the plug-in a second chance before uninstalling it. because I manage many sites and it would be useful for me to keep it, primarily because it is available for free, but since it does not work and I need to put in a lot of work to fix my problem, it is useless..

    I suggest you fix your plugin so that all users can use it.

    The page I need help with: [log in to see the link]

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor overengineer

    (@overengineer)

    Hey @texnologia,

    Thank you for using Pressidium Cookie Consent and for reporting this issue.

    […] i understand that this must be related to the database. and more specifically this has to be related to emojis

    Ιn short the database encoding needs to be converted to utf8mb4 […]

    This is unlikely to be the issue, as the plugin supports both utf8mb4 and utf8 character sets. The main difference is that utf8 (an alias of utf8mb3) supports up to three bytes per character, whereas utf8mb4 supports four, which is required for native emoji storage. However, the plugin converts emoji characters to their HTML entity equivalents before saving, so it functions correctly even on databases using the utf8 charset. This has been the case since version 1.1.2.

    Refer to:

    Settings are not saved when i make changes.

    Could you please provide a bit more information so we can better understand the issue?

    If possible, please submit a bug report on the plugin’s GitHub repository. Alternatively, just fill out the template below and share it here in your reply.

    Describe the bug
    A clear and concise description of what the bug is.

    Steps to reproduce
    Detailed steps to reproduce the behavior:

    1. Go to ‘…’
    2. Click on ‘….’
    3. Scroll down to ‘….’
    4. See error

    Expected behavior
    A clear and concise description of what you expected to happen.

    Screenshots
    If applicable, add screenshots to help explain your problem.

    Environment (please complete the following information):

    • Browser: [e.g. Chrome, Firefox]
    • Plugin version: [e.g. 1.9.1]
    • WordPress version: [e.g. 6.9]
    • PHP version: [e.g. 8.1]

    Server logs
    If applicable, include any server logs that could be related to this issue.

    Browser console logs
    If applicable, include any warnings/errors in your browser’s console. You can open the Console panel in Google Chrome, using ⌘ + ⌥ + J on macOS, or CTRL + Shift + J on Windows/Linux.

    Additional context
    Add any other context about the problem here.

    Thread Starter Stelios Theodoridis

    (@texnologia)

    Hello my friend. From what I’ve seen on the support forum (wordpress, github, etc), there is a serious issue with adding foreign languages ​​beyond English,

    Unfortunately, due to my work, I don’t have time to research the issue. Βecause it is something complex.

    Anyway, you show that you are a serious professional because you are taking the matter seriously.

    For my part, know that i appreciate what you are doing. Because i understand that you love what you do.

    I hope you solve the issue with your plugin at some point.

    Plugin Contributor overengineer

    (@overengineer)

    Hi @texnologia,

    From what I’ve seen on the support forum (wordpress, github, etc), there is a serious issue with adding foreign languages ​​beyond English

    I’m not entirely sure which specific issue you are referring to regarding i18n support. As far as I’m aware, the plugin fully supports translating its modals and displays localized text with no issues.

    There were some quirks in the past related specifically to AI-generated translations, but those have been resolved as of version 1.9.0, which was released in November, 2025.

    due to my work, I don’t have time to research the issue.

    Without concrete details—such as the environment, relevant logs, and clear steps to reproduce the issue—it’s unfortunately not possible to troubleshoot any further.

    If at any point you’re able to share more information, we’ll be more than happy to look into it.

Viewing 3 replies - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.