patlal

I agree with you. I tried to see the sitemap file from the feature tab of the Yoast SEO general settings from another browser and it works perfectly.

I guess that the problem on Firefox is related to an extension or a security parameter or something like that. I should have thought about it before.

Anyway thanks for taking care.

Thanks for your reply.
Actually that’s what I was doing first. Trying to see the sitemap file from the feature tab of the Yoast SEO general settings. It doesn’t work. (I was using Firefox). That’s my problem.

Indeed, if I try to access directly https://scierielabrue.com/sitemap_index.xml from another browser directly (Edge/Chromium browser) I can see 2 sitemaps (post and page).

But still what’s the problem with plugin ?

Hi Tesacu,

I tried everything with Ginger, and also with some others like cookie notice, cookie consent etc, but none of those plugins are working as expected to comply with the GDPR.
If you’re interested here are some working solutions :
– cookieBot
– Onetrust (free only for 1 site)
and of course “tarteaucitron” (https://opt-out.ferank.eu/en/install/). It’s free and opensource and it’s works very well

However, I’m very surprised by the fact that developers of Ginger doesn’t seem interested to comply with the GDPR.

Hello Mark,

Thanks a lot for your advices.

Best,
Patrice

Hello Rogier,

thanks for your reply. I noticed this setting in setting/ssl but I’m asking myself if I have to write the redirection myself or is it done by the plugin ?

If I have to do it myself, I wonder if this code is OK for me ? (knowing that besides the domain nariaconseil.com, I also want to redirect the following domains naria.fr and nariaconseil.fr to nariaconseil.com)

RewriteEngine on
RewriteCond %{HTTPS} !=on
RewriteRule .* https://%{HTTP_HOST}%{REQUEST_URI} [R=301,L]

Best,
Patrice