Copyright © 2011 Kaltura Inc.
All Rights Reserved. Designated trademarks and brands are the property of their respective owners.
Use of this web site constitutes acceptance of the Terms of Use and Privacy Policy.
EduVideo.org
| Project: | Advanced Video Editor (Timeline Based Editing) |
| Version: | partnerServices2 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
| Total votes: | 0 |
In verision 1.0.15.26975 (1000865) of KAE, adding text overlays appears to break mixes. If I create a simple mix with just one or two images, and then add a text overlay, publish and save, when the player loads I get the spinning 'loading' graphic, and then nothing happens.
Comments
#1
Hi Chris,
what version of the KDP are you using ?
Can you post an example ?
#2
KDP is version 1.1.11.21127.
The site I'm testing is not public, but I've attached a screenshot of the waiting screen, and the editor with the title in it.
First
Second
#3
Did you try on the latest version of the player ? (you can use a player generated by the application studio).
#4
OK, I am now using a player I generated (1001434). I created a player with a Remix button, but that appears to be broken. Is there something else I need to do to get a custom player to work with the Drupal module? It plays fine, as expected, but the Remix button just doesn't do anything.
I should also note that to get the new player to work, and edit out a bit of embed code. The embed code generated by the current version of the Drupal module doesn't match what's in the documentation on this site.
In kaltura.theming.inc:
became:
I removed ".'_'. $uicid" which made the player work, and matches the embed code style here: http://www.kaltura.org/kdp-basic-usage-embedding-html-pages-and-playback
..but now the Remix button doesn't work.
#5
Just tested a mix with a text overlay and it does indeed work ok with the new player. So using a new player fixes my problem. If I can get the Remix button working again, I'll be set.
#6
I can also confirm that as of KDP 2.1.2.29057 that remixes with text overlays work.
#7
Ok. Could you advise as to how I get my remix button to launch the editor? Using KDP v1.x, it worked ok. Was there a change in the naming of the javascript function that is triggered by this button?
#8
It looks like the Kaltura team are putting together some documentation for you to address this issue:
http://www.kaltura.org/implementing-javascript-handler-open-editor-or-kc...
But in the meantime, I tried to work out how to get it working - but unfortunately didn't make much progress.
Looking at the source code...
/**
* Click of button / linkButton / label
*/
static public const K_CLICK:String = "kClick";
/**
...it looks like kClick is probably the Javascript function that triggers the button - but I just can't get it to work.
I'll keep trying, and let you know if I work it out...
#9
OK... it's official... I've tried everything... I have no idea how to make it work... Sorry!
#10
After much stuffing around I finally worked it out...
The answer was found by using the TestMe console and looking at the XML file for the UIConf.
I came across this code in the file:
So it seems by default the JS call is gotoEditorWindow! Finally...!
Attached is an example of it actually working. Enjoy!
Best Regards, Chris!
#11
That worked perfectly. Thanks for your help! I've now got KAE v1.0.15.29762 and KDP v2.1.2.29057 working together in the Drupal module. I will document the changes I made and create a patch file for the module, as soon as I tidy up my changes.
In short, though, all I did was edit the 'kalturaInitModalBox' function to replace the 'url' argument with the single argument that's passed to gotoEditorWindow, which is the ID of the entry, and then construct the url for the modal box based on that entry ID.
So in kaltura.js I have:
kalturaInitModalBox(entryID);
}
function kalturaInitModalBoxV2 (entryID)
{
.....
var userid = **grab this from Drupal**
var url = "/kaltura/simple_editor/"+entryID+"/entry/user_id@"+userid
....
}
It's not real clean yet, but it works..
#12
That worked perfectly. Thanks for your help! I've now got KAE v1.0.15.29762 and KDP v2.1.2.29057 working together in the Drupal module. I will document the changes I made and create a patch file for the module, as soon as I tidy up my changes.
In short, though, all I did was edit the 'kalturaInitModalBox' function to replace the 'url' argument with the single argument that's passed to gotoEditorWindow, which is the ID of the entry, and then construct the url for the modal box based on that entry ID.
So in kaltura.js I have:
kalturaInitModalBox(entryID);
}
function kalturaInitModalBox (entryID)
{
.....
var userid = **grab this from Drupal**
var url = "/kaltura/simple_editor/"+entryID+"/entry/user_id@"+userid
....
}
It's not real clean yet, but it works..
#13
Automatically closed -- issue fixed for two weeks with no activity.