![(please configure the [header_logo] section in trac.ini)](/chrome/site/your_project_logo.png){kind=logo}
#6196 closed enhancement (fixed)
New action hook for edit.php for plugin authors to add new filter field...
| Reported by: | nerrad | Owned by: | westi |
|---|---|---|---|
| Priority: | normal | Milestone: | 2.5 |
| Component: | Administration | Version: | 2.5 |
| Severity: | blocker | Keywords: | needs-patch regression |
| Cc: | Focuses: |
Description
Why? If plugin authors want to be able to add a new field for filtering the posts on the "Manage->Posts" menu they can use this action hook to insert the form field before the submit button.
Currently (2.5 beta 1) it is possible to add a field via the 'restrict_manage_posts' action hook (see attached screenshot for example) but that is a cludgy solution at best and isn't good for user-friendly ui.
(This would be a complement to ticket: #5899)
Attachments (4)
Change History (10)
#1
@
18 years ago
- Keywords regression? added
- Milestone 2.6 → 2.5
- Owner changed from to
- Severity normal → blocker
- Status new → assigned
Hmm that looks like restrict_manage_posts may have ended up in the wrong place after the latest changes.
I'll look into this.
#2
follow-up:
↓ 3
@
18 years ago
I don't think restrict_manage_posts is in the wrong place. My understanding is that it's purpose is for adding hook for filtering by type should a plugin author create a new post type. Therefore you'd want restrict_manage_posts to be where it is for adding in the same line as the other post-type filter options.
However, my suggested new action hook would be for plugin authors to add in a new form-field for filtering by a new post-taxonomy in the indicated location. It'd be nice to have the option of the two possible locations for insertion rather than just one (due to the new ui layout)
#3
in reply to: ↑ 2
@
18 years ago
- Keywords needs-patch regression added; has-patch regression? removed
Replying to nerrad:
I don't think restrict_manage_posts is in the wrong place. My understanding is that it's purpose is for adding hook for filtering by type should a plugin author create a new post type. Therefore you'd want restrict_manage_posts to be where it is for adding in the same line as the other post-type filter options.
However, my suggested new action hook would be for plugin authors to add in a new form-field for filtering by a new post-taxonomy in the indicated location. It'd be nice to have the option of the two possible locations for insertion rather than just one (due to the new ui layout)
restrict_manage_post is in the wrong place - trust me I invented it ;-) [4321]
Unfortunately because of the design of the new admin ui where the whole list is inside the form we can't let plugins add there own form.
I think we need to move restrict_manage_post inside the form back where it should be rather than add another hook - and make sure to notify plugin authors that it has changed slightly.
#4
@
18 years ago
I have attached two sample plugins.
The first was my original test plugin for this hook when it was introduced and works fine in 2.3
The second is a version which will work for 2.5 once I check in a fix for this hook in the next few minutes.
Please re-open if there are still issues.
Example screen shot using 'restrict_manage_posts' action hook