[wp-trac] [WordPress Trac] #60491: Fix handling of plugins with unmet requirements

[WordPress Trac]

#60491: Fix handling of plugins with unmet requirements
--------------------------+-----------------------------
 Reporter:  azaozz        |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Plugins       |     Version:  5.1
 Severity:  normal        |  Resolution:
 Keywords:  needs-patch   |     Focuses:
--------------------------+-----------------------------

Comment (by azaozz):

 Replying to [comment:3 costdev]:
 > The main difference between "not loaded" and "deactivated" in the
 context of #60457 is that deactivating performs a DB write to
 `active_plugins`, whereas not loading just skips the `require_once`.
 >
 > We will have to remove the automatic deactivation of dependents with
 unmet dependencies, at least from the frontend.

 Right, makes sense.

 Also perhaps that part of the plugins API can be a bit
 better/faster/simpler? For example what if WP was deciding when to
 initialize a plugin? So initialization of plugins would not happen
 automatically by just loading the plugin file? Then WP would be able to
 handle all the edge cases much better/faster, and also will be able to
 show more consistent warnings to the users? Worth exploring imho :)

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