Website Configuration Error

@wpcork if I look on in the network tab on your website, I can see a request to the rest-api. The request seems to be successful.

Can you check if my visit was recorded? Please also check if you have not excluded your own ip-address or the administrator role from tracking.

Hi Rogier,

Thanks for the fast response and I can confirm that your visit was not captured. I’ve attached a screenshot that I took just now showing zero visits.

Also, I didn’t exclude any IP addresses and the plugin setup is just “out of the box”.

– Donal

@wpcork Can you try the following:

– install the wp debugging plugin
– deactivate, and activate Burst again
– then try in a private browser to visit the site
– Then check the debug log to see if there are any errors, and check if you have any visits.

If you see php errors, please post them here.

• This reply was modified 8 months, 3 weeks ago by Rogier Lankhorst.
• This reply was modified 8 months, 3 weeks ago by Rogier Lankhorst.

Hi Rogier,

Here are the errors that were displayed in the admin area. I’ve left the WP Debug enabled so that you can see the errors on the front end when you visit the site.

WordPress database error: [Specified key was too long; max key length is 1000 bytes]
CREATE TABLE wpwa_burst_statistics ( ID int NOT NULL AUTO_INCREMENT , page_url varchar(255) NOT NULL, time int NOT NULL, uid varchar(255) NOT NULL, time_on_page int, entire_page_url varchar(255) NOT NULL, page_id int NOT NULL, referrer varchar(255), browser varchar(255), browser_version varchar(255), platform varchar(255), device varchar(255), device_resolution varchar(255), session_id int, first_time_visit tinyint, bounce tinyint DEFAULT 1, PRIMARY KEY (ID), INDEX time_index (time), INDEX bounce_index (bounce), INDEX page_url_index (page_url), INDEX session_id_index (session_id), INDEX time_page_url_index (time, page_url) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

WordPress database error: [Specified key was too long; max key length is 1000 bytes]
CREATE TABLE wpwa_burst_summary ( ID int NOT NULL AUTO_INCREMENT , date DATE NOT NULL, page_url varchar(255) NOT NULL, sessions int NOT NULL, visitors int NOT NULL, first_time_visitors int NOT NULL, pageviews int NOT NULL, bounces int NOT NULL, avg_time_on_page int NOT NULL, completed tinyint NOT NULL, UNIQUE KEY unique_date_page_url (date, page_url), INDEX page_url_date_index (page_url, date), INDEX date_index (date), PRIMARY KEY (ID) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

@wpcork Ah, I see the issue. We’ve discovered that this can occur on some hosting environments. We already have a patch ready for this, to be released on Monday, but you can download the latest version from GitHub to get it resolved earlier:
https://github.com/burst-Statistics/burst

Let me know if that helps!

Thanks Rogier,

It’s not urgent, so I’ll wait for the updated version to be issued next week. If it means anything, I also got these pop-up messages…

These are probably related, and should be gone after the next update.

Hi Rogier,

I’ve updated to the latest version of your plugin (1.5.7) but I’m still seeing the error.

It looks like it’s recording visitors and page views, but is there something I can do about the error?

Thanks again,
Donal

• This reply was modified 8 months, 2 weeks ago by wpcork.

Do you mean the errors in the popups?

Can you check if you see any errors in the browser console? And please also check for php errors in the logs.

Hi Rogier,

It’s the original error that I’m seeing…

Due to your server or website configuration it is not possible to track statistics.

There are no errors in the console log and there is one error in the php error log…

[18-Mar-2024 14:04:21 UTC] Cron reschedule event error for hook: rsssl_every_five_minutes_hook, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {“schedule”:”rsssl_five_minutes”,”args”:[],”interval”:300}

Does this help?
– Donal

@wpcork It looks like the test that Burst runs on the endpoint results in a false positive, causing Burst to give this warning.

Burst tries to load the endpoint, if that doesn’t work it tries the Rest API. If that also fails it gives this warning. It is possible that a security plugin, or server configuration is blocking this test request.

As statistics are being tracked, it is a false positive, so you can safely ignore the notice.

The PHP error is not really an error, but rather a warning. It can also be ignored, as it only notifies you of a cron schedule without an action linked to it. It is an obsolete cron schedule from Really Simple SSL, as I manage that plugin as well I’ll include a cleanup on this cron job on the next release.