[wp-trac] [WordPress Trac] #22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)

[WordPress Trac]

#22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)
-------------------------------------------------+-------------------------
 Reporter:  Viper007Bond                         |       Owner:  afragen
     Type:  enhancement                          |      Status:  assigned
 Priority:  normal                               |   Milestone:  6.3
Component:  Upgrade/Install                      |     Version:  3.4.2
 Severity:  normal                               |  Resolution:
 Keywords:  dev-feedback has-patch needs-        |     Focuses:
  design-feedback needs-dev-note has-unit-tests  |
  2nd-opinion changes-requested                  |
-------------------------------------------------+-------------------------

Comment (by azaozz):

 Replying to [comment:289 costdev]:
 > The requirements are currently listed on the plugin tile.

 Uh, I've used the [https://wordpress.org/plugins/wp-plugin-dependencies/
 Plugin Dependencies] plugin from the repo. Perhaps it is a bit older.

 > I ''believe'' listing them in the modal's contents would need to be done
 via wordpress.org consuming the `Requires Plugins` header. I may be
 incorrect on this though.

 Yes, it may be added from wp.org, but probably better to add it from the
 local code. Thinking it may be easier to "see" the required plugins status
 (for example "installed but not activated", etc.) and show the proper
 links or buttons. Also thinking the modal can have a bit expanded "about
 dependencies" section with a bit more explanations, etc.

 > Could you post a mockup of how you're imagining the modal part of this?
 I'm concerned that this may overload users with a lot of information to
 install/activate each dependency all within the tight space of the modal.

 Yea, the exact UI changes to the modal are somewhat TBD. I'll try to make
 some sort of a mockup. As a minimum thinking that the modal would have a
 "Requirements" section with a good inline description that lists all of
 the requirements. That list should include the status (installed,
 activated), "More Info" link and an "Install" button when needed for each
 required plugin.

 As far as I see the UI would probably be best to include the "info" for
 the "main" plugin and all of its dependencies in the same modal. This
 would make the modal taller, but would list everything required in one
 place which would make it easier for the users to understand and follow,
 and to be able to "make an informed decision" without needing to navigate
 away, lose/reopen other modals, etc. To make the UI look better this can
 use an "accordion" type tabs or similar.

 An alternative UI may be to "paginate" the modal (so it has "Previous" and
 "Next" buttons) however thinking that won't be as nice.

 I tried making an example mockup of a "tile" for a plugin with
 dependencies, see above.

 > For themes that require plugins and where the plugins are manually
 installed, these are usually installed after installing the theme, via a
 screen like `Theme Settings > Required Plugins`. However, depending on the
 mockup of the modal-based dependency installation/activation,
 installing/activating dependencies before the dependent may work fine even
 if it's a less familiar UX for users.

 Thinking this depends on whether the plugins are "hard" requirement for
 the theme to work or are optional. I agree that if they are "hard
 requirement" it would be better to add the same "Requirements" section as
 for plugins.

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