A lot of cool features are coming up with this release especially in the beloved link plugin,

1. link plugin: allow users to share links to audio sharing sites such as soundcloud, 8tracks.
2. Repost the attachments along with status (similar to re-share and re-tweet functionality), supported by link and photo plugin.
3. link plugin: inline editing of title and description, cool JS.
4. link plugin: edit the title and description field of the attachment.
5. Support for processing GET parameters in the URL.
6. link plugin now allows to share the URL using the flink GET parameter. More…

The complete list of features and bug fixes can be found in the release notes.

I hope you enjoy creating amazing sites using the new features and share them here for the world to know how cool this module is

What’s in the box
As of today, FBSMP supports the following features:

• Attaches content using AHAH which keeps everything smooth.
• Publishes links, photos, videos, documents (ppt, doc, pptx, odt, etc) out of the box.
• Extensible to publish any kind of content.
• Integration with Activity 2, Rules, Heartbeat, Triggers/Actions, Input Filters, Views, ImageCache, Token, Application Toolbar(Appbar), Emvideo, Userpoints (through Rules), SlideShare.net API and more.
• Extensive developer API (including hooks) and theming methods.

It is difficult for me to elaborate on all the plugins (a plugin allows to publish one kind of content, for example Link plugin allows you to share your favorite links, Photo plugin allows you to share images on your site.), so you will have to explore them yourself. You can look at the documentation here: http://drupal.org/node/876500

How to get involved

