larus-argentatus

Oh hang on, the delete plugin must have completed that side, but only partially the plugin as it was still showing in the list.

the words: deleting… were showing.

It deleted OK the second time.

there might be an issue there with a larger db / lots of tables? I don’t know.

Thanks again

Hi Rogier

That’s working as expected now.

Thank you very much for your kind help.

??

Well thanks again for the prompt action on this. The pop up now appears on deactivation and from a quick scan the tables are now empty. ??

On deletion all the tables remain, however, so was there an option that I missed on deleting the plugin?

Thanks as ever for the rapid response, Rogier. Works partially, but only on the selected subsite and some tables remain (suffice to say I have too many to process manually) … it would great if deactivation had the same pop up option as on subsites and subsequent plugin deletion deleted all the underying tables, which could of course be optional for those temporarily deactivating. Thanks again.

A manual resync did it, I was not even aware that was an option!

Thanks

After a few days, I thought this would sort itself out. Now there are no stats at all. Neither in the backend of the website nor the mobile app, which reports an unhelpful “An error occurred”.

@tamirat22 can you please have another look? Were they merged onto the current website?

Thanks!

??

Mea culpa! I’ve no idea why that was added, but I should have looked there first!

Thank you for the rapid reply

??

That obviously did the trick, my bad!

??

I am assuming there is no easy way to remove the entries that are empty e.g. Report: {Reporting}. I can probably replace the blanks with a “Missing” before I export.

here you go

https://connectingdunbar.org.uk/files/2023/10/Near-misses-with-sane-variable-name.json

OK, I see. Thanks.

This json was the output of a map based questionnaire via a third party service (Maptionnaire), so I have exported a json from QGIS instead as their shape files are less complicated. This should in theory resolve the issue. My shortcode now

[leaflet-geojson src="https://connectingdunbar.org.uk/files/2023/10/Near-misses-with-sane-variable-name.json" circleMarker color=red]
<b>What happened?</b>: {Whathappen}<br>
<b>When?</b>: {When}<br>
<b>Detail</b>: {Detail}<br>
<b>Report</b>: {Reporting}<br>
{responId}[/leaflet-geojson][geojsonmarker property="Detail" icondefault=blue iconprops="purple,orange"  values="I did not report the incident to the police,I reported the incident to the police" groups="I did not report the incident to the police,I reported the incident to the police" disableClusteringAtZoom=16][fullscreen][zoomhomemap]

However, this is classifying everything as “other” … nearly there, hopefully an error on my part?

A supplementary question, which I tag on here as it relates to the use of nested variables.

I would like to display coloured and grouped markers, as per the detailed examples decribed here: https://leafext.de/en/marker/geojsonmarker/

I can get this to work nicely in another example, but the properties are simply structured: https://connectingdunbar.org.uk/map-based-consultation/crash-data/

I cannot see how to get the variable for property

property=popup[3]response

obviously doesn’t work

[leaflet-geojson src="https://connectingdunbar.org.uk/files/2023/10/Drop-a-pin-where-you-had-a-near-miss.json" circleMarker color=red]
<b>What happened?</b>: {popup[0]response}<br>
<b>When?</b>: {popup[1]response}<br>
<b>In detail</b>: {popup[2]response}<br>
<b>Report</b>: {popup[3]response}<br>
{respondentId}[/leaflet-geojson][geojsonmarker property=popup[3]response icondefault=blue iconprops="purple,orange"  values="I did not report the incident to the police,I reported the incident to the police" groups="I did not report the incident to the police,I reported the incident to the police" disableClusteringAtZoom=16][cluster][fullscreen][zoomhomemap]

I’ve tried some alternatives but run out of ideas …

That’s pretty much exactly what I wanted to do, and v useful to know how to get into the nested popup.

Also thanks for the heads up about the CORS violations, I had not noticed them!

Thanks

If on a multisite network pop the code into a new plugin e.g. disable-jetpack-blaze.php and place it in the /mu-plugins for instant satisfaction

<?php
/**
 * Plugin Name: Jetpack Blaze Disable
 * Plugin URI: https://example.com/
 * Description: Disables the Jetpack Blaze module.
 * Version: 1.0.0
 * Author: Your Name
 * Author URI: https://example.com/
 * License: GPL2
 */

add_filter( 'jetpack_blaze_enabled', '__return_false' );

This code does two things: it creates a new WordPress plugin and adds the filter to disable the Jetpack Blaze module.

• Save the file.
• Upload the file to the “mu-plugins” folder on your WordPress site. The “mu-plugins” folder is typically located in “wp-content/mu-plugins”. If the folder does not exist, you can create it.
• Once the file is uploaded, the filter will be activated and the Jetpack Blaze module will be disabled.

The official line seems to be you cannot, which is a pain as clients are confused.

However on reddit I found that there is a filter to remove it:

add_filter( 'jetpack_blaze_enabled', '__return_false' );

which seems to do the trick. Add the line at the end of your functions.php child theme file.