[wp-trac] [WordPress Trac] #43986: Disable "Install Plugin" button for PHP required version mismatch

[WordPress Trac]

#43986: Disable "Install Plugin" button for PHP required version mismatch
-------------------------------------------------+-------------------------
 Reporter:  schlessera                           |       Owner:  (none)
     Type:  task (blessed)                       |      Status:  new
 Priority:  normal                               |   Milestone:  5.0
Component:  Plugins                              |     Version:
 Severity:  major                                |  Resolution:
 Keywords:  needs-unit-tests servehappy dev-     |     Focuses:
  feedback has-patch                             |
-------------------------------------------------+-------------------------

Comment (by joyously):

 Again, you have missed my point.

 This ticket has a narrow scope because it is written with the "solution"
 as the title. That is not the preferred method of writing tickets. It
 should describe the problem, and then the solution is discussed and
 implemented. The problem this ticket is addressing is preventing PHP
 errors from occurring with mismatched PHP versions by using the `Requires
 PHP` header if it exists in the plugin. But we have not discussed the best
 way to accomplish that. What has been left out of this discussion is the
 actual steps the user must go through in order to upgrade PHP.

 With the implementation of the last patch, the user is not helped; he is
 just hindered. What would help is to allow the installation of plugins
 regardless of PHP version, and disallow their activation if there is a PHP
 mismatch. Think about the user trying to upgrade. He has to find some
 plugin replacements and install them before the upgrade so that the site
 is not down long. The plugins being replaced would need to be deactivated
 before the upgrade so the site doesn't crash on upgrade.

 All I'm asking for is the user experience to be given more thought. The
 current solution is not helpful at all. The "disabling" should be the
 activation, not the installation or the plugin update. Given one choke
 point, it's easier to implement and more useful to the user, especially
 since the WP admin is not the only way to get a plugin installed. WP
 doesn't care if the user has old plugins that don't run with the current
 WP version. They don't matter until they are activated, right? So what is
 the problem with installing plugins with higher PHP requirements? They
 aren't a problem until activated. Let the user install what he
 wants/needs, and show him enough info to help him manage them **as he does
 his PHP upgrade** (or all the time).

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