Make WordPress Core

Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#42177 closed defect (bug) (invalid)

Pinterest oEmbed fails with TLD

Reported by: gemmaevans's profile gemmaevans Owned by:
Milestone: Priority: normal
Severity: normal Version: 4.8.2
Component: Embeds Keywords:
Focuses: Cc:


Inserting a Pinterest URL containing a TLD does not embed a board, profile or individual pins.

Steps to reproduce

  1. Go to Pinterest
  2. Copy the URL of a board containing a Pinterest TLD. For example:

  1. Go to Posts > Add New
  2. Click on the Visual editor tab
  3. Paste in the URL from step 2 ( TLD)
  4. Publish the post
  5. View the post on the front end


I expected to see the Pinterest board embedded in my post.


The Pinterest board was displayed as a URL rather than embedded into the post. However, I was able to successfully embed the Pinterest board by changing the Pinterest TLD from to .com:

Once the URL had been updated and the post was saved, the Pinterest board was embedded.

WordPress version 4.8.2

Attachments (1)

pinterest-embed.png (1.4 MB) - added by gemmaevans 7 years ago.

Download all attachments as: .zip

Change History (7)

#1 follow-up: @danieltj
7 years ago

  • Keywords 2nd-opinion added

Is Pinterest in Core as an oEmbed provider? I tried looking for it and found no reference to it in v4.8.2 and I looked in the /wp-includes/class-oembed.php file to double check. This may sound silly, but just in case I've missed something/gone mad, do you have a plugin installed for this? @gemmaevans

#2 in reply to: ↑ 1 @gemmaevans
7 years ago

Replying to danieltj:
I've double checked and I don't have any Pinterest plugins installed on my site.

#3 follow-up: @mzwillus
7 years ago

  • Resolution set to invalid
  • Status changed from new to closed

Hi @gemmaevans,
this may not only be a a plugin related to Pinterest.

If you deactivate all your plugins, WordPress shouldn't be rendering at all.

#4 @mzwillus
7 years ago

  • Resolution invalid deleted
  • Status changed from closed to reopened

Didn't mean to close, sorry.

#5 in reply to: ↑ 3 @gemmaevans
7 years ago

  • Resolution set to invalid
  • Status changed from reopened to closed

Replying to mzwillus:
This appears to be a Jetpack issue so I've created a separate bug report on their repository:

I'll go ahead and close this.

Thanks for taking a look :)

#6 @swissspidy
7 years ago

  • Keywords 2nd-opinion removed
  • Milestone Awaiting Review deleted
Note: See TracTickets for help on using tickets.