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

WordPress Trac noreply at wordpress.org
Sat May 13 02:36:16 UTC 2023


#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 costdev):

 Thanks for the feedback @azaozz

 > For plugins with dependencies: list the requirements on the plugin
 "tile" and in the "Install" modal (on the Add New screen). Not mentioning
 that a plugin requires other plugins in order to work is a pretty bad
 omission imho.

 The requirements are currently listed on the plugin tile. 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.

 > Use the plugin's tile and install modal not only to show but also to
 install missing dependencies.

 Could you post a mockup of how you're imagining 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. I appreciate that you
 may not be on the design team, but nevertheless it would be helpful to see
 a visual repesentation of your thoughts to start things off on exploring
 this option (otherwise potential design work on this may be way off base).

 > I looked around for anything that resembles this "Dependencies" UI/UX
 but couldn't find a good example. The closest one is when trying to
 install an app that requires some operating system part/library. In these
 cases the installation in not allowed until the requirements are met. That
 makes the most sense.

 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.

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


More information about the wp-trac mailing list