Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #61269


Ignore:
Timestamp:
05/22/2024 03:33:49 PM (2 months ago)
Author:
hellofromTonya
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #61269 – Description

    initial v1  
    1818An enhancement ticket is open for exploring an onboarding framework (see #61040).
    1919
    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:
     20The 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:
    2121>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
    2222
     
    4444  * add a new filter `plugin_configuration_data_{$slug}` for the onboarding/configuration URL, with an initial parameter value of `array( 'url' => '' )`.
    4545  * if filtered, it auto-redirects to that URL after activation.
    46 * In 6.6:
     46* In 6.6 (as part of #61040):
    4747  * the filter is the entry point into the onboarding framework.
    4848  * the filter's array is extended for the needs of the onboarding framework.
    49   * evaluate 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.
    5050
    5151== Pros 🟢 and Cons 🔴 Summary