Opened 22 months ago
Last modified 10 months ago
#4346 new defect
Support Forum: Embed loses fragment identifier
Reported by: |
|
Owned by: | |
---|---|---|---|
Milestone: | Priority: | normal | |
Component: | Support Forums | Keywords: | close |
Cc: |
Description
I put this URL into a forum reply, and the embed didn't have the fragment identifier.
https://wordpress.org/support/article/writing-posts/#visual-versus-text-editor
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)
#2
@
22 months 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:
https://wordpress.org/support/article/writing-posts/embed/#?secret=...
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.
21 months ago
#6
@
10 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.
Confirmed
I added
https://wordpress.org/support/article/writing-posts/#visual-versus-text-editor
tohttps://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 tohttps://wordpress.org/support/article/writing-posts/