10 | | 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. |
| 10 | 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 a possible approach comes in of 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. |