Making WordPress.org

Opened 8 years ago

Closed 8 years ago

Last modified 8 years ago

#2180 closed defect (bug) (worksforme)

Tags missing from plugin

Reported by: johnbillion's profile johnbillion Owned by:
Milestone: Priority: normal
Component: Plugin Directory Keywords:
Cc:

Description

The readme.txt file in my Query Monitor plugin contains a bunch of tags, but the plugin isn't tagged with these in the plugin repo. The tags aren't listed on the plugin page, and the plugin doesn't show up when browsing the archive for any of its tags.

The readme file is valid according to the readme validator.

Change History (3)

#1 @Otto42
8 years ago

  • Resolution set to worksforme
  • Status changed from new to closed

Tags are showing up fine for your plugin. Bottom of the page.

Also, please delete some of the old tagged versions from your plugin:

https://plugins.svn.wordpress.org/query-monitor/tags/

That many tagged versions makes it take a lot longer to process your plugin, since a ZIP has to be built for each of those directories on every update. You don't need to offer all of those old versions, do you? Just the latest in each major set is probably good enough.

#2 @johnbillion
8 years ago

Thanks. The tags definitely weren't there when I reported this so there must have been an issue generating the list of tags, although the plugin hasn't been updated in two months.

Regarding tagged releases -- deleting tags kind of defeats the point of tagging releases, no? This sounds like an infrastructure issue rather than something that every plugin developer needs to address.

#3 @dd32
8 years ago

This sounds like an infrastructure issue rather than something that every plugin developer needs to address.

Correct, it's also fixed in the new plugin directory, as it doesn't take the same hard rebuild-every-zip-on-every-commit that the existing directory does. That's why plugins with lots of tags often have issues, as the process can sometimes (but rarely) timeout while doing the build.
In this case I believe the issue was bad caching (unless someone re-ran the plugin import).

Note: See TracTickets for help on using tickets.