Ticket #6374 (closed defect: fixed)

Opened 8 months ago

Last modified 8 months ago

Editing a Post With an Existing Custom Field Value Containing an HTML Encoded Entity Produces an Unescaped Character Upon Save.

Reported by: qweenie Assigned to: markjaquith
Priority: normal Milestone: 2.5
Component: Administration Version: 2.5
Severity: normal Keywords:
Cc:

Description (Last modified by lloydbudd)

Editing a Post With an Existing Custom Field Value Containing an HTML Encoded Entity Produces an Unescaped Character Upon Save.

ENV: WP trunk 2.5 revision 7502
Repro: Always
Steps:
1. update a custom field with value of 'lopez & gwatney'
2. view post and the source of page shows a valid html escaped entity 'lopez & gwatney'
3. edit same post changing category and save
4. view post and the source of page shows invalid unescaped character. 'lopez & gwatney'

Expected Result:
Source of page to show 'lopez & gwatney' when displaying custom field value

Change History

03/24/08 21:40:26 changed by lloydbudd

  • version set to 2.5.
  • description changed.
  • milestone set to 2.6.

03/24/08 22:05:54 changed by markjaquith

  • owner changed from anonymous to markjaquith.
  • status changed from new to assigned.
  • milestone changed from 2.6 to 2.5.

Looks like we moved to using a <textarea /> but are still using attribute_escape() instead of htmlspecialchars()

03/24/08 22:06:18 changed by markjaquith

  • status changed from assigned to closed.
  • resolution set to fixed.

(In [7506]) Preserve HTML entities in Custom Fields. fixes #6374