Mehmet

Dear @araz1991,

Thanks for reaching out.

I noticed that the tracker.js file is missing from the page source of your site. This might be the reason your statistics aren’t being tracked correctly.

Since you’re using the LiteSpeed Cache plugin, could you try disabling it temporarily and check if the statistics start showing up correctly? If it works, you’ll need to exclude tracker.js from the list of scripts in the cache settings.

You can also check this documentation for more help:
https://wp-statistics.com/resources/troubleshoot-the-tracker/

Let me know if you need any further assistance!

Best regards,
Mehmet

Dear @tim-reeves ,

We wanted to inform you that the feature you are referring to will be refactored in version 15.

We truly appreciate your collaboration and the valuable input you’ve shared with us so far.

Best regards,
Mehmet

Dear @danisuluh,

Thank you for your messages and for the detailed information.

We’re aware that some users are currently experiencing issues with visitor and online visitor counts, especially after updating to versions 14.13.2 and 14.13.3.

Our development team is actively investigating this issue and working to identify the root cause.

We truly appreciate your patience during this time, and we sincerely apologize for the inconvenience.

In the meantime, it would be very helpful if you could assist us by sharing any relevant error logs from WordPress.

To enable WordPress error logging, please do the following:

1. Open your wp-config.php file
2. Add or update the following lines before the line that says /* That's all, stop editing! */:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

3. Save the file and try to reproduce the issue
4. Then check the file located at wp-content/debug.log
5. Share the contents of that file with us

Additionally, we recommend deactivating your plugins one by one temporarily to check if there’s a conflict with a specific plugin.

If you identify any plugin conflict or errors in the log, please let us know — this would greatly help us resolve the issue faster.

Thanks again for your cooperation and support.

Best regards,
Mehmet

Hi @the5krunner,

Thank you for your message.

To help us understand the issue, could you please enable WordPress debugging and share the error message with us?

Here’s how to do it:

1. Open your wp-config.php file, which is located in the root directory of your WordPress installation ( where the wp-content, wp-includes, and wp-admin folders are. )
2. Open the wp-config.php file and add these lines before the line that says /* That's all, stop editing! */:

define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );

3. Save the file and try to trigger the error again.
4. Then go to wp-content/debug.log and send us the error message.

This will help us fix the issue faster.
Thank you!

Best regards,
Mehmet

Dear @varactu,

Thank you very much for your support and for reporting this issue — we appreciate your cooperation.

To help troubleshoot the problem, please try the following steps:

1. Enable debug logging in WP Statistics and send us the log file so we can review it.
2. Go to Statistics > General > Tracker Configuration, and disable the option “Bypass Ad Blockers”.
   After that, please check if tracking starts working correctly.
3. Please check for any plugin conflicts, especially with caching plugins.

Also, let us know if the custom filters you added in functions.php are still in place.

Looking forward to your update.

Best regards,
Mehmet

Dear @tarikozaslan,

Thank you for bringing this to our attention and for sharing the detailed information.

We appreciate your effort in reporting this warning.

This issue is not critical and should not affect the functionality of your website.

However, we take such reports seriously and have forwarded the details to our development team for further review.

We’ll keep you updated, and this will be addressed in an upcoming plugin update.

Thanks again for your support and for using WP SlimStat.

Warm regards,
Mehmet

Hi @amirer,

Changing the theme usually should not cause any issues with the plugin.
However, it’s still possible that the theme modifications introduced a conflict or affected the plugin’s normal tracking behaviour.

To help us investigate further, could you please confirm whether you are using any caching plugins on your website?
Sometimes, caching can interfere with how changes or plugins behave.

Also, I recommend double-checking the points mentioned in our troubleshooting guide here:
https://wp-statistics.com/resources/troubleshoot-the-tracker/
Please pay special attention to the sections related to caching and potential plugin conflicts.

Looking forward to your reply.

Best regards,

Hi @mountbest,

Thank you for reaching out and reporting this issue.

We are aware of the problem with the migration process.

Our development team is actively working on a fix.

This will be addressed very soon in an upcoming plugin update.

We truly appreciate your patience and understanding.

If you have any further questions, please don’t hesitate to contact us.

Best regards,
Mehmet