Rogier Lankhorst

It sounds like not all .js files are there on your server. When I install the plugin on a fresh environment there are no issues. Can you try to remove the current plugin, and install a fresh copy, to make sure it’s not caused by missing files?

@ncwebmaster can you share your domain so we can take a look? You can also send your domain to support(at)burst-statistics.com in case you don’t want to share it here.

Hi @lidok33,

Can you install the WP Debugging plugin, then load the Burst Dashboard, and then check in the debug log (accessible to a menu option in the top bar) if there are php errors?

If so, please post them here so I can take a look. Possibly the database tables are not created correctly for example.

@henkbekker Please try this branch:
https://github.com/Burst-Statistics/burst/tree/option-to-dismiss-non-error-notices

which will be included in the next update most likely.

wp-consent-api/assets/js/wp-consent-api.js or
wp-consent-api/assets/js/wp-consent-api.min.js

just excluding wp-consent-api should be enough.

If something is not working correctly, it’s best to contact the Google Site Kit support team. They have built the integration from their end, and tested it successfully as well. Nothing has changed on this side since.

I have created a branch here:
https://github.com/Burst-Statistics/burst/tree/option-to-dismiss-non-error-notices

You can deactivate your current plugin, then download this version (download zip using the green button). Then upload it as a normal WordPress plugin.

Then you will see a new option under ‘advanced’ to dismiss all non-error notices.

Let me know if that is what you’re looking for.

@3cstudio I think you’re referring to the +1 in the Burst menu, not in the plugins overview?

For example, on my own website this plus-one refers to a new feature in the free plugin, regarding email reports. So in this case it’s not about upgrading to pro, but about a new feature in the free plugin.

After clicking the ‘x’ on the notice the plus one is gone.

I’ll add a new setting which allows to prevent any notifications from being added, would that resolve the issue for you?

@kevinburkholder sorry for my late response, vacation came in the way.

In general I think it’s best to call WordPress functionality on a WordPress hook: that ensures that all functions are loaded. So in this case, you could run your code on an ‘init’ or ‘plugins_loaded’ hook, which should solve your issue.

For this reason I always hook the instantiation of my code into the plugins_loaded hook. Using priority 9 ensures that if any code runs on the plugins_loaded hook with default priority (10), everything is already loaded. It also ensures that the WP Consent API in turn also can call all WordPress functions, as we may assume it’s all loaded now.

Hope this explains!

Hi @123nadav,

You can exclude scripts that include wp-consent-api.

Hope this helps.

As there hasn’t been an update recently, it’s most likely that something went wrong on your server when unpacking the zip file.

I would recommend to go to your site using ftp or a file manager, then delete the burst-statistics folder from wp-content/plugins.

Then you can install a fresh copy from the repo.

Let me know if that helps!

@dariuserdt I have created a snippet:

function burst_exclude_post_meta($meta_keys) {
    $meta_keys[] = 'burst_total_pageviews_count';
    return $meta_keys;
}

add_filter('duplicate_post_excludelist_filter', 'burst_exclude_post_meta');

Which you can use to exclude the Burst post meta from the duplication tool. It will be integrated in the plugin in one of the coming releases.

The post meta is copied by the duplication tool, not by Burst itself. So while I understand your remark, we can’t fix the issue in Burst, we’d have to find a way to fix this in the duplication tool.

What tool do you use? We might consider creating a fix for the largest in the repo. On the other hand, maintaining such integrations are often very time consuming.

If you are looking for a solution that does not use cookies, you can enable the cookieless option in Burst:

https://burst-statistics.com/understanding-cookieless-tracking-and-fingerprinting/

No data is collected in any way. This plugin only functions as a communications tool between your consent management plugin, and plugins or services that require consent. The purpose of this plugin is to offer developers a standardized method to check if consent is given for a certain category.

Oh I see, no, currently this is not possible. We will look into that, thanks for your suggestion.