Ticket #5184 (closed enhancement: duplicate)

Opened 1 year ago

Last modified 1 year ago

Make it obvious when you're using deprecated functions

Reported by: westi Assigned to: westi
Priority: normal Milestone:
Component: Template Version: 2.3
Severity: normal Keywords:
Cc:

Description

We need to make it more obvious to plugin authors when they are using depreceated functions.

We can use the new WP_DEBUG define to enable some of this stuff and some stuff should always be enabled.

if WP_DEBUG we should just not include depreceated.php so errors are obvious.

Otherwise we can record calls to depreceated functions and notify the admin somehow

Change History

10/12/07 08:21:32 changed by ryan

rm wp-includes/deprecated.php :-)

10/12/07 12:44:13 changed by JeremyVisser

  • summary changed from Make it obvious when your using depreceated functions to Make it obvious when you're using depreceated functions.

10/12/07 12:44:27 changed by JeremyVisser

  • summary changed from Make it obvious when you're using depreceated functions to Make it obvious when you're using deprecated functions.

10/12/07 13:09:40 changed by johnbillion

Idea: Upon plugin activation when in WP_DEBUG mode, the plugin is grepped for deprecated functions and a warning displayed if any are found.

The Upgrade Preflight plugin hunts down potential 2.3 compatibility problems by traversing the plugin directory and using file_get_contents and strpos to find problem strings. A similar system could be used on plugin activation to hunt down deprecated functions within the a plugin.

Same thing could also be done for themes (related: #4361).

10/12/07 14:20:22 changed by JeremyVisser

John, I think your idea would be better suited to an upload site — you upload, we validate!

10/12/07 23:47:42 changed by Viper007Bond

  • version set to 2.3.

Agreed. I don't see the need for this to bloat core, although I do support the intent.

I had actually considered writing something like this:

http://groups.google.com/group/wp-hackers/browse_thread/thread/682206fd10b32247/f41498554d525641

But I got busy with other things. :(

12/20/07 20:38:36 changed by westi

  • status changed from new to closed.
  • resolution set to duplicate.
  • milestone deleted.

Closing as a duplicate of #4361 as they both share the same intent of increasing the obviousness of depreceated function usage.