Using Kaltura CE v2.0.2
Install went perfect - I can upload and import from KMC.
Steps I took:
Fresh install of Drupal 6.19
Installed a few basic modules: CCK, Views, Admin Menu, Skinr
Installed Theme: Acquia Marina
Enable above modules.
Installed Kaltura Module 6.x-1.5
Enabled Kaltura Module
Went to /admin/settings/kaltura/
Clicked link "Server Integration settings"
Chose Kaltura CE
Kaltura CE URL:
Kaltura CE Admin Email:
Kaltura CE Password:
Partner Info
Partner ID: 100
Email: email...
Password: password...
"Complete Installation"

Then this error:

Fatal error: Uncaught exception 'Exception' with message 'Invalid object type' in /var/web/sites/default/modules/kaltura/kaltura_client/KalturaClientBase.php:339 Stack trace:
 #0 /var/web/sites/default/modules/kaltura/kaltura_client/KalturaClient.php(4597): KalturaClientBase->validateObjectType(Array, 'KalturaPartner')
 #1 /var/web/sites/default/modules/kaltura/includes/kaltura.admin.inc(216): KalturaPartnerService->getSecrets('100', 'myemail@email.com', 'password')
 #2 /var/web/sites/default/modules/kaltura/includes/kaltura.admin.inc(367): kaltura_get_partner_details('100', 'myemail@email.com', 'password'')
 #3 [internal function]: kaltura_settings_form(Array)
 #4 /var/web/includes/form.inc(376): call_user_func_array('kaltura_setting...', Array)
 #5 [internal function]: drupal_retrieve_form('kaltura_setting...', Array)
 #6 /var/web/includes/form.inc(102): call_user_func_array('drupal_retrieve...', Array)
 #7 [internal function]: drupal_get_form('kaltura_setting...')
 #8 /var/web/includes/menu.inc(348): call_user_func_array('drupal_get_form' in /var/web/sites/default/modules/kaltura/kaltura_client/KalturaClientBase.php on line 339

More info here - http://www.kaltura.org/kaltura-ce-202-and-drupal-kaltura-module-6x-15

Comments

Zohar.Babin’s picture

Zohar.Babin commented

Please try the 2.0 version - http://drupal.org/node/847202
It was tested with the new CE.

1.5 is basically 2.0 ... we should really remove the 2.0-dev release and name 1.5 - '2.0'
reason for the major is because the module is completely new and works with a newer version of the Kaltura API.

VanD’s picture

VanD commented

Am I using the most up to date version of the Kaltura Drupal module?

Zohar.Babin’s picture

Zohar.Babin commented

if you're using 1.5 - then yes.
can you provide a public link that can be tested? or attach apach log file with relevant requests/response?

xurizaemon’s picture

xurizaemon
he/him
Location Ōtepoti, Aotearoa 🏝
commented

Actually Zohar, I suggest we use Drupal Kaltura 2.x to match 2.x series Kaltura, and allow the 1.x series to continue for existing users of Kaltura 1.x (CE or EE). There are probably plenty of people in that situation, and these people should be able to receive updates to this module.

Unless we are able to support API for both KalturaCE 1.x and 2.x with the same version of the Drupal module?

See my comment on [#858546 - Compatability issues between KalturaCE v1.5 and Drupal Kaltura 6.x-1.5] for my intended plan of attack. Would appreciate your feedback on that.

Zohar.Babin’s picture

Zohar.Babin commented
Category: bug » task
Priority: Normal » Major

It's a good intent, however, the Kaltura CE 1.x branch will not continue to be developed, and as such people are urged to update to CE v2 which is more secure, provides better performance, is stabler and has a lot more functionality.

module's 1.4 branch is what you need for Kaltura CE 1.x branch. There's no need to continue it's development as Kaltura CE 1.x branch was replaced by CE 2.x.

Current state is that the module's 1.5 == 2.0dev (compare the modules and you'll see it's the same).

What needs to happen is -
module 1.5 will be made 2.0.
1.4 will be marked latest version for Kaltura 1.x branch, and unsupported.
trunk should reflect 2.0 and on-going development will be done on 2.0.

MxRhd’s picture

MxRhd commented

subscribing, get the same errors...

MxRhd’s picture

MxRhd commented

http://drupal.org/node/527246

here it says to edit the kaltura-settings, but in the Kaltura-settings it says

/*
* @file
* This file defines some data needed by the module
*
* changing data in this file might cause the module to stop working
* or working not as expected.
*
* It is strongly advised not to change the settings in this file
*
*/

Is the guide out of date?

xurizaemon’s picture

xurizaemon
he/him
Location Ōtepoti, Aotearoa 🏝
commented
Title: Fatal error: Uncaught exception 'Exception' with message 'Invalid object type' in .../sites/default/modules/kaltura/kaltura » KalturaCE installation fatal error

You're right VanD, that comment shouldn't be in kaltura_settings.php, because if you're running KalturaCE on any site other than kaltura.com, you do need to update (at least) the www.kaltura.com URL hardcoded in that file.

1. We should remove that comment (at least for the server URL setting).
2. Ideally the value should be prompted for, and can default to kaltura.com for people using SaaS. Setup forms can document themselves.
3. If that doesn't happen straight away, we need to make sure the setup docs explain how to install the module for CE (but that's not as good a fix as making it configurable on install, no "fix it in the docs" can ever be...).

