public-api OEmbed effectively double-encodes entities in title

  • Unknown's avatar
    stijnvandrongelen · Member ·

    I recently saw a post on a Mastodon instance that linked to a WordPress article. Mastodon automatically added a preview for this link. However, the apostrophe and a non-breaking space in the title of the article showed up as character entities. After looking closer, I discovered that this must be due to a bug in WordPress.com’s OEmbed endpoint.

    I initially directed this report at the developers of WordPress. Please refer to https://core.trac.wordpress.org/ticket/57190 for more technical information. The developers pointed that this is a ‘custom endpoint’ by WordPress.com and that I should contact WordPress.com directly. Apparently, the only option for me is a post in the public forums.

    Is there a way to attract attention of WordPress.com staff to this post? ;)

    WP.com: Yes
    Correct account: Unknown

    The blog I need help with is: (visible only to logged in users)

  • aleone89 · Staff ·

    Hey there,

    Thanks for sharing this! The endpoint would be a WordPress.com endpoint as this site is hosted with WordPress.com.

    We’re doing some investigating into this – but on first glance, there’s no HTML in the title to speak of, so it could be the case that the issue lies with Mastodon as they are responsible for generating the preview.

    We’ll keep you posted!

  • The topic ‘public-api OEmbed effectively double-encodes entities in title’ is closed to new replies.