Make WordPress Core

Opened 8 years ago

Last modified 8 years ago

#11861 closed feature request

Show list of drop-ins and must-use plugins in admin area — at Version 3

Reported by: archon810 Owned by:
Milestone: 3.0 Priority: normal
Severity: normal Version: 2.9.1
Component: Administration Keywords: has-patch
Focuses: Cc:

Description (last modified by dd32)

Stemming from #10952, this ticket is a suggestion to add a warning somewhere in admin when a custom object-cache.php and/or db.php are present.

Malfunctions related to having those files can be very tricky to trace and debug, as evident from #10952.

Specifically, see http://core.trac.wordpress.org/ticket/10952#comment:19 for dd32's support for adding this warning.

Change History (3)

#1 @nacin
8 years ago

  • Summary changed from Add a flash-type warning if custom object-cache.php or db.php are present and in use to Show list of drop-ins and must-use plugins in admin area
  • Type changed from enhancement to feature request

+1, and also must use plugins as well.

I'm thinking these should be two page filters on the Manage Plugins page, "Must-Use Plugins" and "Drop-ins" (could possibly be one page) that would only appear if you have any mu plugins or drop-ins.

Drop-ins also include maintenance.php and advanced-cache.php, bringing the total to four.

Many of these files won't have headers. But for a drop-in, existence is a big start. And including a way for super admins to see mu plugins will only serve to encourage them to use headers on those.

I'm going to try to do a patch for this later this week. Possibly try it out as a plugin as well.

#2 @dd32
8 years ago

  • Milestone changed from Unassigned to Future Release

Just to repeat my +1

I'd be +1 for either a section on the plugin page Or a Menu item under Tools which lists (for !multisite
is_super_admin) MU-style plugins, and any override files which were present..

In the event that the file doesnt have headers, I'd list it simply as a table row with the filename.. and the description of what that file achieves.

Future release pending patch and/or core developer feedback

#3 @dd32
8 years ago

  • Description modified (diff)

(for !multisite is_super_admin)

By that i meant:

(for !multisite || is_super_admin)

|| got eaten as a table?

Note: See TracTickets for help on using tickets.