Antonio Candela

Hello @digitaltrade ,

Thank you for reaching out. Version 7.3.1 caused many issues for various users and ourselves, so we stopped the release and found the issues. We were trying to comply with the new way of loading translations in WordPress, implemented with version 6.7.x. This has been officially addressed in version 7.3.2, which I see you have already installed on your site.

We are really sorry for what happened in the last couple of weeks. Now, everything should be resolved. If you have any particular issues or inquiries, please reach out to us on our ticketing system available on complianz.io. Due to the WordPress forum guidelines, premium users are not allowed to ask for support on the WordPress page. Therefore, I will close this thread.

Hope this helps.

Best regards, Antonio

Hello @talesf ,

Thank you for reaching out. I’m sorry to hear about the issue. If you keep getting the error even after inserting the file in the folder, you need to insert the value inside the database. This will solve the issue upstream. Please follow these steps:

1. Access your database, specifically the wp_options table.
2. Create the field cmplz_geo_ip_file and set its value to the directory of the MaxMind file (GeoLite2-country.mmdb) in your WordPress installation. If you have difficulties finding the directory, you can find it in the other DB field called cmplz_geoip_import_error located in wp_options.

Regarding the possibility of modifying the capabilities of the GeoIP, I’m sorry but it is not possible, as they are hardcoded to Complianz to ensure compliance with specific regions.

Additionally, due to forum guidelines, for premium plugin inquiries, please reach out to us on our ticketing platform available on our site. Therefore, I will close this thread.
Despite everything, I hope my answer helps you.

Best regards,
Antonio

Hello @vasavi ,

I’m really sorry for the inconvenience. We are working on resolving this issue in the next release of the plugin, which should be available very soon. We also wrote an article on our website about it: https://complianz.io/about-function-_load_textdomain_just_in_time-was-called-incorrectly/.
Please note that this is a notice, not an error.

Even though the current version is not tested for version 6.7.x, it will work but will show the notice you mentioned, and the legal documents and banner will appear in English due to the latest changes in the WordPress environment.

We’d appreciate it if you could re-evaluate your review after the release of the new version.

Best regards,
Antonio

Hello @utnalove ,

We made sure to answer you this morning. Unfortunately, we are being overwhelmed with requests and quite a backlog has been created afterwards. We’ll make sure to get everything back on track very soon.

Please feel free to reach out again, we are at your disposal.

Best regards.

Hello @utnalove ,

My apologies, your ticket must have fallen under the 1st level queue, which is quite long. Could you please re-send the ticket, linking this thread so I can recognize you?

Thanks in advance.

Hello @joesy ,

We’re truly sorry for the inconvenience caused by the recent update of our plugin and WordPress. Unfortunately, this update has led to more issues than we anticipated, and for that, we are deeply sorry. We underestimated the issue, resulting in delays in fixes and updates.

At the current state, an easy and fast fix would be to roll back to the previous version of WordPress, 6.6.2.

Please rest assured that we are doing everything we can to resolve these issues as soon as possible.

Hello everyone,

We sincerely apologize for the inconvenience caused by the latest update of our plugin and WordPress. Unfortunately, this update has created more problems than anticipated, and for that, we are deeply sorry. We underestimated the difficulties, which has led to delays in the fixes and updates. We are working to the best of our abilities to resolve these issues in both the Premium and free versions.

We appreciate your patience and understanding. We will keep you updated on our progress and are committed to restoring the normal functionality of the plugin as soon as possible.

Thank you for your trust and continued support.

@padipaolo , @wriper , @joesy , @profilodigitaleweb , @ilgrizly , @mmazhari

Hello @hebhansen ,

Thank you for providing the URL. The banner on svalinnart.com shows on my end (screenshot here). What I see, though, is that you are loading the entire JavaScript through LightSpeed. You might exclude Complianz from it. You also might just need to clear the cache on your browser or WP to see the banner on your end.

To exclude Complianz from LightSpeed, please follow these steps:

1. LiteSpeed Cache > Page Optimization > [8 Tuning] > JS Excludes and/or JS Deferred / Delayed Excludes and exclude:
   complianz
   cmplz
   
2. LiteSpeed Cache > Page Optimization > [9 Tuning – CSS] > CSS Excludes / UCSS File Excludes and Inline and exclude:
   cmplz
   complianz-gdpr/assets/css/*
   complianz-gdpr/cookiebanner/css/*

Regarding the WordPress 6.7 error, we are working on releasing an upcoming fix as soon as possible. I’m really sorry for that.

Please let me know if this helps. Looking forward to hearing from you.