Lightroom 1 Export Plugin for Flickr
This page is for the old Lightroom-Version-1 version of this plugin. Go here for the current version.

Initial Preview  ·  Install Instructions  ·  “Piglets” (Plugin Extensions)  ·

(version history is below)

Some users on Windows get a FormatMessageW failed error when uploading with this or other plugins. Most users don't get it, but those that do seem to get it often.

If you get it, you may find a solution at Alexander Kiel's blog.

Version History

20080714.47Flick Pro users can now opt to Replace previously-uploaded images. I'm not 100% sure exactly what the semantics are with respect to what is preserved from the prior image and what is taken from the new image; let me know how it goes.
20080622.46Fixed the "_update_status" bug that was still happening when the plugin was used with an export preset configured to save non-sRGB JPGs to a photoset selected at export time.
20080613.45A couple of small bug fixes that might help this run in the 2.0 beta a bit better.

Minor tweaks: Added the Flickr logo to the head of the export dialog. Moved the plugin debug log to the Documents / My Documents folder.

Mac Users: if you get an error when you try to install the plugin, something along the lines of "this plugin is already installed or not compatible with your version of Lightroom", please see the install instructions and manually remove the previously-installed version(s). If that still doesn't let you install the new version by clicking, then manually install it. I have no idea why this is happening, so if someone figures it out, please let me know.

20080413.43Uh, a version of the .42 fix that actually fixed.
20080413.42Fixed a problem that caused some people to get an internal error with the previous version. I also reverted the change added in .39 that was aimed to get around a problem in 1.4.0. That problem no longer exists in 1.4.1, so I've put things back.
20080411.41Fix for the "_update_status" bug that those few who export non-sRGB JPGs ran into.

The “Filesize was zero” bug has been solved. Sort of.

It turns out that “Filesize was zero” is Flickr's shorthand for “The size of the file you attempted to upload ended up being larger than the per-image upload limit of your account, which is 5MB if your account is a free one, or 10MB for a pro account.”

The plugin now checks the image that Lightroom builds for the export, and reports the error prior to uploading. The entire export is canceled at that point. I'll work on more sociable error handling for a future version.

Thanks to Ken Rachynski for his help in debugging this.

20080315.39To work around a time-related bug in Lightroom 1.4, I've changed the option that used to be “Set 'taken on' date with each shot when Minimize Embedded Metadata is set” to one that always sets the proper time on the image. It's now ”Set 'taken on' date with each shot (to work around a Lightroom 1.4 bug)”, so you'll probably want to set that if you're using Lightroom 1.4, unless you don't want any date-related metadata sent. Even with this option selected, the file sent to Flickr will still have the wrong “00:00:00&#&8221; time encoded in the EXIF, but the plugin will tell Flickr the proper time, so Flickr's idea of the image's time will be correct.
20080314.38Minor update to allow the plugin to work with Lightroom 1.4.
20080221.37Minor UI tweaks for better appearance on a Mac.
Updated Swedish translation.
20080217.36Small fix to the wording in the Title/Description dialog
  • Updated French translation.
  • Now includes a Swedish translation by Niklas Sjöström.
  • The “select photoset at time of export” (for export presets) feature should actually work now.

Refactored a bunch of the photoset-related code — could have introduced some bugs.

You can now sort the list of photosets, and for presets, have the photoset dialog come up with each export (so now you can select a photoset, or create a new photoset, from export presets).

Includes New version (20080130.4) of my Run Any Command piglet.

20080128.33Tidied up some mistakes in the translation hooks. Interested in doing the translations for my plugins for your favorite language? It's a difficult and thankless job, but you earn good karma for giving to the greater community. If interested, please contact me (jfriedl‍@‍
20080123.31Fix "internal error" bug introduced in previous build, that affected those upgrading from several versions back.
20080122.30Added "Run Any Command" Piglet.
Some internal refactoring to better support the piglet infrastructure.
20080117.29Have export dialog allow file types that any enabled piglets allow. Bail if the resulting filename has an extension that can't be uploaded.
20080115.28Added the piglet manager for fourth-party add-ons
20080109.27New and tidied French translation
20080107.26Housekeeping changes to allow auto-install on OSX
20080104.25Add an option to have the "taken on" date sent with each image even when "Minimized Embedded Metadata" is checked in the Metadata section, to address the issue reported by Scott McMillin
20071227.24Updated French translation
20071222.23Ensure that a long login status message does not crowd out the logout button
20071217.22Update to the title/description logic. Properly handle a no-gallery situation. New French translation file.
20071213.21fix bug introduced in .19
20071213.20new French translation file
20071213.19Can now filter the export so that only images previously exported to Flickr will be processed, or, conversely, only images that have not been previously exported to Flickr.
20071212.18Minor internationalization prep.
20071210.17More internationalization prep. Added a first draft of a French translation, courtesy of Gilles Theophile. (Contact him with any suggested changes.)
20071205.16Can now export the original master file. Can now note an image resolution in pixels per inch/cm in the image metadata.
20071204.15More internationalization prep.
20071204.14Fixed keywording
Added the ability to enter extra keywords in either Flickr style (space separated), or Lightroom style (comma separated).
Lots of internal work to lay the groundwork for internationalizing the plugin.
20071127.12Fix typo introduced in the previous version.
Send along a per-install random identifier with the version check, so I can count how many of each plugin is being used.
20071127.11Make it so that the previous item (bandwidth quota not shown for pros) works without requiring reauthentication.
20071127.10Don't show upload quota remaining if the user has a pro account, since such accounts have unlimited bandwidth (or so I'm told... I don't have a pro account, so I really can't test this)
20071127.9Fix typos introduced in previous version

Added some HTTP error trapping in an effort to get around the 'FormatMessageW failed' error that some Windows users have been seeing:

When the trapping is enabled, those errors are ignored, which may allow things to mostly work, or may simply lead to silent failure. Features that rely on the result of the upload (the new photoid) will stop working for uploads that experience a trapped error, such as the 'delete previously uploaded versions' feature.

This may not help, but it's worth a try until the underlying issue can be found and resolved.

20071125.7Now handles properly ampersands in Flickr photoset names
20071125.6Updated the Upload-Management section to allow visiting the exported photos only when not visiting the exported photoset, which allows one to always visit exactly one Flickr page after the upload, the photoset if a photoset was used, or the list of exported photos otherwise.
20071125.5Added a "Save to Local Disk" section to the dialog:
20071123.3Added plugin debugging option, to track HTTP calls
20071123.2Report under the Title/Description the result of what is chosen
20071121.1Initial public release

All 101 comments so far, oldest first...

Excellent tool. I do miss the meta data editing of the Aperture Flickr plugin but this is very nice.

— comment by David on November 21st, 2007 at 11:20am JST (16 years, 8 months ago) comment permalink

Jeffrey, this works great! Thanks for posting this!

— comment by Frnk Pajonk on November 21st, 2007 at 1:24pm JST (16 years, 8 months ago) comment permalink

Jeffrey, completely not working for me, it transfers the first picture and then fails badly, it keeps coming back saying there are HTTP issues between Lr and Flickr. I can take a screenshot of the error if you want.

