#15824 closed defect (bug) (fixed)
Introduce _doing_it_wrong to mark places where plugins / themes are calling functions incorrectly
Reported by: | westi | Owned by: | westi |
---|---|---|---|
Milestone: | 3.1 | Priority: | normal |
Severity: | normal | Version: | 3.1 |
Component: | Warnings/Notices | Keywords: | |
Focuses: | Cc: |
Description
We are starting to mark incorrect usage of functions with _deprecated_function
where as we should have a specific way of marking these so the message is correct as we are not deprecating something but telling people the code they have written won't work
Change History (17)
#5
@
14 years ago
Not sure if there are any other places we are using _deprecated_argument when we should be using this.
#6
@
14 years ago
Just checked them all. We could really use a _deprecated_message() function for a few cases where we've overloaded _deprecated_argument(), but all are indeed deprecated instances of arguments or something.
#13
@
14 years ago
sorry for reopen this ticket.
getting this message in the dashboard after updating to the latest trunk (from yesterday)
Warning: Missing argument 3 for _doing_it_wrong(), called in /wp-includes/plugin.php on line 663 and defined in /wp-includes/functions.php on line 3404
have you all a great xmas time
Note: See
TracTickets for help on using
tickets.
Example: Notice: register_uninstall_hook was called with an argument that is deprecated since version 3.1! Only a static class method or function can be used in an uninstall hook.