#4758 closed enhancement (invalid)
There should be a Hook between a pages/posts textarea and the submit button.
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Severity: | normal | Version: | 2.2.2 |
Component: | Optimization | Keywords: | |
Focuses: | Cc: |
Description
I replaced TinkerMCE "Rich Editor" with one i prefer (and one that is standards-compliant, and faster at the same time). Unfortunately i dont know how to parse that pages complete source (as i have seen dashboard-modifiying plugins did with ob_start). So there is no way for me or my plugin to add my <object> above the Submit-Buttons for saving and publishing a post or a page. Thus resulting in a strange order.
Another Scenario where this would be helpful is when you need to use custom fields more intense (eg. for a posts translation into another language) in this case you'd normally want the custom field directly below the other language.
Or when you use wordpress for a photolog, where you'd want another custom field (eg for the images URL, or its filename.) Here, the custom field also would be of the most importance on that posts admin-page, but one can't give it an appropriate place.
Regarding WP2.3's Tagging-functionality, i'd like to see the hook even above the tag-area :)
Are there any possibilities to get that additional hook into there? What reasons one can think of not to include one there.
Attachments (1)
Change History (4)
#1
@
17 years ago
no pros? no cons? is someone listening? regards (added a screenshot. hope that explains it better)
Btw: its not joomla. its wordpress. Jon of Belus Technology, the developers of XStandard, offers including a GUID for WordPress (so it would read XStandard Lite for WordPress instead). There are a lot of Examples (like Joomla, CMS MAde Simple, etc. etc.) of even smaller CMSs than WordPress take part in the XStandard for Open Source Partner CMS Program. I wish WordPress could take this small step and opened a bit regarding WYSIWYG-Integration. For the benefits of a better User Experience.
illustrates what the ticket (tries to) describe. no action between textarea and submit buttons