Unfortuantely when I looked at the setup form ... there's a bit of cleanup to be done there (due for a bit of a FAPI rewrite, uses $_REQUEST[''] a lot etc). There's actually a hidden value already in that form for server_url, which we should be prompting for!

---

As you're on KalturaCE 2.x, I'd think you're probably better off trying out the 6.x-2.x-dev release of this module anyway. Move to 6.x-2.0 when it comes out shortly if you like.

xurizaemon’s picture

xurizaemon
he/him
Location Ōtepoti, Aotearoa 🏝
commented
Title: KalturaCE installation fatal error » KalturaCE installation fatal error "undefined method Exception::Message()" - allow custom CE server URL in setup
Version: 6.x-1.5 » 6.x-2.x-dev
MxRhd’s picture

MxRhd commented
Version: 6.x-2.x-dev » 6.x-1.5

Oh, so i should enter my values in the kaltura-settings file after all? (i AM using my own server)

MxRhd’s picture

MxRhd commented

Oh yeah apperently i should have done that. Thank you! No more errors for me (except the Drupal Error message on line 138, but i commented that away)

xurizaemon’s picture

xurizaemon
he/him
Location Ōtepoti, Aotearoa 🏝
commented

Yes, you should rip in and change those settings :)

The proper fix for this is to lose the hardcoding except as a default URL and have the form prompt for your Kaltura server URL, which is why I'm moving this to 2.x. I'm sure it'll backport to 1.x fine too if need be, but most new development will be happening on the 2.x series.

xurizaemon’s picture

xurizaemon
he/him
Location Ōtepoti, Aotearoa 🏝
commented
Version: 6.x-1.5 » 6.x-2.x-dev

er, ... which is why i'm moving this to 2.x

for both 2.x and 1.x the initial fix is "ignore or remove the line saying 'It is strongly advised not to change the settings in this file'

VanD’s picture

VanD commented

Thanks for the info.

I have updated to Kaltura Module 6.x-2.x-dev
I commented out line 138 in modules/kaltura/includes/kaltura.admin.inc
I hardcoded my Kaltura 2.x CE URL on line 15: define('KalturaSettings_SERVER_URL', "http://serverURL/ or IP address");

Then all went well. Cheers.

Zohar.Babin’s picture

Zohar.Babin commented

We should really fix the module in that we'll remove the ce related special functions and use a single unified installation flow.
That installation flow should include a field to define the server url, and that will have this issue fixed.

xurizaemon’s picture

xurizaemon
he/him
Location Ōtepoti, Aotearoa 🏝
commented
Assigned: Unassigned » xurizaemon

Currently working on this - there's a branch in Github for it @ https://github.com/GiantRobot/drupal-kaltura/tree/6.x-2.x-891128

Testing welcome :)

xurizaemon’s picture

xurizaemon
he/him
Location Ōtepoti, Aotearoa 🏝
commented
Status: Active » Postponed

Please see #1026426: Installation issues: FAPI rewrite of installer to test a rewritten installer which uses the same functions for both CE and SaaS installations.

There are some minor differences in flow still, which are:

1. CE currently skips the option for remote reg. In testing I found that CE did not appear to support remote registrations. (Feedback welcome - I was using the supplied AMI.) This is disabled but can be easily re-enabled if you can give me a CE server which supports remote reg to test against.

2. If SaaS is selected, we need T&C agreement still, but not for CE.

3. If SaaS is selected, we conceal the URL field using JS to simplify the flow.

I've opened a separate issue to implement Zohar's request in #15 above. This issue covers several topics, all of which should be resolved with the new installer, so I'm marking this issue postponed and request your feedback on the new issue: #1026426: Installation issues: FAPI rewrite of installer.

This issue will be marked fixed when that issue is resolved.

xurizaemon’s picture

xurizaemon
he/him
Location Ōtepoti, Aotearoa 🏝
commented
Status: Postponed » Closed (duplicate)

Fixed by work in #936752: Syntax error, or undefined var on line 138 kaltura_admin.inc and #1026426: Installation issues: FAPI rewrite of installer.

xurizaemon’s picture

xurizaemon
he/him
Location Ōtepoti, Aotearoa 🏝
commented
Assigned: xurizaemon » Unassigned