Closed (fixed)
Project:
Media entity Twitter
Version:
8.x-2.x-dev
Component:
Code
Priority:
Critical
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
9 Oct 2023 at 08:55 UTC
Updated:
27 Aug 2025 at 12:34 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
paulrad commentedComment #5
paulrad commentedI've modified the regex check to work with both
twitter.comandx.comlinks. But the issue i that we still don't have a Media oEmbed provider for thex.com. So to properly work with links from the new domain you should create your custom provider using the oEmbed Providers module or wait for the core's Twitter provider update.Comment #6
it-cruThere is also an existing issue to support x.com in providers of oembed.com on Github.
https://github.com/iamcal/oembed/issues/710
Comment #7
kaszarobertAnd when the X oembed provider will be added to https://oembed.com/providers.json finally, the array in src/Plugin/media/Source/Twitter.php getProviders() function also needs to be changed to include the new X with the same provider_name, otherwise it won't work.
Comment #9
granik@paulrad, thanks four your MR, I just added a commit, now it seems to work fine.
Btw, X is now in provider list, thanks for your note, @kaszarobert.
p.s. Also added a patch to use with composer for now.
Comment #10
styx1983 commentedThe patch provided in #9 works fine for me.
Comment #11
kaszarobertNow that twitter.com site is being redirected and replaced with x.com, users will expect to embed new content with x.com URLs. Therefore I think this is a pretty important thing to merge this to the module ASAP.
Comment #12
lmoeniI tested the patch from #9 which works fine. Thanks!
I agree with @kaszarobert that this should be published soon.
Comment #15
chr.fritsch