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

[WordPress Trac]

#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 costdev):

 > Follow up question: Why does any of the functionalities need AJAX? I
 would think anything we do via AJAX we could also do via hitting a
 specific "action URL" and then redirecting back (like was done before)?

 ''Redirecting on the install page/outside the modal''
 Installing and activating dependencies is a multi-step process. Retaining
 a redirect within or outside the modal would mean users are redirected
 from `Plugins > Add New` to `Plugins > Installed plugins`/onboarding for
 each dependency, then have to navigate to the install page again, repeat
 for each dependency, and finally for the dependent.

 ''Redirecting inside the modal''
 Post-activation redirection within a modal (whether dependency or
 dependent) leads to either `plugins.php` or onboarding experiences
 ''inside'' the modal. We had near-immediate consensus that this was both
 horrible visually and for UX.

 ''Redirecting only for plugin card buttons''
 Much of the code for the install/activate buttons is the same for the
 plugin cards on `Plugins > Add New` and in the modals. We felt that being
 able to install and activate multiple plugins without being removed from
 the `Add New` context was beneficial, and that navigating to any other
 page would display either the onboarding, or the plugin's menu items,
 which would lead to their onboarding (the problem being: How does the user
 know to refresh/navigate away, and why should they?). - That's where being
 more restrictive in the selectors so that the `Activate` button in plugin
 cards redirects as it did previously, which means the multi-step process
 of installing/activating dependencies remains the same as it is now, while
 individual installation/activation remains as it did before 6.5.

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