Make WordPress Core

Opened 15 years ago

Closed 15 years ago

Last modified 15 years ago

#9562 closed defect (bug) (wontfix)

mu-plugins do not call activate/deactivate()

Reported by: denis-de-bernardy's profile Denis-de-Bernardy Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.8
Component: Plugins Keywords: dev-feedback
Focuses: Cc:


When you add a plugin into the mu-plugins folder, it will not run activate() and deactivate() as it should the first time it is used.

We should at least try to run activate(), so as to set up new database tables and other once-only actions.

One potential workflow could be:

  • We scan every php file as we currently do, but keep a trace of what was included
  • After including each plugin, we check that it exists in a mu_plugins array
  • If not, we activate on the fly
  • We strip the mu_plugins array of plugins that were not included and save if relevant

Change History (3)

#1 @DD32
15 years ago

This should perhaps be offered up the the MU Trac really, As its a MU functionality which is ported over to WP for compatibility reasons. Those on MU Trac would have a better understanding of the current MU plugin generations

#2 @ryan
15 years ago

  • Resolution set to wontfix
  • Status changed from new to closed

mu-plugins aren't really like regular plugins. They're always-loaded site admin type stuff. Closing as wontfix for WP. Will bring it up with WPMU and see if they want it there.

#3 @ryan
15 years ago

  • Milestone 2.8 deleted
Note: See TracTickets for help on using tickets.