Notifal: Active Versions chart frozen at v1.3 for 5 months despite confirmed 2.x installs

[hosseinalehabib]

Hi,

I previously corresponded with the plugins team by email about this plugin's stats (​https://wordpress.org/plugins/notifal/advanced/), and I want to follow up with a specific, time-based observation that I think is worth a second look.

Background (brief):
Notifal (slug: notifal) was rewritten from 1.x to 2.0.0 in February 2026, main plugin file renamed from Notifal.php to notifal.php. Current version is 2.4.0, confirmed correct on trunk and via the API. The plugins team confirmed by email that pre-rewrite sites may still be deactivated due to the old basename, but also confirmed that fresh installs after the rewrite should not be affected by that basename issue at all.

The new data point:
It has now been five months since the rewrite. We have 15+ confirmed sites actively running 2.x, and "Active installations" shows 40+ with fewer than 10 deactivations recorded since the rewrite. Despite this, the "Active versions" chart still shows exactly 100% on version 1.3 and 0% on any 2.x version, not 1%, not 5%, an absolute zero, completely unchanged in five months.

In the previous email correspondence, the guidance given was that "the public stats are still derived from update-check reporting" and would "adjust over time as sites continue to check for updates." Five months of continuous update-check traffic from 2.x sites is, by any reasonable measure, enough time for that adjustment to show some movement if the underlying data pipeline were functioning normally for this plugin. A flat, unchanged 0% over that entire period suggests something specific to this plugin's stats record is stuck, rather than this being a normal lag that resolves with more time.

What I'm asking:
Given that the "wait and it will self-correct" timeline has now clearly elapsed without any change, is there:

Any further diagnostic that can be done on the stats pipeline specifically for this plugin's slug/record?
Any known historical case of a plugin's version-stats record getting permanently stuck after a main-file rename, and if so, was there ever a resolution (even an unofficial one)?

We're a very small team who put everything into this product, and active installs are the one external signal we have to gauge whether we're actually reaching people. A flat, unmoving 0% for five months on a stat WordPress.org itself describes as something that should adjust with ongoing update-check traffic, feels like a real anomaly rather than expected imprecision, and we'd appreciate it if someone could take one more direct look at the record for this specific plugin.

Screenshots are attached. PLEASE HELP US.

Thank you

[frantorres]

Hi!

The data makes sense. If you made that change, then all users updating to 2.X had the plugin deactivated. With that number of installations, it makes sense that only the previous version is being reflected for a time.

As long as new installations take over from users still having the previous version, it will reflect that. However, with such a small amount of data, it is possible that it is not yet being reflected.

Please bear in mind that these are just stats. This does not prevent your plugin from working or affect the directory functionality in any way, so this is not considered a high-priority issue at all.

[Otto42]

main plugin file renamed from

Never, ever change the name of your main plugin file. The plugin is getting deactivated on upgrading, And that, naturally, will lower the stats. That is an active version chart. If the plugin is not activated anymore, then it's not counting in the stats.

Also the numbers are low enough for this plugin that it statistically doesn't count for much. It has less than 50 active installs. Statistics are bulk based, at low numbers it will not really count anything.