-
I am having a problem displaying an MP4 file in a post after upgrading to WordPress 4.0. Pinboard seems to handle the video file as an error and throws a black block on top of the video image. Formatting for the thumbnail is also a bit messy now. Switching to a different theme eliminates this problem, so I am assuming it is related to the Pinboard code… Can you help?
http://ontherocks.biz/tubular-herringbone/There are several issues with the compatibility between WordPress’ built-in MediaElement script and the way this theme used to handle videos. The theme used to come bundled with the MediaElement script before it was included into core and have its own implementation. We’re probably have to rethink that entire implementation as WordPress’ implementation does not appear to support dynamic loading. This will take a while so you’ll probably want to roll back to an older version of WordPress or switch the theme until the issue is resolved.
Hi,
there are not only problems with video when using Pinboard with WP 4.0.
Same goes for Audio posts.The layout of the player is messed up and does not show controls to play the audio but only to download the audio. If you click on download nothing gets downloaded either.
Any thoughts on time needed to correct this?
Rolling back to an older WP version is not an option for me, sadly.Thanks
AlexHi,
The problem with embedded videos lies in WordPress core’s implementation of the MediaElement.js script. It is added synchronously in the page’s footer and no event to reload it after AJAX requests (or at least we haven’t been able to discover them).
Even their own themes suffer from this implementation, take for example Twenty Thirteen‘s demo at wordpress.com. With infinite scroll the audio player doesn’t load.
The only compromise solution we have found is to scrap the MediaElement skin the theme uses and fall back to the native HTML5 player on AJAX events. That’s how we’ve implemented it in Enlightenment theme.
Before going forward with this change I would like to ask your opinion in this regard. How important is the audio and video player’s skin for your videos? Would you agree to use the default skin from WordPress and fall back to the native HTML5 player on events such as infinite scroll?
Hi,
my highest priority would be, that it works and I can upload videos and music and play it from within pages and articles.
If it also works as “article image” in the blog roll and as “featured image” it would be perfect.
Looks fine with me in the Enligtenment demo.
This change would not have an effect on embedding videos from youtube, right?Regards
AlexHi,
maybe I was not precise enough with my answer: Falling back to WordPress’ default skin is no option for me. I’d need and want video and audio to work with Pinboard. 🙂
Can it be done? And what’s the time line?Alex
The WordPress default skin is HTML5 and fully compatible with both audio, video and playlists. Converting the current skin for compatibility with WP 4.0’s MediaElement.js implementation is not a do-it-fast task. What do you find insufficient with the default skin?
There are several downsides to using the Twenty Fourteen theme. E.g. the way it handles featured articles. Or the general layout and look. I’m running two sites with Pinboard because it suites my wishes of design and functionality most and works with all the plugins I’m using. So changing the theme is not really an option for me.
Thanks Alex
I believe we are in a terminology conflict here. Let’s call Pinboard and TwentyFourtheen “themes” and the MediaElement.js polyfills “skins”. What I mean by default skin is how WP 4.0 styles the HTML5 video player by default. Pinboard theme uses a custom skin that overrides WP’s default behavior. It used to do this since WP 3.1 when MediaElement.js wasn’t part of WP Core. That’s where all the incompatibility comes from.
Ah ok. I sort of had a similar suspicion as well in the meantime, that we might have a terminology conflict. 🙂
I understand: Is there a quick possibility for me to test this by disabling the customer MediaElement.js? And how do I do it? That might actually be a solution I could work with. So I’d like to try it out.Thanks, Alex
The theme will use the built-in MediaElement.js skin except for AJAX requests where it will fall back to the default HTML5 skin.
Version 1.1.10 has been released where this issue was fixed. Usually it takes a while for the update to appear in the WP admin. You can download it here.
You must be logged in to reply to this topic.