The Kaltura CCK field cannot be used without the node_kaltura_entry module, but this dependency is not indicated in field_kaltura.info.

Furthermore, the actual code for displaying the field depends on the function kaltura_get_node_for_mix, which means the node_kaltura_mix module is also required.

The function kaltura_get_node_for_mix should be abstracted so the field_kaltura module can work without the node_kaltura_mix module being enabled.

field_kaltura appears to be a glorified node reference field... which is totally cool, and I wish CCK node reference field could have the kind of power field_kaltura has in browsing nodes, creating new ones as needed, etc.

Comments

Zohar.Babin’s picture

Zohar.Babin commented

Hi,

this is kind of duplicate, but not entirely...

You're right - dependencies were not indicated properly in .info file - will be fixed.

About the kaltura_get_node_for_mix() - duplicates #363720: Kaltura CCK field not working which was fixed and I hope I can get the next release (which includes this fix) up faster...

davidseth’s picture

davidseth commented

This is from February and still no new release. The bug with the remix function is a BAD one that you have fixed. Please release a new version of this module...

Thanks,

David

xurizaemon’s picture

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

This issue was recently resolved with the 2.x release of this module.

Also just now resolved in the DRUPAL-5 and DRUPAL-6--1 branches with the same fixes - you can grab the upcoming 6.x-1.x-dev if you prefer.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.