Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Moving to JW 7

Been using JW 6 with the cloud based player for a while and it's been great but we are really confused on how to move to JW 7. Tried just replacing the .js file in the head of my pages with a new player for JW7 but then nothing works. Do I need to replace the .js file and redo the code when updating to JW7?

Here is a live streaming page.
http://www.lakevillemn.gov/index.php?option=com_content&view=article&id=1080&Itemid=1563

Also have looked here
http://support.jwplayer.com/customer/portal/articles/2037989-migration-from-jw6-to-jw7
but it covers things that are different, it really doesn't explain how to actually move to JW 7.

Very frustrating.

Tim

11 Community Answers

Up Down

Todd

JW Player Support Agent  
0 rated :

When changing from JW6 to JW7, the only two things that need to change on your page are the jwplayer.js and potentially the license key. If you are using a JW7 cloud-hosted player URL from the account dashboard, then there is no need to define your jwplayer.key.

From the page URL you provided, it looks like all you need to do is remove the <script> tag that points to http://jwpsrv.com/library/

Up Down

tklausler

User  
0 rated :

When we replace the jwplayer.js with the new .js it does not work.

Tim

Up Down

Todd

JW Player Support Agent  
0 rated :

Did you also use the new license key? Or were you using a cloud-hosted player URL? Can you send a link to the test page?

Up Down

tklausler

User  
0 rated :

We were using cloud-hosted player for JW6 and want to use it again for JW7. I replaced the old script in the head of the page with the new player library URL.

http://www.lakevillemn.gov/index.php?option=com_content&view=article&id=1080&Itemid=1563

Up Down

Todd

JW Player Support Agent  
0 rated :

I see an error that jwplayer is not defined in the console, but I see you are linking to the player library correctly.

When I copy your entire page source and load it from my test server, the player loads fine, so perhaps the browser is trying to call jwplayer().setup() before your cloud-hosted player is done loading? Can you try moving our player library to the top of the <head> to see if that makes a difference?

Up Down

Todd

JW Player Support Agent  
0 rated :

Looks like this might also be some sort of conflict with mootools.js

Up Down

tklausler

User  
0 rated :

Moved the player library code towards the top of the script and it now works. Never would have thought to do that. Thanks for your help.

Tim

Up Down

Todd

JW Player Support Agent  
0 rated :

I’m glad to hear that worked. There’s a known issue with mootools and WebPack (which the player makes use of). Mootools is doing some not-good things to some native browser functionality which causes issues (not just for us, search in Google for “mootools and webpack” for a list of complaints).

Up Down

webmaster

User  
0 rated :

I'm also running up against the issue with JW Player 7.2.3 not working with MooTools running on the same page.

It throws the following error:

jwplayer.js:7 Uncaught TypeError: Cannot read property 'css' of undefined

> function j(a,b){var c=b.css,d=b.media;b.sourceMap;

I can confirm loading mootools.js AFTER jwplayer.js does resolve the player issue.

Up Down

Will

User  
0 rated :

I was really hoping for a better solution here. Not possible without completely rebuilding architecture to load jwplayer players before mootools. Has nobody properly solved this bizarre issue?

Up Down

Will

User  
0 rated :

Apparently Mootools corrected this conflict in v 1.6. Upgrading the site from MT 1.4 to 1.6 was my easiest route, not much code I had to migrate.

This question has received the maximum number of answers.