reki1801

Send you the URL and the necessary details by e-mail. Found the contact on the linked website from your user profile. I hope you are fine with that!
A working testuser on the website is deleted.

• This reply was modified 4 years, 8 months ago by reki1801.
• This reply was modified 4 years, 8 months ago by Jan Dembowski.
• This reply was modified 4 years, 8 months ago by Jan Dembowski.

Ok, got some bad news. I uploaded the page (fresh install) and the error is still there. Now, we enter the scenario that I will have to tell you the .htaccess/.htpasswd credentials ??
Can I send you a mail? I really don’t want the site to be accessible by the general public right now.

I did not know that it could be due to Xampp. I will reach out to you if uploading the website fixes the error. Thanks for your help so far!

Regarding the login credentials: I’m aware that I shouldn’t share these ?? I meant the temporary .htaccess/.htpasswd login credentials as you need them in order to access the frontend (the uploaded website would still be in the staging phase). Sorry for expressing it in a misleading way.

Currently, it’s an offline build version but I will upload it later to a test server. How can I share the login credentials for the server with you?

Already done that. Used only your plugin and twenty-twenty. The behaviour still persists. You can easily test it by visiting the membership-login-page and hitting the submit button. In my case the page reloads and no error is displayed. Same scenario if you solely enter an username.

Hi,
first of all to clarify that: I’m not involved into the website I was browsing. I am a normal user. Now back to the issue:
My extension allows me to select which scripts are allowed and which aren’t. Therefore, it is possible to allow Google Analytics while disallowing Cookiebot. If the webmaster did choose an Opt-Out and not an Opt-In this would result in Cookies getting set, while neither Information about it nor a possibility to Opt-Out is provided.
As far as I know an Opt-Out is legal regarding the GDPR. But if the admin uses your plugin and chooses Opt-Out there are possible use cases leading to a non-legal behavior which your plugin tries to avoid. You stated that the website owner is responsible to implement Cookiebot correctly so my question is: Is providing the option of an Opt-Out resulting in possible non-legal situations sensible if the whole goal of your users is to avoid these? In my opinion with this setting a situation could arise in which your clients are entitled to pursue remedies against you (if cookiebot is setup correctly while using your Oup-Out setting).

As previously stated, I am definetly willing to admit possible misunderstandings on my side. I wish you a nice week-end and I’m looking forward to your response!