ps. the latest version is working stable.

I have been a fan of this plug-in for a while, and first of all want to thank you for your work.

I recently upgraded to Vista 64, and have installed LR 2.0 64bit. I installed ver 6.7 of the plug-in, and when I try to export to FLICKR I get the following error: At Line 13871: Assertion Failed(!). I tried going down one version (5.x) and had the same error. This was using the default settings.

NOTE: I as able to get this to work by configuring the following settings:
- Sharpening: OFF (Note: I turned this back on and can still upload)
- Upload to your flickr photoset: …Don’t add to photoset… (Note: this was blank, so I just chose something)

I don’t have any photosets on Flickr, and wonder if its related to this setting.

I have one question and one comment about your plugin.
But first of all, thank you for all your work, you did a super job !

My question is: is this plugin compatible with Lightroom 2? Do you know if we can encounter any limitations / problems by using it?

Its results should work fine in Lightroom 2, but there are a bunch of new things I should add to it that are new in 2.0. Sigh, my todo list is just way too long…

My comment: you said you replaced “Jog identifier” by “Blog URL”. I don’t find this solution really clean, because you are changing the semantic of an element defined by the IPTC-standard which says:
“job id: Identifier for the purpose of improved workflow handling. This ID should be added by the creator or provider for transmission and routing purposes only and should have no significance for archiving.”
I know that all tool-vendors like Adobe aren’t always following 100% from these standards, but when they are I find important to keep the original semantic of the implemented elements.

When it comes down to it, you’re right. I know it’s fine for me (in my own little world where I don’t need to interact with anyone else, IPTC-wise) to hijack the fields for my own random uses, but it’s a slippery slope. I’ll put a footnote there referencing this comment, so that others at least know that I’m choosing to do something explicitly outside the design of that field. —Jeffrey

Thank you!
Etienne

Also I tested .8, and based on the few test exports with various combinations of metadata it now appears to work ok. Big thanks.

Regards,
/KPa

I will second the suggestion that Enver put in about the tags, that would be really great.

Wonderful application you have here, many thanks!!
John

I’m not, sorry. I somehow expect that they wouldn’t want to provide a developer’s account for me to do it with… —Jeffrey

After the total upload:
One photo was double uploaded and the photo was not in a set.
I have seen this problem in many upload application’s.
Is it possible to build in some kind of verification in the the future releases?

Hopefully, crashes (and hence, this issue) are few and far between. The problem is that the crash apparently happened between a successful upload and the notation of it being successfully written to the database. There are perhaps ways to guard against this, but it doesn’t seem worthwhile to spend the energy on that kind of edge case… —Jeffrey

Hmmm, it should be possible. Added to the to-do list. —Jeffrey