Okay, here is a big piece of feedback to TPTB.
The plugin process needs a version checker, something that says “this plug in test only until version x.x”, and when you go past that version, the plug in is either disabled or a large warning comes up on the main dashboard about potential incompatible plugins.
First off, this would eliminate about 50% of all the support posts here. Many of the posts in the support reflect problems because wordpress’s methods have changed and plugins are not up to date.
Secondly, this would encourage plugin creators to stay current. It wouldn’t be hard as a result to have lists of plugins by version, so that people don’t try to implement plugins that either are not compatible with their wordpress install or worse are way out of date and no longer supported.
Third, it would be a step in reigning in the posting, deleting, and maintenance procedures of wordpress. Too many plugins get in the way of these very basic functions and turn wordpress into an even larger resource pig than it can already be.
In my mind, many of the things that are being done with plugins during the post, maintain, or delete functions are not needed and just cause system resources to get wasted. Many of these procedures would be better done as background tasks, rather than as foreground tasks that make the authors wait significant amounts of time to get things done. Perhaps in the future having a background launch system that triggers once per day to allow certain types of maintenance or updates to be done, rather than doing them over and over again for each post, edit, or deletion?
- The topic ‘Plug-in compatibility Coding’ is closed to new replies.