- Issue created by @IT-Cru
- First commit to issue fork.
- Assigned to paulrad
- last update
about 1 year ago 5 pass - Issue was unassigned.
- Status changed to Needs review
about 1 year ago 11:58am 9 October 2023 - πΊπ¦Ukraine paulrad
I've modified the regex check to work with both
twitter.com
andx.com
links. 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. - π©πͺGermany IT-Cru Munich
There is also an existing issue to support x.com in providers of oembed.com on Github.
- Status changed to Needs work
about 1 year ago 10:45am 13 November 2023 - πΈπ°Slovakia kaszarobert
And 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.
- First commit to issue fork.
- last update
9 months ago 5 pass - Status changed to Needs review
9 months ago 1:59pm 4 March 2024 - last update
9 months ago 5 pass - π¦πΉAustria granik Vienna
@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.
- Status changed to RTBC
6 months ago 7:06am 23 May 2024 - πΈπ°Slovakia kaszarobert
Now 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.
- π©πͺGermany lmoeni
I tested the patch from #9 which works fine. Thanks!
I agree with @kaszarobert that this should be published soon.