[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:  6.5.3
Component:  Plugins                              |     Version:  6.5
 Severity:  normal                               |  Resolution:
 Keywords:  has-patch needs-testing has-         |     Focuses:
  testing-info needs-design-feedback             |
-------------------------------------------------+-------------------------

Comment (by kevinwhoffman):

 I realize the short-term fix may be headed in a different direction, but I
 wanted to add some considerations about the "Configure" link mockup that
 was previously shared.

 **As a standard link in the Add Plugins search results**

 This "Configure" link concept was designed to be timeless rather than
 something that only applies to onboarding after activation. This means the
 "Configure" link can be present whenever an already active plugin card
 appears in search results, providing one-click access to configuration. It
 should always point to the page where the plugin can be configured, not
 just for first-time onboarding. If the plugin wants to include logic on
 that page that detects whether a first-time wizard UX is needed, that's up
 to the plugin to decide.

 [[Image(https://core.trac.wordpress.org/raw-attachment/ticket/60992
 /Configure-button.jpg)]]

 **As a standard link in the Plugins list table**

 The "Configure" link could also be in the Plugins table where every plugin
 currently does this differently. For example, Yoast has two separate
 links—one for first-time config and one for settings. Much like
 "Deactivate" is a standard link for all plugins, we have an opportunity to
 establish a standard "Configure" link for configuration. So whether you
 encounter the plugin in search results or the Plugins list table, you are
 always one click away from configuration. Everyone knows how to deactivate
 a plugin; it should be just as obvious to configure it.

 [[Image(https://core.trac.wordpress.org/raw-attachment/ticket/60992
 /configure-link-plugins-list-table.png)]]

 **Defined in the plugin header**

 Allowing plugin authors to define a `Configuration` field in the plugin
 header means that the value could be used by core in multiple contexts
 including the plugin cards and list table described above. Simply define
 the field and it's available for use.

 **Generic enough to work everywhere**

 I chose the term "Configure" intentionally because we know that some
 plugins are configured on their own top-level WP Admin pages, others are
 nested under WP Admin > Tools, and others still are nested under WP Admin
 > Settings. For example, calling the link "Settings" implies you would be
 linked to the  WP Admin > Settings or one of its child pages, which is not
 always the case. "Configure" is a generic term that can point anywhere in
 WP Admin and still make sense.

 **Simple fallback**

 If a `Configuration` field is not defined because a plugin like Hello
 Dolly has no configuration, then core can continue to show the disabled
 "Active" button in the plugin card and omit the link from the Plugins list
 table.

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