Aaron Winborn

Embedded Media Field has grown exponentially in the last year since I've begun developing it. From its humble beginnings as a brainstorming session at DrupalCampNYC last spring, it has grown from a quirky method of make embedding YouTube videos easier for editors to a full-featured suite of modules allowing for drag-and-drop placement of third party videos, images, and audio clips.

Used on a wide range of sites, such as Air America, NRDC, and Drupal Dojo, the module is a flexible and powerful solution for embedding multimedia.

Read on for its strengths and weaknesses...

As referred to in YouTube API for Drupal on the Way, beeradb has now opened the YouTube API module for development. He and I have been working to polish it up and make it ready for release.

You can take a look at the YouTube search on this site if you want to try it out! You can currently search YouTube for tags or users from the form, and see the results right here.

Obviously, that's just the tip of the iceberg. There are some cool things planned for it in the near term, such as integration with Media Mover, Embedded Media Field, and yes, Rob, I haven't forgotten about Annotation Field...

And of course, the holy grail of single site integration of a YouTube video upload from your browser...

I blogged briefly recently about YouTube's new and improved API. Soon thereafter, there was a flurry of discussion about creating a Google Summer of Code project to integrate it with Drupal, including a proposal that wasn't accepted, but I believe nothing further happened from that point.

Until now.

Brad Bowman (beeradb) has stepped up to the plate and created a YouTube API wrapper. He hasn't released it yet, though he indicated that he plans to early next week. I have had the honor of an early review, and it is nice to work with.

I set it up on a test server, and was able to upload a video to its file directory and have it also uploaded to YouTube, showing up in my user account almost immediately. The API also let me view my YouTube video user feed, so I could verify the results without leaving my site.

Additionally, when retrieving videos, you have access to everything stored at YouTube with that video, including video duration (as shown in the screen shot), description, and user comments.

Read on, anxious reader...

On IRC, Károly Négyesi (better known as chx) asked me about the status of the Drupal FTP project. He was concerned that it stores FTP usernames and passwords, which could open up the possibility for security holes and malware if extended or used improperly. Additionally, one of its stated goals was as a possible means to automatically download and install modules on one's site, which is also a stated goal for the Plugin Manager Summer of Code project.

At first, I said that I would remove the project entirely, as I hadn't worked on it in over a year, and had no intention of continuing development in the near future. Even at that time, although I saw the possibility for using it to install modules on your site, I wasn't really that interested in pursuing that aspect, as I really didn't want to get into the security issues involved.

However, I decided to post to the Developer's list first, to get further feedback before removing the project. I had had a few queries regarding the project over the past year, and suspected that there might be some developers actually using it. Additionally, I wanted to find out if there were any compelling reasons to actually keep the module in the project repository.

Turns out to have been a good thing, it looks like. Not only are there a few people actually using the module, I was reminded of other efforts to use FTP with Drupal, most notably Media Mover and, of course, the upcoming Plugin Manager module.

Read on...