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

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

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

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.

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

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

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?

Richard

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

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 ???

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.

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

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

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.

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!!

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.

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.

John

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.

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

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

Jeffrey,
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…

Thanks,
– Gyuri

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!

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

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

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 *
——–[Players]
———-[#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

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 😉

Thanks dude, you’re doing good work!

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?

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.

Jeffrey,

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.

Cheers
Ben

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.

Thanks!

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

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 ?

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

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.

Hello
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

thanks
david

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

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!

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

Jeffrey,

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 🙂

Ross

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.

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?

Thanks,
Tim

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

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

-Art

Jeffrey,

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,
Mike

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!

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.

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!

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

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.

ArazPhoto.com

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

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!)

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….

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

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.

John