I’ve received occasional reports like this, although this is the first with the Flickr plugin. As best as I can figure it now, there’s a bug in Lightroom that seems to be tickled sometimes, although it seems quite random as to who gets it. Most people seem to have no troubles, but some always run into troubles. At this point, I’m pretty much at a total loss as to what it might be )-: —Jeffrey

— comment by Sam on November 23rd, 2007 at 3:46am JST (16 years, 8 months ago) comment permalink

I see that you have new versions with debugging support; I’ll have to give it a try when I’m home tonight, as I’m one of the people who always runs into troubles. I wonder if there could be a Windows dependency (e.g. works with certain versions of XMLHTTP installed but not with others) somewhere? If it is a Lightroom bug, hopefully Adobe can fix it quickly; the idea of getting the export SDK and then finding out that any plugins written with it are utterly unusable on my machine would be a very frustrating thing… 🙂

— comment by David on November 23rd, 2007 at 10:03pm JST (16 years, 8 months ago) comment permalink

This looks like being a very useful plug-in; also a very good reason for me to get round to upgrading to v1.3! If it uses your existing tags when tagging on Flickr, I will be so happy 🙂

It uses the keywords you’ve already assigned in Lightroom, plus whatever ones you add in the Export dialog. —Jeffrey

— comment by David Keaveny on November 24th, 2007 at 6:43pm JST (16 years, 8 months ago) comment permalink

Looks pretty good so far…

One nit to pick is that when authenticated to my Pro account, it claims I have 2048MB left in my upload quota. Pro accounts are actually unlimited. I am guessing that this number comes directly from the API, but the “official” Uploadr utility is somehow aware that Pro accounts are unlimited, so you could be too.

As of .10, I now report “pro” instead of the quota, for pro users. At least, I think I do, but I can’t actually test it myself unless Yahoo want’s to give me a pro upgrade 😉 —Jeffrey

I look forward to the rest of the SDK becoming available so that we can synchronize changes to title, tags and description made at Flickr (possibly by our friends and family who usually know more than we do) back to the LR catalog. I know that the current SDK doesn’t permit this, I just want to add my voice to the crowd that wants the feature.


— comment by RBerteig on November 26th, 2007 at 8:17am JST (16 years, 8 months ago) comment permalink

I spoke too soon…

“An internal error has occurred: Win32 API error (unknown error — FormatMessageW failed) when calling HttpSendRequest from private_AgHttpClient_post_L”

For what its worth, I got this very same message when trying the SDK sample plugin. I’ll retry with your HTTP debug option enabled.

— comment by RBerteig on November 26th, 2007 at 8:20am JST (16 years, 8 months ago) comment permalink

For some reason I am getting the same error RBerteig is getting (apart from the fact that I am also getting the 2048 message even though I am a Pro user) . Quite sad cause your plug-in is exactly what I have been looking for (although additional sync would be great too). Great work, BTW! and hope this gets solved at some point (it might not be your code but the beta SDK, not sure).

The Error:
An internal error has occurred: Win32 API error (unknown error — FormatMessageW failed) when calling HttpSendRequest from private _AgHttpClient_post_L
Version of your plugin: 20071125.7

— comment by Gerardo on November 26th, 2007 at 12:39pm JST (16 years, 8 months ago) comment permalink

Wonderful – thanks. Do you operate some kind of tip jar?

No, but thanks for the though. I take enough from the collective free offerings of the world that it’s only fair to return a bit back. —Jeffrey

— comment by Bahi P on November 27th, 2007 at 4:08am JST (16 years, 8 months ago) comment permalink

very helpful. thanks

— comment by Alex on November 27th, 2007 at 5:21am JST (16 years, 8 months ago) comment permalink

Got the following error in LR 1.3 running under Vista Ultimate x64:

An internal error has occurred: [string “LrHttpDebug.lua]:300: attempt to index global ‘LrDialogs’ (a nil value)

This occurred with the FormatMessageW trap set.

Oops, sorry, silly mistake on my part. Fixed in .9 —Jeffrey

— comment by Carlos Echenique on November 27th, 2007 at 7:53am JST (16 years, 8 months ago) comment permalink

The image settings resize option doesn’t seem to work quite correctly, the units for the resize seem wrong.

I’m not sure what you mean, but the resize box is the standard Lightroom resize box, with the resolution-related stuff removed. It’s changed in 1.3, as Victoria Bampton describes in here.

Are there any plans to be able to transverse down a folder or collection tree creating the collections on Flikr using the folder names for the collection names? Is this even possible with the current SDK?

Sadly, no. The plugin has no way to get the path of an image. —Jeffrey

Excellent work and thanks


— comment by Richard on November 28th, 2007 at 7:18am JST (16 years, 8 months ago) comment permalink

On my export screen there is no units drop down option for the resize it just says pixels. If I go to the export to disk then I get a drop down option box with in/pixels/cm? I hope this clarifies things?


That’s working the way I intended, Richard. Images are always sized in pixels, so any discussion of length in other units (e.g. inches) must be done in the context of a conversion ratio (e.g. pixels per inch). That makes no sense for web-based viewing and just confuses many people anyway, so I removed the whole issue from the upload-to-XXX plugins. —Jeffrey

— comment by Richard on November 29th, 2007 at 7:18am JST (16 years, 8 months ago) comment permalink

I think I’ve found a bug….

Go to the Adobe “Export to Disk” exporter, set the dpi to say 402 ppi and the resize to long edge and set to 2 inches.

Now switch to your Flickr exporter and you’ll notice it it says 2 pixels, if you export this you’ll get an image 804 pixels on the long edge not 2 pixels!

If you switch back to the Export to Disk and set the resize to long edge and use pixels as the dimension and then go to your exported you’ll notice that the number of pixels is correct at 804.

So the conclusion is that you need to use the API to set the resize to pixels as at the moment it seems to be set to whatever you last used in another exporter.

Hope this makes sense?


— comment by Richard on November 30th, 2007 at 4:15am JST (16 years, 8 months ago) comment permalink

The reason you get a “FormatMessageW failed when calling HttpSendRequest …” is that, by default, FormatMessageW only searches the “standard” message libraries for the text associated with an error code; To get the text associated with HttpSendRequest() et al you need to specifically pass the library/module handle to the API — i.e. set the FORMAT_MESSAGE_FROM_HMODULE flag in the first parameter and pass the HMODULE for Wininet.dll as the second one — this will then at least give you the user-readable error message hopefully allowing you to track down what the problem is. After having a very quick look at the plugin, I guess this is actually done within the LUA runtime ???

— comment by David Field on December 4th, 2007 at 2:22am JST (16 years, 8 months ago) comment permalink

This is an AMAZING product, this brings productivity, and daily posting to the next step! The only tweak I could imagine is having a reverse order upload. I shoot a lot of “events” and like my images presented in the order that they happened. This works with the sets, but not the stream, If I upload event_image_01 – 23, I would like my stream to read 01-23 and the set to read 01-23. Is this doable?

Well, you could just change the sort order to Z-A in the toolbar before the upload, and that would take care of it. A quick look at the API makes me think that it wouldn’t be easy for the plugin to do for you, except in an inefficient “render everything, then upload everything” way. —Jeffrey

