[wp-hackers] About page for a plugin?
stephen at netweb.com.au
Sat Apr 26 02:35:29 UTC 2014
Both bbPress and BuddyPress indeed have an 'about' page, and are activated after activation and update though there are no checks to see if 'another' plugin is about to do the same.
@tw2113 gave this a try last month https://twitter.com/tw2113/status/444602541482196992
Core commiter, contributor & moderator of #bbPress http://bbpress.org
From: wp-hackers [mailto:wp-hackers-bounces at lists.automattic.com] On Behalf Of TV productions
Sent: Saturday, 26 April 2014 4:16 AM
To: wp-hackers at lists.automattic.com
Subject: Re: [wp-hackers] About page for a plugin?
Thank you all for your opinion! I think I move to a notice, as you suggested. This is also easier than redirecting all those cases.
TV productions :: Web development and stuff http://tv-productions.org
On 25-04-2014 16:06, Nicholas Ciske wrote:
> On activation or upgrade? Those are entirely different scenarios --
> e.g. one time vs. all the time. Sounds like BuddyPress only does so on
> direct *activation* (not bulk) which is not intrusive as I'm in the
> flow if activating that specific plugin for the first time.
> Those are also all very large plugins that require significant initial
> setup -- so I can see the use case there. Few plugins need that kind
> of interaction on *every upgrade* (except maybe in the case of a major
> version bump with breaking changes, but a dismissible notice is still
> the better pattern there, if you must do anything).
> The only place I could even see a potential argument for would be a
> direct upgrade (just that plugin) but even that is a bit overkill (and
> misses a lot of upgrade cases - ftp upgrades, bulk upgrades, external
> upgrade managers like ManageWP, etc.
> If I want to see the changes, that's what the changelog option on the
> upgrade screen (and repo) is for.
> A tab or submenu could give access to that post upgrade (e.g. the same
> about page he has now).
> A notice is a bit more intrusive, but dismissible and can handle all
> cases (on next admin visit).
> A redirect on upgrade is very intrusive, and misses a good deal of
> Nick Ciske
> On Apr 25, 2014, at 8:12 AM, J.D. Grimes <jdg at codesymphony.co> wrote:
> Both bbPress and BuddyPress do this, as does WooCommerce (and probably
> many others).
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
wp-hackers mailing list
wp-hackers at lists.automattic.com
More information about the wp-hackers