Making WordPress.org

Opened 3 years ago

Last modified 22 months ago

#4346 new defect

Support Forum: Embed loses fragment identifier

Reported by: joyously Owned by:
Milestone: Priority: normal
Component: Support Forums Keywords: close


I put this URL into a forum reply, and the embed didn't have the fragment identifier.

The link in the embed was to the page without the fragment ID, thus losing the specific detail that was wanted.

Could be related to #3916

Change History (6)

#1 @netweb
3 years ago


I added https://wordpress.org/support/article/writing-posts/#visual-versus-text-editor to https://wordpress.org/support/topic/test-helphub-urls/ (now archived). When editing that post the link is correct, though viewing the post embed the link is truncated to https://wordpress.org/support/article/writing-posts/

#2 @dd32
3 years ago

This ultimately comes back to a short-coming of the WordPress oEmbeds, bluntly fragments are not supported.

If you look at the resulting embed, it's something like this:

I think there's two things in play here:
1) Core doesn't support Fragments, and should not embed URLs if they have fragments, and/or should support fragments (This needs to be filed on core.trac)
2) The Support Forum can probably work-around this and disable embeds for URLs which have a fragment specified.

This ticket was mentioned in Slack in #meta by tellyworth. View the logs.

3 years ago

#4 @tellyworth
3 years ago

Given point (1) this really should be reported upstream to Core.

#5 @tellyworth
3 years ago

  • Keywords reporter-feedback added

#6 @dd32
22 months ago

  • Keywords close added; reporter-feedback removed

Reported upstream as #core49682, Let's keep this ticket open for now to see what core does, it might still be best to disable the embedding of WordPress.org URLS for the support forums.

Note: See TracTickets for help on using tickets.