Opened 8 years ago
Closed 7 years ago
#43643 closed enhancement (fixed)
Properly document the `$page_hook` action
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Milestone: | 5.1 | Priority: | normal |
| Severity: | normal | Version: | |
| Component: | Plugins | Keywords: | has-patch 2nd-opinion |
| Focuses: | docs | Cc: |
Description
The $page_hook action lacks meaningful documentation. This is the only action in core that uses a completely dynamic hook name, which means it needs to be well documented to help developers who may wish to use it.
Most of the documentation from the load-{$page_hook} action immediately above it can be reused, and then the @ignore tag can be removed so the unnecessary private flag gets removed from the developer reference.
Refs:
Attachments (1)
Change History (4)
Note: See
TracTickets for help on using
tickets.
So, this hook is used by core itself to load the plugin page, but there's technically no reason for it to be ignored / marked as private. Thoughts?