Opened 13 years ago
Closed 12 years ago
#20311 closed enhancement (invalid)
Docblock error for wp_unique_filename
Reported by: | transom | Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | trivial | Version: | 3.4 |
Component: | Inline Docs | Keywords: | has-patch |
Focuses: | Cc: |
Description
The current docblock for wp_unique_filename inaccurately describes the third parameter passed to this function
Attachments (2)
Change History (8)
#1
@
13 years ago
- Component changed from General to Inline Docs
- Keywords needs-refresh added
A note: patches should be made from root.
#2
@
13 years ago
- Cc joachim.kudish@… added
- Keywords needs-refresh removed
- Severity changed from normal to trivial
Amended transom's initial patch with the right format :)
#6
@
12 years ago
- Keywords commit removed
- Milestone 3.5 deleted
- Resolution set to invalid
- Status changed from new to closed
The documentation itself appears wrong.
* The callback is passed three parameters, the first one is the directory, the * second is the filename, and the third is an optional supplied callback * to generate a unique filename.
This paragraph is not talking about the function, whose third argument is indeed the optional supplied callback. This is talking about how the supplied callback gets called. As you can see, the third argument is indeed the extension:
call_user_func( $unique_filename_callback, $dir, $name, $ext );
Note: See
TracTickets for help on using
tickets.
Update docblock for wp_unique_filename