Make WordPress Core

Opened 14 years ago

Closed 14 years ago

#16663 closed defect (bug) (invalid)

YouTube oEmbed code invalid, therefore not showing mobile version.

Reported by: hotforwords's profile hotforwords Owned by: hotforwords's profile hotforwords
Milestone: Priority: normal
Severity: normal Version: 3.1
Component: Media Keywords:
Focuses: Cc:

Description

The YouTube oEmbed code is giving incorrect code and as a result the mobile version of the resulting embed is not showing.

The resulting Object that is embedded is putting in a /e/ in the URL when it's supposed to be putting in a /v/

For example, when I put the following URL into a post:

http://www.youtube.com/watch?v=H6m0EPQOKPw


the resulting current incorrect embed code created is:

<object width="655" height="398">
<param name="movie" value="http://www.youtube.com/e/H6m0EPQOKPw"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/e/H6m0EPQOKPw" type="application/x-shockwave-flash" width="655" height="398" allowscriptaccess="always" allowfullscreen="true"></embed></object>

Note the /e/ after the www.youtube.com that is repeated twice.

value="http://www.youtube.com/e/H6m0EPQOKPw"

The embed code should be:

<object width="655" height="398">
<param name="movie" value="http://www.youtube.com/v/H6m0EPQOKPw"></param><param name="allowFullScreen" value="true"></param><param name="allowscriptaccess" value="always"></param><embed src="http://www.youtube.com/v/H6m0EPQOKPw" type="application/x-shockwave-flash" width="655" height="398" allowscriptaccess="always" allowfullscreen="true"></embed></object>

With /v/ being inserted in the two URLs not /e/

Change History (2)

#1 @ocean90
14 years ago

Maybe you should report it directly to YouTube, because the code comes from the YouTube API; see
http://apiblog.youtube.com/2009/10/oembed-support.html
http://core.trac.wordpress.org/ticket/10337#comment:37

#2 @nacin
14 years ago

  • Keywords needs-patch removed
  • Milestone Awaiting Review deleted
  • Resolution set to invalid
  • Status changed from new to closed

Indeed, this needs to be reported upstream.

Note: See TracTickets for help on using tickets.