— comment by Scott Winklebleck on December 4th, 2007 at 3:03am JST (16 years, 8 months ago) comment permalink

Hi Jeffrey,
Thanks for this usefull tool.
Would it be possible to add an option to *not* recompress jpg file on sending to flickr ? Because I have noticed that the file size on the server is not the same as the one I have exported (probably depending on the jpg quality parameter ?). Of course, I don’t do any resize. Dont know if it has some importance but I am using your tool on a Mac (10.5).

That sort of goes against the whole Lightroom paradigm, but it seems reasonable to me if you’ve made no changes (to the image, or the metadata). Perhaps they’ll add that feature in a future version of Lightroom.

Another thing I notice, accents in tags are well supported (thanks so much for that!) but the accented tags are duplicated and the second one doesnt have the accented letters in it. Strange ?

It could be that Flickr is pulling them from the image itself, and doing it differently than I am. I’ll have to check it out, so thanks for the heads up. —Jeffrey

Hope this help to improve the tool.

— comment by iolo on December 4th, 2007 at 7:48am JST (16 years, 8 months ago) comment permalink

Fabulous plugin… so handy. Thanks for your work on this.

I would love to have the ability to apply a transparent watermark to an image, based on a graphics file, rather than just the © 2007 Duncan Babbage text. Thinking about it though, your plugin can presumably only access features that are already in Lightroom, and as far as I know Lightroom hasn’t got a feature like that yet. (I would love to be able to do that on export from Lightroom more generally!) So probably nothing you can do about this?

— comment by Duncan Babbage on December 4th, 2007 at 6:34pm JST (16 years, 8 months ago) comment permalink

Today’s build exported a single full-size image just fine, complete with appropriate keyword/tag handling. I’ll abuse it more in a few days.

Since I didn’t spot any feedback on my bandwidth remaining vs. Pro account nit, I’ll report that it now simply says (Pro) without comment about bandwidth available. That looks more like the Flickr way 😉

I fixed it because of your comment, so thanks. At the time, I added a note directly to your earlier comment in the same way I’m adding this one, but since you didn’t put your email, that’s the best I could do. In any case, I’m glad it’s working properly.

It sounds like the messed up error message issue is going to require a patch from Adobe; David Fields sounds like he’s read the MSDN documentation more recently than I have. It certainly is true that correcting use of a Windows API is well outside of what we can control in Lua from the LR SDK environment. Now if they let us load our own DLLs…… the request for improved watermarks would be easy to do….

Well, I can invoke any random executable, so in theory I could execute a program that I include with the plugin that added a watermark, but that involves recompressing the JPG prior to upload, which is really an ugly solution…. —Jeffrey

— comment by RBerteig on December 4th, 2007 at 7:29pm JST (16 years, 8 months ago) comment permalink

Regarding the no-recompress thing, actually Adobe already includes it: it is call ‘Original’ in the File Format dropdown list. By having a look at your code in Flickr.lua, I have noticed that you forced the file format to JPEG, preventing us to set the item to ‘original’. I have commented out the line “allowFileFormat” and the ‘original’ item is then again. With this option the export is made without any recompress of my JPEG. Would it be possible in future version to add the ‘original’ item to the list of allowed file format ? I think this would be realy usefull for people like me that use Flickr also as a JPEG backup tool (by the way, metadata are embedded in the exported JPEG file if you set the correct option in catalog preference even with the ‘original’ export format). Thanks again for this GREAT tool! iolo

— comment by iolo on December 5th, 2007 at 4:58am JST (16 years, 8 months ago) comment permalink

I’m really loving this tool and I thank you for it!

Is there any way to add an option to automatically add photo’s to a collection when they are exported? I like to track the photo’s that I have uploaded and I prefer to do that via a collection, so it would be nice to do that in one easy export dialog…

Sadly, the API doesn’t yet allow for this… —Jeffrey

— comment by Sean Phillips on December 5th, 2007 at 1:34pm JST (16 years, 8 months ago) comment permalink

Morning Jeffrey,

I noticed an update message in the export dialogue that appears in LR so I clicked, downloaded and loaded into my Modules folder. However, restarting LR and the new version note still appears – what have I missed?

And like everyone else, thanks your script is superb.


— comment by Paul on December 7th, 2007 at 12:05am JST (16 years, 8 months ago) comment permalink

One thing I noticed when I get the dreaded FormatMessageW error. Within 24 hours all of my requests get completed and uploaded to Flickr. I end up having multiple copies of the shot on the gallery and looking like a newb.

— comment by Carlos Echenique on December 9th, 2007 at 3:15pm JST (16 years, 7 months ago) comment permalink

I just updated to the latest version, but it’s not working for me. On export, I receive a message, “No images to process. All were filtered out”

Any ideas?

I’ve no idea…. well, no idea except “stupid error on my part.” Thanks for the heads up… fixed in x.21 —Jeffrey

— comment by Matthew on December 13th, 2007 at 12:42pm JST (16 years, 7 months ago) comment permalink

Wow! I thought it would take months to get a decent quality Flickr plugin for LR 1.3+ but this is brilliant – just what i’ve been waiting for. Thanks so much!!

— comment by Ed Lawford on December 13th, 2007 at 10:24pm JST (16 years, 7 months ago) comment permalink

You are amazing! I thank you sir. This is a great plugin.

— comment by Ryan on December 20th, 2007 at 4:35am JST (16 years, 7 months ago) comment permalink

I gather this doesn’t allow for manually-derived ordering? The order of the photos in my photostream is important to me, and not date-based, so I’d like to be able to exert control over this.

That’s pretty much the only feature that’d keep me from using this.

— comment by Geoffrey Wiseman on December 20th, 2007 at 8:46am JST (16 years, 7 months ago) comment permalink

This is an incredibly useful plugin, Jeffrey; thanks for the hard work!

Here’s a request: I’d like to be able to append the file name to the description field. Instead of using the radio buttons for the description I’d like to be able to specify a format string that is filled in with the meta data I specify. Like: “{$description$} [{$filename$}]”. So that if the image’s description were “This is my picture.” the plugin would set the description to “This is my picture. [c04_1234]”.

What I’m trying to do is to get the file name visible on my photo pages so that I can tie those photos back to my local catalog. But allowing a generic string like this instead of using the radio buttons (which should be kept, they’re a cool idea) would let people get creative with the information put into the title and description fields.

I’d be happy to donate programming time!

Thanks again for the plugin!

— comment by -glenn- on December 20th, 2007 at 12:19pm JST (16 years, 7 months ago) comment permalink

Nice work Jeffrey.

But I’m finding the process dead slow on my Windows XPPro box. The export process seems to last forever, and I’m just outputting 800 pixel 75% quality.

Does it generate a log file somewhere so one can see where the delay is occurring. That might be a handy feature.


— comment by John Beardsworth on December 30th, 2007 at 8:56pm JST (16 years, 7 months ago) comment permalink

Thanks very much for this plugin. It is a very nice refinement to my new LR workflow.

— comment by Quentin Fennessy on January 3rd, 2008 at 11:47am JST (16 years, 7 months ago) comment permalink

