Skip to:
Content

BuddyPress.org

Opened 9 years ago

Closed 9 years ago

#6522 closed defect (bug) (worksforme)

Media Extractor not correctly respecting post content markup

Reported by: hnla's profile hnla Owned by:
Milestone: Priority: normal
Severity: normal Version: 2.3.0
Component: Activity Keywords: reporter-feedback
Cc: hnla

Description

This is a follow-up to #6177.

It appears that paragraphs are stripped that follow after the image in a post.

If I add three paragraph tags and in first add text in second add an image from media library, in the third further text in the activity excerpt returned the third paragraph is removed and it's text appears in the second one above the image.

I'm also a little concerned that in stripping out the WP classes i.e removing 'thumb' we lose the ability to have uniform images unless forced via CSS i.e we can't make use of custom thumb sizes to ensure post images are an even size but that is probably an unwarranted concern.

Change History (5)

#1 @hnla
9 years ago

To qualify things:
The markup issue is not one belonging to this newer implementation of media in activity stream, it existed before media extractor class was introduced in 2.3.

#2 @DJPaul
9 years ago

  • Keywords reporter-feedback added

Can you stick a small example of markup demonstrating this problem, and attach to the ticket? Will be much easier to test/repro with a known bad sample and save time.

#3 @DJPaul
9 years ago

@hnla did you ever get chance to get a sample of markup?

#4 @hnla
9 years ago

No sorry slipped by me, but can't really produce markup it's created in the editor, as per the opening comment, the markup would be three paragraphs, BP removes the third one when creating the act item and adds the data to the second and with the image following after the cdata.

I would close this ticket, no one else has spotted this or raised concern so probably not worth fixing.

#5 @DJPaul
9 years ago

  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Status changed from new to closed

Closing issue because we've not been able to reproduce it

Note: See TracTickets for help on using tickets.