| 3 | | Prior to WordPress 6.5, it was common for users to install a dependent, activate it, then be greeted with a notice that they needed one (or on occasion more than one) other plugin. They'd often then click a link to the install page, install, activate, then find their way back to the dependent they actually wanted to use. This meant users navigating between multiple screens, plugin authors using various patterns (i.e. inconsistency for users), and so on. Plugin Dependencies was (continuously) requested for a very long time (by all types of users), and while as we see from this ticket it didn't land perfectly, it's gone a long way towards delivering on this and we want to see issues like the one raised in this ticket have a path forward (such as these PRs, plus #61040). |
| | 3 | Prior to WordPress 6.5, it was common for users to install a dependent, activate it, then be greeted with a notice that they needed one (or on occasion more than one) other plugin. They'd often then click a link to the install page, install, activate, then find their way back to the dependent they actually wanted to use. This meant users navigating between multiple screens, plugin authors using various patterns (i.e. inconsistency for users), and so on. In that regard, some recent assertions that only developers install multiple plugins at once is somewhat inaccurate as users actually can often find themselves installing an addon first then finding out that they have to go through a process similar to the above. |
| | 4 | |
| | 5 | Plugin Dependencies was (continuously) requested for a very long time (by all types of users), and while as we see from this ticket it didn't land perfectly, it's gone a long way towards delivering on this and we want to see issues like the one raised in this ticket have a path forward (such as these PRs, plus #61040). |