[wp-hackers] "Outdated plugin"
notice (was: load_plugin_textdomain() )
wordpress at santosj.name
Tue Jul 29 02:43:53 GMT 2008
There is this problem called phpDocumentor. Luckily, Peter Westwood has
blessed us with his public installation: http://sandbox.ftwr.co.uk/doc/
Hopefully, one of these days this will find itself on wordpress.org.
Peter did suggest a better domain for it, so who knows (but Peter).
There is also the source, which has deprecated functions as marked, and
wp-includes/deprecated.php, which holds obsolete functions and globals.
> I think that we are missing something very important here. The Codex
> is consistently outdated on what is or is not deprecated, and often is
> an unreliable source of accurate and current API information.
> What mechanism could possibly keep track of the status of all function
> calls and valid parameters when the Codex doesn't even contain that data?
> If we can fix this problem either programmatically or procedurally,
> then we can start talking about automated checks for deprecated code.
> Until such a time, I feel that such checks will be nothing more than a
> pipe dream.
> - Chris
> Stephen Rider wrote:
>> On Jul 28, 2008, at 5:01 PM, Otto wrote:
>>> On Mon, Jul 28, 2008 at 4:32 PM, Stephen Rider
>>>> I think we need a narrow column in the plugins screen that can display
>>>> icons, and the icons either have a mouseover "tiptext" and/or are
>>>> to pop up a message window. This could cover both this caution
>>>> message, and
>>>> the "not checked for updates" message (and whatever else comes up
>>>> down the
>>>> road.) (Or maybe put said icons in the "version" cell? Better
>>>> than a whole new
>>> I'd put it in front of the plugin name.
>>> However, given the separation of plugins in 2.6 and 2.7-bleeding, I'd
>>> prefer to simply create a new section at the top of the page: "Plugins
>>> that need attention."
>>> Move plugins that need updates, plugins not checked, plugins found to
>>> use deprecated functions, etc, all up there.
>> FAR to intrusive. There should be a notice, but they shouldn't
>> radically alter the plugin organization. These are relatively minor
>> cautions, not major RED ALERTs.
>> On Jul 28, 2008, at 6:42 PM, Adam Hunter wrote:
>>> create a mechanism ( using the same concept that updates the plugins
>>> ) to check them against a depreciated function list before updating
>>> wordpress to a new version?
>> Interesting idea, but probably a bit much. What we could do, RE the
>> idea above, is to have different levels of warning --
>> 1) This plugin contains outdated (deprecated) code.
>> 2) This plugin contains obsolete (called functions are gone!) code.
>> I was almost going to suggest auto-deactivation, but I don't think we
>> should go that far, as the outdated code might be part of minor
>> functionality and we shouldn't DEMAND that the user can't try to use
>> the plugin.
>> What we're really doing is telling them where to look first if
>> there's a problem.
> wp-hackers mailing list
> wp-hackers at lists.automattic.com
More information about the wp-hackers