Making WordPress.org

Opened 6 years ago

Closed 20 months ago

#152 closed enhancement (wontfix)

Add a field onto WordPress.org support forums for plugin version number

Reported by: Daedalon Owned by:
Milestone: Priority: low
Component: Support Forums Keywords: has-patch commit has-screenshots


Migrated from #wp23704:

WordPress.org support forums ask the user to specify the version of WordPress they are using.

In plugin-specific support forums such as http://wordpress.org/support/plugin/events-manager there should also be a field for the plugin version number. Like the WordPress version number, this should be a dropdown list, for which the values should be available in the WordPress.org database.

This way plugin authors don't need to ask the user for that version, which speeds up the resolution of support tickets and saves the plugin authors' time, letting them concentrate more on creating and improving the plugins.

Attachments (3)

152.PNG (26.7 KB) - added by SergeyBiryukov 3 years ago.
152.patch (18.6 KB) - added by SergeyBiryukov 3 years ago.
152.2.patch (18.6 KB) - added by SergeyBiryukov 2 years ago.

Download all attachments as: .zip

Change History (12)

#1 @ocean90
3 years ago

#817 was marked as a duplicate.

3 years ago

3 years ago

#2 @SergeyBiryukov
3 years ago

  • Keywords has-patch commit added

This was mentioned in #1181 as a prerequisite for further review enhancements (e.g. a rolling timeline).

152.patch extends wporg-bbp-version-dropdown to allow for specifying a plugin or theme version in addition to WordPress version. Both versions are then displayed in the sidebar with an appropriate icon: 152.PNG .

In my testing, everything seems to work as expected, but I'd appreciate if someone tested ::get_project_versions() with real data. It's supposed to pull plugin or theme versions from the respective directories. I don't have them on a local install yet, and Meta Environment doesn't work on my laptop for some reason I have yet to figure out.

Version 0, edited 3 years ago by SergeyBiryukov (next)

#3 @SergeyBiryukov
3 years ago

152.patch still applies. Tested with some real data on a local install, appears to work as expected.

#4 @SergeyBiryukov
2 years ago

  • Keywords has-screenshots added

Refreshed to replace 'draft' plugin status with 'new' after [5318].

@coffee2code The patch uses switch_to_blog() and WP_Query to query plugin or theme versions from the respective directories. The support-forums plugin uses direct queries for a similar purpose (to query plugin author and contributors). Is that due to the overhead of WP_Query? What would be the preferred way here?

#5 @netweb
2 years ago

Neat patch @SergeyBiryukov +1

This ticket was mentioned in Slack in #forums by sergey. View the logs.

2 years ago

This ticket was mentioned in Slack in #forums by sergey. View the logs.

2 years ago

This ticket was mentioned in Slack in #forums by clorith. View the logs.

20 months ago

#9 @Clorith
20 months ago

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

This is more likely than not going to end up being another field users ignore, or fill in wrong if they try to use it, so avoiding it seems the best approach (and also looking into removing the WordPress version field for the same reason).

As for review weight, time rather than version is a better basis for that.

Note: See TracTickets for help on using tickets.