The "You need to download the Echove PHP library" link redirects here, where it says

Please note that the PHP MAPI Wrapper v2.0 is not compatible with any previous versions (when it was known as "Echove"). The class name has been changed, numerous functions have been re-named, and methods have been updated to take advantage of Brightcove API changes.

The earlier version of the library doesn't seem to be available in an obvious place on that site or the GitHub repo it links to.

Oh joy.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

drewish’s picture

subscribing... also seeing this.

Garrett Albright’s picture

Priority: Normal » Major

Upgrading to "major" because, essentially, this module does not work right now.

I've finally got the go-ahead to get our system working with Brightcove, so I'm going to grab the repository and start working on getting this module functional again with the new library. drewish, do you think you could help code and/or test?

I tried to ping Aaron Winborn (the creator of this project) earlier in IRC to talk about collaboration, but didn't get a response. Aaron, if you're reading this, I'd like to hear your input and how best I can move forward and contribute my work back to the project.

aaron’s picture

sorry, it's been a busy month. i'm happy to make both you (@garrett & @drewish) co-maintainers of the project, if you want, and/or you can do the usual patch review routine.

thanks!
aaron

aaron’s picture

for that matter, i just added you both to the project. :D

Garrett Albright’s picture

Ooh, nifty. I'm already making local commits. My goal for the day is to remove all mention of "echove" from the code base and have something working, however incorrectly, by the end of the day. I'll post back here after I've pushed.

Looking at the code, it looks like the MAPI library isn't as different from Echove as I was led to believe (or, at least, the parts of it this module is using), so perhaps this will be an easier task than I thought it would be.

Garrett Albright’s picture

Version: 6.x-1.1-beta5 » 6.x-2.x-dev
Status: Active » Needs review
FileSize
13.69 KB

Okay, pushed into a "mapi" branch. It did in fact turn out that pretty much all that had to be done was changing references to Echove to use the new MAPI instead… pretty simple. The possible exception is video thumbnails and uploads; if I'm understanding things correctly, one needs to have at least a $500-a-month account level in order to use the API which gives you access to that. Uploads I guess I can understand, but you gotta pony up that kinda cash just to access thumbnails?! Anyway, the test account I have access to is not at that level, so I couldn't test that. From what I can see, however, it still works in theory.

I've also attached a patch of my changes, though from what I've seen, applying a patch via Git is strictly theoretical and has never in the history of man worked successfully in practice. It's browsable, though.

skwashd’s picture

The echove library required by the current stable version of brightcove is available from https://code.google.com/p/echove/downloads/detail?name=Echove-1.1.2.zip&...

The current development version of the brightcove module depends on the newer MAPI library. There are some other improvements in the git version of the module, which is expected to be released shortly as the 6.x-2.x series of the module.

skwashd’s picture

Someone pointed me at this issue and I didn't realise when posting that it is a "Media: Brightcove" issue rather than a "Brightcove" issue. Sorry for the noise.

marcp’s picture

@Garrett Albright - The patch applied pretty cleanly with:

marc@tenten:/var/www/sites/d6brightcove/sites/all/modules/media_brightcove$ git apply patch_45.diff
patch_45.diff:163: trailing whitespace.
  
warning: 1 line adds whitespace errors.

When I go to admin/content/emfield/emvideo, the path to Path to Brightcove Media API library gets picked up properly.

After saving a node with an embedded video field url that starts with http://bcove.me/ I'm noticing that a Brightcove ID gets picked up.

My problem, though, is that I'm not seeing the embedded Brightcove video. I'm still troubleshooting but was wondering if anyone's gotten this working with the patch in comment 6 and by downloading the latest PHP MAPI Wrapper?

marcp’s picture

Status: Needs review » Needs work

The reason why I'm not seeing this working is because of the isset() vs. !empty() issue in #942034: use empty() instead of !isset() in template_preprocess_media_brightcove_video which is partially incorporated in the current patch here.

Since the patch in #942034: use empty() instead of !isset() in template_preprocess_media_brightcove_video is against 6.x-1.1-beta5 I'm going to re-roll this current patch with that fix incorporated.

Also, I've tested this with the Brightcove Read API keys and it appears to be working. Re-rolled patch is coming soon.

marcp’s picture

Status: Needs work » Needs review
FileSize
14.81 KB

The attached patch has been tested to work with the latest Brightcove API's read keys. Would be great to have someone else take a look at this.

To apply:

1. Checkout the 6.x-2.x branch from git
2. Put the patch in the media_brightcove directory
3. Run:

   git apply replace-echove-1071226-11.patch
soulston’s picture

I'm working with a company using brightcove at the moment although only to embed video, not upload.

I am using the 6.x-2.x branch and this replace-echove-1071226-11.patch but after creating a video field and adding some embed code I see no video on a node page?

kpr($node) shows the data in the node object. If I add the actual embed code from the $node object manually (print $node->field_video[0]['embed']) I can see the video in the page in the div that I created, so I'm just wondering why the video isn't being output in the $content variable.

What theme_function should I be using to output this video?

I tried:

theme('media_brightcove_video', $video_id, $width = 300, $height = 268, $options = array());

to no avail. Any ideas would be great.

frankcarey’s picture

Assigned: Unassigned » frankcarey
Status: Needs review » Fixed

Merged #6 to 2.x branch
Commit: fd3ec2558f9cc2bf88483a0ba2244c940dc1d78d

Status: Fixed » Closed (fixed)

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