Migrate from the LVP Player
What changes when moving from the legacy LVP Player to the Uplynk Player.
Migration from the LVP Player
To migrate from the LVP Player to the Uplynk Player, change the src reference from the LVP Player URL (https://ovp-static.uplynk.net/limelightjs-player.js) to the Uplynk Player URL (https://ovp-static.uplynk.net/player.min.js). All LVP function names and naming conventions are supported by the Uplynk Player.
Before:
<!doctype html>
<html>
<head>
<meta charset="utf-8">
</head>
<body>
<div id="lvp_player_211280"></div>
<script charset="UTF-8" src="https://ovp-static.uplynk.net/limelightjs-player.js"></script>
<script>
LimelightPlayerUtil.embed({
"height": "321",
"width": "540",
"autoTitle": "item", // Sets title to asset name
"mediaId": "mingle",
"orgId": "0933a56ee6f5434c8ffe5e00bee4e178",
"enableCookies": false,
"playerId": "lvp_player_211280",
"playerForm": "LVPPlayer"
});
</script>
</body>
</html>After:
<!doctype html>
<html>
<head>
<meta charset="utf-8">
</head>
<body>
<div id="lvp_player_211280"></div>
<script charset="UTF-8" src="https://ovp-static.uplynk.net/player.min.js"></script>
<script>
LimelightPlayerUtil.embed({
"height": "321",
"width": "540",
"autoTitle": "item", // Sets title to asset name
"mediaId": "mingle",
"orgId": "0933a56ee6f5434c8ffe5e00bee4e178",
"enableCookies": false,
"playerId": "lvp_player_211280",
"playerForm": "LVPPlayer"
});
</script>
</body>
</html>The only change is on Line 8, the script charset line.
When time permits, adapt the function calls and naming conventions to the new Uplynk Player terminology.
Updated about 1 hour ago
Did this page help you?