Twitter vs X - oembed url

[Nathan Explosion]

Spotted that there are some x.com/ URLs now appearing for the normal tweet links - as a result, oembed will fail and they'll be links.

'twitter.com' => array( 'https://publish.twitter.com/oembed', static::EMBED_TWEET ),
'mobile.twitter.com' => array( 'https://publish.twitter.com/oembed', static::EMBED_TWEET ),

Tested and adding x.com equivalents of the above to oembedServices in \IPS\Text\Parser will sort it out.

'x.com' => array( 'https://publish.x.com/oembed', static::EMBED_TWEET ),
'x.twitter.com' => array( 'https://publish.x.com/oembed', static::EMBED_TWEET ),

 

[Matt]

Cheers, moved to our issue tracker.

[marklcfc]

1 hour ago, Nathan Explosion said:

Tested and adding x.com equivalents of the above to oembedServices in \IPS\Text\Parser will sort it out.

Is this a file to edit?

I've been having complaints about this for a while

[marklcfc]

Is there any fix for this until the 4.7.13 is released proper? (assume its fixed in that?)

Happy to edit a file but need to know the changes to make, having so many x.com links being posted

Edited August 26, 2023 by marklcfc

[Randy Calvert]

It is fixed in 4.7.13. Generally IPS does not promote manually editing files and instead will recommend waiting for the version to be released.  

[Marc]

On 8/26/2023 at 12:45 PM, marklcfc said:

Is there any fix for this until the 4.7.13 is released proper? (assume its fixed in that?)

Happy to edit a file but need to know the changes to make, having so many x.com links being posted

The fix if you want it before 4.7.13 is released 'proper', would be 4.7.13 beta 

[Marc]

This issue was resolved in the recently released 4.7.13 release. Please update in order to fix this issue, and if you see any problem after that point, please let us know.