[wp-trac] Re: [WordPress Trac] #3700: Adding a custom field to an unsaved Page before publishing causes weirdness

[WordPress Trac]

#3700: Adding a custom field to an unsaved Page before publishing causes weirdness
----------------------------+-----------------------------------------------
 Reporter:  markjaquith     |        Owner:  Andy 
     Type:  defect          |       Status:  new  
 Priority:  normal          |    Milestone:  2.6  
Component:  Administration  |      Version:  2.3.2
 Severity:  normal          |   Resolution:       
 Keywords:  needs-patch     |  
----------------------------+-----------------------------------------------
Changes (by felipelavinz):

 * cc: guillep2k (removed)

Comment:

 Custom fields cause "publishing weirdness" on Pages even if you don't move
 quickly (as initially reported on this bug)... I've been working with
 Pages and custom fields on 2.5.1 and even with the trunk svn checkout, and
 everytime I try to add a custom field to a page I'm redirected to some
 other place... if, in fact, I go really quickly, before the auto-saving
 acts, clicking on "Add Custom Field" takes me to Write > Page, but none of
 the info I just entered it's there and I can't find that page anywhere...
 if I go slow and the page it's auto-saved before I add the new custom
 field, I get to Write > Page again, not to the Page I was editing, so I
 have to go to Manage > Pages and try to find it... The only "solution"
 I've found it's to write the info of the custom field and then, instead of
 clicking on "Add Custom Field", just click on "Save"... this, at least,
 works, but it feels totally primitive without the AJAX fireworks.

 Maybe this should have a higher priority/severity level, since it leads to
 unpleasant loss of work... just my opinion

-- 
Ticket URL: <http://trac.wordpress.org/ticket/3700#comment:14>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software