Random plugin structure should be deprecated
|Reported by:||robertaccettura||Owned by:||anonymous|
|Severity:||minor||Keywords:||plugin directory update|
Plugins are currently a bit of a mess. They generally fall into a few categories:
- A single file. often wp-name.php
- A handful of files.
- A directory full of files, and perhaps a few subdirectories within that.
There are several problems here:
Namespace Collisions - each plugin potentially violates each other's namespace if they don't use unique filenames. A good example of this is readme's. Most are lost unless you rename them. Potential for worse exists with common names "feed", "comment", etc.
Management - uninstall isn't always easy since associated files aren't always clearly named. This leaves potential files on the filesystem, and could be a potential security issues.
Upgrades - I've already had one case where I didn't upload a plugin to the ideal location, and the one click update functionality failed.
All plugins should have a parent directory. For example:
By doing this, the entire thing is simplified. All plugins can then be easily upgraded by replacing the directory, removed by removing the directory, etc. Many plugins already do this on their own (such as wp-cache).
My suggestion is that this methodology be encouraged, and eventually the old method of php's in the plugins directory require opt-in via a constant in wp-config.php perhaps in the 2.7 timeframe.
This would remedy the above problems and provide a much cleaner plugins directory that's easier to manage.
Change History (9)
- Keywords changed from plugin, directory, update to plugin directory update