J-Flickr

J-Flickr provides shortcode (e.g. [flickr key=”value”]) syntax access to the Flickr API.

Author:John Noel (profile at wordpress.org)
WordPress version required:2.5
WordPress version tested:2.9.2
Plugin version:1.0
Added to WordPress repository:29-04-2009
Last updated:14-02-2010
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
Rating, %:0
Rated by:0
Plugin URI:http://japanographia.com/j-flickr/
Total downloads:1 492
plugin download
Click to start download

J-Flickr is designed to be as unintrusive as possible in giving you access to the Flickr API service. This means that you are not limited to the methods you can call or hamstrung by the output of the plugin. If you want to search for photos with an Attribution License uploaded last year then you can, just as you can get a list of your public contacts or talk to the Flickr Pandas. Essentially you construct the shortcode as if making an API call and then either use one of the existing general templates or make your own! The templates are in XSL and operate directly on the XML sent back from Flickr so you’re never wanting for data that other plugins may not expose.

Examples

Get a list of photos updated in April 2009:

[flickr method="photos.recentlyUpdated" min_date="2009-04-01" extras="license,geo,tags"]

Get the photos from a specific group pool:

[flickr method="groups.pools.getPhotos" group\_id="57342295@N00" per\_page="25" page="4"]

Get the comments for a specific photo with a custom template:

[flickr method="photos.comments.getList" photo\_id="3459139116" max\_comment_date="2009-04-01" jflickr\_template="commentTemplate"]<h3>Thanks</h3>

Many thanks to Fabien MARTY for his PEAR Cache_Lite work.

Future

I had originally intended to include a web-based template editor with version 1.0 but decided that it muddied the purity of what I was trying to achieve. J-Flickr is still very much a developer led plugin and it seemed an odd usage of time for fluffy UI elements, especially for a 1.0 release.

In no particular order:

  • Admin template manager
  • Proper, remote API key validation
  • WP Media integration
  • Tighter error checking of prerequisites (writable cache directory etc.)
  • Better error reporting than silence or crunchy PHP output
  • Authentication support

These should all be included in a 2.0 release although the development of that will likely depend on interest (if any) of this version.


FAQ