The best WP YouTube Lyte to date!

March 1, 2013 by futtta

Today WP YouTube Lyte 1.2.0 got finally pushed out the gates! This new version is beyond any doubt the best version to date, with the following new features:

LYTE embeds are now fully responsive
automatic inclusion of scheme.org microdata (VideoObject) (also known as “rich snippets”)
even better performance (less requests; was 5, now 3)
updated to the current YouTube look & feel, see this YouTube video about microdata:

Introduction to Rich Snippets

Introduction to Rich Snippets

Watch this video on YouTube

Although I did go through a small beta-cycle, with feedback from 5 users (thanks guys), I am pretty sure there still are bugs that will rear their ugly head in the following days (some strings haven’t been translated yet, for example). Do contact me, add a comment here or create a post on the wordpress.org forum in case you encounter unexpected behavior!

21 thoughts on “The best WP YouTube Lyte to date!”

frank
March 3, 2013 at 7:50 am
We have our first bug; modernizr classes on html-elements confuse LYTE into thinking it should display an audio-only YouTube embed. There’s a workaround in the comments of the linked blogpost above, a real fix will be in 1.2.1.
Reply
Peco @ Dub Techno Blog
March 3, 2013 at 10:15 am
Hmmm the new update seems to have messed up my embeds from previously added posts
example – http://www.dubtechnoblog.com/2013/02/14/free-tune-advanced-dreams-monotone-live/
Reply
- frank
  March 3, 2013 at 10:21 am
  Hi Peco; that indeed is a bug (sorry about that), will be fixed in 1.2.1 (tomorrow). temp. fix: open up /wp-content/plugins/wp-youtube-lyte/wp-youtube-lyte.php and on line 283 in the CSS replace all occurences of “.audio” with “.lyte-audio”.
  Reply
  - Peco @ Dub Techno Blog
    March 3, 2013 at 10:25 am
    couldn’t actually find any “.audio” in the file, ill just wait till tomorrow no biggy
    thanks again for all the work put into this
    Reply
    - frank
      March 3, 2013 at 11:02 am
      can you try with this development build?
      Reply
  - Delphuk
    March 3, 2013 at 11:21 am
    Yes, this build work a good.
    Reply
Nils
March 3, 2013 at 1:37 pm
All videos i have embed with youtube lyte are have only a black screen and no graphics from you lytesprite.png
http://www.nils-snake.de/archives/sin-city-the-all-green-version
Reply
- frank
  March 3, 2013 at 3:59 pm
  The problem seems very cloudflare-related Nils, lyte-min.js isn’t loaded?
  Reply
Massa (fruityoaty)
March 4, 2013 at 5:19 am
Fantastic plugin! Loved it since its early beginnings. Anyhoo… the audio player widget is broken now on my blog since I updated to 1.2.0 (and even 1.2.1). Worked fine before. Just appears as a gray bar with no controls. Looks like this (example 250w x 200h chosen): http://images.plurk.com/Yx4-VXuQDJVMNjDpfGI1baD02.jpg
Thank you for continuing to share and maintain your awesome plugin. 🙂
Reply
- frank
  March 4, 2013 at 7:08 am
  Hi Massa! Glad to see you’re still around 🙂
  The problem is this style your theme’s CSS:
  .secondary div { margin: 30px 0 0 }
  which adds 30 pixels to every div in your sidebar (which is pretty … extreme if widgets have multiple div’s in them as does WP YouTube Lyte).
  I you add this to your CSS:
  .lyte div { margin: 0 !important; }
  Your audio-player-widget should look (&work) OK.
  Reply
- frank
  March 4, 2013 at 8:10 am
  I’ll probably -if this gets through some more testing- add something like this to 1.2.2;
  .lyte-wrapper-audio div, .lyte-wrapper div, .lyte-wrapper-audio, .lyte-wrapper { margin: 0 !important; padding: 0 !important; overflow: hidden; }
  This will probably also tackle the issue you mention you observed in posts.
  Reply
