skirridsystems

To be honest I’d not heard about the closure until now, which is why the documentation hasn’t changed

I found this notice added by the WP plugin team in 2.9.1.1

We would like to inform you that several plugins from the author “essentialplugin” have been reported by the community as not compliant with the guidelines. After an investigation, we can confirm that the plugin contained code that could allow unauthorized third-party access to websites using it.

In response, we have taken immediate steps to close the plugin in the ww.wp.xz.cn Plugins directory and release an update that already tried to remove affected code from your website. Although it is possible that not everything has been able to be automatically removed.

Specifically, this plugin downloaded code from analytics.essentialplugin.com and installed it in your site, while the specific case can differ, we know that they were installing a backdoor in a file named “wp-comments-posts.php” that looks closely to the core file “wp-comments-post.php”. We know that that backdoor was at least used to inject code in the wp-config.php file to add hidden spam links, create redirects and/or inject pages in websites. Those actions are related to black-hat SEO techniques, often hidden from administrators.

While our update attempted to remove the backdoor automatically, it cannot confirm that it was fully eliminated. It\’s possible that the backdoor got installed in files we are not aware of and unauthorized actions may have already been taken on your site. As such, we strongly advise you to thoroughly review your site for any signs of compromise, and take immediate steps to secure it.

So I would say no, not safe!

Thanks for the update, it was the single item in the array that was causing the test to miss. I’ll get the fixed version released soon.

And no, nothing you’ve done wrong. Wrong user data is expected to cause an incorrect display but it should never be able to cause a site crash.

Thanks for the report. Invalid data definitely should not crash the website! There is some sanitisation but evidently not enough. I will look into this.

I had been thinking about moving the marker file interpreter into the client side Javascript, which would also reduce server load, but I’ve not had time to do it yet.

Sorry, meant to add the page is here:

https://skirridsystems.co.uk/os-datahub-maps/adding-markers/

Apologies, I wrote a reply and must have missed hitting the submit button.

You cannot use HTML in markers directly in the shortcode due to the way WordPress handles quoting and escaping. You’ll need to use a marker file.

https://skirridsystems.co.uk/os-datahub-maps/adding-markers/#markers-html

Maybe a conflict with WP Google Maps? Try disabling other plugins one at a time. Anyway, I’m pretty sure this does not originate within the OS Maps plugin or Leaflet.

Where you specify a colour it uses the markerPath passed in. You do that for one of your locations (Farmborough & High Littleton) and that marker does indeed appear. All the others are using the Leaflet default marker, which is being referenced incorrectly.

But that post is 8 years old. I don’t see any issues relating to this in the current release on GitHub.

And it only seems to be happening on your instance. I’ve been using that version of Leaflet since Jan 2024 and no one else has come up against this