[wp-meta] [Making WordPress.org] #2365: Plugin Directory: Restore links to previous versions of plugin

Making WordPress.org noreply at wordpress.org
Mon Apr 3 16:30:13 UTC 2017


#2365: Plugin Directory: Restore links to previous versions of plugin
------------------------------+-------------------------------------------
 Reporter:  jimtrue           |       Owner:
     Type:  defect            |      Status:  new
 Priority:  normal            |   Milestone:  Plugin Directory v3 - Future
Component:  Plugin Directory  |  Resolution:
 Keywords:                    |
------------------------------+-------------------------------------------

Comment (by FolioVision):

 @clorith, this obsession with the latest version is really unhealthy. This
 is how WordPress consultants bilk clients. Everything on the latest
 version means that something is sure to be breaking, either WordPress
 4.7.1 (recent example) or plugins.

 Not every version of every plugin (far from it) is a security related
 update. WordPress consultants with this update frenzy appear determined to
 bleed our clients to death. People will get tired of WordPress and just
 move onto something which doesn't require constant consultant bills or
 endless fiddling to keep running. I don't want that to happen.

 We even coded a [https://wordpress.org/plugins/businesspress/ whole
 plugin] to keep WordPress.org off the back of our clients (reducing update
 pressure, controlling admin notices, enabling preferences for oEmbed,
 emojis, XML-RPC, REST API which should be in core). Unfortunately we can't
 repair the plugin repository ourselves. And you and your friends and
 should not have broken it [https://wptavern.com/wordpress-plugin-
 directory-redesign-why-so-many-people-feel-their-feedback-was-ignored
 against the advice of 90% of the developers] who cared to contribute to
 the discussion.

 I.e. your "hard work" workarounds - do them yourself Clorinth if you want
 to but please let us allow our clients to live easier lives. I.e. could
 not disagree more strongly with both your premises and your conclusions.

 Is there anyone else at charge in Automattic who wants to come out and
 tell all of us doing really work with clients how naive and misguided
 developers we are and how we aren't willing to work hard enough to be part
 of the WordPress community?

 Alec

--
Ticket URL: <https://meta.trac.wordpress.org/ticket/2365#comment:25>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org


More information about the wp-meta mailing list