[wp-trac] [WordPress Trac] #60992: Plugin management: AJAX plugin activation consequences

WordPress Trac noreply at wordpress.org
Tue Apr 16 10:17:34 UTC 2024


#60992: Plugin management: AJAX plugin activation consequences
--------------------------+------------------------------
 Reporter:  jeherve       |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Plugins       |     Version:  6.5
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------

Comment (by justlevine):

 Seems there's a bit of conflation between what needed for a viable UX, and
 what some devs are (ab)using those hooks for.

 Premise: there is no justifiable use case for **forcing** users into an
 onboarding wizard after activating a plugin. There are dozens of reasons
 why a user would not want to setup a plugin as soon as they activate it.

 The proper pattern is to use an Admin Notice, informing the user they must
 complete setup. (Its beyond the scope to get into the irony about the
 positive correlation between plugins that abuse admin notices and have
 forced onboarding wizards).

 With redirect hijacking aside, we're now left with the justifiable issue
 of guiding people to the next actionable step from the plugin activation
 screen.

 A simple, non-intrusive solve that's also forward-compatible with whatever
 other reactive Admin UI updates would be changing the success notices to
 add something along the lines of 'Go to your <link>Dashboard</link> to see
 the changes'.

 A step up from this would be allowing users to provide an
 `activation_success_message` that could be displayed on the screen. This
 would also fill the gap caused by the lack of new links in the Admin
 Menu/Bar

 Neither offers as comprehensive a solve as @benlk's suggestion for an
 Admin Notices REST API, which I love, but can only assume will also be
 required by future Admin UI updates anyway - and as a result likely hard
 to implement beforehand without it turning into tech debt.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/60992#comment:10>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform


More information about the wp-trac mailing list