Needs work
Project:
Kaltura
Version:
6.x-1.x-dev
Component:
Documentation
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
19 Jul 2010 at 16:56 UTC
Updated:
5 Nov 2010 at 10:21 UTC
Jump to comment: Most recent file
Comments
Comment #1
BeaPower commentedSame issue here! Are we supposed to download KalturaCE with this drupal module or not?
Comment #2
xurizaemonI've just made the 2.x-dev release visible on the main project page.
This is based off Kaltura's "Andromeda" SVN branch, which should be used with KalturaCE 2.0.
Please report back your results once you've upgraded to kaltura-2.x-dev?
Comment #3
gerold commentedI tried KalturaCE 2.0 (on CentOS 5.4 x64) with Drupal-Kaltura module 1.5 and 2.x-dev, but both are not working. I got blank screen (movie not loaded) when trying to add kaltura node.
Anyone got KalturaCE 2.0 and Drupal-Kaltura module 2.x-dev working?
Comment #4
arkiii commentedsame problem here
I can get to the Kaltura KMC, upload and download videos. Everything on the server side works perfectly...
Prior to this, i was using Kaltura's shared service but quickly ran out of space so decided to setup my own linux server (Fedora 13) with XAMMP for linux .
Since i already had the Drupal module configured and working, all i did was update the module to 6.x1.5. I then changed the server integration settings to reflect that i was now serving videos, entered the correct email and password in the partner id area. I have 4 green checks indicating that everything is ok. So I am assuming that the Drupal module sees my Kaltura server.
When I try to create any content, the page just hangs and never does anything. I have a feeling it has to do with some old pointers or some old database settings that are still pointing to Kaltura's server instead of mine but i dont know where to look. There are still some old nodes that i created when i first installed Kaltura to work with their shard solution. I can view them but obviously, they do not work any more. They only disly a thumbnail of the video?
any ideas?
Can i clear the SQL database of any records of videos since they are no longer available?
Comment #5
xurizaemon@arkiii - I don't know about your specific situation, and I'd request you open it as a separate support issue please. Once you've done that I can give you a few pointers on where to start. I'm not going to attempt to address it here because it's only going to confuse this issue.
Comment #6
xurizaemon@all - I want to flag with you that I've seen this issue and will follow it up shortly.
An imminent work deadline means that I will not be able to look at this issue in depth for about a week. I've drawn the attention of the Kaltura team to this issue (and a few others which have arisen as a result of the KalturaCE 2.0 release, which is looking really exciting).
In the meantime I'd suggest you engage proactively in debugging this issue. Don't be shy about jumping into IRC on #kaltura as well. Any debug input is welcome, and you can start posting some debug here if you get stuck - someone else might be able to tell you how to dig a little deeper.
You are welcome to file patches against 2.x-dev (DRUPAL-6--2 in CVS) for this module, or jump on it in Github (use http://github.com/GiantRobot/drupal-kaltura there) if that works for you.
Thanks all. I'm marking this postponed for the reasons stated here, but it shouldn't be for long :)
Comment #7
xurizaemonIf you are using KalturaCE 1.5, please test with the 1.5 Drupal module - not 2.x-dev.
If commenting, please be specific about which KalturaCE and Drupal Kaltura module versions they are using by commencing with "KalturaCE x.x / Drupal Kaltura x.x-x". If you just posted and forgot to do this, please edit your comment to provide this information.
People having trouble with 1.5 - if you have a suitable test environment, I'll ask you to test with a copy of the 1.4 code (which is no longer available on Drupal.org; I'll need to discuss with you if you want to do this). We MAY need to move 1.5 issues to a separate issue from 2.0 issues.
Thanks!
Comment #8
gerold commentedI've tested on fresh installs of KCE 1.5 against Kaltura Drupal module 1.5 on 32bit and 64bit machines (centos 5.4, xampp) and KCE 1.0 as well -- all got the a blank screen/movie not loaded issue.
However, I got it working on KCE 1.0 (xampp, 32bit centos 5.4) and Kaltura Drupal module 1.4. Looks like an issue with 1.5 release. I will do another test on KCE 1.5 and module 1.4 - will post later with result.
Comment #9
gerold commentedFyi -- I got my KCE 1.5 working again with Drupal module 1.4. Kaltura Drupal module 1.5 have the "Movie not loaded" or blank screen problem when adding Kaltura media.
Comment #10
xurizaemonOK, thanks to @davereid I think I know what happened here.
It seems that code for the KalturaCE 2.x series was checked into Drupal CVS at DRUPAL-6--1 after the release of kaltura-6.x-1.4.
This means that the security fix for SA-CONTRIB-2010-078 - Kaltura - Information disclosure which was applied for the kaltura-6.x-1.5 module release was actually against code for integrating with KalturaCE 2.x. (Ref #392736: Remove hidden stats iframes also for more info on this SA.)
This was the point where I stepped in as module maintainer on behalf of the Drupal community, so I wasn't familiar with the code history enough to spot the compatability issues before I released 6.x-1.5. I should have reviewed the most recent checkin more thoroughly, but at the time was focussed on getting a release out the door ASAP so that there would still be a Kaltura release available for people affected by the impending SA.
I will (in a week or so, when I have availability) take the following steps to resolve the situation for KalturaCE 1.5 users -
My plan here is based on understanding from discussions with @davereid; I don't have time today to action it. However, if you're skilled, you can help it happen (and I'll welcome anyone engaging so that this can happen faster).
If you are familiar with CVS and Drupal module maintenance and can see any error in the above process (ie, should I just do a cvs revert?) then please speak up. We just want to reverse the inclusion of the Andromeda codebase on July 7th 2010.
If you want to engage and attach patches for steps 1 and 2 (separately, please) then please do so. It will help speed things up and get you all back on the road.
While the old code is still available in CVS, I would ask that people DO NOT upload copies of kaltura-6.x-1.4 to Drupal.org unless they have applied the fix for SA-2010-078 as well. I know it seems a straightforward workaround, but it's in contravention of d.o policies to upload the code in 1.4 (see the SA for more).
EDIT: Fixed issue reference.
Comment #11
xurizaemonComment #12
xurizaemon@gerold, @arkiii - are you in a position to confirm if this tarball works as expected for you?
I would like to push this as DRUPAL-6--1-6 to bring the 1.x series back into line for users of older Kaltura installations. But as it's a major change to the current DRUPAL-6--1 CVS, I don't want to pollute the CVS with an untested version.
This tarball reverts to kaltura-6.x-1.4 which I understand you're both using at present, then applies fixes from #358937: node_kaltura table schema doesn't support nid's > 65535 and #392736: Remove hidden stats iframes.
If you can confirm this is good, I'll get it out as a 6.x-1.x-dev ASAP.
Sorry for the extended wait on this.
Comment #13
gerold commented@grobot - Thanks for the updates. I'll post my test result within this week. Right now I have Kaltura Drupal module 1.4 working fine on KCE 1.5 and KCE 2.0.
Comment #14
arkiii commented@grobot
Thanks for the update. I will try it asap and let you know if it fixes my problem...
Comment #15
arkiii commentedNo joy yet...
here is what i did.
un-installed existing Kaltura 6.x-1.4
deleted the kaltura folder from the modules folder
ran update.php
copied Kaltura 6.x-1.4 patch module
enabled module
when I try to configure th module, it asks if i have a partner ID. I use ID#1 and my email and password that i use to access my KalturaCE server.
I get the following error:
Couldn't import partner details.
Array ( [0] => Array ( [code] => ADMIN_KUSER_NOT_FOUND [desc] => The data you entered is invalid ) ) :
ideas?
Comment #16
xurizaemon@arkii
Please verify that you have changed the file kaltura_client/kaltura_settings.php in your copy of 1.6-pre to match your KalturaCE site URL.
You will get the error stated if you leave that file as per default (it will try, and fail, an auth against www.kaltura.com).
I did mention this previously in the issue #866358: Issues with KalturaCE integration after Kaltura server relocation you reported, but it'd be easy to miss this when trying out a new version of the module. This really needs to be documented better, or a configurable setting during Kaltura partner setup.
Unfortunately that is a topic for a separate issue (the partner registration form, and settings forms in general for 1.x, need a bit of loving.)
Comment #17
arkiii commented@grobot
You were correct!
Changing the kaltura_settings.php solved the problem.
your 1.6 Patch worked for me....
Thank you for the help.
I Now have KalturaCE working with both Moodle and Drupal...
Comment #18
xurizaemonOK, 6.x-1.x-dev will come out shortly for people to try out what's posted as 1.6-pre above.
1.x-dev and upcoming 1.6 will be strictly for people using KalturaCE 1.x or KalturaEE 1.x series.
If you're using SaaS or 2.x, you'll want the 2.x series module to match now.
Release notes on 6.x-1.x-dev give a bit more detail (you may also want to check my comments on #887362: 1.5 and 2.x-dev are the same source code).
Comment #19
dslamngu commentedBeen having this same set of issues too. I have a new installation but the project requires that I use exactly one server. I've been told on the Kaltura boards that KalturaCE v2.0 doesn't support such a configuration. I can only install Drupal alongside KalturaCE v1.5.
http://www.kaltura.org/kalturace-v20-and-drupal-same-server-mykalturacon...
Installing the newest module you posted fixes an initial issue with the Media Node coming up as a black box. Which was good times :-) I can upload and import media using the module in Drupal. However now I get black boxes when I try to play any videos. My theory is that the Drupal module generates incorrect URLs.
For an example video I uploaded, here's a comparison of URLs between the embed code generated by the KMC and the Javascript code from the Drupal module:
KMC yields
data="[...]/kaltura/index.php/kwidget/wid/_1/uiconf_id/48410/entry_id/vnurhgpw0k"
And I can watch the video just fine.
Drupal module yields
var kaltura_swf = new SWFObject("[...]/kaltura/kwidget/wid/_1_605/entry_id/vnurhgpw0k/uiconf_id/605", "kaltura_player_vnurhgpw0k", "410", "364", "9", "#000000");
And I get a black box.
These are very different URLs for the same video. Where in the Drupal module is the URL generated, and how can we alter this to work?
Comment #20
xurizaemon@dlamngu, please tell which exact version of this module you're using?
Comment #21
dslamngu commentedSure! I had kaltura-6.x-1.5.tar.gz, then I installed code from the module you posted above, kaltura-858546-drupal-6--1-6-pre.tgz
Comment #22
dslamngu commentedGrobot, I can absolutely understand if you haven't been able to find time for this. In the meantime, could you point me to the place in the source these URLs are generated so I can fix it for myself until you find a free second?
Thanks!
Comment #23
xurizaemonCheck includes/kaltura.themeing.inc where you will see the swfObject code (search for 'new swfObject').
The swfURL is coming from KalturaHelpers::getSwfUrlForWidget() by way of function kaltura_get_embed_options() in includes/kaltura.themeing.inc
It looks like the problem with your URL is that the widget ID is getting included in the partner ID. That's odd.
Try accessing these two URLs directly and see if the latter works?
If that does work, you want to know why KalturaHelpers::getKalturaServerURL() is adding that extra info. Check the entry 'kaltura_server_url' in your Drupal variables table, and remove it if that's there please. (replace _1_605 with _1)
Hope that helps ... let me know how you go. I suspect the other differences in the URLs are not significant.
Comment #24
dslamngu commentedThanks for the tip! My code includes this:
Deleting the first .'_'. $uicid fixes my problem. For now I'll make my change locally, same with the other branches of this IF statement. I'm going to guess you want to test the fix against whatever installations you can access before it goes into the next version, so good luck!
Thanks grobot!
Comment #25
dslamngu commentedOne thing after another. Now my thumbnails are broken, especially on my Views. I'll dive in, but if any of you on this board have tips please post.
Comment #26
xurizaemon@dslamngu - open a separate issue for the thumbnails, please.
Feel free to post a patch which fixes this one for you :)
Comment #27
MichaelP commented@dslamngu: Did you get anywhere with the thumbnail issue? URL I'm getting for (broken) thumbnails is: http://www.mysite.com/width/100/height/100
Tks.