Opened 4 years ago
Closed 2 years ago
#8805 closed enhancement (fixed)
Inline Documentation corrections for 2.8
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | low | Milestone: | 2.8 |
| Component: | Inline Docs | Version: | |
| Severity: | trivial | Keywords: | has-patch commit |
| Cc: | CharlesClarkson |
Description
Fixes for the inline documentation in WordPress 2.8.
Attachments (5)
Change History (23)
comment:1
jacobsantos — 4 years ago
comment:2
jacobsantos — 4 years ago
- Keywords has-patch commit added
comment:4
jacobsantos — 4 years ago
- Keywords needs-patch added; has-patch commit removed
comment:5
jacobsantos — 4 years ago
- Keywords has-patch commit added; needs-patch removed
comment:6
jacobsantos — 4 years ago
- Resolution set to fixed
- Status changed from new to closed
Patch was committed in early revision.
comment:7
jacobsantos — 4 years ago
- Keywords has-patch commit removed
comment:9
CharlesClarkson — 4 years ago
- Cc CharlesClarkson added
- Resolution fixed deleted
- Status changed from closed to reopened
Change to the Inline documentation for wp-includes/post.php.
comment:10
follow-up:
↓ 13
rmccue — 4 years ago
- Keywords has-patch commit added
comment:11
ryan — 4 years ago
- Component changed from General to Inline Docs
any traction?
comment:13
in reply to:
↑ 10
westi — 4 years ago
Replying to rmccue:
Change update_option() documentation to the right order for the filter
Not quite right that comment refers to the action really. Quite confusing!
Gonna fix it still. Good catch.
comment:14
westi — 4 years ago
comment:15
westi — 4 years ago
comment:16
westi — 4 years ago
- Resolution set to fixed
- Status changed from reopened to closed
Gonna close this for now.
Maybe another push on this for 2.9!
comment:17
CharlesClarkson — 2 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Added a minor (2 line) change for inline documentation for next WP release.
comment:18
nacin — 2 years ago
- Resolution set to fixed
- Status changed from reopened to closed
Please open a new ticket, thanks.
Note: See
TracTickets for help on using
tickets.

Hmm, The HTTP API stuff should be safe, but it'll probably be better to have its own ticket.