update to 1.7?

[anointed]

any progress on the update to 1.7?

If someone will take the time to update the actual embed portion to the new 1.7 system, then I would like to contribute by cleaning up the WordPress side, removing and replacing depreciated WordPress functions etc.

Then once the plugin is switched over to the new 1.7 system, I have no problem contributing by adding the ability to use the all-in-one plugin to insert videos into the WordPress metabox/custom-fields boxes.

Currently the plugin is setup to only allow the ability to insert a video into the post-content. While this is nice, it severely limits the ability of the theme designer to come up with custom video themes if the video is only inserted into the post content. By saving the output kaltura embed code into a custom field for each 'post', designers can then call that custom field in any area of the theme template quite easily.

While I did this same thing for the current plugin vs. I am sure the logic is going to change considerably with the new vs.

I just would love to get this plugin rolling

[diffalot]

Looking at line 292/304 of all_in_one_video_pack, I think I see where to add in a link to mwEmbed, but I'm not sure how to add in an external url rather than one of the included javascripts.

How do you add in a full URL?

[mdale]

we should remove the dependency of swfObject, and instead use kWidget to embed. In terms of the kaltura url to use.. we should try and use the uiConf urls provided by the KMC .. but that may be difficult if we don't know the uiConf ahead of time when we are doing page build out. Worse case we could just create a uiConf and point it to 1.7 per http://html5video.org/wiki/Kaltura_HTML5_Configuration#Controlling_the_HTML5_library_version_for_.com_uiConf_urls ( for a default, but make it configurable so that folks can point it to their respective uiConf redirection scripts or host mwEmbed locally if they want to )

[zoharbabin]

@mdale - totally agree. we shouldn't use swfobject anymore, just use kwidget.embed or kwidget.thumbembed (can be chosen in settings).

The uiConf shouldn't be an issue with the WP plugin, when installed the user is asked to select the uiConf he wishes to use for the player, and then asked again in the wizard when embedding videos. So you always have the uiConf.

Only thing with this, is that this change to the WP plugin will essentially render the plugin non-usable for Kaltura versions earlier than Eagle (/CE 5).

@anointed - what are the specifics you're having trouble with updating? maybe we can help guide your way while you work on the contribution.

[anointed]

@zoharbabin sorry I missed your reply
If someone could just rip out the old swfobject stuff and replace it with the new system, then I'll take care of the WordPress side.

I have no idea how the new system is supposed to work but I do understand WordPress conventions pretty decently. I've built enough WordPress plugins to have a general idea where to start.

There isn't actually a whole lot on the WordPress side that needs to change. There are a few depreciated functions and a few new ways of doing things, plus a few new ideas that I have, but overall that's it.

Right now, I'm just in limbo with WordPress. I have no system that I can use that works properly no matter which direction I go and it's getting quite frustrating. Been talking about this going on for months and months now. It's just really hard not to get overwhelmingly frustrated with the whole kaltura WordPress situation. We're over a year without a single update to the plugin..... just frustrated is all...,.

[zoharbabin]

@anointed - I think what needs to be done is to add to the < head > of the theme the proper URL to the Kaltura HTML5 library (according to Kaltura Server settings, and whether to use the hosted Kaltura CDN or self-hosted CE/OP version) and replace the token replacement in WordPress from swfObject calls to kwidget.thumbEmbed or kwidget.embed (according to a settings page option selection).

Team is full force ahead with next version, and can't get to it, but source is open and it should be a simple enough task. Considering your great WP experience, will be great if you can take a crack at it, and we'll help with guidance.

Thanks!