Hi Marjon,
I’ve checked your website and the tracking seems to work. Could you describe what exactly is not working? Is there no data in the dashboard?
Please let me know and I’ll be happy to help!
Kind regards,
Hessel
Hi Hessel,
Thanks for checking our website. That is correct, there no data in the dashboard. I installed Burst a few month ago.
Kind regards,
Marjon
Hi Marjon,
That is strange. I’ve checked again, it seems to me there is no tracking request executed. Our tracking script does not seem to work properly, but is loaded properly and isn’t throwing any errors.
- Can you check if there are any errors in the Burst Dashboard?
- Could you try and disable cookieless tracking? Make sure also to disable any caching you’ve enabled.
Kind regards,
Hessel
Hi Hessel,
1.There are no errors in the burst dashboard. But in the underwaterscreen on the backend statistic site, I saw two errors, I don’t know whether they have something to do with it. (i replaced the domainname with mydomain.nl)
index.js?ver=4ad96c021f4addae4b27:382 Uncaught TypeError: Cannot read properties of undefined (reading ‘menu_items’)
at Zv.getDefaultMenuItem (index.js?ver=4ad96c021f4addae4b27:382:577759)
at index.js?ver=4ad96c021f4addae4b27:382:576561
getDefaultMenuItem @ index.js?ver=4ad96c021f4addae4b27:382
(anoniem) @ index.js?ver=4ad96c021f4addae4b27:382
jquery.min.js?ver=3.6.4:2 POST https://mydomain.nl/wp-admin/admin-ajax.php 403
2. I did disabel cookieless tracking just now. I don’t use any caching plugin. So maybe that will help?
I have another site with the same problem. That website did not have the same error as I mentioned under 1.
Kind regards,
Marjon
Hi @marjontas,
I see a 501 error appearing on the Burst Statistics endpoint on the attached website, which I would expect to be the related to this behavior.
Could you check whether the burst-statistics-endpoint.php file exists in the “root” folder of your WordPress Installation? That folder is typically called ‘public_html’.
In addition, something else you could try is re-saving the permalinks in WordPress. Navigate to Settings > Permalinks, don’t make any changes to these settings, and just press Save once. And then check if the behavior has been corrected once more.
Let us know if there are any further updates, we’d be glad to assist further.
Kind regards, Jarno
Hi Jarno,
Thanks for your answer and my apologies for my late response.
The burst-statistics-endpoint.php file exists in the “rootfolder of my WordPress Installation. I just now resaved the permalinks, and I will check in a few days whether that will solve the issue.
Best regards,
Marjon
Hi @marjontas,
We are interested to hear if you managed to resolve the issue.
Thank you in advance for your response!
Kind regards,
Leon
Hi Leon,
Sorry for my late response. No, the issue is still unresolved. I just checked the statistics on the site. And there are still no visitors shown.
Do you have another suggestion?
Best regards,
Marjon
Hi @marjontas,
The 501 error still appears on your website and I think this is what causes the tracking to fail.
We would be glad to assist further with the described issue, but would require some further information/logs that can point us in the right direction.
In order to obtain these logs, you can enable Debugging on your WordPress site (such as by activating a plugin like WP Debugging).
And when you have Debugging enabled on WordPress, try visiting a number of pages on your website so that the error is triggered again; which should then result in more details about the error being saved in a debug.log file (which can typically be found in the /wp-content/ directory of your website).
You may contact us via support(at)burst-statistics.com to attach that debug.log file, and you can also ask us any questions that may arise about the debugging process described above (even in Dutch, if preferred).
Kind regards, Jarno
-
This reply was modified 2 years, 11 months ago by
Jarno Vos.
