Rogier Lankhorst

To explain why I think this is the issue: since a few updates, the integration in Complianz has become more strict, and tracking will get blocked if you have selected “ask consent for statistics”.

You can also try switching to cookieless tracking in Burst, this will prevent tracking from being blocked.

@nickdgreen can you try what happens if you deactivate Complianz?

@vgstef you can use the same solution, it’s the same plugin.

@wpgerd I’m not an expert on WP Optimize, but I just installed the plugin to check. It sounds like you used the correct method: When I select ‘minify’, I get a ‘settings’ option behind that toggle. Or you can go to ‘minify’, ‘javascript’. Then you see a text area where you can insert the string ‘burst-statistics’, to exclude from minification.

If you used the option to ‘Merge tracking settings and script’, you need to exclude /burst/js instead. Maybe that was the issue?

@nickdgreen do you also use WP Optimize? Can you share your domain so we can take a look? It’s probably better to start a separate thread, as it might have a different cause.

@mplanet5 I see you have this error in combination with the Gutenberg plugin. Do you also have this error with the Gutenberg plugin disabled?

As Gutenberg is a beta plugin, it sometimes has experimental features which might cause issues.

I tried installing Gutenberg, but didn’t encounter any issues.

Hi @mplanet5,

An error in the Gutenberg files does not necessarily mean it has something to do with an issue in Burst you might have. I assume you have a problem loading the Burst dashboard? Can you give a bit more details about the issue you are experiencing?

Can you check if it helps when you deactivate WP-Optimize? If so, you might need to exclude the string ‘burst-statistics’ from the optimization.

Glad that helped! In WP Rocket, settings, file optimization, you probably have something like lazy loading or defer enabled. You can add the ‘burst-statistics’ string there to get it excluded. They have some help links there to help you get started.

@kazerniel Thanks for reporting your issue. The statistics report that your website can send you is a new feature in the plugin, which is why you didn’t receive it before. It sounds like the javascript in your dashboard is not updated yet, can this be cached in your browser perhaps?

Please try to log in in a private window, to see if that resolves the issue.

I’ve just tried this with a fresh install from the repository, and the email settings field works fine there.

You can always switch to “today” or, check the live visitors overview. Then visit your site in private mode. The hits should then show up.

But as it’s been a few hours now, you should see some visits now if it was caused by javascript optimization.

Can you try what happens if you deactivate WP Rocket? If the hits return, please exclude the string ‘burst-statistics’ from defer and lazy loading to see if that resolves it.

Can you share your domain so we can take a look?

Hi @tobaco,

Thanks for reporting the issue. The testing only occurs every 10 minutes if the last test fails: if the test succeeds, the interval is 24 hours.

To prevent this from happening every 10 minutes, I’ve added a filter here:
https://github.com/Burst-Statistics/burst/tree/add-time-between-endpoint-test-filter

You can install it using the green button, and download the zip file. The deactivate your current Burst plugin, and install this one like a normal plugin.

If you add the following snippet as a mu-plugin you can override the test interval:

/**
 * Override the default time between tests, which is 10 minutes when the last test returned an error, and 24 hours otherwise.
 * 
 * @param int $time_between_tests //the time between tests in seconds
 * @return int
 */
function burst_time_between_tests(int $time_between_tests ): int
{
    return WEEK_IN_SECONDS;
}
add_filter( 'burst_time_between_tests', 'burst_time_between_tests' );

This will be merged in one of the upcoming releases, it will be mentioned in the changelog.

Let me know if this helps!

@mplanet5 are there any other errors you can see in the console? Can you post the entire error here, including the character and line number?

Are you updated to the latest version of Burst? And is the entire page blank, or just a part?

If you install the WP Debugging plugin, do you get any PHP errors in the debug log?

Any information might help. As I can’t reproduce it myself, I have to deduce the issue purely based on your info.

@tobaco this is the filter for all REST url’s, so Burst should pass through it as well. Could this be caused by caching?

Not sure why other plugins don’t have this issue, but it could be they already have a fix in place, or they don’t use the wp.apiFetch method? The REST route is declared with standard WordPress code.