[wp-trac] [WordPress Trac] #61269: Plugin Dependencies: Add filter to restore auto-redirect after plugin activation

[WordPress Trac]

#61269: Plugin Dependencies: Add filter to restore auto-redirect after plugin
activation
-------------------------------------------------+-------------------------
 Reporter:  hellofromTonya                       |       Owner:  costdev
     Type:  defect (bug)                         |      Status:  closed
 Priority:  normal                               |   Milestone:
Component:  Upgrade/Install                      |     Version:  6.5
 Severity:  normal                               |  Resolution:  duplicate
 Keywords:  needs-dev-note has-patch has-        |     Focuses:
  testing-info                                   |  administration
-------------------------------------------------+-------------------------
Changes (by hellofromTonya):

 * status:  reviewing => closed
 * resolution:   => duplicate
 * milestone:  6.5.4 =>


Comment:

 Hello all,

 Thank you everyone for contributing to this ticket and effort. Power of
 open source!

 The work done here fits better into a major release, i.e. into Trac
 #61040. Notice, there were back-and-forth discussions about what
 parameters should and shouldn't be in and what the naming of them should
 be in the configuration data registration. These kinds of discussions are
 important and need thoughtful consideration and experimentation.

 But that's the point: the onboarding / configuration step into the add
 plugin workflow is still in the ideation stage. Time is needed for the
 idea to become a next step.

 While there's a strong intent that the filter is and will be part of the
 next step / workflow, there's still a risk that maybe it or the `url`
 parameter might not fit what that idea becomes. Thus, it locks in the
 entry point or could cause a deprecation.

 With the new approach in #61319, it directly addresses the scope of the
 regression. There's consensus to move forward with that approach for the
 minor.

 This ticket is being closed in favor of #61319. But the work and
 discussions here are the part of the ideation stage and need to continue
 on into the next step, i.e. continue in #61040.

 I invite you all to stay actively engaged and contributing to #61040 and
 the next step in refining and defining the add plugin workflow and how
 configuration / onboarding fits into it to improve the experience for the
 majority of the users.

 Thank you again. Happy contributing :)

 Trac note:
 I'm marking this as a duplicate of #61319. Though the implementation is
 not a duplicate, the problem it seeks to solve, i.e. the regression, is
 the same.

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