We just installed Kaltura module into a Drupal 6.10 multisite configuration. The way that works is that the sister sites use the code and modules from the main site; each sister site has its own file system and separate database. However, you also have to activate specific modules used in each of the sister sites.

So we activated the Kaltura module on the main site and followed the instructions re server and partner activation, etc. We also set permissions.

We then did the same thing on one of the sister sites. We uploaded video to the sister site and it did not appear. We found it a few minutes later on the main site. We then had someone else upload video on the sister site from another location; that upload did not appear on the sister site but appeared in a few minutes on the main site. Both uploads turned up fine on our Kaltura account.

More troublesome was that on the main site the video upload done by someone else was created on the main site with a random user's username, perhaps because the person who had created the video node on the sister site does not have an account on the main site. Hmmm. Not good.

So is this a path issue on our server (We are in a Media Temple Dedicated Virtual server). Is there a mysql issue? And is there a security issue given that a node was created under a random username?

Thoughts? Suggestions? Has anyone run into this? Any thoughts from Kaltura folks?

One more thing: When you edit the video node that was created on the main site, this error appears at the top:

warning: preg_match() expects parameter 2 to be string, array given in /var/www/vhosts/MYSITE'S URL/httpdocs/includes/bootstrap.inc on line 771.

Would love some help. This seems a great module but perhaps it is not equipped to handle multisite configuration.

geoff gevalt

Comments

ggevalt’s picture

ggevalt commented
Title: Problem with MultiSite configuration -- video appearing on wrong site » Problem with MultiSite configuration -- video appearing on wrong site -- update

Wish we could edit bug reports....

Have found out that the reason we were having posting issues centered on the server notification address set on our account at Kaltura.com. We've experimented and we can get the uploads to appear in the proper place when we change the server that we want to be notified. This is not a solution to how to have the module serve a multisite configuration, but it does explain the odd behavior.

Is there a solution for multisites?

And what does the warning mean?

Zohar.Babin’s picture

Zohar.Babin commented

Well,
regarding the warning - I'm not really sure what is it source. never had that before.

Regarding the multisite support -
The module is build in a way the nodes are created through kaltura notifications.
Since each partner has only one notification URL, you can use 1 partner with 1 drupal site only.

If the multisite scenario means that each site has a different database and should not share content - why wouldn't you register one partner per sister site ?

If you don't want to create partner for each sister site, and the main site has access to sister's database, you can use the partner_data field (which is passed to the CW and then returned in the notification) to specify which instance (main or sister) made the upload, and then - from the main site notification_handler - create the node on the relevant DB.

My feeling is that if each sister in the multisite has a different DB, then each sister should have its own partnerId (meaning you should register in order to activate the module in each sister rather than import the same partner in all sisters).

Gonen

ggevalt’s picture

ggevalt commented

Gonen,

Thanks so much for the response. I will do that. And I kind of figured that was the solution.

I will do that.

Regarding the warning, I will continue to look into that and see what I can find out.

Thanks again for your response.

cheers

geoff

ggevalt’s picture

ggevalt commented
Status: Active » Closed (fixed)

Never got any info on why we were getting the warning. Does not seem to have reoccurred and we have resolved the other problem -- you need a separate account for each site in a multi-site configuration.

Issue closed

paogarciac’s picture

paogarciac commented
Issue tags: +kaltura

Hi,

I know it's been a while since this issue happened, and Zobar.Babin's answer was very clear... But I was wondering why not implement the notification URL under Kaltura's Integration Settings to add as many URL notification fields as needed?

ggevalt’s picture

ggevalt commented

Hi paogarciac,

As someone who uses these forums and issue threads regularly, I feel a duty to respond when someone comes in much later to comment. Frankly, one of the problems we are having with Drupal these days is that threads such as these are still searchable -- the problem was a severe one, but I am sure it is long out of date. More and more when I search I find discussions about issues on module versions for Drupal 4.7 or Drupal 5 that really are not much use.

CONTEXT on this one: At the time, we were an earlier adopter of Kaltura. Then Kaltura began having some problems; this particularly one was a huge issue and brought down all our sites and had to do with some haphazard coding and support by Kaltura. Drupal called them on it. I think they've since cleaned up their act considerably. However, we never resumed use of Kaltura. Partly it was this experience. Partly it was that they went to individual paid plans as they talk about in the response. And partly it was that we found that having users post their videos to a more public place gave them more options -- we just offer them instruction on how to embed from say youtube, vimeo or other services.

To respond more directly to your question, yes, he was clear. But what is lost is that this was a huge change that Kaltura implemented without letting us know. They had a very different arrangement initially and then switched it on us and that is why we were having problems. And yes, we would have had to create separate accounts for each one which, under their new paying model, would have cost us a fortune. We are a small nonprofit. And no, I didn't necessarily believe that we were the only ones having problems.

Hope that helps.
geoff

paogarciac’s picture

paogarciac commented

geoff,

Thank you very much for your explanations. It definitely helps to learn about other user experiences.

Thanks again,
Paola G.