Old plugins are unfairly blacklisted :-(

Callum Macdonald
(@chmac)

13 years, 6 months ago

I’ve written a handful of plugins which were written 2+ years ago, are very simple, require no updates, are still 100% functional today. But they’ve been removed from the plugin listing because they’re old, haven’t (required or) been updated in 2+ years.

I’ve just spent an hour or two going through and bumping all their versions to 0.X.0 so they’re back in the listing. It would be nice if the system was smart enough to recognise when a readme.txt was updated to say the plugin is compatible with 3.4.2, that it’s “maintained”. Now any users of my plugins will be given an update notice for no reason other than getting the plugin back into the directory.

Viewing 10 replies - 1 through 10 (of 10 total)

Moderator Ipstenu (Mika Epstein)
(@ipstenu)

🏳️‍🌈 Advisor and Activist

13 years, 6 months ago

You mentioned this before.

The plugins team is aware, however there’s a bug in it that crashes things. tl;dr, no one gets updates, or the 2 year thing shows up. We’re working on it, though, it is NOT supposed to be that way.

Thread Starter Callum Macdonald
(@chmac)

13 years, 6 months ago

@ipstenu: Ahh, my bad, you’re absolutely right! I was so impressed by the action on my last post here I thought I’d go around again. I completely forgot I’d already posted on the same topic, apologies.

If it’s a bug, fair enough, makes sense. I’ve pushed version updates to almost all my plugins which qualify by now anyway. I noticed a couple of Matt Mullenweg’s plugins were in the same boat!

Thanks for the confirmation, glad to hear a fix is in the works. 🙂

uamv
(@uamv)

13 years, 4 months ago

Any more news on this fix? i just uploaded a plugin today and am receiving the same message. Do i just wait? Thanks!

Chris Olbekson
(@c3mdigital)

13 years, 3 months ago

@uamv what message are you receiving?

uamv
(@uamv)

13 years, 3 months ago

Ah, it has since gone. It was something along the lines of my plugin being older than two years without any maintenance or updates … even though i’d just uploaded it. All was well at first commit, but then the error appeared and the banner disappeared. i was having some issues with svn commands not taking. The error left and i removed/re-added the banner and it reappeared.

esmi
(@esmi)

13 years, 3 months ago

Plugin url?

uamv
(@uamv)

13 years, 3 months ago

i just recently requested removal of the plugin, as i found it to be unstable and i found another plugin with similar functionality and proper support. The URL had been http://wordpress.org/extend/plugins/act-as-user/

Moderator Ipstenu (Mika Epstein)
(@ipstenu)

🏳️‍🌈 Advisor and Activist

13 years, 3 months ago

You asked us to close act-as-user… So … what’s going on now?

Last Updated: 2013-1-15 and it has a banner (Only plugin mods and you can see the closed ones, BTW, which is not ‘great’ but we’re still trying to figure out a better closed message).

uamv
(@uamv)

13 years, 3 months ago

Correct, i did request removal. i was simply responding to the questions asked by Chris and esmi in response to issues i had with the plugin upon initial upload.

Moderator Ipstenu (Mika Epstein)
(@ipstenu)

🏳️‍🌈 Advisor and Activist

13 years, 3 months ago

Ahh, okay, sorry this is an old post, so I didn’t pay as close attention to post dates as I should have.

Why does the updater get stuck sometimes? Hell if I know. It’s better than it was, though, but sometimes you have to check in a ‘real’ change (like editing a readme) to make it catch.