This forum is now read-only. Support is provided at https://wordpress.org/support/plugin/sermon-browser/
Log In
Register
Home
Topic RSS
2:17 pm
Moderators
18 June, 2009
Offline
It looks like WordPress 3.6 is going to include MediaElement.js as part of the core software. While this will probably make it easy for new users to set up their site, I don't know what it is going to do to our existing installations. It might force us to deactivate our media player plugins and change our "MP3 shortcode" settings.
I haven't tried out WordPress 3.6 yet (currently in beta). Anyone want to try this out?
Ben Miller, Pathways Church, Appleton, Wisconsin, USA
Read the new FAQ, last updated 11/21/2013
Announcing version 0.45.12
4:26 pm
19 February, 2013
Offline
HI Ben,
I have a WP 3.6 site running on nightly updates here - http://ddandh.ca Talk about frustrating. So far as I can determine the core files presently do not include MediaElement.js even though WP itself says it will. So I installed MediaElement.js, created a test post and spent the last 3 hrs or so, dare I say playing with it. Currently I've deactivated MediaElement.js for a break. I can at this point say that using {audio}{/audio} didn't work for me until I made these {mejsaudio}{/mejsaudio}. Next I tried all the shortcode options. Just before turning the MEJS off all I could get working was the first player. The others look fine but they do not play anything.
A few minutes ago I purchased this http://www.tsplayer.com/audio-.....deo-player (the WP plugin) because ultimetly it will do more of the things and $30 was not going to break the bank. I want i.e.: playlists Note this is based on MediaElement.js
Ben if you want to play be glad to give you Admin access ... just let me know. I'll be out now until later so that will allow my alleged brain to cool down.
Cheers,
John Vickers, Church of Our Lord, Victoria, BC, CA
Customized Sermon Browser vs. 0.45.12 on WordPress 4.1
4:07 am
Moderators
18 June, 2009
Offline
Thanks for looking into it, John. If I get bored, I might try setting up my own 3.6 site to test.
Ben Miller, Pathways Church, Appleton, Wisconsin, USA
Read the new FAQ, last updated 11/21/2013
Announcing version 0.45.12
6:36 pm
Moderators
18 June, 2009
Offline
I've done some testing with WordPress 3.6, and I have a few notes:
1. So far, Sermon Browser 0.45.7 seems to work great with WordPress 3.6 beta3. 
2. MediaElements.js is indeed included in the WordPress core. So if you are currently running the MediaElements.js plugin, then after you update to WordPress 3.6, you should be able to deactivate it. Here is the shortcode setting that worked for me:
(left-square-bracket)audio mp3="%SERMONURL%"(right-square-bracket)
The "mejsaudio" shortcode won't work, it needs to be "audio". I'm assuming that they'll be updating the Jetpack plugin to remove the media player, since the media player is now in the core.
3. If you are running the old Audio Player plugin from Martin Laine (this is the one that was originally recommended), it turns out that it still works in WordPress 3.6, and will override the built-in MediaElements.js player. So you shouldn't need to change anything if you want your player to stay the same, with the default shortcode setting:
(left-square-bracket)audio:%SERMONURL(right-square-bracket)
If you decide to switch to the new player, just deactivate the Audio Player plugin and switch your MP3 shortcode setting to the one above in item 2.
After WordPress 3.6 is released, we should probably change the default MP3 shortcode setting so that it uses the built-in player. Then Sermon Browser will work without any additional plugins required.
Ben Miller, Pathways Church, Appleton, Wisconsin, USA
Read the new FAQ, last updated 11/21/2013
Announcing version 0.45.12
7:59 am
4 February, 2013
Offline
So Wordpress 3.6 has now been released. Has anyone tried it? Any thing to know before upgrading, other than what Ben's written above?
8:38 am
19 February, 2013
Offline
I tried it ...
Installing the latest version…
Warning: copy(/home/dd3ndh7/public_html/churchofourlord.org/wp-cron.php) [function.copy]: failed to open stream: Permission denied in /home/dd3ndh7/public_html/churchofourlord.org/wp-admin/includes/class-wp-filesystem-direct.php on line 200
Could not copy file.: /home/dd3ndh7/public_html/churchofourlord.org/wp-cron.php
Installation Failed
Yet, the plugin "Automatic Upgrader", earlier err yesterday upgraded two of my client sites and they both completed with no hitch.
I've posted my problem to the WordPress support forum here - http://wordpress.org/support/topic/fatal-error-require-functionrequire-new-installation?replies=2 Wonder what they will come up with.
John Vickers, Church of Our Lord, Victoria, BC, CA
Customized Sermon Browser vs. 0.45.12 on WordPress 4.1
5:02 pm
Moderators
18 June, 2009
Offline
I've upgraded my main development site to WordPress 3.6, and so far, it seems to be running Sermon Browser 0.45.10 just fine.
Just as I wrote before, I am able to turn off the MediaElement.js plugin, and MediaElement is still there on the screen, due to the built-in functionality of WordPress 3.6. The correct setting for Sermons, Options, MP3 shortcode is this:
(left-square-bracket)audio mp3="%SERMONURL%"(right-square-bracket)
This setting has been the default setting since Sermon Browser 0.45.8.
A few notes on the shortcode setting:
- 'mejsaudio' won't work. It needs to be 'audio'.
- The 'preload="none"' text that has been recommended in the past is not needed. See my StackExchange answer for details.
I've noticed that WordPress 3.6 appears to allow a plugin to take over the "audio" shortcode. So if you activate the MediaElement.js plugin or the old Audio Player plugin, which each use the "audio" shortcode, you will be using that plugin, not the WordPress core player. An exception of this appears to be JetPack; I believe that JetPack turns off its own built-in media player as soon as you update to WordPress 3.6.
One thing I've noticed about the new player: With the MediaElement.js plugin, the width of the player was set (by default) to 400px. In the new WordPress 3.6 player, the width is set to 100% (meaning that the player fills the entire width of the column it is in). If you want to override this so that the player has the same look as before, one way to do it is to add this to your Sermon Browser style template (Sermons, Templates):
Ben Miller, Pathways Church, Appleton, Wisconsin, USA
Read the new FAQ, last updated 11/21/2013
Announcing version 0.45.12
3:29 pm
22 February, 2012
Offline
Just wanted to say thank you for this, this has been annoying me all day!
Can anyone tell me why I'm getting one skin load first, and then the second skin load? Is there a way I can change the skin? (have looked and cant find it anywhere! (skin for the MP3 player)
thanks in advance!
(apologies If the answer is already on teh forum and I've missed it, if it is please point.shove me in the right direction!)
3:58 pm
Moderators
18 June, 2009
Offline
henry.matter,
The first "skin" that you are seeing is the built-in player for whatever browser you are using. If you change browsers, you'll see that this initial view of the player is different in every browser.
As the page loads, the built-in WordPress 3.6 player (based on MediaElement.js) takes over, and that is the final look that you get on your site. This should look identical no matter which browser you are using.
It is possible to skin this player; however, it looks like WordPress didn't build-in any alternative skins into the WordPress 3.6 core. To skin it, you need to change the CSS rules for the player. I don't know all the details on how to do this. If you are a developer, you could start at the MediaElement website for documentation. A WordPress plugin that would skin the 3.6 player would be a great idea, but I don't think anyone has written one yet.
Ben Miller, Pathways Church, Appleton, Wisconsin, USA
Read the new FAQ, last updated 11/21/2013
Announcing version 0.45.12
4:14 pm
22 February, 2012
Offline
Ah now aren't you a clever one, thanks Ben!
I'll have a look at the MediaElement.js site and look in to the skinning, its just a shame that MediaElement.js doesnt kick in quicker, it just looks a little messy when it effectively changes (although the page loads a lot quicker in firefox compared to chrome so you only see it the first time the page loads) i don't suppose you or anyone knows of a way to force MediaElement.js to load first do you? <- long shot I expect!
Thanks for your speedy reply anyway, much appreciated! I'll have an experiment with the CSS (having just looked here it seems the CSS is rather involved, but could be worth it!)
Cheers
H
1 Guest(s)