Great plugin – essential for me to make Lightroom a good alternative to Aperture. I’ve tried it a few times and it works really well.

Similar to Sean’s question: my Flickr export plugin for Aperture allows adding a keyword to every photo that it uploads and can add metadata for the Flickr photo ID and URL. Having both would be very nice (and probably needed for replacing too), but just the keywords would be nice.

— comment by Erik Romijn on January 4th, 2008 at 7:28am JST (16 years, 7 months ago) comment permalink

Holy freaking AWESOME this is great, great, great. Precisely what I’ve been looking for in a Lightroom -> Flickr exporter. Thank you!

— comment by Jim Ray on January 5th, 2008 at 8:29am JST (16 years, 7 months ago) comment permalink

it seems a great feature for me but I get an error when I want to authenticate

“Oops! Flickr can’t find a valid callback URL.

An external application has requested your login credentials and permission to perform certain actions on your behalf, but has failed to include all the required data”

I use Mac OS X 10.4.11 and Lightroom 1.3

Very odd. It seems as if Flickr is thinking that the plugin is a web app (a web app would have a callback url – a desktop app like the plugin does not). 1,500 people have authenticated with the plugin and yours is the first report like this, so perhaps Flickr was just having a hickup? —Jeffrey

— comment by tgpapa on January 5th, 2008 at 9:38am JST (16 years, 7 months ago) comment permalink

Great plugin, thanks for your hard work. I’ve been looking for a solution to cut down on extra workflow burden in exporting and dealing with Uploadr. I’m a pro photographer, but occasionally I want to throw up some personal photos for my friends. Cutting out that extra work means I’m more likely to do it now (before it could take me weeks or months to get around to it)!

— comment by Tim on January 6th, 2008 at 5:53am JST (16 years, 7 months ago) comment permalink

Hi Jeffrey,
I’m trying to install the new version (2008) of the plugin and it tells me that the update is already been done ot thet this version of the plugin is not compatible with the version of Lightroom. Is there a workaround? It still shows that there is an update avail so it did not install…

I’m on Mac 10.4.11 LR 1.3

Thanks for making our lifes so much easier with LR!

This is fixed in x.26. It’s just some housekeeping things that allows the plugin to be installed on a Mac just by clicking on it — you could have always installed it manually, but not it should work either way. I think. We’ll see… —Jeffrey

— comment by Fred Ranger on January 7th, 2008 at 3:10am JST (16 years, 7 months ago) comment permalink

Great stuff – thanks for your efforts.

one question, I notice that your plugin tracks what it has already been uploaded to Flickr

is there anyway i can tell it which ones ive uploaded prior to your plugin?
(ive got a keyword which i place on everything I upload… but i dont want to re-upload everything via plugin)

that way i can tag my new photos that i want to upload with flickr, and then just use your upload ‘new’ function.

thanks again,

— comment by Mark on January 7th, 2008 at 7:08am JST (16 years, 7 months ago) comment permalink

First of all, Thank You for this great plugin; it will save me a great amount of time.

One problem I’m seeing: I’ve turned off the Export Containing Keyword and Include on Export on some of my keywords, but I still see them being set on my uploaded photos. Seems like a bug…

– Gyuri

— comment by Gyuri on January 7th, 2008 at 9:57am JST (16 years, 7 months ago) comment permalink

Great program. I am using the mac. When uploading the final photo I get the error message “Bad Upload: filesize was zero”

This was finally fixed in version .40. It turns out that “filesize was zero” is Flickr’s shorthand for “the image is larger than your account’s per-image upload limit.” —Jeffrey

— comment by john k on January 8th, 2008 at 2:20pm JST (16 years, 6 months ago) comment permalink

Awesome plugin! Thank you very much for creating this – it’s saved my life.

Any plans to add Proxy support by the way? Would be handy for those of us who need to upload in a corporate network…

Thanks again!

— comment by Matt Fahrner on January 11th, 2008 at 5:39am JST (16 years, 6 months ago) comment permalink

I use this daily, and it’s superb.

One minor thing is that you could add an image header to the export drop down, as with the LR/Mogrify plugin – it’s just a prettification though.

I have images there in my SmugMug and Zenfolio dropdowns, but Flickr requires that I obtain written permission before I can add it here, and I just don’t have the energy to go deal with that. —Jeffrey

Another thing is that I’d like to be able to have my IPTC data from metadata posted to flickr somehow…. actually I think that’s a Flickr limitation rather than anything your plugin can do.

You should set up a Paypal donation button somewhere. I’m so pleased with this plugin that I’d be happy to contribute.

— comment by Andy Piper on January 12th, 2008 at 2:24am JST (16 years, 6 months ago) comment permalink

The error “Internal Plugin Error Bad Upload: Filesize was zero” is due to trying to upload photos that are in excess of 10Meg. Flickr sets a 10Meg limit per picture.

Doh! After figuring this out on my own and pushing a fix, now I noticed this comment. I wish I had noticed it two months ago; I’m not sure why I didn’t. In any case, the plugin now (as of version .40) reports the actual error. The 10MB limit is for pro accounts; us cheap schlobs have a 5MB limit. —Jeffrey

— comment by Skip Harris on January 12th, 2008 at 1:12pm JST (16 years, 6 months ago) comment permalink

Can you add an option to tag the uploaded photos in LR with “uploaded to flickr” or something similar? Maybe even with a date field?

Is it possible to when exporting to add “use existing location” as an option for saving a local copy? Or is this a limitation in the LR api?

Thanks for the great tool!

Both are great ideas, but alas, the API doesn’t allow for them yet. —Jeffrey

— comment by CuriousB on January 13th, 2008 at 2:24am JST (16 years, 6 months ago) comment permalink

I keep getting ‘Internal Plugin Error’ when I try to do anything using either the Picasaweb or Flickr plugins. When I switch to the plugin I get the error (then it says checking for updates aborted) or when I try to login same thing.

I’m on Lightroom 1.3.1 403270

— comment by Dylan on January 14th, 2008 at 5:21am JST (16 years, 6 months ago) comment permalink

Hi Jeffrey,

First – thanks so much for the export program – I use it virtually everyday for uploading pics to Flickr.

I have been attempting to get the Mogrify tool to work as I now want to send images to Alamy who have a min file size of 45 megs, but as yet I can’t get the tool to work. Here’s the question – can I use your tool to export an image of the required size but to then place the file on my desktop before sending on to Alamy?

Thank you once again,

LR/Mogrify is written by Tim Armes, so you should probably contact him. —Jeffrey

— comment by Paul Hodgson on January 14th, 2008 at 11:57pm JST (16 years, 6 months ago) comment permalink

I’ve noticed that some keywords that should be ignored on export are being included and tags created. When I look at the “Will Export” list of keywords the list is correct. When I export to JPEG, everything is fine. Some of the keywords that I’ve chosen not to export and correctly being ignored. Ones below that, are being included. My Keywords look like this (tabs might destroy this, but it’s a simple cascade).

