Opened 16 years ago
Closed 16 years ago
#6343 closed defect (bug) (fixed)
Adding custom field: wording and behaviour
Reported by: |
|
Owned by: |
|
---|---|---|---|
Milestone: | 2.5 | Priority: | normal |
Severity: | normal | Version: | 2.5 |
Component: | Administration | Keywords: | AJAX has-patch needs-testing |
Focuses: | Cc: |
Description
Adding custom fields has changed with 2.5rc1.
It seems impossible now to add more than one custom field before saving the post.
Clicking "Add Custom Field" does NOT (only) what the button says, but will also save the post. Either the wording is wrong or the behaviour.
Please bring back the 2.3.3 behaviour. I am developing a site where every post is just one or two sentences and two, sometimes three custom fields. It used to take about 20-30 seconds to write a post using 2.3.3, now its turning into a clickfest.
One or two more form elements for adding custom fields would also solve my problem, but the old way to do it used to be far better than that. I am considering to stay with 2.3.3.
Attachments (2)
Change History (9)
#1
@
16 years ago
- Keywords AJAX added
- Milestone changed from 2.7 to 2.5
- Owner changed from anonymous to mdawaffe
#2
@
16 years ago
- Status changed from new to assigned
I'll have a patch for this by Saturday afternoon PST.
#3
@
16 years ago
- Keywords has-patch needs-testing added
6343.diff
- Fixes custom field add/update/delete.
- Uses autosave functions after adding a custom field to a never-before-saved post to update post id.
- Fixes strange wp-lists animation bug.
jQuery( ... ).stop(); // doesn't work jQuery( ... ).stop().stop(); // does
#4
@
16 years ago
Working well here. I notice that after adding a meta key to a new post, if you add title text and then change focus to another field the autosave on title blur doesn't kick in. Not a big deal.
#6
@
16 years ago
- Resolution fixed deleted
- Status changed from closed to reopened
Adding new meta keys when no meta keys currently exist is broken after the commit.
Upon clicking add, I get several PHP errors, To me, it looks like its not taking the correct branch.
Heres the post data:
array '_ajax_nonce' => string '92ea72e0e5' (length=10) 'action' => string 'add-meta' (length=8) 'post_id' => string '136' (length=3) 'metakeyinput' => string 'testkey' (length=7) 'metavalue' => string 'testvalue' (length=9)
I'll attach a patch for what seems to be the correct behaviour & is working for me
Looks like the Add Custom Field AJAX is busted.