[wp-trac] [WordPress Trac] #5257: Pages Must Be Saved Before Adding
Custom Fields
WordPress Trac
wp-trac at lists.automattic.com
Thu Oct 25 13:08:23 GMT 2007
#5257: Pages Must Be Saved Before Adding Custom Fields
----------------------------+-----------------------------------------------
Reporter: hughbiquitous | Owner: anonymous
Type: defect | Status: new
Priority: normal | Milestone: 2.3.1
Component: Administration | Version: 2.3
Severity: normal | Keywords:
----------------------------+-----------------------------------------------
If you add a custom field to an unsaved page, publishing the page turns it
into a '''draft post''' and data is lost.
'''Environment:'''
* At 2.3.1-RC1, SVN version 6280
(http://svn.automattic.com/wordpress/branches/2.3)
'''Repro Steps:'''
1. Create a new page.
2. Title it "Custom Field Bug".
3. Enter some text into the Page Content area.
4. Create a custom field (I used key="file", value="foo bar baz"). Click
"Add Custom Field".
5. Click Publish.
'''Expected Result:''' Page should publish.
'''Observed Result:'''
* After you click publish, it navigates to "Manage->Pages" menu but the
page is not there.
* Click on "Manage->Posts" and you will see a new, unpublished '''post'''
(not '''page''') that
* (A) '''does''' have the custom field, and
* (B) does '''not''' have the Post Content entered in step 3, and
* (C) does '''not''' have the title "Custom Field Bug" from step 2 --
instead, the title is "Draft created on (date & time)".
'''Note:''' I could not reproduce this for a post. It only happens for
pages.
'''Workaround:'''
1. Create a new page.
2. Title it "Custom Field Bug Workaround".
3. '''Click "Save and continue editing".'''
4. Create a custom field (I used key="file", value="foo bar baz"). Click
"Add Custom Field".
5. Click Publish.
This gives the expected result.
--
Ticket URL: <http://trac.wordpress.org/ticket/5257>
WordPress Trac <http://trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list