Sport *
–Basketball *
—-League *
——Team Name *
———-[#6 Player Name]
————{Player Name} *

The plugin is correctly ignoring [Players]. It is incorrect in that it exports [#6 Player Name]. The only tags I expect to be created are for the ones with the asterix *

This is a bug in Lightroom; I’ve reported it to Adobe. —Jeffrey

— comment by Rob Scriva on January 17th, 2008 at 2:17pm JST (16 years, 6 months ago) comment permalink

Just thought I’d pop back to note that Alexander’s registry hack that increases the timeout seems to have solved my problems with the FormatMessageW() error. All in all, I’m a much happier camper.

Now to go play with your piglet idea a little… that seems like a clever approach to the general problem of chaining operations before an upload.

Thanks again!

— comment by RBerteig on January 17th, 2008 at 6:49pm JST (16 years, 6 months ago) comment permalink

Hi Jeffrey; re: above 2 blogs….
Sorry about all this…new developments are as follows…I have finally managed to get the new piglet/mogrify menus up, however the only option I am given bottom right is to “Cancel”…the Export button is not hi-lighted…..any suggestions?…I’m usually not this incompetent…really 😉

The export button is greyed out when some configuration in the export panel is in an incomplete or invalid state, whether in the host plugin’s pannels or a piglet’s. If you’ve installed the LR/Mogrify piglet but have not configured it with the location of the “mogrify” command on your system, the piglet may well disable the [Export] button.

It sounds like you should remove the piglet, or, if you think you need that piglet, read the LR/Mogrify piglet instructions. —Jeffrey

— comment by Rob on January 20th, 2008 at 1:04am JST (16 years, 6 months ago) comment permalink

Great plugin, makes my life so much easier. Running fine on XP and LR 1.3.1

— comment by Garry on January 25th, 2008 at 10:20pm JST (16 years, 6 months ago) comment permalink

Thanks dude, you’re doing good work!

— comment by Flickrfan on January 26th, 2008 at 5:23am JST (16 years, 6 months ago) comment permalink

I’m seeing the same keyword export issue as Rob Scriva with that addition that child > parent relationships are exported along with the parent and child keywords.

Unfortunately, I can’t do anything about that – it’s a bug in the plugin API. I’ve reported the bug to Adobe. —Jeffrey

— comment by John Buxton on January 26th, 2008 at 9:59am JST (16 years, 6 months ago) comment permalink

Thanks. Installed it and it works like a charm. Does it apply the preses that are set on the selected picture to export to Flickr?

— comment by Andre Fortier on February 4th, 2008 at 1:31pm JST (16 years, 6 months ago) comment permalink

After following your instructions on how to put a (flickr)plugin in Lightroom: after restarting Lightroom nothing shows up under ‘export’ but Lightroom presets and user presets.
What went wrong?

— comment by Lex Eckhardt on February 7th, 2008 at 6:15pm JST (16 years, 6 months ago) comment permalink

I’ve just added this to my copy of Lightroom and it works a treat. That should speed up my workflow a fair amount. Thanks.

— comment by Carl on February 18th, 2008 at 9:04pm JST (16 years, 5 months ago) comment permalink

Thank you for this export plugin. It is a wonderful time saver. I use Mac OSX and Lightroom 1.3 and I have just one minor issue. Text Spacing. within the export dialog.

Your text labels are squeezed closely to checkboxes and any other UI component. Unlike Lightroom’s “Image Settings” section. Also the “add images to flickr photoset” dropdown box is slightly cut off. So thanks again for the plugin. And none of these prevent your plugin from working, just doesn’t look so pretty. 🙂


— comment by Joe on February 20th, 2008 at 5:12am JST (16 years, 5 months ago) comment permalink


After doing a bit of searching I still can’t find a reason why the plugin won’t show up in lightroom 1.3.1 export dialogue. Any ideas? It is installed in the module folder in my library with all the other lightroom presets. If I try double ckicking on the latest release of your plugin, lightroom says that it is not compatible.


— comment by Ben Geldreich on February 24th, 2008 at 4:12am JST (16 years, 5 months ago) comment permalink

Fantastic plugin. Couldn’t live without it (use both Zenfolio & Flickr).

One request/question. Would it be possible to provide an option to build a custom string for title and caption/description like in web gallery module in LR? At the moment we are limited to predefined metadata fields. I would like to be able to assemble my own string consisting of exposure information, camera model, lens used etc.

— comment by yOOrek on February 26th, 2008 at 9:50am JST (16 years, 5 months ago) comment permalink

Great job!

Feature request for you (or if it already does it, can you please explain how?) — It would be great to have a way to change each photo I exported in a way so that I know it’s been exported. Something like “Upon successful export, flag image as yellow” or “After export, add the keyword ‘exported to Flickr’ to each photo”

It would be nice ot keep this open-ended so that we could do anything to the photos that have gone through the export.


That’s a great idea, but sadly, the current API simply doesn’t allow for the plugin to reflect any state back to image settings you can see. Adobe has hinted that some future version of the API will allow for it, so until then, we just have to wait… —Jeffrey

— comment by Joe on March 3rd, 2008 at 6:21pm JST (16 years, 5 months ago) comment permalink

Thank you

— comment by Conor on March 6th, 2008 at 1:36pm JST (16 years, 5 months ago) comment permalink

Nice job, I have been longing for this for a long time!

Only problem: When exporting tags with umlaute (äöü) and probably other characters too (áùø) the special characters are deleted out of the word. maybe some problem with character encoding ?

— comment by Stefan on March 8th, 2008 at 7:48am JST (16 years, 5 months ago) comment permalink

To be more precise, there is actually a duplicate tag generated with the special characters missing!

— comment by Stefan on March 9th, 2008 at 10:07am JST (16 years, 4 months ago) comment permalink

I have the same problem than Ian:

An internal error has occurred: [string “colorspace_check.lua”]:95: attempt to call field ‘_update_status’ (a nil value)

Strangely, this only occurs when I use an export preset; if I go via the “Export…” dialog the upload works fine.

This is fixed (finally) as of .41 —Jeffrey

— comment by Matthias on March 15th, 2008 at 11:58pm JST (16 years, 4 months ago) comment permalink

Jeffrey, first off this thing rocks! I couldn’t deal with Flickr without it. Second, is there a possibility that you could change the Refresh option under Upload management to behave a tad different.

Ideally instead of a “delete any previous uploaded versions of the exported images in your Flickr account” there would be a “replace any previous uploaded versions of the exported images in your Flickr account”

Yes, that would be an excellent feature, but it requires a Pro account (it’s not supported in the free accounts). I’ve asked Flickr numerous times whether they’d provide a Pro account for me to develop with, but I’ve never gotten a response (and it’s not something I’m willing to pay for, nor let someone else pay for). I’ve also asked whether they’ll let me put a Flickr logo at the top of the plugin as I do with all my other plugins, but no response to that either. —Jeffrey

Currently, if I make a small tweak to a file, or decide I want to change some output setting, I have to export it again directly with Mogrify and then go to Flickr and do a replace image. The reason is otherwise the image is deleted and it is no longer in any of the sets or pools it was submitted. This is bad as some pools you can only submit so many times per day, and some moderators don’t like it if you delete and repost the same image as they feel you are “bumping” it to the most recent spots.

Other than that minor nitpick, again this ROCKS!


— comment by John on March 17th, 2008 at 3:48pm JST (16 years, 4 months ago) comment permalink

Awsome job with the plugin.

I am one of the users who unfortunatly recieve the FormatMessageW failed error, but its finicky in that sometimes even with the error the image(s) are uploaded. Othertimes only some are, and sometimes no pictures are.

I’m on Vista running Lightroom 1.3.1.

Can’t wait for updates to the API’s, giving this plugin more functionality.
And getting the pesky error resolved aswell, of course.

— comment by Pavan Chander on March 22nd, 2008 at 12:42pm JST (16 years, 4 months ago) comment permalink


This is a great plug-in, but I have to add my name to the list of people getting the file size is zero error. What I have noticed is that I only seem to get it at the 50th image in my filter or later. I just tried to upload 58 photos and the only thing I can see is that photos 50-58 all give this error even if selected individually.

Hmm, I tried a little further by taking the last nine images and putting them in a quick collection and seeing if the filter might have been part of the cause. Even with only nine pictures to upload the plugin still fails to upload all of these. I can’t really see how these are any different than the other 49.

Lightroom 1.3.1 402355
Plugin 20080315.39
OSX 10.5.2

With Ken’s help, I was able to track down the problem (that the images are too large for Flickr’s per-image upload limits), and now version .40 fixes this by reporting a helpful message. — Jeffrey

— comment by Ken on March 25th, 2008 at 1:59am JST (16 years, 4 months ago) comment permalink

Great plug in but … I have the HTTP error and even with the HTTP silent alert checked, the problem is that some commands like “add to an album” seems not to work.

the error occurs when the image is too big (ie : not resized or resized up to 1000*1000 (not sure, I have not make more precise tests in that way but at 2000*2000 it crashes, at 700*700 it works fines)

note : I have the piglet mogrify but with or without it activated, it’s the same

It will be great if you could help … thanks a lot.

contact me if you need more infos, or if I can help debuging or something


— comment by David on April 5th, 2008 at 5:56pm JST (16 years, 4 months ago) comment permalink

Thanks for the work, Jefferey.

I’m mot getting the sizes that I specify. I can specify jpg “Long Edge” 640 or “Width & Height” 640×640 yet I still get large images. Examining the html log file and finding the tmp directory where Lightroom is creating the exported files I find images at their Lightroom Cropped sizes (the sizes indicated in the metadata panel). Any clues as to what I’m doing wrong?

— comment by pelón on April 7th, 2008 at 2:02pm JST (16 years, 4 months ago) comment permalink

Have you looked at allowing the plugin to insert pics directly into Flickr groups? That would be a huge time saver! If the Flickr API doesn’t allow it then perhaps there’s a way to tie it into the Flickr Multi Group Sender GreaseMonkey script?? I’m no programmer and so I don’t know how to do this, it just seems like there should be a way.

It looks like the Flickr API allows for this, so I’ll see whether I can code something up…. —Jeffrey

— comment by Sean Phillips on April 11th, 2008 at 3:26am JST (16 years, 3 months ago) comment permalink

After installing the plugin on Windows XP with LR 1.4.1 it appears in the Export options, but says it’s not usable due to an internal error 🙁 Is there some way to get more debugging or is there something stupid I’ve missed? Thanks for your work on this 🙂

— comment by david on April 13th, 2008 at 8:53am JST (16 years, 3 months ago) comment permalink

very nice work, I wonder when Adobe will integrate that into Lightroom 2.0

just a wee question please: I have Lightroom 1.3.1 running on Windows XP. I dowloaded both Flickr and Picasa plug-ins into the module folder as instructed.

However. Although the picasa plug-in seems to be working fine. Flickr plug-in won’t show at all and just gives me a generic: The plug-in had an internal error.

Could you please help me on that? Thanks in advance Jeffrey!

— comment by Calliope Georgousi on April 13th, 2008 at 9:20am JST (16 years, 3 months ago) comment permalink

Hi. Enjoying the Flickr plug-in; thanks.

Here’s an idea for the (no doubt long) future features list. At the moment all the photos from a given export end up in the same photoset (or none). How about allowing per-photo setting? Two methods spring to mind:
1. Respond to a tag of “flickr-photoset:X” and put the photo in that photoset.
2. Have a configuration table in the settings of the plug-in along the lines of “put photos with these tags into this photoset”.

Would just improve something that’s already very nice. Thanks again.

— comment by Lorenzo Wood on April 13th, 2008 at 7:58pm JST (16 years, 3 months ago) comment permalink

Hello Jeffrey

Thank you so much for your wonderful plugin.

I am using your plugin on a few computers with great success. For some reason, an install attempt on a MacBook gives me:
“Can’t Use Plugin” followed by “The plugin had an internal error”

I have installed and reinstalled a few times. I have even tried reinstalling lightroom. Any thoughts?

Thank you so much!

lightroom 1.4.1
Intel MacBook running OS X 10.4.11

— comment by Mikey on April 16th, 2008 at 7:14am JST (16 years, 3 months ago) comment permalink

Hi Jeffrey, I have been using your plug in for a while and it is quite good. I have noticed however, that all keyword tags get exported in lightroom hierarchichal format even when that option is not selected. That or something weird is happening, as when I go to flickr I will see some keywords like color > red rather than color; red. Is this a known issue? I have done the same exporting to my hard drive without your plug in and in that case the option is respected.


— comment by Gerardo on April 16th, 2008 at 2:44pm JST (16 years, 3 months ago) comment permalink


Outstanding job on the Flickr uploader.

Would you consider a custom version to help simplify my need to upload both sample and deliverable images for delivery to customers?

Paid, of course 🙂


— comment by Ross Cobb on April 25th, 2008 at 12:27pm JST (16 years, 3 months ago) comment permalink

Hi Jeffrey

This worked for a couple of pics, but when exporting any now I get

Bad upload: empty response

Using LR2.0 beta, and latest version of your plug-in

These are cropped photos and even at 75% jpeg I get the error so can’t be anywhere near 10 MB file

Any ideas?

— comment by Paul Webster on May 1st, 2008 at 5:07pm JST (16 years, 3 months ago) comment permalink

Does the plug in handle inclusion of GPS metadata when uploading to flickr? I have photos properly tagged within Lightroom, but after uploading to flickr it would seem the information is lost.

— comment by Kevin on May 24th, 2008 at 3:40am JST (16 years, 2 months ago) comment permalink

Disregard my last comment. flickr requires you to enable the automatic importing of GPS data. Your plug-in, which rocks, is working fine.

— comment by Kevin on May 24th, 2008 at 10:38pm JST (16 years, 2 months ago) comment permalink

This plugin is great, but it seems to frequently hang or get stuck during upload. When this happens, I’ve let it run for a few hours, and it stays on the same photo, which never appears in Flickr. If I try to cancel it, it never cancels. I have to restart Lightroom (using 1.4.1 on Mac OS X 10.5, not the beta) and retry the export.

Any ideas?


It sounds like a flaky internet connection to me, but it’s hard to tell… —Jeffrey

— comment by Tim Norman on May 27th, 2008 at 8:15am JST (16 years, 2 months ago) comment permalink

Thanks a lot for this. It’s working great so far and I’m sure will help me with my photography as I stop being lazy and load more pictures for critique.

— comment by Brent on May 27th, 2008 at 10:59am JST (16 years, 2 months ago) comment permalink

I seem to have a problem crop up with my plugin. It worked just fine for quite some time but then one day, I tried to export to Flickr and it does not show up at all in the drop down menu (in the exports dialog). All it shows is “Export to Disk.” I’m betting that there is a problem with the recent version of Lightroom because updating LightRoom is the only thing that I can think of that has changed. I’m running Lightroom 1.4

Any pointers would be great.

You have to reinstall the plugin when you go from 1.3 to 1.4. The 1.x plugin install/upgrade support is really minimal, so you have to do everything manually (it’ll be better in 2.0). —Jeffrey


— comment by Art on May 28th, 2008 at 11:07pm JST (16 years, 2 months ago) comment permalink

And trying to export without the photo set got this error:

Bad upload: Service currently unavailable (API Disabled)

Maybe it’s just Flickr, then?

Yeah, the “Service currently unavailable” message is one from Flickr; I suspect that they were doing maintenance, or having “issues”. I’d not programmed to handle that error (or many other errors… they’re weak in that respect). I’ll try to update the plugins to be a bit better… —Jeffrey

— comment by Suzanne on May 29th, 2008 at 2:40am JST (16 years, 2 months ago) comment permalink


I have downloaded and installed your plugin for Flickr. Every time I attempt it I get the following message: Internal Plugin Error Bad Upload: Empty Response.

Only the first image I am trying to upload makes it, and it does not put it in the set I want it to go to. I am using Windows XP and LR Beta 2.0. I have also tried it in LR 1.3 with similar results. I also tried the Adobe version and had similar results.

Any help would be appreciated,

— comment by Michael on May 29th, 2008 at 10:43pm JST (16 years, 2 months ago) comment permalink

Love the plugin. With LRMogrify it has sped up my work and reduced the number of files on my computer.

That said I have one request for addition. Can you add the ability to automatically add the original filename as flickr metadata? I often rename the pictures for posting on flickr and this would be a nice addition for me.

Mark Alston

— comment by Mark Alston on June 1st, 2008 at 1:10am JST (16 years, 2 months ago) comment permalink

Hi Jeffrey,

Just a quick thanks for this plugin. I’ve been making a conscious effort to embrace the new workflow tools that exist and this is certainly a major benefit of such. Whilst im only in my mid to late 20’s i have been using the internet and digital cameras since the inception of both and for the most part have (being a PC user) utilised manual image copying and archiving. XP never really got close to even the ease of iPhoto in image management IMHO. Dont even start me on XP’s attempts at batch file renaming. The most automated i have been is via custom macros in Photoshop and a collection of specific renamers, res/size editors and the like. Over the last month i have evaluated Lightroom and tried to get my head around FlickR (as i was an avid SmugMug user i have struggled with FlickR’s reverse display of photo sets, its lack of elegant private galleries and the lack of grid photo navigation) but now i am sold. The workflow has become fun! Tagging and indexing 20 gig of photography is not so fun :/

Once again thanks for your work and hello from Australia!

— comment by Dave on June 11th, 2008 at 10:18am JST (16 years, 1 month ago) comment permalink

I still get

An internal error has occurred: [string “colorspace_check.lua”]:95: attempt to call field ‘_update_status’ (a nil value)

When using an export preset. When run with the normal export dialog no problems.

I’m exporting a RAW image with AdobeRGB to JPEG 100% quality sRGB.



— comment by Dave on June 20th, 2008 at 6:26pm JST (16 years, 1 month ago) comment permalink

I just noticed an anomaly . My Export plugin will not allow me to create a new Photostream because it says I have exceeded my Photostream quota. I can’t find any reference to a Photostream Quota in the help pages of Flickr (but have posted this question there, too.) This seems odd as I only have three Photostreams in my flickr account.

3 is the limit for free acounts. Flickr Pro (paid) accounts have no limit. —Jeffrey

Thanks for this plugin – it is so useful. And thanks for sharing your life with us via your blog. I feel like I really know your family and am getting to know japan at the same time.

— comment by Brian Jones on June 23rd, 2008 at 9:20pm JST (16 years ago) comment permalink

Enjoying this plugin. Haven’t seen anything else that would let me tag everything in lightroom and export the picture, tags and all, to flickr. So much better than doing it both places!

Unfortunatly, you can group me with the people getting the ‘Bad Upload: Empty Response’ error. Running the Beta2 on Windows XP SP2. For me, I can only upload a single picture at a time. Settings: Photos all in RAW, convert to JPEG/sRGB, Sharpen at low for glossy paper, Write Keywords as Lightroom Hierarchy, and save image files to disk after upload, and I’ve enabled both debugging options.

The files don’t get saved to the disk. That isn’t a big deal; I was doing that to keep track of what shots got uploaded in batches. But, since I’m doing one at a time, no need for the extra export.

Hope some of that helps.

— comment by Chris on June 25th, 2008 at 10:24pm JST (16 years ago) comment permalink

This plugin is amazing! I use it all the time. Is there any way to have the plugin wait until any in-progress uploads are finished before starting? It takes me awhile to upload to Flickr and when I have two uploads running simultaneously the photos get out of order in my photostream. If there’s any way to do this it would be awesome! Thanks for this great plugin!

— comment by mangtronix on June 26th, 2008 at 11:02am JST (16 years ago) comment permalink


Really good plugin.
Except that since the last update, I can’t export anymore to flickr… the plugin detect there’s an update version X.XXXXX, so I came and installed it… but it still detect it and so I can’t export. I dunno if it’s because of the update detected.
tried to reload LR but nothing changed. Uncheked auto detect updates but idem.

please help?

(sorry for my english, i’m french)

— comment by minipez on June 27th, 2008 at 5:35pm JST (16 years ago) comment permalink

Thanks so much .. you are a complete gem!

I’ve been loving this for some months now and recently added the LR/mogrify which has been incredibly useful not to mention the time & effort I save in not having to go to PS just to add a watermark (how dumb to leave that out Adobe!!!)

… anyway, I have just tried to use a droplet with the ‘run any command’ piglet and it appears to run & complete and then proceeds to complete the mogrify command but when it gets uploaded to Flickr there is no result from the droplet, only the mogrify result. If I run the droplet standalone it works fine so something is getting lost in the process of exporting. I have tried turning off the mogrify and running just the ‘run any command’ but still no results. It seems to complete the droplet action but then overwrites it again in the next stage of exporting. I’ve tried changing the order too but still no luck.

Any suggestions?

LR does offer basic watermarking during export. I don’t use droplets (I’m not even sure what they are), but I know others have gotten them to work with the Run Any Command piglet…. —Jeffrey

— comment by Cindy on June 27th, 2008 at 8:39pm JST (16 years ago) comment permalink

I love the concept behind the plugin and it’s proving to be a very useful tool for me, I wish I had found it sooner. Unfortunately I’m having a major stumbling block with it and I can’t seem to work out what the issue is. I use it on a Mac and it installed and loaded just fine, but when I start the export and have the upload running if I try to upload a lot of photos, it freaks out and times out, so now I’m attempting to do it in small batches which gets me a little further each time, but in the end still ends up timing out, is there a solution I’m missing to this problem?

— comment by Jonathan on June 29th, 2008 at 1:12am JST (16 years ago) comment permalink

If you are getting an error – with “check now” with
“Internal Plugin Error
Reply from the version server not understood:
The requested URL /LightroomPlugins/v/2.0 Beta/flickr was not found on this server.

The solution I found is to make sure that the “Add to Photoset” section says “don’t add to a photoset”. Somehow the adding to photoset from the plugin does not work properly.

— comment by on July 10th, 2008 at 1:25am JST (16 years ago) comment permalink

Thanks so much for this extremely useful plugin. Funny thing is that I was using it to upload my photos and then created my photosets on the Flicrk website. After having done this ten or more times, I realized I could do it directly from the plugin! Flickr (Yahoo!?) owes you some money, as your plugin was what made me ultimately decide to switch to Flickr for my phonots. Thanks again!

— comment by Kamal on July 12th, 2008 at 11:00pm JST (16 years ago) comment permalink

This plugin is excellent! Thanks.

What license is it released under? I’m thinking about tweaking it a little (specifically, adding the replace support that you can’t test) but I don’t know if I’d be allowed to share my changes.

Actually, Flickr did finally get back to me, and gave me a free Pro account. I’ve built the “replace” feature into the Flickr plugin (and into the Zenfolio one) for the LR2.0 version that I’ve been working on for ages, just w a i t i n g for Adobe to release. I’ll release those versions the day LR2.0 is released. —Jeffrey

Update a few hours later:
Ah, what the heck, I just added it to the 1.x version of the plugin, so if you upgrade to 20080714.47 or later, you’ll see the replace option in the Upload Management section. —Jeffrey

— comment by dave glasser on July 14th, 2008 at 6:59pm JST (16 years ago) comment permalink

Well, couldn’t ask for better service! Thanks!

I tested this out, and as I guessed from the Flickr API, when replacing a picture *only* the image itself is changed; changes to title/caption/tags/access control don’t seem to take effect. That’s probably a good thing (since you wouldn’t want to overwrite changes made on Flickr, especially to tags which other users can change). I guess the ideal solution would be to save this flickr metadata when you upload a photo into the database, and when replacing a photo, make API calls to look up that metadata on Flickr; then make calls to change the metadata if it *has* changed in Lightroom but *hasn’t* in Flickr. Or something. But “don’t clobber Flickr changes” is a fine start.

— comment by dave glasser on July 15th, 2008 at 1:43am JST (16 years ago) comment permalink

Character set bug?

If my LR keyword is “«Test»”, then it shoes up in Flickr as “ÇTestÈ”.

Actually, it shoes up as both “«Test»” and “ÇTestÈ”.
– If I edit the «Test» keyword in LR and uncheck “Include on Export”, then Flickr only shows “ÇTestÈ”.
– If I check “Minimize Embedded Metadata” on export, then Flickr only shows “«Test»”. (But then the other metadata is stripped from the file stored on Flickr—not really what I want.)
– (It doesn’t seem to make a difference if I check “Write Keywords as Lightroom Hierarchy”.)

So it looks like Flickr is reading “ÇTestÈ” from the embedded EXIF or XMP.

Any ideas? Is Flickr just broken? Or can your plugin tell it somehow that the EXIF is in UTF-8?
(Thanks for all your hard work!)

— comment by Peter Davis on July 18th, 2008 at 12:24am JST (16 years ago) comment permalink

I really like to integrate uploading to flickr into Lightroom. The plugin functions are excellent!

Actually I get the following error message:
Bad upload: empty response

I’m currently using LR 2.0 BETA / Vista with a flickr pro account. I don’t know if there is a problem with the picture size, but if I decide to resize the image (for example 1000px width) uploading is working properly.
Any ideas? Thanks for your hard work!

— comment by Stephan on July 19th, 2008 at 8:05am JST (16 years ago) comment permalink

As a new user of Flickr and your upload plugin for Lightroom
( LR V 1.4.1 Plugin 20080724.47)
I don’t seem to get the Camera Metadata posted to flickr. It may well be a setting in Flickr I haven’t found or in the Export Plugin.

Any help/suggestions…many thanks

PS. Thanks for the plugin, great time saver….

— comment by Mike on August 6th, 2008 at 1:25am JST (16 years ago) comment permalink

Thank you so much! I have here more than 8500 photos from the Faroe Islands and needed a month or so, to make a first selection and Flickr upload. I was frustrated, how much time this took, forcing me to spend a lot of time just waiting on LR and my browser to operate. I almost resignated.

Today, I accidently found this plugin (just for fun google after “Lightroom Flickr plugin” only to look, if anybody is out there).

Mail me, if you need a German translation of your interface. You know, both Flickr and Lightroom offer German interfaces, and many users are not familar with all the English terms.

— comment by Arne List on August 28th, 2008 at 3:53am JST (15 years, 11 months ago) comment permalink

Thank you so much for releasing such a useful plugin! 😀

— comment by Paulo Sacramento on October 6th, 2008 at 2:43pm JST (15 years, 10 months ago) comment permalink

Jeff, don’t know if you’re still answering questions about users of your plugin for the first version of Lightroom, but in case you are:

I’ve been using the Mac version successfully for some time (great product, by the way). Then Apple advised me to erase my hard drive and re-install everything, due to problems that couldn’t be more easily fixed. I re-installed Lightroom, downloaded your plugin again, installed it as per your instructions (it wouldnt’ automatically install, as you mention in your instructions), and…nothing. Lightroom won’t recognize the plugin.

I’ve deleted it from my system twice, downloaded again and re-installed, to no effect. Any ideas? Thanks! John

Plugin install for LR1 was a much more hands-on approach.. you have to place the plugin folder “flickr-jfriedl.lrplugin” into the specific folder on your system, then restart Lightroom. It should just pick it up. The zip file for the final version of the LR1 plugin has not changed since last summer, so if you had it working once, you should be able to get it again, but as I said, LR1 is sort of finicky. —Jeffrey

— comment by John on February 4th, 2009 at 8:45am JST (15 years, 6 months ago) comment permalink

Thanks, Jeffery. That’s what I did, following your instructions–the module folder for Lightroom in application support/adobe/lightroom/modules.

When I select “Export” in Lightroom, I get four options: custom, burn JPEGs, Export to DNG, and For Email.

The reinstall seems to have given my computer the flu, when it comes to plugins. I’m having some problems with another, too.


— comment by John on February 4th, 2009 at 9:35am JST (15 years, 6 months ago) comment permalink
Leave a comment...

All comments are invisible to others until Jeffrey approves them.

Please mention what part of the world you're writing from, if you don't mind. It's always interesting to see where people are visiting from.

IMPORTANT:I'm mostly retired, so I don't check comments often anymore, sorry.

You can use basic HTML; be sure to close tags properly.

Subscribe without commenting