WordPress.org

Make WordPress Core

Opened 4 years ago

Last modified 5 months ago

#32803 new defect (bug)

get_extended() Loses Container Tags When Opening Tag is in [main]

Reported by: rcgordon Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.2.2
Component: Editor Keywords:
Focuses: Cc:
PR Number:

Description (last modified by dd32)

get_extended($post->post_content)['extended']) loses container tags that were opened in [main] and completed in [extended].

The missing opening tag should be inserted at the start of the [extended] HTML segment and the missing closing tag should be add at the end.

For instance if there is a <blockquote> tag in the [main] section (prior to a <!--more--> comment/tag), and the blockquote completes anywhere within or following [extended], that blockquote element is entirely missing in the [extended] segment.

I'm not sure if the Editor section is necessarily where this ticket should go. But it concerns the way the editor modifies the final code.

Change History (3)

#1 in reply to: ↑ description @rcgordon
4 years ago

Replying to rcgordon:

Sorry, I misformatted the bracketed component of extended. (Hoping backslashes help.)


get_extended($post->post_content)\['extended'\]) loses container tags that were opened in [main] and completed in [extended].

The missing opening tag should be inserted at the start of the [extended] HTML segment and the missing closing tag should be add at the end.

For instance if there is a <blockquote> tag in the [main] section (prior to a <!--more--> comment/tag), and the blockquote completes anywhere within or following [extended], that blockquote element is entirely missing in the [extended] segment.

I'm not sure if the Editor section is necessarily where this ticket should go. But it concerns the way the editor modifies the final code.

#2 @dd32
4 years ago

  • Description modified (diff)
Note: See TracTickets for help on using tickets.