Mostafa Soufi

Yes, that’s absolutely the cache issue, since the parameters name are changed, I’d prefer to try to clear your cache (CloudFlare or WordPress)

Best

Upon reviewing the source code of your website, I noticed that the file tracker.js?ver=14.9.2 is not updated as expected, likely due to caching issues.

Are you using a caching plugin? If so, please try purging the cache. Alternatively, you can enable the “Bypass Ad Blockers” option in the settings to resolve this issue.

Best

Have you checked the response code mentioned in the document?

Please provide your website URL here. We’ll review it and let you know what the issue is.

Yes! {"status":true} in the response.

Sorry, here is the correct filter name. wp_statistics_request_signature_enabled

add_filter('wp_statistics_request_signature_enabled', 'disable_request_signature');

function disable_request_signature($enabled) {
    return false; // Disable signature verification
}

Alright, I see the response {"status": false, "data": "Invalid signature"} which means your request payload contains a nonce, which has been deprecated and replaced with a signature as we mentioned in the Troubleshoot the Tracker previously.

For more information on this change, please refer to the following resources:

• How to Track Visitor Statistics in Headless WordPress Themes Using WP Statistics
• Managing Request Signatures

To generate the correct signature, follow the instructions provided in the documents linked above. Alternatively, you might prefer to clear your cache or disable the signature verification.

You can disable the signature by adding the following code to your functions.php file:

add_filter('request_signature_enabled', 'disable_request_signature');

function disable_request_signature($enabled) {
    return false; // Disable signature verification
}

Best.

Hello,

Is the cache enabled in your WordPress site? If so, please clear it. Additionally, please refer to our troubleshooting guide at this link for detailed instructions on how to resolve issues with the tracker.

If you need any further assistance, feel free to let us know.

Best regards,

Could you please update to the v14.9.3 and let me know to review your website? I have to check the requests on your website in the latest version of plugin. @varactu

Thank you for testing. Yes, that’s correct.

Could you please inspect the source of the notices in the new version of the plugin? I want to ensure that the notice functionality is indeed new and not from an older version.

Sorry for the late reply. w’ve been busy working on tracker.js and improving the development version. You can check the latest changes here.

In this change, we’ve changed the request type from GET to POST to solve caching issues and improved IP detection. However, It would be great if someone could test these and let me know how it goes.

In the case of the Tracking Mode, I know server-side tracking is important to you, but please read our latest blog post. It might help address your concerns: Deprecating Server-Side Tracking in WP Statistics 15.

Best

The source you referred to is relevant for versions before v14.8, as you can see in this line of the changelog: See Changelog and not sure why your notice functionality is not new. how do you update the plugin? via CLI? manually or via admin?

If I can disable the messages, I will update.

Checkout the option “Disable Inactive Essential Feature Notices” in the settings, then update the plugin to the latest version.

What is your current WP Statistics version? ??

Alright, I am convinced that some notices need to be reconsidered. In the new changes, all notices will only be displayed to users who have the manage_options capability and some notices will be restricted to plugin pages only.

Also, I forgot to mention that you can disable all notices by enabling the “Disable Inactive Essential Feature Notices” option in the settings. @mellitan

PPS: the update of V. 14.9.2 was followed by this error:

Regarding the error you mentioned, I think it happened during the upgrade. It should be working fine consistently.

but it always reappears when a page is changed or reloaded.

Weird indeed. The dismissed notices are stored in the options, meaning they won’t be displayed in subsequent visits, as you can see here.

Can you tell me does the close/dismiss button has the url? the link should be something like this https://capture.dropbox.com/Y4F9D6eoF12leIpD

Best

• This reply was modified 3 months ago by Mostafa Soufi.

For the website https://www.varactu.fr/, I noticed something unusual. The LazyLoad feature is affecting all requests, not just images. As a result, requests are not being executed immediately after the website loads, causing a delay. You can see what I mean in this video I recorded: https://capture.dropbox.com/M70tsnKjyJHRqVuo.

Do you know why this is happening? @varactu

Also, can you please check this on your website? @spielo

Neither deleting the cache again nor repeatedly closing the message has resulted in it being permanently hidden. That was also the message of my first post.

I am quite certain that the notice should disappear when clicking the dismiss/close button, Please refer to the video I recorded for reference → https://capture.dropbox.com/jSWGP8cwiCbNbHOD

Nevertheless, please make absolutely sure that the message is no longer displayed after closing once. It is also generally not very helpful.

Can you record a video and show the issue in the video? @zappob

When will that be? For now, nothing about this question is “resolved.” It continues to be a major annoyance that interrupts workflow, and I’m about to permanently disable/uninstall the plugin because of it.

This change is pushed 1 day ago ?? @mellitan

https://github.com/wp-statistics/wp-statistics/commit/52695c7ea182064a88a50c030ddc6671032f0c79?diff=unified&w=1