#4503 closed enhancement (invalid)
Options Page Hooks
| Reported by: |
|
Owned by: |
|
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | Administration | Version: | |
| Severity: | normal | Keywords: | hooks |
| Cc: |
Description
Unless I'm overlooking something, there's hardly any hooks at all available for plugin authors to add items to existing options pages. Initial attempts here and probably limited by the data entry on the backend, but I can do more work if these hooks seem appropriate.
Attachments (1)
Change History (12)
technosailor — 6 years ago
comment:1
Viper007Bond — 6 years ago
Yes, Viper007Bond's explanation makes sense.
I see no reason to fix. Anyone else?
comment:3
technosailor — 6 years ago
Wouldn't that be up to plugin authors to decide? I mean I agree with you, but for single option things that belong with other relevant options, it seems to me we should make it possible to do.
- Milestone changed from 2.3 to 2.5 (future)
- Type changed from defect to enhancement
- Resolution set to fixed
- Status changed from new to closed
invalid, no? there are do_settings_fields() and do_settings_sections() function in the 2.7 branch.
comment:7
jacobsantos — 4 years ago
- Milestone changed from 2.9 to 2.7.1
comment:8
jacobsantos — 4 years ago
- Keywords 2nd-opinion removed
comment:10
azaozz — 4 years ago
- Resolution set to invalid
- Status changed from reopened to closed
Close as invalid not fixed..
comment:11
westi — 4 years ago
- Milestone 2.7.1 deleted
Note: See
TracTickets for help on using
tickets.

I think this idea is so that people don't start sticking things into the official options pages. From what I've heard, there's been a push to keep plugin options distinctively separate.