WordPress.org

Ready to get started?Download WordPress

Make WordPress Core

Tagged: plugins directory Toggle Comment Threads | Keyboard Shortcuts

  • Andrew Nacin 8:07 pm on April 20, 2012 Permalink
    Tags: plugins directory,   

    We’re seeing increased reports in readme.txt files not updating for plugins. Likely related to the migration to nginx from earlier this week, as in the process a number of configurations were updated (also PHP 5.2 to 5.3), and now signs point to memcached caching algorithms (riveting). @bazza is looking into the problem; @otto42 and I are also looking into some wider issues.

     
  • Andrew Nacin 2:57 pm on December 28, 2011 Permalink
    Tags: plugins directory   

    The plugins directory should now update in near real-time. Previously updates only ran every 15 minutes and some other things (namely adding committers) fired less often.

    If you notice any problems, please comment here.

    Thanks @bazza for doing this!

     
  • Andrew Nacin 11:44 pm on August 14, 2011 Permalink
    Tags: plugins directory,   

    Matt announced today at the 2011 State of the Word that plugins and themes are now hidden from the search results (on both WordPress.org and in the plugin/theme install screens) if they have not been updated in two years.

    For plugins only: Older plugins that are still compatible and secure only need to have their “requires” and “tested up to” version numbers bumped. If you do this, actually releasing a new version of the plugin is not necessary, so leave the version number the same.

     
    • Ramoonus 5:30 pm on August 15, 2011 Permalink | Log in to Reply

      isn`t 2 years a bit long? I always stop using plugins which haven`t been updated for 1 year.

      • Andrew Nacin 3:16 am on August 16, 2011 Permalink | Log in to Reply

        It’s a start.

      • Jeremy 3:20 pm on August 16, 2011 Permalink | Log in to Reply

        Might there be plugins out there that are so good and really basic that their utility spans greater than 2 years?
        It seems that you would want something more to go off of in addition to the last modified date.

        • Andrew Nacin 10:32 pm on August 16, 2011 Permalink | Log in to Reply

          We looked at the old plugins with the highest download counts and saw nothing that caught our eye. Ultimately, if a plugin author can’t update just the “Tested up to” version, then it’s pretty safe to consider it abandoned. The “Tested up to” values for such plugins are no higher than 3.0, and most are far worse. Otto and I are going to poke around the data and see if further refinements can be made, though.

    • Pasta Maker 8:04 pm on August 15, 2011 Permalink | Log in to Reply

      Why 2 years and not a shorter period? From what I understand, many wordpress plugins/themes are not really secure and can be easily hacked. Is that true?

    • pavelevap 5:44 pm on August 16, 2011 Permalink | Log in to Reply

      Old plugins should be also hidden from tags archive on WordPress.org?

    • Mark 12:15 am on August 17, 2011 Permalink | Log in to Reply

      Rather than just hide plugins I think it could be useful for them to be listed somewhere for new would-be authors to get inspiration and learn.

      • DrewAPicture 6:20 am on August 22, 2011 Permalink | Log in to Reply

        Agreed. Though they’d be hidden from main search, it would be nice to still be able to search/browse them elsewhere .Forks could/would happen.

    • Adam 8:36 pm on August 17, 2011 Permalink | Log in to Reply

      I think this is a good policy. You get rid of plugins and themes that may not work with the newest flavors of WP and it causes less problems. Thanks!

      -A

    • WraithKenny 6:33 pm on December 14, 2011 Permalink | Log in to Reply

      Is this still a two year limit, or is it now a “tested” version?

      WP-reCAPTCHA has disappeared (I assume it was marked abandoned), but it looks like it was updated 8 months ago, but was only tested up to 2.9.1. It looks to be a truly abandoned plugin as the authors site is gone, yet people still use this plugin (even if they have to patch it themselves).

      Any news on the adopt-a-plugin program?

  • Andrew Nacin 11:44 pm on May 12, 2011 Permalink
    Tags: dotorg, plugins directory   

    A few weeks ago a change was deployed to the plugins directory. If you click “Other Versions” on the sidebar when viewing a plugin, there’s a new section called “Browse the Code” with three links to:

    • the development log on Plugins Trac
    • the plugin’s directory in Subversion
    • the stable tag in Subversion (or trunk)

    Hopefully this makes it easier to find the right URL for plugin checkouts, and to browse the code.

    Check it out here.

     
    • Lloyd Budd 1:04 am on May 13, 2011 Permalink | Log in to Reply

      This is fantastic @nacin! I’ve bumped my… elbow on this many times previously.

    • Jan Fabry 6:54 am on May 13, 2011 Permalink | Log in to Reply

      I always go from the Trac /log/ to the /browser/ URL, I want to read the code as it currently is, but with the nice browse interface that Trac offers. Have you considered not linking to the SVN page but to the Trac browser page? The “Repository URL” link at the top of the page should then maybe link to the real SVN URL, with an extra “Directory URL” that links to the plugin directory page.

      • Andrew Nacin 4:48 am on May 17, 2011 Permalink | Log in to Reply

        This was designed to provide a direct link to the SVN, for such operations, rather than for actually browsing the code. I tried to not keep the list of links from becoming too bloated, and considering that you can get from /log/ to /browser/ pretty easily, I think it’s currently pretty good. Maybe that’s just me though.

        • Scott 7:35 am on May 19, 2011 Permalink | Log in to Reply

          I would actually prefer the Trac browse page (and thus two Trac links) more than the two different SVN links. But as you said, maybe that’s just me.

    • Jeremy Zilar 12:43 pm on May 13, 2011 Permalink | Log in to Reply

      Well done! That will definitely make getting the SVN URL much easier.

c
compose new post
j
next post/next comment
k
previous post/previous comment
r
reply
e
edit
o
show/hide comments
t
go to top
l
go to login
h
show/hide help
shift + esc
cancel