• Play with it and share your site creativity here in the comments
• Write about this module so other folks can find it (http://drupalmodules.com/module/facebook-style-micropublisher)
• Report bugs or help in the support issues queue (http://drupal.org/project/issues/fbsmp)

Enjoy it with your holidays, wish you all a Merry Christmas and a great year ahead.

Note: Feature and Support requests should be made through the Facebook-style Micropublisher Forum. I may not be able to answer them here.

Today, I am happy to say that Drupal now has a complete Micropublisher which can be used to create any kind of microblogging platform such as Facebook, Google Buzz, Twitter, etc. I will be posting the first release of the module soon, but before here is the small list of features and a few screenshots.

Among a lot of other features, Facebook-style Micropublisher :

1. Publish links, photos, videos, documents (ppt, doc, pptx, odt, etc) out of the box.
2. Attaches content using AJAX which keeps everything smooth.
3. Extensible to publish any kind of content.
4. Integration with a lot of other modules, such as:
   • Activity, Heartbeat: Create a stream of your statuses, or log messages or status posts/delete.
   • Emfield/Emvideo: Post links directly from YouTube, Google Video, Dailymotion, and others.
   • LightBox2: Create slideshows for your photos and videos (from youtube, etc or directly posted).
   • SlideShare.net: Post documents such pptx, ppt, docs and pdf.
5. Extensive API (good news for developers) and theme overrides (never forget the designers).

I am posting a few screenshots of the module, which will soon have a stable release. Till then, you can download the development build and play with it (which will be actually the stable release in a few days) and report issues if any or just enjoy the module.

(Click on the images to see full view in a ThickBox)

Screenshot of FBSL on LondonFuse.ca

FBSL is designed to be used quite intuitively, this screenshot shows the FBSL status form as themed by Thomas Cermak on LondonFuse.

FBSL status update form

FBSL can be used out of the box, though you can customize it from the settings page. All other information (installation, usage, and changelog) can be found inside the packaged module which is available for download here.

This module has been sponsored by Thomas Cermak of LondonFuse.

Resources:

• Project Page (Download): http://drupal.org/project/facebook_link

Note: Feature and Support requests should be made through the Facebook-style Links Forum. I may not be able to answer them here.

[Google Reader (with thumbnails) can be imitated on a Drupal site by using Feeds, Feeds Image Grabber, FileField, ImageField, ImageCache, ImageAPI and Views module].

How it works
A classic method of mimicking the behavior of Feeds Image Grabber would be to do the same thing manually. Let us go through the procedure if you were to do it manually:

1. Refresh the feed to create nodes for feed items (using FeedsNodeProcessor).
2. For each feed-item, go to their respective webpage and save the image to display.
3. Upload the image to CCK image field for each feed item.

Feeds Image Grabber automates the last 2 steps of the three step process described. Imagecache module can be used to create thumbnail of the image retrieved which can be attached to the node.

What’s in the box
On 3rd March, first version of FIG was released. As of today, FIG supports following features:

1. Automatically downloads and attaches image to the node created by Feeds module.
2. Configurable XPath of the desired image location on the webpage of the feed item on per feed basis (using element’s id or CSS class).
3. Support for FileField Paths module.
4. Configurable maximum image size.
5. Configurable minimum and maximum image resolutions.

Get involved
You can get involved by doing any of the following:

1. write about this module, so that other folks can find it.
2. report bugs in the issue queue.
3. help in the support forums of the module.
4. buy me a Beer

Resources:

• Project Page (Download): http://drupal.org/project/feeds_imagegrabber
• Tutorials: http://publicmind.in/blog/tutorial-for-feeds-image-grabber

Note: Feature and Support requests should be made through the Feeds Image Grabber Forum. I may not be able to answer them here.

I get a lot of requests for this, so here is a tutorial explaining the 3 W’s (What, Why and How) of FeedAPI ImageGrabber.

Motivation

a feed item from google reader

This is a screenshot of a news item from my Google Reader. Anyone who has a moderate knowledge about the feeds would know that the image on the left in the above news-item is actually not published with the feed.

In other words, If you refresh any feed on your Drupal website using FeedAPI, you won’t get the image in the posts, unless they are published along with the feed which is quite rare.

The purpose of FeedAPI Imagegrabber is to make the feed more informative as well as interesting for the user. As, we all know that “comics are much better than novels”, this module appends the feed-item with an appropriate image from its content URL. The goal of the FeedAPI ImageGrabber is to mimic the thumbnail display of Google Reader for the feeds on your Drupal website.

As soon as you refresh the feed, ImageGrabber automatically attaches an appropriate image from the original article to the feed-item node on your website. You don’t even have to press an extra button!!

How it works
A classic method of mimicking the behavior of FeedAPI Imagegrabber will be to do the same thing manually. Let us go through the procedure if you were to do it manually:

1. Refresh the feed.
2. For each feed-item, go to their respective original URL and save the image to display.
3. For each node, crop the image, convert it into a thumbnail and then upload it in an CCK imagefield.

FeedAPI Imagegrabber automates the last 2 steps of the three step process described. You just need to refresh the feed and the ImageGrabber do the rest for you. The most difficult part which only humans can do is to select an appropriate image, for which I am constantly improving on the heuristics.

Download and Install
Download the latest release of FeedAPI ImageGrabber, compatible with your Drupal release, from the project page. Uncompress the folder in your site’s module directory and enable it from the admin/module page.

You are now ready to create new feeds with ImageGrabber enabled.

Next, you must install the following modules to get going:

• Imagefield
• Filefield
• CCK

You must then decide the content type for your feed-items for a particular feed and add CCK imagefields to that content type, before proceeding.

Form User Interface
You can enable the ImageGrabber for the feeds you want to download images for. When you add or edit any feed (i.e. feedapi enabled node), you will see the following additional settings for ImageGrabber:

Form Interface for ImageGrabber

Here is an detailed explanation of the input fields:

1. Enable ImageGrabber: Check this box if you want to enable ImageGrabber for this particular feed.
2. Select image field: ImageGrabber stores the downloaded image in a cck imagefield. You must select one of the imagefield from the drop-down menu.

If you receive this message “There are no imagefields associated with the ‘abcd’ content type.” , then you must add imagefield to the content type mentioned or change the content type of the feed-items to the one which has imagefields associated with it.

3. Search for an image between the tag identified by:
   To understand this, consider that the every feed-item associated with a particular feed has the following structure (HTML source code):
   

   HTML source code of a feed-item webpage

   For the above example, we know that the images associated with this particular post will always be within the

   <div class="post">...</div>
   tag

   Therefore, for this feed you must select the ‘class’ option here and enter ‘post’ in the text-field.
   Similarly, you must find out one such tag from the feed-items of the feed you want to create, see if it is identified by an id or an class. Then, select the appropriate option and enter the class or id in the text-field below. If you select None, the default tag will be ‘body’.

   simple way to find the id or class: Just find out the title of your article in the source code, and start looking for its parent/grandparent tags. Select the nearest parent which has an id or class.

   Now ImageGrabber will look for the images just between this tag, hence eliminating the download (and selection) of images in the sidebar or the header advertisement.

4. Enter the id or class (whatever you selected) in the text-field. Leave it empty if you selected the None option above.
5. Feeling Lucky: This has definitely been borrowed from the big devil Google. It will just select the first image it encounter between the tag specified, if ‘feeling lucky’ option is selected. Otherwise, it will select the largest image between the tags. I would personally recommend you to try out the ‘feeling lucky’ option as it helps saving a lot of bandwidth!! But if it doesn’t work for you, select the otherwise.

When you are done, just refresh the feed and you will see the images attached to the feed-item nodes.

Note: You can also modify your theme a little to get the Google Reader look in which the image floats on the left of the feed-item.

After refresh, you might get the following warning:

ImageGrabber: PHP execution time limit for system is 30 seconds, due to which images for some feed items couldn’t be downloaded. Please click on ‘Grab Images’ to refresh those feed-items.

If you get such a warning, no need to get afraid, just click on ‘Grab Images’ and the remaining feed-items will have their images as well. You may get multiple warnings depending upon your system’s execution time.

Enjoy grabbing images!!

Do leave a comment about this tutorial. Please make support and feature requests using support forums only.

Introduction

FeedAPI Imagegrabber is a add-on module for FeedAPI. It consists of a parser which visits the original URL of a new feed item, and retrieves the main image from the post. Once the main image has been retrieved, it is then converted into a thumbnail using the ImageCache module, and stored in the node created by FeedAPI, inside a CCK field.

The purpose of FeedAPI Imagegrabber is to make the feed more informative as well as interesting for the user. As, we all know that “comics are much better than novels”, this module appends the feed-item with an appropriate image from its content URL. The goal of the module is to mimic the thumbnail display of websites such as digg.com. This goal is acheived by using FeedAPI to turn RSS feed-items into nodes, and then using FeedAPI Imagegrabber to append these nodes with an appropriate image from the feed-item’s webpage.

How it works

A classic method of mimicking the behavior of FeedAPI Imagegrabber will be to do the same thing manually. Let us go through the procedure if you were to do it manually:

1. Refresh the feed.
2. For each feed-item, go to their respective original URL and save the image to display.
3. Crop the image, convert it into a thumbnail and then upload it in an CCK Image field.

FeedAPI Imagegrabber automates the last 2 steps of the three step process described. It uses cURL to download the images and then crop them using Imagecache. Then the image is stored into the CCK Imagefield. The most difficult part which only humans can do is to select the image,  for which I am constantly improving on the heuristics.

Download and Install

Visit the project page : FeedAPI Imagegrabber

Features and Future Releases

Visit the project page : FeedAPI Imagegrabber

History

I understand history is boring, but it is only for those who think the other way round. I started working on this module during December 2008.  At the time, when I started working on this module, I had a little or say no idea about Drupal or its API. It took me quite some time to get used to it and start working on the module. In the Initial release, I thought of very simple heuristics and decided to select the largest image available on the web-page. I completed the module in about 1 month and was very happy with my performance, and then a big blow came which delayed the release of FeedAPI Imagegrabber by 2 months. I had to include an external BSD licensed script for converting relative URL’s to absolute URL’s but Drupal denied to accept this. They said they allow only GPL licensed code and I started to convince them that both licenses are compatible. Unfortunately, I was unable to convince them and I had to create an external link to that BSD script on sourceforge. And now, the module is released with the hope to enhance the visitor-experience on several websites around the globe.

You may find these posts useful:

Tutorial for FeedAPI ImageGrabber
PHP: Relative URL to Absolute URL
Open Source Software and Licenses

Do Leave your comments to let me know what you think.

Note: Support queries and requests should be made through the FeedAPI Imagegrabber Forum. I may not be able to answer them here.