Hessel de Jong

Hi @louise1970,

If the problem is still not solved please let me know and please provide me some information.

I’ll close this issue for now, but feel free to re-open ??

Kind regards,
Hessel

Hi @pbedouk,

It could be that enabling debugging reset the database install, but I’m not 100% sure!

Happy to hear your issue is resolved though!

Kind regards,
Hessel

Hi @pbedouk,

I suspect some database files might be missing. Can you enable debugging in WordPress and share the relevant log entries. You have two options:

1. Use the WP Debugging Plugin (recommended for ease of use)
2. Manually enable debugging by editing wp-config.php

Option 1: Use the WP Debugging Plugin

1. Install and activate the WP Debugging plugin.
2. Visit the Burst Dashboard.
3. In the top admin bar, hover over “Debug Quick Look” and click “View File Raw”.
4. Copy the contents of the debug log and share them with us.

Option 2: Manually Enable Debugging

1. Open the wp-config.php file in the root of your WordPress installation.
2. Add the following lines before /* That's all, stop editing! Happy publishing. */:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
define('SCRIPT_DEBUG', true);

3. Save the file.
4. Visit the Burst Dashboard.
5. Locate the debug.log file inside the /wp-content/ directory. Open it with a text editor and share any relevant error messages with us.

Important for Live Sites: Once you have shared the errors, disable debugging by removing the added lines in the wp-config.php file or disable the WP Debugging plugin. This is to prevent performance or security issues.

Let us know if you need any help!

Kind regards,
Hessel

Hi @kvncrll,

This is most likely because Burst currently excludes bounces from all data. If you add the number of bounces to the number of visitors, the totals should match up.

We made this decision early on, but we realize now it wasn’t the best choice. In the near future, we’ll update the Dashboard to include bounces by default. You’ll then be able to filter your data to view it with or without bounces, or simply show everything together.

Kind regards,
Hessel

Hi @louise1970,

Thanks for your message. Could you maybe provide the following:
– Browser of the customer
– Device of the customer
– User role of the customer

Kind regards,
Hessel

Thank you for the review Lane! We appreciate it and are always here to help! ??

Hi @ilariastrazzulla,

Do you still need help? If so, please reply here.

I’ll close this issue for now, but feel free to re-open! ??

Kind regards,
Hessel

Hi @mariogovoni,

Thanks for notifying us! I will check if we can solve the issue, so other don’t run into this issue and so you can enable the setting again!

If you’re enjoying Burst and feel like we’ve been helpful, we’d be super grateful if you could leave us a quick review. As a small business, every bit of feedback and support goes a long way in helping us keep improving.

You can leave a review here: https://www.ads-software.com/support/plugin/burst-statistics/reviews/

Kind regards,
Hessel

Hi @marcoslmdb,

We can’t answer questions about the paid plan on the wp.org forums. You can send us an email: support[at]burst-statistics.com.

That being said, the short answer is no. But please share over email what you would like to see.

Kind regards,
Hessel

Hi @mariogovoni,

To help us diagnose the issue, please enable debugging in WordPress and share the relevant log entries. You have two options:

1. Use the WP Debugging Plugin (recommended for ease of use)
2. Manually enable debugging by editing wp-config.php

Option 1: Use the WP Debugging Plugin

1. Install and activate the WP Debugging plugin.
2. Visit the Burst Dashboard.
3. In the top admin bar, hover over “Debug Quick Look” and click “View File Raw”.
4. Copy the contents of the debug log and share them with us.

Option 2: Manually Enable Debugging

1. Open the wp-config.php file in the root of your WordPress installation.
2. Add the following lines before /* That's all, stop editing! Happy publishing. */:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
define('SCRIPT_DEBUG', true);

3. Save the file.
4. Visit the Burst Dashboard.
5. Locate the debug.log file inside the /wp-content/ directory. Open it with a text editor and share any relevant error messages with us.

Important for Live Sites: Once you have shared the errors, disable debugging by removing the added lines in the wp-config.php file or disable the WP Debugging plugin. This is to prevent performance or security issues.

Let us know if there is anything in the debug log!

Kind regards,
Hessel

Hi @ilariastrazzulla,

Does this issue just happen on your homepage?

To help us diagnose the issue, please enable debugging in WordPress and share the relevant log entries. You have two options:

1. Use the WP Debugging Plugin (recommended for ease of use)
2. Manually enable debugging by editing wp-config.php

Option 1: Use the WP Debugging Plugin

1. Install and activate the WP Debugging plugin.
2. Visit the your website in an incognito window and be sure to (temporarly) disable blocking your own IP in the settings.
3. In the top admin bar, hover over “Debug Quick Look” and click “View File Raw”.
4. Copy the contents of the debug log and share them with us.

Option 2: Manually Enable Debugging

1. Open the wp-config.php file in the root of your WordPress installation.
2. Add the following lines before /* That's all, stop editing! Happy publishing. */:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors', 0);
define('SCRIPT_DEBUG', true);

3. Save the file.
4. Visit the your website in an incognito window and be sure to (temporarly) disable blocking your own IP in the settings.
5. Locate the debug.log file inside the /wp-content/ directory. Open it with a text editor and share any relevant error messages with us.

Important for Live Sites: Once you have shared the errors, disable debugging by removing the added lines in the wp-config.php file or disable the WP Debugging plugin. This is to prevent performance or security issues.

Let us know if you need any help!

Kind regards,
Hessel

Hi @mobilenasim,

Thanks for the feedback! Did you want to give us a review instead of opening a support request? You can leave a review here: https://www.ads-software.com/support/plugin/burst-statistics/reviews/#new-post

It would be much appreciated!

Kind regards,
Hessel

Hi @pissenlit,

Are other WordPress emails, such as password reset emails, being received successfully?
If those emails are arriving, but Burst Statistics emails are not, it could indicate an issue with how your email is set up for sending notifications.

To resolve this:

1. Check Your Spam Folder – Sometimes, emails may be incorrectly marked as spam.
   Verify Your Email Settings – Ensure that the email address set in WordPress > Settings > General is correct.
2. Test Email Delivery – You can install an email logging plugin (e.g., WP Mail Logging) to check if the emails are being sent from WordPress but not reaching recipients.
   
3. If the above steps do not help, please try these two steps: Check Hosting Restrictions – Some web hosts block or limit outgoing emails. Contact your hosting provider to verify if any restrictions apply.
4. Use an SMTP Plugin – WordPress relies on PHP mail(), which can be unreliable on some hosting providers. Consider using an SMTP plugin like WP Mail SMTP to improve email deliverability.

If you’ve confirmed that other WordPress emails work but Burst emails do not, let us know, and we can investigate further.

Kind regards,
Hessel

Hi @checksumdk,

Thanks for your feedback!

We’ll consider sorting devices by percentages. I think it could be nice.

Remembering the filters and sorting is on my wishlist as well. Through browser URL and also saving it to the user account or browser. I expect it to be released in summer.

Kind regards,
Hessel

Hi Lane,

Weird!

I can’t access the debug.log. Can you send it in an email to me at support[at]burst-statistics.com?

I’ll help you fix it over email ??

Kind regards,
Hessel