Massa (fruityoaty)
March 4, 2013 at 5:40 am
Hi, me again. I should also add that the video player widget functionally works (controls + background image appears, video plays fine when play button is clicked), BUT the player now appears strangely (control bar appears higher, background image appears lower from top). Used to look fine before I updated to 1.2.0 (and 1.2.1). Not a deal-breaker since I don’t use the video player widget… but I do love, love, love the audio player widget so I hope the audio player widget issue can be addressed some day. 🙂
Reply
- frank
  March 4, 2013 at 7:11 am
  Pretty sure this is CSS-hell as well. Any post/ page with a video for me to look at? 🙂
  Reply
Massa (fruityoaty)
March 4, 2013 at 4:59 pm
Thank you! Indeed, my problem with both the widget’s audio & video display had to do with my theme’s CSS: .
.secondary div { margin: 30px 0 0; position: relative }
1. As you suggested, adding this to my theme’s CSS fixed the audio widget display:
.lyte div { margin: 0 !important; }
2. .secondary div { position: relative } in my theme’s CSS was making the control bar appear higher.
To fix my issue, I did one of the following:
A) Remove “position: relative” in .secondary div { } in my theme’s CSS.
OR…
B) Add .lyte div { position: absolute !important } in my theme’s CSS.
Thank you for troubleshooting my theme! Problem solved! 🙂
Reply
Collin
March 30, 2013 at 1:48 pm
Google Webmaster tools notified me of a soft 404 issue which was caused by YouTube Lyte. What happened is that a video on one of my pages was set from public to private by the YouTube user. This caused Youtube Lite to crash with an array error taking down the parsing for the rest of the page (which is a soft 404 in google webmaster tools).
Would love to see this fixed in the next version as it is a situation that isn’t easy to detect and takes down an entire page if triggered. 😉
This is the error that’s triggered:
Fatal error: Cannot use string offset as an array in [redacted]/wp-youtube-lyte.php on line 236
Reply
- frank
  March 31, 2013 at 8:15 pm
  Hmm, obviously got some error-handling to improve here. Thanks for reporting!
  Reply
- frank
  March 31, 2013 at 9:40 pm
  regarding the ugly error; add this on line 230:
  if (is_array($yt_resp_array)) {
  and close the if-block on line 244 with }
  would be great if you could test & confirm if this works?
  Reply
Justin Morrison
June 25, 2013 at 9:00 pm
I’m very much enjoying the use of this fantastic plugin. There is one very small issue in that posts published with embedded youtube videos (using your functions.php handler for regular youtube links) do not serve thumbnails to Facebook pages, which is an issue for folks like me who primarily use Facebook to publicize WordPress posts with embedded content.
I’m reviewing the plugin source and resulting post html to see if I can make a suggestion for a quick fix here.
Reply
- frank
  June 26, 2013 at 6:22 am
  Hi Justin; Had a quick look at your site, and guess the problem is due to the fact that you specifically specify an image for Facebook here
  
  And so Facebook does not pick up on the video thumbnail that is specified in the microdata section of the lyte-player. This is about the only logical explanation I can find, really, as Facebook does not have a problem to find the thumbnail-image in my own posts 🙂
  Reply
  - Justin Morrison
    June 26, 2013 at 7:57 am
    Thanks for your quick reply. Unfortunately your observation vis a vis the specific post you mentioned doesn’t apply in this case as that particular post came before I began using Lyte, and there were no issues, at the time, with FB interpreting thumbnail specifics when I did promote it. My issue at this moment is that NO thumbnail is being picked up by FB since using Lyte, which wasn’t an issue before with regular wordpress handling of youtube embeds (in conjunction with Video Thumbnails plugin).
    I’ll continue to poke around and let you know if I find anything that might be of help. Could be theme layer. Could be something else.
    Reply
    - frank
      June 26, 2013 at 8:16 am
      That’s very weird, moreover so as I did see a thumbnail (the /wp-content/uploads/2013/05/weapon-trailer-june-7-8-9-counterpulse-150×150.jpg one) when adding the link to your post on Facebook?
      I would disable SEO ultimate if I were you, just to see what that changes 😉
      Reply

Leave a Comment Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.