WP YouTube Lyte

An API is a way to have two pieces of software talk to each other to exchange information. In this case WP YouTube Lyte contacts YouTube to ask it for the thumbnail, the title and the description of the video you added. The thumbnail and title are visible on the webpage (in the Lyte player) while the description is in the HTML as microdata for search engines optimization reasons (see below).

1. Go to Google Developer Console and log in with your Google account.
2. Click on 'Create Project' and:
3. Fill in a Project Name
4. Fill in a Project ID
5. Click on 'Create'
6. On the next page (or when there is no next page, click on your Project's name):
7. Scroll down to YouTube Data API v3 and click on it
8. Click on 'ENABLE' at the top to enable the API
9. Optionally disable other API's
10. In the sidebar on the left:
11. Click on 'Credentials'
12. Click on 'Create Credential' at the top.
13. Click on 'API key'
14. Set as little restrictions as possible, most problems with getting this working are caused by these settings.
15. Click on 'Create'
16. Copy your API key to WP YouTube Lyte settings page.

In certain cases when adding restrictions the API key when tested might give technical warnings even if things are working correctly, make sure to check if new video’s are having the title displayed to confirm all is well.

Yes, with some exceptions; WP YouTube Lyte will continue to work, rendering Lyte players, but without the title and microdata (description, time, ...) and without thumbnails for playlists.

Just enter "none" (without the quotes) in the API key field and Lyte will stop nagging you.

As opposed to some of the most important plugins there is no 3rd party tracking code in WP YouTube Lyte, but YouTube off course does see visitor requests coming in for the thumbnails unless the option to cache thumbnails locally is enabled. If thumbnails are cached locally, no request will be sent to YouTube by your visitor's browser until/ unless the video is played.

LYTE by default uses WordPress' "the_content"-filter. Page builders don't apply that filter to their content and thus LYTE does not get triggered on those. As a workaround you can either add the LYTE widget or add the LYTE video using the shortcode in your page-builder Text-block, this works in most page-builders.

Just pass the httpv url of such a field to lyte_preparse like this: if(function_exists('lyte_preparse')) { echo lyte_preparse($video); } and you're good to go!

Starting from version 1.1.0 it does; in Infinite Scroll's configuration you just have to add "ly.te()" in the "Javascript to be called after the next posts are fetched"-box.

• There is a specific microdata scheme for "videoObject" which WP YouTube Lyte can add to your page, which Google can use to display the video thumbnail next to the search-result
• This is optional and can be disabled in the options page
• The videoobject microdata is NOT added for audio-only embeds, playlists or widgets
• Google will not always display the thumbnail, this presumably depends of the relevance of the video to the rest of the page.

In January 2014 Benetech, a U.S. nonprofit that develops and uses technology to create positive social change, offered a patch that adds the accessibilityFeature property to the microdata for videos that have captions. If you have microdata enabled, WP YouTube Lyte will automatically try to check (in a seperate, asynchronous call via a proxy-webservice, as YouTube only offers captions in their API v3 which requires authentication) if captions are available and if so, adds the accessibilityFeature property with value captions to the microdata. This can be disabled by either disabling microdata or, if you want microdata but not the accessibilityFeature-property by using the "lyte_docaptions"-filter to set captions to false (example-code is in lyte_helper.php_example).

• The video width in posts and pages will adapt to the width of the container (the div) in which your blogposts/ pages are shown. This means that if your theme is responsive, WP YouTube Lyte will follow.
• Widgets are not responsive.
• if the content div width gets to around 200 pixels, the LYTE UI will become garbled (YouTube requires the minimum embed width to be 200px as well).

Yes, starting with version 1.5.0 normal YouTube links are automatically transferred in Lyte embeds as well. You will automagically also get a (non-Lyte) preview of the video in your visual post edit screen. Starting from LYTE 1.7.5 YouTube iframes can be automatically converted as well.

A whole lot; there are filters to pre-parse the_content, to change settings, to change the CSS, to change the HTML of the LYTE-div, ... There are examples for all filters (and one action) in lyte_helper.php_example

All in One SEO Pack be default generates a description which still has httpv-links in it. To remove those, you'll have to use (example code in) lyte_helper.php (see above) and add lyte_filter_aioseop_description to the aioseop-filter in there.

You probably added a link around the httpv-url. No link is needed, just the httpv-url.

By default (unless "cache thumbnail locally" is active) WP YouTube Lyte will indeed load slower normal YouTube video's instead of Lyte ones, as Lyte video's require would require two clicks from the user to play a video (once to load the YouTube video and once to start it) because there is no autoplay-support on mobile. If you want to, you can force WP YouTube Lyte to make video's Lyte on mobile with this code (add it in your child theme's functions.php, in a seperate helper plugin or using the code snippets plugin; add_filter( 'lyte_do_mobile', '__return_true' );

lyteCache.php is a standalone file (it does not rely on WordPress) that is used when local thumbnail caching is active, which means requests for those thumbnails are handled by PHP. In WP YouTube Lyte 1.7.14 logic was added to prevent lyteCache.php doing thumbnail caching when being called directy without "local thumbnail caching" being active. Moreover if you want to ensure the thumbnails can only be used on your own site (and not hotlinked) you can use this code snippet: add_filter( 'lyte_filter_local_thumb_doublecheck', '__return_true' ); This will have WP YouTube Lyte set (in JavaScript in the HTML) and check (in the request for the thumbnail) a cookie. If the cookie is not set, the image request will be redirected to the YouTube origin URL.

• Having the same YouTube-video on one page can cause WP YouTube Lyte to malfunction (as the YouTube id is used as the div's id in the DOM, and DOM id's are supposed to be unique)

Just tell me, I like the feedback! Use the Contact-page on my blog, leave a comment in a post about wp-youtube-lyte or create a new topic on the wordpress.org forum.

• Tell me about bugs you think you've found and if you can't find any, confirm it works with your version of WP on wordpress.org
• Ask me for a feature you would like to see added
• Rate my plugin on wordpress.org