Changes between Initial Version and Version 1 of Ticket #61269
- Timestamp:
- 05/22/2024 03:33:49 PM (8 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #61269 – Description
initial v1 18 18 An enhancement ticket is open for exploring an onboarding framework (see #61040). 19 19 20 The Plugins Dependencies (aka PD) feature made a technical and design decision for its workflow. In talking with @costdev, the feature did not set out to ban redirects after activation. Jorbin summarized the feature's problem statement as:20 The Plugins Dependencies (aka PD) feature made a technical and design decision for its workflow. In talking with @costdev, the feature did not set out to ban redirects after activation. @jorbin summarized the feature's problem statement as: 21 21 >The problem PD aims to solve is that when a plugin has a dependency on another, users are left to their devices which leads to inconsistent user experiences and potential for site breakage by deactivating plugins that are relied upon 22 22 … … 44 44 * add a new filter `plugin_configuration_data_{$slug}` for the onboarding/configuration URL, with an initial parameter value of `array( 'url' => '' )`. 45 45 * if filtered, it auto-redirects to that URL after activation. 46 * In 6.6 :46 * In 6.6 (as part of #61040): 47 47 * the filter is the entry point into the onboarding framework. 48 48 * the filter's array is extended for the needs of the onboarding framework. 49 * e valuate combining Install/Activate on the Plugins > Add New Plugin screen to mitigate the 3-click approach created by the new button.49 * explore combining Install/Activate on the Plugins > Add New Plugin screen to mitigate the 3-click approach created by the new button. 50 50 51 51 == Pros 🟢 and Cons 🔴 Summary