doffine

@raster02,

great! Your new version indeed fixed the bug in both of our installations, too.

Thanks a lot,
-doffine

Hey @sterndata,

ahh, thanks so much.

Maybe I edited the post in the status of being held for moderation. I don’t remember this for 100%. But perhaps editing of a not published post could be a reason for this. Just as a thought.

Anyway, thanks again!

Greetings,
-doffine

Hey @sterndata,

no sorry, then I must have taken the wrong link out of my browser history. There must be another new thread by myself posted this afternoon.

I got the message to wait until it gets published, but now I cannot find it anywhere.

Greetings,
-doffine

Hi @alekv,

you have fixed the problem mentioned above and as you told me this will be in the next plugin update, too. This is support on premium level. Simply amazing!

I’ll mark this as resolved now.

Respectfully,
-doffine

@rogierlankhorst,

first thanks for coming back.

We don’t want to change the .htaccess even with only one of these lines just to get rid off your plugin’s notification in the Site Health page.

We just want that your plugin doesn’t push this notification into WordPress’ Site Health page.

Or at least it should be possible to switch that off via a setting in your plugin or via a filter.

Again: We are a web agency maintaining 200+ completely different WordPress installations with several hundrets of different plugins. Not a single one of them uses the Site Health page in this way.

To be precise: Every single of our 200+ Site Health pages show the check mark and 0 problems to be solved.

Now every single Site Health page shows just your note and we simply don’t want to upgrade to premium and also we don’t want to add only a single line to the .htaccess. The .htaccess are exactly as they should be. We won’t change them only to silence your plugin.

It would really be more than enough if your plugin would inform the admin on your own plugin pages about these additional possible security features and not to hijack the Site Health page for ad purposes. I would be interested in what wordpress.org staff would say to this behaviour.

So what can we / you do here to solve that. We else really would consider removing your plugin and replacing it.

Greetings,
-doffine

@lorro, you are our personal hero! This works perfectly, we already tested it. Great!

I mark this as resolved now.

Many thanks again for this help and idea,
-doffine

Hello @trsupsys,

meanwhile we are considering to replace your plugin by other solutions, since we as a professional agency in the EU cannot risk to be non-GDPR compliant as this can become very expensive.

We use your plugin in over 200 active WordPress installations, and so we would prefer not to be forced to take this step.

The only thing necessary would be that you would integrate the leaflet.js into your plugin itself instead of loading it from an external CDN (unpkg.com).

Could you please say a “Yes, we can do so, wait until next update.” or a “No, we never will do this.”, so we know what this will be about? For now you didn’t say anything.

Thank you very much,
-doffine