[wp-trac] [WordPress Trac] #26334: Disable 'Featured Plugins' if they're included in Core

[WordPress Trac]

#26334: Disable 'Featured Plugins' if they're included in Core
-----------------------------+--------------------
 Reporter:  Ipstenu          |       Owner:
     Type:  defect (bug)     |      Status:  new
 Priority:  highest omg bbq  |   Milestone:  3.8
Component:  Upgrade/Install  |     Version:  trunk
 Severity:  normal           |  Resolution:
 Keywords:                   |
-----------------------------+--------------------

Comment (by markoheijnen):

 A plugin is a plugin and nothing more. So MP6 has the same value as any
 other random plugin. WordPress itself shouldn't know anything about
 plugins and what they do. This has nothing to do with building new
 features as plugins. If they shouldn't exists after it is in core then it
 maybe shouldn't be on WordPress.org in the first place.

 I also don't see why we should care much if users don't upgrade their
 plugin first before core. We also didn't care when we introduced
 has_shortcode(). Then we also didn't check if that function maybe already
 existed and this did broke quite a few websites. So we don't live in a
 perfect and that does mean that sites break when doing updates.

 That said deactivation isn't the solution. Users can activate it again.
 Removing isn't the solution since it's confusion. Even when showing a
 notice about it since the person seeing it doesn't mean to be responsible
 for it. Even when someone has a new installation they can still install
 the plugins if they still in the repo. And removing the plugin can be
 risky if there are security issues in that part of the code. Then we can't
 push those changes.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/26334#comment:7>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software