Jump to:
| Project: | Kaltura |
| Version: | 6.x-1.4 |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
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
#1
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?
#2
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
#3
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
#4
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