Posted 2 years ago #
Since at least last week, the plugins SVN repository script does not update the "last updated" field when a new version of a plugin is uploaded.
Other information such as plugin version is updated, only the date stays stucked.
Active plugin version information in the stats tab also seems to be unreliable, although it may not be related.
I don't know where to submit bug reports about the SVN repository, so I hope someone will see it here.
Posted 2 years ago #
I noticed this the other day with my plugin, hopefully otto will see this!
Posted 2 years ago #
Oddly enough, not all plugins seem impacted: I noticed today that new versions of plugins from Donncha and Akismet were correctly dated. However, two of my recently upgraded plugin have the wrong date, and I am afraid that automatic upgrade notices were not dispatched.
Let's add Otto to the topic tags ;-) !
Posted 2 years ago #
What plugin?
Posted 2 years ago #
Also, the last updated date doesn't affect upgrade notifications. It's only really used for display.
And the stats have nothing whatsoever to do with it, those are entirely independent from everything, more or less. However, remember that the version stats can be a couple days behind reality too. This has to do with the reporting system and when the data gets collated and such.
Posted 2 years ago #
I tagged a version of theme-check 4 days ago, yet the last updated shows last month
Posted 2 years ago #
Wow that was quick. Praise the magic tag!
Here : http://wordpress.org/extend/plugins/yd-network-wide-wpml/ (updated today)
and here: http://wordpress.org/extend/plugins/yd-wpml-switcher/ (updated few days ago, in 2011)
Possible relationship with upgrade notifications or stats were just wild guesses. There might be something wrong with the readme or whatever, but I don't see a date field anywhere and it always worked up to now.
Posted 2 years ago #
The stats here say 100% of users are v.1.0.0 while last week most users were from previous versions so I doubt everyone upgraded : http://wordpress.org/extend/plugins/myposeo-dashboard/stats/
Same thing here: http://wordpress.org/extend/plugins/yd-wpmu-bloglist-widget/stats/ 100% users of latest version all at once.
I don't mind about the version stats anyway: they're nice to have, but it's no big deal if they aren't completely right. The date thing is a bit more annoying because it can be misleading about the fact that a plugin is being actively maintained.
Thanks for looking into this Otto, and once again thanks for appearing so fast ;-)
Posted 2 years ago #
Re stats: For those two plugins, there aren't enough active users of either one to produce meaningful statistics.
What you're seeing is basically the "null" result. To be specific, there's only two recorded users of myposeo-dashboard (one of which is active) and eight recorded users of yd-wpmu-bloglist-widget (again, one of which is active).
The stats are accurate, to a point. When there's nobody using the plugin, or nobody that has reported back recently, then stats won't be meaningful.
That said, the data gathering system is not perfect, and some data may be lost. We only retain the data for a week, tops. So if nobody reports in in that week, then we think nobody's using it.
The Last Updated date is supposed to be updated from the SVN, but it's possible that there's a bug there preventing it from updating sometimes. I'll try to figure it out. Regardless, that date has no actual effect on anything meaningful like upgrades and such. It's basically for display purposes only.
Posted 2 years ago #
Yeah, I was figuring also that the stats might have to do with the small user base of those plugins. What are recorded users? Different IPs that downloaded the latest version or something like that? and what are "active users" then? They don't show up in the public stats, right? (that would be cool!)
The myposeo thing being a web-service tools, the guys at myposeo told me that there were only 2 users one week ago according to their logs. However they had some user feedback since then so I guess the real user count must be a bit more by now.
Thanks for looking into the date thing. I'm quite sure it's a recent problem so you might be able to track it down maybe to beginning of 2011. I never experienced any other date issue before, and I've been releasing and regularly maintaining 20 plugins, so I would have noticed before, for sure.
And thanks for the explanations.
Posted 2 years ago #
Recorded users = websites that use the automatic update-check for plugins
Active users = sites that have the plugin activated
Only active users show up in the version stats pie chart.
Posted 2 years ago #
BTW, there is one way to hork up the time.. If you change the readme file to point to a new stable tag before that tag directory actually exists, then it won't be able to get the right time on it, if the updater runs on the plugin before you create the directory.
Best to make the tag directory and put the files into it first, and then to update the Stable Tag number in the readme.txt second.
Posted 2 years ago #
Makes sense, I'll try that in a couple of days when i tag.
Posted 2 years ago #
All my stable versions are released in the trunk only. However, it is possible that the readme was previously updated without updating the version or anything in the code (ie to correct typos), could that have something to do with it? (like if the readme file svn serial number does not match? - however I just checked and it does match)
For the recorded/active user numbers, do you think we might get those displayed in the stats or in the extend/plugins Admin tab someday?
Posted 2 years ago #
Looking into what could possibly have gotten wrong:
http://wordpress.org/extend/plugins/yd-wpml-switcher/ says date is 2010-12-23.
Well, according to readme.txt file SVN history the plugin was initially released on 2011/01/03 only.
According to SVN history of root directory, it was created on 2010/12/26
So the displayed date dates from 3 days before that plugin's directory was even created in the SVN!
Posted 2 years ago #
Mine plugin is doing the same. Weird. New release and new tag was pushed yesterday but the last updated date still shows May 2010.
But I updated the Compatible to 3.1 and Requires to 2.9. SVN knows the current tag is 1.5 but Last Updated didn't change.
http://wordpress.org/extend/plugins/current-location/
Requires WordPress Version: 2.9 or higher
Compatible up to: 3.1
Last Updated: 2010-5-12
Same here http://wordpress.org/extend/plugins/islidex/
Updated the plugin twice in 2011, but it's still showing as last update Sept 2010.
It might not be the most important data on the page, but it definitely affects users (I personally wouldn't download a plugin that hasn't be mantained more than 6 months in certain cases).
Any WP updates on this?
Posted 2 years ago #
I have also had similar problems lately. Have updated a few of my Plugins recently and all updates do not reflect the latest SVN date.
This means any update doesn't show on the recently updated Plugins list. I never had this problem before, just started to notice it recently.
Posted 2 years ago #
I also noticed that my last plugin's download counter started before the plugin was actually committed to the SVN (it had 14 downloads before even existing!).
If you want an update from Otto on those issues, I suggest putting him again in this forum threads tags (Tags > Add in the right column). He removed himself from the tags after answering our initial questions, above. Two weeks ago he said: "I'll try to figure it out."
My plugin Connections date will not update either.
Posted 2 years ago #
So, what is weird now is that mine has started updated. I think it has something with the way you might be posted to the SVN. The last two changes I've push I did it this way.
Made all my changes in the trunk folder as usually. Then Commit those to the SVN (only trunk folder changes).
Once that finished then I did the svn cp trunk tags/<newtag> then Commit that change. Within the 30minutes the plugin page showed it updated.
Someone else who is having issues, try those steps and see if it fixes your issue.
Any update?
I usually tag my releases using Aptana tag/commit but that broke a few months ago on my system for some reason. It always complain mid commit about a file lock problem. So I resorted to using the command line for tagging, regular commits work just fine within Aptana. The command line syntax that I've been using is
svn cp svn\url\trunk svn\url\tags\version
By SVN URL I mean the WP SVN URL to my plugin.
Next time I'll do svn cp on my local folder structure and then commit as suggested above.
Of note, I did notice that the last updated in now accurate. I'm wondering if someone fixed that manually or if the system fixed itself???
Posted 2 years ago #
Just updated my WP Content Filter Plugin today and the updated date STILL refuses to update properly, it is showing as being last updated June 2010!
http://wordpress.org/extend/plugins/wp-content-filter/
This is a bit of a pain so new versions of my Plugins never get to the 'Recently Updated' WordPress page. :(
Posted 2 years ago #
I just added Otto to the topic tag again, maybe he can give some update on resolution of those issues.
Posted 2 years ago #
I've put in a temporary fix until the underlying issue can be figured out. This may make the update time happen more often than expected, but at least it will update.
Posted 2 years ago #
Thanks Otto!
Not sure if this is Otto's doing or not, but I added some more info (one sentence at the top) to my Changelog from my last update and committed it and my Last Updated date is now current to today.
Thanks,
Ed
Oh also I believe there was another part of the equation that is important. I made some minor modifications to some of my core plugin files. The file that I believe kicked things into gear was updating my admin.php file. The reason for this is I have updated all of the other core plugin files many times and the Last Updated date issue still remained. Now what is contained in that core file could be a logical explanation for what is being seen or not seen when updating files. What was removed was 2 lines of wp_register_script code that was no longer being used and 2 lines wp_enqueue_script. Now this of course could all just be coincidence.
[Code moderated as per the Forum Rules. Please use the pastebin]
Ok so I had wanted to remove all the Last Updated info that i had added to my readme.txt file yesterday. So I made the changes to the readme.txt and did a commit. The readme.txt file did not update. I added one word in a commented out section of the admin.php file, made the changes i wanted updated for the readme.txt file and the readme.txt file updated successfully. And this sounds goofy, but i had a bad experience a while back when i had the files open in Dreamweaver that i was trying to commit. Once again this could all just be a hit or miss thing, but thought i should put in my 2 cents. Thanks.
PS I removed a section of code from my admin.php file that i felt was not relevant in the paste above.
Ed
This topic has been closed to new replies.
