flickr-20100209.156.zip
· Version History
· Update Log via RSS
· Installation instructions
· “Donationware” Registration Info
· More Lightroom Goodies
· All-Plugin Update Log via RSS
· My Photo-Tech Posts
· My Blog
This Export-to-Flickr plugin has been completely rewritten for Lightroom 2.0 and later, and is not compatible with Lightroom 1.
Please see the known issues before reporting bugs. If this is your first look at my export plugins, please see the announcement post for an overview and some important information.
(See the old plugin page for a version compatible with Lightroom 1.x)
Availability
This plugin is distributed as “donationware”. I wrote it and make it available for free — everyone can use it forever, without cost of any kind — but unless registered, its functionality is somewhat reduced after six weeks. Registration costs the minimum 1-cent PayPal fee; any additional donation you'd like to make in encouragement or thanks is optional and completely up to you. For details, see my blog post titled Lightroom Plugin Development: Now With Added Encouragement.
Lightroom 3 — Registrations in Lightroom 2.x will not carry over to Lightroom 3 when it is released, so plan that you'll have to re-register if you upgrade to Lightroom 3. (That's for the real Lightroom 3.... registration is not required in the Lightroom 3 Public Beta, but be warned that plugin support is spotty and plugins may not work well there.)
( Update Log via RSS )| 20100209.156 | Changed the semantics of the Places filter (in the tokens understood by the preset templates of my plugins) in two ways: if applied to a string value rather than a number, it works on the first number found in the string. Another is that you can now use something like Places=-1 to round to the 10s, Places=-2 to round to the 100s, etc. |
| 20100208.155 | Title/Description presets weren't getting saved across LR restarts in some cases (for definitions of "some" meaning "all", sorry). |
| 20100205.154 | Oops, the upload date/time custom metadata items were swapped. Doh! With this new version, each catalog will auto-update to correct the issue the first time it's loaded. The format used for the date and time are restricted in LR2 to whatever I've chosen, but the first time you load the plugin in the real LR3 (whenever it comes out), the catalog will update itself again to write the dates/times in your user-customized, localized format. Fixed the {GPSAltitude} template token so that it should now actually work. |
| 20100203.153 | Lots of updates to the Twitter support:
|
| 20100125.152 | Caught a few more LR3b issues. |
| 20100124.151 | Reverted some changes in the logging code that seems to be causing “attempt to index upvalue ‘?’ (a boolean value)” errors for some. As far as I can tell from looking at the code, it's one of those "can't be happening" types of things, so I'm sorta' stumped as to why it's happening. Also fixed (maybe) an esoteric bug realted to the "associate images" feature. |
| 20100123.150 | Fixed an assert while resyncing to Flickr. Added the ability to control whether to send a Twitter tweet with photo keywords. |
| 20100121.149 | Fixed the "posted date" stuff added in v134 that got broken some time in between. |
| 20100121.148 | Completely changed how the one-click upgrade applies the newly-downloaded zip file, in the hopes that it'll work for more people. Rather than unzipping over the old copy, it now unzips to a temporary folder, then moves the old folder out of the way and the new folder into place. Prior versions' folders are now maintained (with the version number in the folder) in case you want to revert a version; you may want to clear them out from time to time. Of course, it won't take affect until you try to upgrade after having upgraded to or beyond this version. |
| 20100118.147 | Added two new template tokens, {DaysSince} and {PhotoDaysSince}. They're a bit tricky, but could be useful. |
| 20091230.146 | Added a "Repopulate URLs" button to the Plugin Extras dialog, to allow correcting for the bug fixed in the previous push, and to correct for photos uploaded with old versions of the plugin. |
| 20091230.145 | Sigh, it seems 30,000+ lines of code are getting to be hard to keep track of, and I unintentially removed the exported url from the custom metadata (from the 'At Flickr' item) a few versions back. This should fix it, at least for images uploaded from now. |
| 20091229.144 | Figured out a way around a Flickr bug that causes "sort'a large" sets of keywords to disappear on upload. Fixed a problem with refreshing metadata in LR3b. Added some tentative support for Flickr machine tags. Machine tags seem to be a total mess, as one might expect when there's no standardized format published for even the most common things. We'll see how it goes. A lot of keyword-related stuff was changed this time, and Flickr has a lot of keyword-related bugs to work around, so watch out for any new bugs that might have been introduced on my side this time. |
| 20091223.143 | Fixed a template-related bug introduced in v138 that caused <br> tags to be stripped form HTML titles and descriptions. |
| 20091222.142 | Fixed some issues with the metadata resend (in the Plugin-Extras dialog) when images had been exported to multiple Flickr accounts. |
| 20091221.141 | Reallow TIFF uploads. Not sure how it got disallowed. |
| 20091216.140 | Figured out when the "AgExportSession.photoExportSequence is obsolete; use photoIdExportSequence instead" error was coming from. A bug in LR3 beta. I had to disable the export filter for the beta to avoid this. |
| 20091215.139 | Allow changing the font size of list of upload destinations. Those with long names might want to choose a smaller size to allow more text to fit on each row. |
| 20091214.138 | Added the special {NOJOINERS} token to the Template Language understood by my plugins. |
| 20091209.137 | A few small fixes for LR3b, and tweaks to the extra-keywords stuff do tidy up repeated keywords in the display. Also, it seems that although I added export-dialog options for keyword-based inclusion/exclusion for Flickr public search, I never actually got around to implementing it. Doh! I realized the problem only after I ran into an email in my queue from May reporting it (thanks Konstantin).... just shows how far behind I am on email )-:. I think I've fixed it, but I don't actually see that there's a way to confirm on Flickr whether an image is/isn't part of image search, so I haven't really been able to test. |
| 20091205.136 | Minor internal debugging tweaks. |
| 20091130.135 | Keyword processing for the various keyword-related upload options stripped leading/trailing hyphens in error.... now fixed. |
| 20091125.134 | Added a field to enter the 'posted date', so you can pick any date between when you joined Flick and the current time. |
| 20091118.133 | Added an {Altitude} item to the templates understood by the plugin. It's the numeric altitude in meters, as opposed to the {GPSAltitude} item which is a description of the altitude along the lines of “32.7 m”. Also updated the Places filter so that it can be used on fields that merely begin with a number. |
| 20091116.132 | Added the ability to set the Flickr "posted date" during upload. It defaults to the normal default (the date actually posted), but now you can select the date of last edit in LR, or the date the photo was taken. Attempting to set a date prior to when your Flickr account was created results in it being ignored, and so the posted date for those photos remains at the current date. |
| 20091115.131 | Fixed a bug that would have prevented resending image metadata (via the Plugin Extras menu). |
| 20091115.130 | Fixed a problem with location data and Flickr permissions. Flickr doesn't allow the plugin to send latitude/longitude location info with the photos until the Flickr account owner has set a default privacy level for location data, so the plugin checks the status, and doesn't offer the "send location data" option until the user has made a privacy selection at Flickr. However, until today's version, the plugin did not properly respond when the plugin was later used with a different account that had not yet had a privacy selection made. Now it notices the situation and resets things. This is a bit sloppy (the plugin should really pay attention to the settings on a per-account basis), but not worth fixing at this point, it's only a problem the first time when used with a new account (and only when that account has no default geo-privacy setting). |
| 20091027.129 | Added the ability to set photo licenses, and to set groups via keywords. (One little sentence makes it seems so trivial, but there are lots of details and it took all day to code up. I don't have a lot of Flickr Groups experiences, so take care at first to make sure it's working properly, and if it's not, report by sending a log along with details, via the "Send to Jeffrey" button in the plugin manager.) |
| 20091023.128 | A bunch of UI fixes for LR3b, such as fixing the scrollbar and the token-examples dialog. |
| 20091022.127 | Added a first draft of some rudimentary support for Lightroom 3 Beta. See this important note about plugin support in Lightroom 3 Beta and Lightroom 3, including future plans for features and my registration system. |
| 20091013.126 | After some offline projects and a really nasty cold, I'm getting back into the swing of things.
This update contains a fix for a bug that prevented more than 400 groups from showing in the
"Flickr: Group Pools" section. (Yes, some people are members of more than 400 groups!).
Also, some UI tweaks to highlight that multiple sets can be selected, and that if "Replace" is chosen, the selected set(s) apply only to newly-uploaded images. |
| 20090916.125 | Some UI tweaks earlier in the month had an unintended side effect of breaking the "choose destination at export time" feature. Sorry... fixed! |
| 20090915.124 | Fixed some keyword-related issues. First, due to a silly bug on my part, there had been an artificial limit on the number of keywords sent. Second, also due to a bug on my part, the keyword order was scrambled. The plugin now sends them in the order Lightroom provides them (which seems to be alphabetic). (Sorry to everyone who couldn't contact my server for the last few days... it had "issues", that are now fixed.) |
| 20090904.123 | I'm back from a long trip and starting up the plugin machinery again. Getting back into the game gingerly, this version adds one simple feature to the Twitter section, a special <slideshow> tag that's comparable to <url> except that it goes directly to the set's slideshow (and is empty when the upload was not to a set). |
| 20090725.122 | Big change with Geoencoding. I noticed that Flickr had added some geoencoding-related calls to the API that would let me get rid of some ugly "make sure you check this option at Flickr..." sections of the dialog, but what I thought would be a short bit of cleanup turned into a colossal endeavor. The whole geoencoding setup at Flickr is pretty simple for any one person, but to take every permutation of every possibility into account.... there are a lot of geoencoding-metadata-related dials that can be twiddled at Flickr and in Lightroom.... it just got really complicated, really quickly. I've moved the geoencoding options into their own section, "Flickr: Geoencoding". I try to make it useful even if you disable the geoencoding stuff, by warning you if an embedded image might contain location information that will become available to Flickr viewers. Most people want the location info available, but if you don't, I figure you'd want to be warned. There are new options that you should check; rebuild export presets if need be. In particular, the "default geo privacy" setting at Flickr is no longer relevant; you now set the geo privacy yourself in the export dialog. It's been a big change, and there are likely bugs. Please let me know via email or by sending a plugin log (via the "Send to Jeffrey" button in the upper-right of the Plugin Manager). |
| 20090716.121 | Sigh, Twitter engineers treat developers like a bunch of twits. Twitter just made a sudden, unannounced, undocumented change to how they allow external applications like this plugin to connect to Twitter, breaking every external application out there. If a plugin follows the Twitter documentation, it will not work. I couldn't believe Twitter engineers could be so inexperienced or hostile (which?) the first time they pulled a stunt like this, but again? This is ridiculous... do they have children running the shop over there? If they do this again, I may just yank Twitter support from the plugins... it's not worth the frustration. For the time being, this push should fix things. |
| 20090715.120 | Fixed the url that I over-tided two days ago. Sorry.... Must. Engage. Brain. |
| 20090713.119 | Add an option to the group-pool dialog to indicate how to handle when you've reached the upload limit for a group pool. |
| 20090713.118 | Tidied up the photoset-url sent when Twittering. It worked, but had a superfluous slash. Fixed the comment-as-html stuff to allow entities. |
| 20090705.117 | Added colon as a joining character for the squelching stuff mentioned in the previous release. Fixed the "attempt to get length of a nil value" error some might have gotten when having Internet-connection issues. |
| 20090702.116 | Following up on the fix in the previous version, the plugin now handles broken accented characters in Flickr tags derived from the image city/state/country. Completely rewrote how the “extra tags to send...” line is parsed. It could sometimes be a bit wonky, especially when template tokens were used, but hopefully it's more solid now. (Hopefully I didn't just move the bugs around; it's a touchy area of code.) Speaking of the template tokens, I added a bunch more somewhat esoteric things, filling out all the metadata items available to the plugin. Something like “Workflow Job Identifier” might not be all that useful, but if you repurpose a field with my metadata-viewer preset builder plugin, these otherwise esoteric items may prove to be useful. For example, I've relabeled the Job Identifier field as “Blog Url” in my custom view, and can now use the {JobIdentifier} token to refer to it. I redid all the code on squelching joining characters to make more sense (I hope), and included <br> and friends (e.g. <br/>) as special joining characters that should magically do the right thing. I haven't gotten a chance to update the Templates page with these changes, but I will soon. (If you find something that doesn't seem to work, let me know with specific examples.) Enhanced the one-click upgrade stuff quite a bit, now detecting ahead of time when it will fail because the plugin is installed where Lightroom can't write (if Lightroom can't write to it, it can't update itself). I also added a progress bar, and now download in smaller chunks to avoid 'out of memory' errors on the larger plugins. Do remember that this new functionality becomes available after you upgrade to or past this version, when you then upgrade with it. |
| 20090630.115 | Finally figured out the problem that some users reported with respect to tags showing up twice on Flickr, once properly and once with '?' where some accented characters should have been. Turns out to be a bug in the Mac version of Lightroom. The plugin now look for, and forcefully removes, such tags after the initial upload to Flickr. This is an imperfect solution because it still leaves the broken tags in the original file, so until Adobe fixes this bug (doubtful before LR3), you might consider using my Metadata Wrangler plugin to remove the IPTC block upon upload, which is where Lightroom is writing the broken tags. Fixed that during an upload of a single image, the progress-bar status didn't reflect when the image was being uploaded (it said "rendering..." the whole time). Added a defensive error check: try to detect some of the weird error messages that the OS returns when a firewall blocks Lightroom from using the Internet. You'd be shocked to hear how much time I spend telling people "check your firewall and enable an exception for Lightroom...". Hopefully this'll stem that stream. |
| 20090617.114 | Yikes, it turns out that if you launched an export and then, while it was going on, visited
the export dialog again, changes to the set of groups to upload to actually applied to the
export that was already in progress! Turns out that there was a detail about how Lightroom's
plugin architecture worked that I hadn't know that, well, let's just say that I do now. 
|
| 20090616.113 | Sigh, this upload-destination fiasco is a real pain. Maybe have it nailed down this time. |
| 20090615.112 | Some people are still having images uploaded to the wrong album, and I'm starting to think that it's a case of corrupt Lightroom preferences. I've looked at some logs and it seems to be a case of "this can't possibly happen" happening. I've added something in this version that kills some old information with prejudice.... if this doesn't take care of it, please send a log again (via the "Send to Jeffrey" button in the upper-right of the plugin manager), but I suspect my reply will be to ask you to blast your LR preferences file and start over. |
| 20090614.111 | Sigh, it turns out that a few days ago, Twitter suddenly changed authentication methods in a way that was guaranteed to break every strong-authentication application (such as this plugin). Sigh. This update handles the new authentication style, and includes better error reporting for the next time they pull a stunt like this. |
| 20090613.110 | Better error reporting if the plugin wasn't able to contact Twitter during authentication. |
| 20090607.109 | Added some detail ("X of Y...") to the progress bar shown while resending metadata to Flickr |
| 20090605.108 | Two bug fixes... fixed progress bar during upload, and fixed an "Access to undefined global" error that popped up when trying to clear uploaded-to-Flickr data via the Flickr-Extras menu. |
| 20090604.107 | Oops, it looks like I neglected to test how the previous change would impact someone installing the plugin for the first time (answer: not well). Fixed. |
| 20090603.106 | Added a couple of new custom metadata fields, "Flickr Upload Date", and "Upload Time". The former can be used in the Library Grid Filter to sort/select/filter by the date you uploaded to Flickr. Because the new custom fields mean a change to the database, the first time you load this new version, Lightroom will pop up a dialog asking "Update catalog for plug-in?" to which you'll want to answer yes ("Update"). I'll add these to my Metadata-Viewer Preset Editor plugin soon, but for those maintaining their own viewer tagsets, these can be found at info.regex.lightroom.export.flickr2.uploadDate and ....uploadTime. |
| 20090603.105 | The <dest> token in the new Twitter stuff didn't work properly when a new photoset was being created as part of the upload. Works now. Also fixed photoset names with ampersands in them, which saw the ampersands doubled when uploaded from a Windows box. |
| 20090602.104 | Sigh, small bug fix for the new <home> stuff. |
| 20090602.103 | Added a <home> token to the Twitter tweet template, to refer to our home page at Flickr. Also fixed the default tweet template, which wasn't showing up automatically. |
| 20090601.102 | Well, here's something new: Twitter support. It may be a bit iffy, mostly because I don't use Twitter myself, so perhaps I've missed something about the culture in which it's used, but I've added something that allows you to send a tweet after a successful upload, with a mini template language that allows you to include a photo url or destination-set url in the tweet. The plugin uses Twitter's new strong secure authentication, so you don't even have to tell the plugin your username or password. Similar to how it works when you "Authenticate at Flickr", you authenticate at Twitter and grant the plugin application permission to send tweets on your behalf. A note to fellow developers, who will feel my pain: in order to get this strong-secure authentication support working, I had to code up SHA-1 Secure Hash computation from scratch, in pure Lua... a horrid language, I'll remind you, that has absolutely no bitwise operations, or even integer support. No masks, no bitwise xors, no way to test bits or shift words or any of that stuff. As I coded it, I felt as if I were chiseling NAND gates from rough blocks of silicon. I felt quite the achievement once I got it working, but only then realized that I also need to code up my own HMAC-SHA1 secure signature routine. It's less involved than the original SHA-1 stuff, but again, filled with bytewise xors. Fun stuff, in a very old-school way. |
| 20090521.101 | Sorry, another quick bugfix. It seems an internal change I made to try to get around a bug in Lightroom wasn't quite ready for prime time. Hope it is now. |
| 20090521.100 | The 100th push for the LR2 version of this plugin. It seems that the move to multiple sets a couple of versions ago tickled a bug in Lightroom that caused some export presets to become corrupt (those saved while "don't add to a photoset" was selected). Once corrupted, those presets wouldn't even show up in the list the next time you started Lightroom. I've reported the bug to Adobe, and built a workaround in this version that should hopefully take care of things. It won't resurrect the presets that had problems, but you should now be able to rebuild/resave them. You can now use the scroll wheel with the scrollable lists (such as those for sets and groups)... sort of. It works while the mouse is actually hovering over the scroll bar. That's the best I can figure out so far... it's better than nothing if you're a scroll-wheel user. Added some new token filters to the preset templates used for things like extra keywords and image captions: They're listed in the docs, but include new items like UCFirst capitalize first character of the item, or LC to lower-case the entire item. For example, if you want to include the city as an extra tag, but prefer your tags to be all lower case, you might use {City:LC} in the extra-tag dialog. |
| 20090518.99 | Somewhere along the way the plugin stopped updating the progress bar as it worked. I've restored it, so now you can see it inch along as the uploads complete. I also included some stuff to communicate with the next version of my Metadata Wrangler plugin help coordinate a canceled export. Unfortunately, if you cancel an export, Lightroom does not tell filters like the Metadata Wrangler, so it blindly continues trying to process images that will not show up. I've added some hooks here to help the next version of the Metadata Wrangler detect a canceled export and not complain. It's imperfect, but I'm hoping it'll help. |
| 20090514.98 | With this version you can now select multiple photosets to upload images to. Multiple selection is available only if you use the scrollable-list format for the list of photosets in the "Flickr: Upload Destination" section of the Export Dialog. If you see a popup list, click on "configure list appearance" and choose one of the scrollable lists, then close and reopen the dialog to effect the change. When the list view is shown, Control-click to add/remove items from the selection. Some items, such as "don't add to a photoset", can't mix with others. Click on the "currently selected:" line to scroll the selected item into view, or, if more than one item is selected, scroll into view the next one not currently visible. The selected group of photosets is encompassed in an export preset (along with all other settings). If you enable "visit destination photoset after upload" and the plugin ends up sending to more than one photoset, the pages of only two are opened in your browser. I'm not really sure what would be most useful here, so I just picked two for now. Let me know if you have ideas on what would be most useful. Adding support for multiple photosets has been on the to-do list for a long time, but it's taken this long to get it done because it was a huge effort. I know it sounds easy... "just allow more items to be selected... how hard can it be?", but the concept of THE upload destination was well and truly ingrained throughout almost every thread and fiber of the code base. Not only that, but the code base is shared with my four other "export to..." plugins, so I had to accommodate the needs of all of them when making this big change. This version also contains a fix for the update-metadata feature added a couple of versions ago, which died in some cases with "geo-removeLocation failed" in some cases. By the way, while testing this, I noticed that Flickr now has collections. (I don't use Flickr except for testing the plugin, so I'm slow to notice new features.) I like the hierarchical nature of it — I use hierarchical collections to back up my photos on another site — but the 5-deep limit seems troublesome. Still, I can imagine, now that I also know a photo can be in more than one set, to automatically create a per-date set, and automatically put that set into a date-based collection hierarchy. For example, a photo taken today would be placed in a "2009-05-14" set within an "05" collection within a "2009" collection within an "all photos by date" collection. Off the top of my head this seems like it would be useful... comments? |
| 20090510.97 | Added a link in the Plugin Manager to the plugin's update-log RSS feed. Fixed a typo in a dialog introduced in yesterday's push. |
| 20090509.96 | Added the ability to resend more metadata: GPS data, image title, and image caption. This is in addition to the ability to resend tags that was there before. See "Resend Metadata" in the "File > Plugin Extras > Flickr Extras" dialog. |
| 20090509.95 | Added items to the title/description presets: ZenfolioUrl, SmugMugUrl, and PicasawebUrl. If you have previously uploaded this image to one of those sites with my plugin that uploads to those sites, you can refer to that copy of the image by reference. Using the tag alone, e.g. {ZenfolioUrl}, it becomes the raw url, or nothing if the image wasn't previously uploaded. Using a =text argument inside the tag turns it into a link with the given text, e.g.
See the {ZenfolioUrl=photo at Zenfolio}.
becomes:
See the <a href='...'>photo at Zenfolio</a>.
if the url is known. If the url is not known, the tag is replaced with nothingness, so you might want to include an "|..." fallback section, such as:
See the {ZenfolioUrl=photo at Zenfolio|"photo at <a href='http://myname.zenfolio.com'>my Zenfolio site</a>"}.
The entire double-quoted part after the "|" is used when what comes before ends up being empty. In this case, that double-quoted part is some text that includes a link to a Zenfolio user's home page (you'd want to put yours, of course). So, if the url isn't known, the entry becomes
See the photo at <a href='http://myname.zenfolio.com'>my Zenfolio site</a>.
|
| 20090429.94 | Fixed a bug that could potentially crashed the plugin while editing caption/title and auto-destination presets. |
| 20090425.93 | Tweaked how the plugin tries to update itself during the one-click upgrade process, to hopefully get things working for those few Windows users that have never had it work. Crossing fingers. We'll see. |
| 20090422.92 | Fixed the caption preset stuff to disallow editing of the built-in caption presets, and added a note to that effect in the preset editor. I also reset the 'None' preset to an empty value, just in case it had gotten edited in a prior version of the plugin. Sorry it took so long to get around to this fix. |
| 20090422.91 | A few minor housekeeping updates: the 'enable enhanced debugging' checkbox in the Plugin Manager now turns on logging of all web traffic. It'll be useful if I ask you to send a log, but you probably want to leave it turned off during general use. I also added an icon to the registration page to reinforce what plugin is being registered. |
| 20090417.90 | The new group pool stuff added in .78 popups up a dialog warning you to resave export presets if you have them, but it turns out that I didn't handle some cases that might arise if the user didn't update presets. Such cases caused a plugin crash prior to this, but now should work nicely. |
| 20090403.89 | Corrected the photo-date related items in the preset templates to properly use the dateTimeOriginal metadata field, rather than the edit-time dateTime field. It now uses the first of the following that it finds with a value: dateTimeOriginal, dateTimeDigitized, and dateTime. This bug was reported to me long ago, but I let it slip through the cracks, sorry. Added scroll-one-line arrows to the top and bottom of the scrollbars, to allow fine-grained control of
scrolling very long lists. (I've been programming for almost 30 years, but this is the first time I've
ever built a graphical scrolling system from scratch, so I may be a bit slow on the uptake at times |
| 20090324.88 | Big UI changes in some areas. I've cobbled together a way to add what appears to be a real scrollbar, so I've replaced the kludgey scrolling solution I had before. It seems to work okay. I also changed the "Token Examples" dialog from paging to use the new scroll stuff. Added {OnlineID} to the list of tags understood for the image description. This allows you to create a preset along the lines of: <a href="http://BigHugeLabs.com/flickr/onblack.php?id={OnlineID}&size=large">View on Black</a>
which creates a result at Flickr like this, which then includes a link with this result. |
| 20090319.87 | Finally getting going again after a nasty cold. In this update, I added a way to configure the size of the group-pool list, so those with a lot of groups who don't like scrolling can see more at once. I also added a "clear selections after export" option to the group-pool section, to reset the list of chosen groups to none, so that you have a clear list the next time you export. If you have export presets, it might make sense to resave them after enabling this option so that exporting with a preset doesn't leave the export dialog with pools chosen (which might be surprising when you come back a week later and forget to clear it out manually). To resave presets, enter the Export Dialog, choose your preset from the left, click the checkbox to turn on this option, then right-click (cmd-click) the preset name and choose "Update with Current Settings". |
| 20090313.86 | It seems that PayPal doesn't give everyone a "Unique Transaction ID" in the registration confirmation mail; some people get a "Receipt Number". So, the registration dialog now accepts that as well. I also removed the "Resolution value to record in metadata" control in the Metadata Management section. That had dated back to a time when the resolution setting was not available in the standard "Image Sizing" section of the export dialog, and I forgot to remove my custom one when the standard setting appeared. It was sort of silly having two controls for the same thing, sorry. The resolution setting is still utterly meaningless unless you use it to actually compute the pixel size of the image (that is, if you have the "resize to" setting to something other than "pixels"). Once the image has been created, it's just a hint about how you intend it to be rendered when printed, but it has exactly zero impact on the quality that can or can't be achieved when printing. |
| 20090312.85 | After adding the multi-user login stuff last month, I hadn't noticed how dorked the "Logged in as..." message at the top of the dialog had become, especially when you had only one login on record. Really sloppy, sorry. Someone pointed it out (thanks!), and I went in and cleaned it up. I also removed the "Resolution value to record in metadata" control in the Metadata Management section. That had dated back to a time when the resolution setting was not available in the standard "Image Sizing" section of the export dialog, and I forgot to remove my custom one when the standard setting appeared. It was sort of silly having two controls for the same thing, sorry. The resolution setting is still utterly meaningless unless you use it to actually compute the pixel size of the image (that is, if you have the "resize to" setting to something other than "pixels"). Once the image has been created, it's just a hint about how you intend it to be rendered when printed, but it has exactly zero impact on the quality that can or can't be achieved when printing. |
| 20090310.84 | I've added a popup dialog that appears the first time you install this plugin that explains how to activate it from the Export Dialog. It's currently not very “discoverable” (in UI lingo), and it leaves a lot of people befuddled. I hope this helps to stem the flow of “I can't get it to work” messages I get each day. I've begged Adobe to tweak the UI to make it more clear in the future. |
| 20090309.83 | Yikes, very embarrassing.... I left some debugging code in *.82 that helped me understand the keywording issues, but at the same time aborted the export (because I didn't want to actually export while debugging). I've got a horrible cold and I guess I shouldn't be coding while my brain is frying with a high fever. Sorry! |
| 20090307.82 | There is either a bug in Lightroom or in my understanding of how keywords work, that caused the set-via-keyword features (image visibility, safety level, etc.) to fail in some situations where the keywords in question were part of a hierarchical structure. If it's a LR bug, I've worked around it, and if it's a bug in my understanding, I now do it the right way. In either case, it should now cause no surprises. |
| 20090306.81 | Fixed a bug that caused a plugin crash if an auto-destination was used that calculated to an empty result for an exported photo. I added an option to allow an empty result to mean "don't add to a photo set", and if that option is not checked, throw an error that's actually readable by a human. This version also contains a big internal change that should have, I hope, have no impact except for faster load times. |
| 20090305.80 | Fixed a bug that caused the plugin to crash (and stay crashed across Lightroom restarts, even!) when deleting the caption preset that was actually chosen for the caption. |
| 20090304.79 | Change in the Group Pools stuff to allow multiple selections. Also, the selections are remembered on a per-username basis. NOTE: one byproduct of this change is that you'll have to resave any export presets you made earlier, at least if they have a group pool set. |
| 20090303.78 | If there's an error calculating the automatic destination for a photo, now actually reports that error instead of just crashing |
| 20090302.77 | Fixed a bug that could cause the plugin to crash when using the File > Plugin Extras |
| 20090228.76 | Realized that Flickr's "Description" can actually be HTML, so added a switch for you to indicate whether your comments are text or HTML. Also have it interpret <br> and <br/> as line breaks. Also fixed a bug that caused a plugin crash if my server couldn't be reached during registration. |
| 20090223.75 | Tweaked the multi-user login stuff a bit. It was working for everyone, but some users might have gotten a confusing presentation when not authenticated to any Flickr account. I also made the "click here to authenticate at Flickr" dialog a bit more verbose to explain that if you're already logged into Flickr in your default browser, the authentication will immediately use it. The point is that if you wish to authenticate as a different user, you must first log out in your browser, then continue with plugin authentication. |
| 20090221.74 | NOTE: you may need to restart Lightroom after installing to this (or a later) version from the previous (or an earlier) version. Please try a restart if you get an error the first time you try to use the plugin. As per the ongoing discussion on my blog, with this version this plugin moves over to
a "donationware" model, in which the plugin remains free, but registration eventually becomes
required (and an eventual donation hoped for For details, see Lightroom Plugin Development: Now With Added Encouragement. (For info about what drove this decision, see What To Do When a Hobby Becomes Work?) The plugin no longer expires, and correspondingly, I will not pay much attention to reports of bugs that have already been fixed, so please check your version and the version history before submitting bugs or feature requests. There was a lot of internal upheaval in the code, so I expect that some boo-boos my surface. If something breaks for you with this version, please let me know, but until I fix it, feel free to revert to the previous version. Several fixes and enhancements in this release: It can now track multiple Flickr authorizations, and you can easily switch between and among them. There have been a lot of UI tweaks to make things look more natural (but Lightroom's plugin infrastructure still places great restrictions on what can be done, so it's not like it's smoothly polished yet). It now has more robust error reporting in the face of network problems. |
| 20090131.73 | The whole "newlines in image descriptions" thing is a big can of worms that I need to address properly sometime. It's a hassle for a number of reasons, not the least including that Lightroom doesn't allow newlines to be entered in a text-edit boxes, and that the policies are different among all the various photo sites that I write plugins for (and that the code is shared among them on my side, and that the presets are shared among them on the user's side). But anyway, in response to a bug report, I've made it so that you can at least cut-n-paste a newline into a Description preset (Flickr doesn't seem to recognize newlines in Titles). I've got a headache just thinking about it, but we'll see how this goes... (By the way, happy birthday, Dad.) |
| 20090129.72 | Added a way to hide the Flickr/Geoencoding warning stuff, so that you can get it out of your face if you know you've already dealt with it. |
| 20090129.71 | Small housekeeping update for the new locales supported by Lightroom 2.3. Added more info to the debugging log when an export operation begins, to help diagnose any subsequent problems with the export. |
| 20090126.70 | The new scrollable-list stuff didn't deal with ampersands very well... things should be better now. Also added tooltips to the list items so that the full text can be read even if the display is cut short, although ampersands may appear in duplicate (or quadruplicate, depending on the OS)... it just wasn't worth the effort to get ampersands right in the tooltip. |
| 20090126.69 | Fixed a few spelling mistakes, and tweaked the debugging-log stuff to help debug keyword problems. |
| 20090119.68 | Okay, so I spent the entire weekend working on my own scrollable-list control from scratch, because the built-in popup menu is just not very easy to work with when one has a lot of galleries. I didn't have much to work with, and the result is a bit wonky, but it's much more usable when the list is long, so I'm throwing it out there. If you don't have a long list of export destinations, you can revert back to the original via the "configure list appearance" button. With that button you can also change how much of the list is shown at once, to suit your personal preference. Removed the "Flickr: Tools" section, since it was empty. I have no idea how I didn't catch that earlier. |
| 20090116.67 | It turns out that the automatic upgrade stuff doesn't work if the plugin folder has been renamed from its original. That should generally not happen, but it's possible, so the plugin now checks its own location reports the issue to the user if it finds it. |
| 20090115.66 | Added more debugging-log stuff to the 'Upgrade Now' button action, to try to understand why it doesn't work for some people. |
| 20090115.65 | Added a 'click here to change the export destination' note to the masthead image, because some new users are confused how to change export destinations. |
| 20090110.64 | Added a checkbox in the Plugin Manager to turn on enhanced debugging (more stuff in the plugin's debugging log), and added a button in the same place that sends your log to me. Particularly for “the upgrade button doesn't work” and “error while uploading” type issues, this should be useful for debugging. |
| 20081228.63 | My preset dialog (for caption presets) was a bit wonky and didn't update itself when a preset was added. Fixed that. Also, in the export dialog proper, the example text next to the preset dropdown didn't auto-expand as the preset was changed. Fixed that, too. |
| 20081224.62 | The "Extras" item in the File menu had stopped working. Works now. |
| 20081223.61 | Bumping back the expiration date. |
| 20081209.60 | Added more to the debug log about the bandwidth achieved during upload. I'm getting reports that Flickr uploads are slow, and indeed, when I try uploading to Flickr I get one tenth the bandwidth that I get when uploading to PicasaWeb. It seems that Flickr is just really slow these days. I dunno. |
| 20081208.59 | Fixed a problem that sometimes caused errors during login/authentication, or after logging out. |
| 20081204.58 | Try to work around a fairly rare Lightroom bug that sometimes causes large exports to fail with the note Whoa, exported image doesn't exist after waitForRender by pausing for a few seconds to see whether the image shows up. If not, then you still get the error and the export fails. |
| 20081129.57 | There have been a lot of spurious errors that some have seen that I think I've tracked down to a race condition at Flickr, where immediately after uploading a photo, the data hasn't propagated through Flickr yet, so when the plugin tries to set some metadata (add to a set, for example), it could see a "no such photo" error. I this version, I've added a retry ability.... I think. It's hard to test because I've never gotten the error myself. We'll see.... |
| 20081127.56 | The counting of previous uploads (for the All/Update/New of the Upload Destination section) was not working right. |
| 20081127.55 | Added some extra debugging to try to track down networking errors. |
| 20081125.54 | Well, I've added something to the "Flickr Extras..." dialog (via the File > Plugin Extras Menu) that, in theory, should allow you to connect previously-uploaded images at Flickr to your Lightroom Library. Select the images you want to check and invoke it. I didn't spend much effort to make it efficient, so it may take a few minutes if you invoke it on 30,000 images at once. It also may not work well in various edge cases, such as multiple images taken during the same second (because neither Lightroom nor Flickr give easy access to photo times down beyond one-second granularity). Another fix for a bug that had disabled plugin presets (for captions, etc.). Anyway, it's a start... give it a try and let me know what you think. |
| 20081124.53 | Perhaps fixed a problem whereby the "Upgrade Now" button didn't work for some Windows users. We'll see whether it works when those users upgrade from this version to whatever version is next. |
| 20081123.52 | Fixed a plugin crash when using the plugin's built-in preset system. |
| 20081122.51 | No problems from the upheaval recently, so pushing back the expiration a bit. |
| 20081118.50 | Fixed (I think) a problem with tags that have embedded commas. Flickr's documentation of how to upload tags does not reflect reality (that is, it's wrong), so it's a matter of trying to figure out what works.... |
| 20081118.49 | The same as .48, just to test whether the one-click upgrade stuff actually works in .48. |
| 20081117.48 | Oops, wouldn't let you log in / authenticate if you weren't already. Doh. Fixed. |
| 20081117.47 | No new functionality in this version, but a huge upheaval in the underlying code to repair an unfortunate design choice I made early on in the development that had limiting consequences I'd not foreseen. There are likely bugs introduced in this version, and as such, it has a short expiration date to encourage updates as those bugs are reported and fixed. If you do run into an error, please send (via email) the log referenced in the upper-right of the Plugin Manager. Thanks. |
| 20081113.46 | Fixed yet another list-of-upload-destinations bug. There are sure a lot of edge cases here. Also, deal with Flickr's roadblocks to geoencoding happiness. By default, Flickr ignores geoencoded information until you tell it not two, twice, in two separate places. See the bottom of the "Flickr: Metadata Management" section of the plugin for details / links. |
| 20081111.45 | Fixed a crash that happened sometimes when there are not yet any preexisting destinations at Flickr. |
| 20081104.44 | Perhaps squelch a spurious error dialog |
| 20081103.43 | I don't know what's causing the slew of networking problems that have been reported, but I've gone ahead and added a retry mechanism. It'll retry operations that failed due to network problems indefinitely, but you can cancel out of the retrys if you like. If the problems are some kind of flakiness on the machine (somehow introduced in LR2.1???) this may allow operations to complete. |
| 20081031.42 | Now works properly with the shadow GPS data maintained by my geoencoding plugin. |
| 20081024.41 | Added an option to not add Lightroom keywords as metadata when uploading images. This allows you to not send any keywords if you also have them stripped from the image itself, such as when enabling the "Minimize Embedded Metadata" option, or when stripping keywords with my Metadata Wrangler. This applies only to keywords in the Lightroom library that are marked for export; those not marked for export are never sent. (Also related, recall that due to a Lightroom bug, images in a catalog upgraded from Lightroom 1.x with Lightroom 2.0 lost the ability to export keywords until a fix is applied.) |
| 20081022.40 | Addressed (and perhaps even fixed) a bug introduced in the previous build. |
| 20081021.39 | Small update so that a stuck background version check does not disable the plugin. Added a message in the login area with instructions on how to use the plugin with multiple accounts. Added the ability to put the "select at time of export" item at the top of the destination list, as had been requested a few times. Added some items to the template language that had inexplicably been missing: {HH}, {MIN}, {hh}, {min}, {ss}. |
| 20081015.38 | Internal change to the user-agent string that the plugin sends when uploading, to better conform to web standards Added back the ability to set the print size via DPI and inches/cm. I think it's more confusing than anything (because it has nothing to do with what size something gets printed at unless you take care to set the printer DPI the same), but someone asked for it and I should really leave it up to the user. The plugin now allows you to use any color space registered on your computer when generating images to upload. I don't think this will be useful for very many people, but perhaps it might be a benefit when combined with some printing services(?) |
| 20081007.37 | Fixed a problem with the newly added "refresh tags" stuff: extra tags in the refresh dialog derived from template tokens were not being computed for each image, but instead, were being reused from the first image. Fixed. |
| 20080929.36 | I've included in this release a first try at a "refresh tags for previously-uploaded photos", added to the Flick Extras page (See File > Plug-in Extras > Flickr Extras...). Please note that this is a one-way refresh and not a two-way sync. All tags already at Flickr for the selected photos will be deleted, replaced by the current set of tags from the Lightroom library and/or the update dialog. Tags that had been manually added at Flickr will be lost.. A two-way sync is not in the cards because the Lightroom plugin architecture does not support the plugin adding/deleting keywords in the Lightroom catalog. The UI is pretty rough, and I'll likely move this to its own dialog at some point. Test it gingerly on a few images to make sure it works before using it whole-heartedly, just to be safe. |
| 20080925.35 | I've added a "Group Pools" section, to see how it works. It allows you to add the uploaded photos to a single group pool. I can expand on this with tag-based pool stuff if there's a demand... |
| 20080924.34 | Fixed a race condition that sometimes caused the export destination to not appear in the synopsis of a closed "Upload Destination" dialog section. Also fixed an issue whereby doing a "replace" would abort when the image previously uploaded to Flickr was no longer present at Flickr. Now, if the image isn't there anymore, the "replace" turns into a simple upload. (A "replace" goes to whatever the gallery the original was in; but a replace that turns into an upload goes to the export's destination gallery.) Moved the items in the "Upload Management" section into the "Upload Destination" section, since they are really quite related. |
| 20080923.33 | I created a "Metadata Management" section in the dialog, and moved some things into that from other sections. This prepared things for another big change that allows you to control some of the Flickr metadata via keywords. You can now configure the upload to work such that “images with such-and-such a keyword are marked private, while those with this-n-that a keyword are visible to friends only, while all others are visible to everyone.” You can do this with image visibility, the Flickr "safety level", the image type, and whether the image should be included in the Flickr image search. It's better to encode your intended status into the Lightroom database, via keywords, rather than something ephemeral like a changeable setting in a dialog. |
| 20080923.32 | Added a note to the export dialog that the “replace” option is meant to update the image only, and not the metadata. That's the whole point of Flickr's replace — so that you can update the image without diddling its caption, tags, etc., or removing it from whatever groups it's in. For the future, I'll work on something that allows one to update metadata separately.... |
| 20080923.31 | Sigh, just realized that the "check for new version" stuff did break in 2.1. Totally my fault, sorry. Fixed. |
| 20080921.30 | There seems to be a bug in the Flickr API that disallows an empty title or description on upload. I now include a workaround that blanks out such a title/description immediately after the upload, when needed. |
| 20080920.29 | Enhanced the {Rating} token to allow {Rating=*} to create "*****" through "". You can put most anything instead of the asterisk, so you might consider {Rating=great } to end up with "great great great". Since these forms result in nothing for an unrated photo, you can use the "|" pipe to provide a default "when empty" value, such as "rating": {Rating=*|"unrated"} |
| 20080918.28 | Added the ability to use template tokens like {Filename} in the "extra tags" input box. |
| 20080916.27 | Update an error message to reflect an apparent bug in LR that causes LR to hand off a file to my plugin for upload before the file is actually available. This seems to happen when using LR/Mogrify or other filters. Updated the url shown in the "status" section of the plugin manager |
| 20080916.26 | Finally have the upgrade button working on both Win and Mac. Since I returned home last week, I now have access to both kinds of machine for the first time since LR2 was released. I can sum up the 5 hours I spent wrestling with the unzip code in three word: I hate Windows. Microsoft owes me five hours of my life back. Note that you may have to install this one by hand in order to get the newly working upgrade button... it's the next upgrade that should be easy-as-click. |
| 20080914.25 | Added a few more descriptive tooltips to the example-token dialog |
| 20080914.24 | Oops, fixed a boo-boo introduced in the previous version. |
| 20080914.23 | Remember (again) the upload-destination across exports. It used to work, and I'm not sure when it stopped working, but it must have been really annoying while it was broken, sorry. |
| 20080914.22 | Fixed tokens "OriginalWidth" and "OriginalHeight" in templates. Added a bunch of new template tokens and a new token filter. Added a token-examples button, which brings up a dialog listing all tokens and their value for an example photo (the first photo in the export list). |
| 20080905.21 | Fixed an "undefined global: DestinationSynopsis" error that could happen when using a preset with a "select at export time" upload-destination setting |
| 20080904.20 | Added support for auto-generated destinations (see the "auto dests" button near the destination-photoset pulldown). Disable/ignore "replace" for non-pro accounts. No longer report "couldn't delete prior image" errors, since that's not really an error in the light of for our workflow. |
| 20080831.19 | Handle a race condition in the upgrade logic that sometimes results in a superfluous "You have version XYZ, but version XYZ is now available" message |
| 20080829.18 | Added a bunch of new items to the template language. |
| 20080829.17 | Oops, left some debugging cruft that results in an "empty" dialog if the logged-in-user has no galleries or the like. Fixed. |
| 20080828.16 | fix |
| 20080828.15 | Minor tweaks |
| 20080828.14 | A few more tweaks to report a failed upgrade attempt a bit more clearly |
| 20080828.13 | Whoo-hoo, finally figured out the "assert" problem that some people without photosets were having. When upgrading, ignore a status of “50” (which means “out of disk space”) from the unzip the plugin performs. It seems Windows often reports this status even when there's plenty of disk space left, so until I can understand it better, I'll just ignore that code. |
| 20080827.12 | Fixed the Caption {Filetype} token (was broken for DNGs). Layout tweaks in my preset dialogs. Made some Layout tweaks in my preset dialogs. |
| 20080817.11 | Lots of little tweaks as I cleaned things up. Added a bunch of stuff to the Plugin Manager, including a “What's New” button that shows up next to the “Upgrade Now” button when a new version is available. |
| 20080814.10 | Fixed infinite cycle of 'assert' messages one might get in odd situations |
| 20080812.9 | Fixes (I hope) a "bad argument #1 to '?' (table expected, got nil)" error |
| 20080811.8 | Moved and renamed the debugging logs to a temporary folder, and added log Show/Delete buttons to the plugin's custom section of the Plugin Manager. |
| 20080806.7 | Fixed {State} and {Rating} in preset templates. |
| 20080805.6 | Oops, the Windows versions had lost the ability to upgrade themselves. Once this version is installed manually, subsequent versions should be able to upgrade as discussed here. |
| 20080804.5 | Fixed "Access to undefined global: LrError" error that happens when trying to report a login-related problem. |
| 20080804.4 | Fixed a couple of internal errors related to the "choose destination at time of export" feature |
| 20080804.3 | Export Presets should now work. |
| 20080731.2 | Added the public/private/friends, etc., options that I forgot to include from the v1 plugin. |
| 20080729.1 | Initial public release |
Great job, the new plugin looks wonderful!
Quick bug reports on the bleeding edge–
Using “{Rating}” in the new title/caption editor says “Incomplete token {Rating” (note missing brace).
Template “Help” button goes to 404.
The “help” link was fixed right away, thanks. I’ve finally fixed the {Rating} issue in .7. —Jeffrey
Hey- thanks for continuing to offer an awesome flickr plugin for Lightroom, it really doesn’t get any better.
I just upgraded myself to Lightroom 2, and installed the latest plugin (20080729.1). I’m noticing an issue when I try to use an export preset (newly created with this version of the plugin), where it fails with an error that says, “This plug-in‚Äôs post-processing task did not finish successfully. Can’t log in to Flickr: missing credentials”
However, if I use the “Export…” dialog, and do it by hand, everything works fine.
Thanks again for your dedication to a great product.
Fixed in .3 —Jeffrey
Great plugin! Thanks for the effort.
A question: how can I set privacy level of uploads? I remember this was possible in version 1.
Thanks again.
I’d forgotten it. Added in version .2. —Jeffrey
Just noticed the missing privacy levels too – could you add this to facebook and picasaweb as well if it’s not in them
Thanks. These version 2 plugins are awesome frankly
Added in .2 —Jeffrey
Thanks for this — really like the new feature of deciding on photoset at export time. Unfortunately, choosing this option (select at export time) results in a dialog with the content ‘At line 13616′ and then another dialog with the content ‘Unable to export: An internal error has occurred: bad argument #3 (boolean expected, got string)”.
Otherwise seems to work well.
Both fixed in .4 —Jeffrey
Thanks for the great plugin! Besides the minor bugs mentioned aboved, everyting works like a charm.
One feature I really miss, however, is exporting lens model metadata to Flickr tag. ( similar to FlickrExport plugin for Aperture ).
Is this possible ‘coz I can’t seem to find a way to do it?
Thanks again!
It’s there… look at the captioning templates in the dialog. —Jeffrey
Great plugin! Thanks again for making these available. Such a huge help.
I’m wondering about the “export to folder” option in the Flickr export plugin. Is that new? I don’t remember it from the last one. What purpose does it serve?
That’s part of the standard Lightroom 2 export dialog. I always leave it set to “temporary folder”, but some people like to keep copies of the files they upload, so this allows them to do that. The only difference is that with “temporary folder”, Lightroom picks the location (a temporary one), and deletes the images at the end of the export. —Jeffrey
It’s really nice of you to quickly release the new plugin for the latest Lightroom. I really appreciate for what you have done for the flickr users! One minor question i’d like to ask is that in previous version we can customize the privacy setting. That is, we can set who is allowed to see the uploaded picture.
It’s a very nice and decent feature so that we don’t have to readjust the setting one by one in the flickr after uploading them. Have you had any plan of integrating this into the next version. (Or do I miss something in your setting panel?)
Thank you so much!
Geez, 10 comments saying the same thing. Added in .2 —Jeffrey
How do I edit the “Uploaded to Flickr” metadata?
I need to do this for all my files that were uploaded with the older plugin.
This was covered in the announcement post, in the section on migration.
Also I would love to see another metadata field to check images that I want to upload but have not been uploaded yet? I am trying to figure out how to do this with the sdk but I am having to learn lua from scratch.
You can easily do this with keywords, or just create a “to be uploaded” collection. I suppose I could add a custom metadata field that would allow you to mark an image for upload, but that seems a tad overkill…. —Jeffrey
Nice plugin!!!
Hi, I installed the flickr export plugin, but can’t get it to work at all. The error generated is:
This plug-in’s post-processing task did not finish successfully.
?:13814: assertion failed!
I did follow the installation instructions and I tried installing on a second pc the lightroom trial available on adobe’s site. Nothing changed though and that’s what I expected to happen, since this is the same version of the application (2.0 481478). Is this a beta and is this why I get the error?
I have a problem with the LR/Mogrify piglet. I have donated and have version 3.90 (unrestricted Version) however when i try to upload to Flickr it only allows me 10 pictures. Is there a fix for this or have i got the wrong piglet installed?
Thanks in advance.
You should talk to the LR/Mogrify author about LR/Mogrify, but FYI, “piglets” are not supported by this new version of my Flickr plugin. —Jeffrey
Hi, great plugin!!
I used the Lightroom 1 version six month ago and I’m very pleased with it. However in this version I’ve a problem with it. When I export a photo it doesn’t send all the keywords to flickr. It’s this a bug or something so?
Thanks and regards !!!
This is a Lightroom bug, now covered on the known issues page (which was added after you left your comment). —Jeffrey
Hi Jeffrey
Thanks for this plugin ! I tried to install it on my LR 2.0 beta but it says :
These new plugins do not work the the 2.0 beta, only the real 2.0. —Jeffrey
Plugin error log for plugin at: G:\Photos\Outils\Lightroom\Plugins\flickr-jfriedl.lrplugin
**** Error 1
An error occurred while attempting to load this plugin.
The plugin’s description resource (“Info.lua”) did not finish properly. (“?:3: attempt to index field ‘?’ (a nil value)”)
(Of course, I re-downloaded the zip file, etc)
Could you help me ?
Thanks very much for including upload privacy options! That was really quick (and now I’m gonna go and upload 80 pictures of cousins — see what you did?
.
thank you for a fantastic tool….my most used tool for my photos. and I love following your photography and your son….thank you for letting us into your life.
Now, about a problem about accented characters (probably similar to the comment on your site reported by Peter Davis on 18th July).
It occurs with the plugin for v1.x and the newer for v2.x
I’m french, so I have keywords & locations data with accented characters (éèà…)
What I get into flickr page after the export:
- For metadatas entered in the Keyword area of lightroom, if I set one with accents (eg “écran”) on flickr I get both tags “écran” and “cran” (the good tag plus a version where the accented character(s) have been removed)
- For medatata in the Exif part (location/city/country) I get only the version where accented chars have been removed (for instance if I set “Grèce” in lightrrom, I get only “Grce” on flickr side).
Very best regards and congratulations for this great plugin
Uploading isn’t working for me (LR 2.0, Mac 10.5.4). I’m select 12 images, doing a Flickr Export, and then getting two dialogs:
At line 13631Unable to Export: An internal error has occurred: bad argument #3 (boolean expected, got string)Bummer.
Fixed in .4 —Jeffrey
Love the plugin, makes it very easy to upload! Thank you!
Is there a way to take the camera/lens data and propagate them to the caption easily through the plugin?
Yes —Jeffrey
Thanks a lot for this great piece of software!!!
Great plugin… it’s working well for me. I have just started exploring geotagging, and it appears the plugin is not exporting/uploading the GPS data which is shown in Lightroom. Is this by design, or a bug, or am I just doing it wrong?
I’m using MS Pro Photo tools to add GPS data, which is shown in Lightroom. When I export with the plugin, the location data doesn’t seem to appear on Flickr.
If it shows up in Lightroom, it’ll show up on Flickr unless you have stripped them. Make sure that the Minimize Embedded Metadata option in the Metadata section of the export dialog is not checked. —Jeffrey
Plugin will stop after first file
An internal error has occurred: ?:17404: attempt to concatenate field ‘?’ (a nil value)
the version is saying that the plug in will stop working after aug 30 2008
I have the version 20080731.2
The plugins expire to encourage (force) people to upgrade from older versions. I know that there will be a lot of bugs fixed early on, so I don’t want old buggy versions hanging around out there. This was mentioned on the announcement post —Jeffrey
Just moved to LR2 and upgraded to your 20080731.2 version of the plugin. I am getting an error I don’t see listed above:
Unable to Export:
An internal error has occurred: ?:13829: assertion failed!
I can still get the 20080714.47 version to run in LR2, so will continue with that for now.
Thanks for this great tool!
Fixed in version .15 —Jeffrey
I might be missing something, but I think I found a discrepancy that turns out to be a huge inconvenience for me between the plugins for 1.0 and 2.0. We have multiple flickr accounts, one for me, and one for my wife. Before I could export to either account and it wouldn’t matter which I was logged into with my browser (Lightroom lives on my computer, so I’m usually logged in with my flickr account). With the new plugin for 2.0 your plugin only remembers one flickr login at a time. Is there a way that you can make it work like the previous version did? It’s a hassle to go to flickr, log out, log back in, then go into Lightroom and export.
I’m not exactly sure what you’re referring to… the plugin doesn’t care what you’re logged in to in your browser. However, there was a bug that might have been related, and that’s fixed as of version .4. The currently-logged-in-user is now encapsulated into an Export Preset, as it was with the older plugin, so you can create “His” and “Hers” presets that you can select from within the Export Dialog to change the destination user. —Jeffrey
I’m finding that the current version in Lightroom 2.0 is not applying tags to the uploaded images. None of the options in the Metadata section of the plugin are checked… although I’ve just spotted that in the extra tags section the radio button for space separated is selected (although there are no extra tags set there, so I presume it should be ignored…. I’ll try switching to comma-separated and see what happens)
Otherwise, it’s as great as it always has been!
There’s a Lightroom bug related to keyword export, now mentioned on the known issues page, along with a fix. —Jeffrey
I like the plugin very much and have learned to use it properly. Sometimes the upload is finalized by the statement
Ein interner Fehler ist aufgetreten: ?:17389: attempt to index a nil value
(translates as “an internal error has occurred: …”
The picture is being uploaded, but LR says “Uploaded to Flickr: No”
Any idea why this happens? I use the latest version of the plugin.
Thanks! Thomas
I can confirm the issue that others have been reporting with exported photos to flickr not getting tagged with the keywords applied in lightroom.
There is a Lightroom-wide bug related to keywords that may be the culprit here. I am still crushed with so much work that I can’t investigate this on my side yet, but perhaps that link will give someone here a clue.
I also noticed that the functionality to ‘replace’ an already-uploaded photo no longer appears to work for me either.
Was the previous image uploaded with the previous plugin? If so, you need to migrate your LR1-plugin data to the new LR2-plugin data. —Jeffrey
Thanks Jeffrey, it looks like it must be that Lightroom 2 bug you pointed to… I set the “export keywords as Lightroom hierarchy” option in the export dialog and now the tags are getting through with the Flickr upload. Adobe are working on a proper fix, it seems.
Hi Jef,
Most of the problems are solved with the latest version flickr-20080805.6.zip
I found out that there will be almost every time an error when you create a new set.
and doing uploads directly.
Is it possible to display more set names at the same time.
I have lot of set’s it’s difficult to scroll trough the sets
Thanks
Hi Jef,
I’m having problems installing the flickr plugin. This is the dialog:
At line 13871:Assertion failed(!)
I’m working on Windows XP 64bits.
Thanks!!!!
Fixed in version .15 —Jeffrey
Hi Jef,
I was wondering if it’s possible to only update the keywords from Lightroom to Flickr.
Hmmm, it should be possible. Added to the to-do list. —Jeffrey
At the time of the upload Lightroom crashed..i had to kill Lightroom and restart the upload.
With the upload to flicker filter it was easy to select the not uploaded photo’s
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
Jeff,
Cannot tell from the comments so far if the “Upload Management” “All/Update/New” function is working or not, mine is not. I can export a few then go back and export them again and all I have for counts with the “Update” or “New” is “(?)”. Seems I am keeping no history of uploaded files. Current Lightroom 2.0 and Current Plugin.
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 would also love the ability to update only the tags since I don’t want the “expense” of waiting for my photos to upload a 2nd time.
Jeff,
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.
This is now fixed in version .15. The problem was that the default destination wasn’t being set properly when the user had no sets. —Jeffrey
Jeffrey,
I have another request about tags,
Is it possible to have the option of sending folder names as tag/set to Flickr?
ps. the latest version is working stable.
Hi Jeffrey and thanks for that plugin!
I would just suggest you a feature, I would be very happy to use : to use the lightroom collection system to automaticaly create albums on flickr.
I would be very happy to use special keywords to automaticaly set access rights on flickr.
Thanks again for your work, it was just suggestions I think about using your plugin.
Best regards,
And Again! Thanks Dude!!!
I got the followning error while exporting to Flickr using the latest plugin as of today:
This plug-in’s post-processing task did not finish successfully.
?:15996: bad argument #1 to ‘?’ (table expected, got nil)
Hmmm, I’d be interested to hear (via email) the kind of export you were doing. I’m not really sure how it would have happened, but I just pushed .8 that should fix it. —Jeffrey
Any ideas?
Is it possible that the plugin takes the keywords of each picture which I have entered in Lightroom 2.0 instead of the keywords which I have to enter using the plugin when I want to export pictures to Flickr?
It would be useful especially if I want to upload many pictures.
Thanks for a excellent plugin.
Would it be possible to get more Exif data available to use in the Title preset template. I’m missing Exposure, ISO Speed Rating, Model, Lens.
Very nice plugin !!!
I want to convert EXIF Camera and Lens to Flickr tag, but I didn’t get it
Same think with contact information.
Any idea ?
Jef,
I got the same error this was when i was in the plugin setting for the second upload..(parallel upload)
I did some single uploads without any problem
An internal error has occurred: ?:17689: attempt to concatenate field ‘?’ (a nil value)
Jeffrey,
Just started using the plugin. A small request — would it be possible to move the “add to new photoset” functionality and its related ilk to the top of the menu, rather than at the bottom? I have lots of photosets, and whenever I export to a new one I have to scroll all the way down to access the functionality I want.
Thanks
Jeffrey-
First off, hi from an old co-worker at Yahoo! I really love what you’ve been doing with the plugin. It has dramatically sped up my Lightroom to Flickr processing time. Thank you for all the work that you have put into this.
Second, I know a number of people have mentioned issues with keyword uploading problems and I just wanted to mention mine. When I add new keywords to an existing photo and re-upload the photo to Flickr, those new keywords don’t seem to appear as tags upon upload.
This isn’t a Lightroom 1 to 2 issue as I was updating a photo that I had just uploaded this morning. I tested with another image and I had the same problem. I’m using the latest version of your plugin, so I’ve ruled that out as well. This issue is somewhat minor, but it does appear to be a bug.
Thanks again for your hard work on such a handy plugin.
BTW, I second the motion for just updating keywords rather than the entire image. This would be super useful.
Cheers,
Randy Stewart
Hy Jeffrey,
this is excellent work! Especially the integration of flickr into the workflow process and saving the flickr-number in the database is more than I ever imagined.
If I may add a wish however, it would be that you give us the chance to save the flickr-image-numbers to the pictures already uploaded before the plugin was available. Not sure if I was clear enough with this statement. What I meant is, that I can enter the flickr-address of the picture into the metadata-section (what the plugin does automatically for each picture on upload) by hand. I have about 2500 photos on flickr, where the link in lightroom is missing (because I uploaded them before your plugin was available).
This functionality would make the best plugin even better.
So thanks once more for a wonderful tool and please keep on the great work.
Best regards
Reini
a big improvement for me will be a more easy selection for “add to a new Photoset”.
I make 1 photoset for 1 photo serie. so I have many photoset and it’s boring to go each time to the bottom of the long list to select “add to a new photoset”.
I hope you understand what I mean
thanks for your help ! this LR 2.0 plugin is great and far better than the LR 1.3 version ! great !
david
Love the plugin. But with 2.0 I’ve intermittently received an error message “no response from flickr” which stops uploads from completing (and for my large uploads creates a pain as I have to figure out where I left off). any idea what causes this?
Love this plug-in and just started incorporating it into my upload to Flickr workflow. Ran into a bit of a snag with the Title/Description Presets … I tried to adjust the window that the dialog pops-up in while performing an Edit/Add. In doing so, LR completely froze up. After closing down and reloading, LR now continually locks up every time I even click on either Edit/Add button for these presets. Tried removing the plug-in files and reloading them, and even tried a fresh install of LR … the same problem still continues. Where is the data for these presets being written to? Maybe it will fix the problem if I can specifically eradicate those files, but I cannot find them. Using Windows XP with Service Pack 2. Thank you in advance for your assistance.
They’re saved in your preferences. If you don’t mind, could you zip up a copy of your preferences file and mail it to me? (It’s a text file, so you can scan the copy prior to zipping, to ensure that there’s no sensitive data that you’d rather not share). If I can replicate the problem, I’ll then pass it along to Adobe. —Jeffrey
Hello Jeffrey
I started using your plungin in Lr 1.x on Windows XP, but now I have migrated to Lr 2.0 and Widdows Vista 32. I updated the plugin but now I can not use it. When I try to authentication with Flickr, I get:
INTERNAL PLUGIN ERROR
Flickr login aborted
and later
An internal error has occurred
17430:attempt to index a nil value
Is something wrong on my side or is it a bug?
Thanks for your great job!!!
Antonio
Madrid-Spain
jeff-
When i authentication flickr i get
INTERNAL PLUGIN ERROR
Flickr login aborted
then
An internal error has occurred 17430:attempt to index a nil value
How do i fix that
im runnig wins xp
and
flickr-20080827.12
Thank you so much for writing and maintaining this. That’s it! I love it, no problems to speak of.
The latest release solves my problem, yes, thanks!
Now all I want is the ability to re-order the photos so that I can control the order they appear (If I’m uploading five, I want the best photo uploaded last, so that it appears first in my photostream).
You can order the images as you like, in the Library’s Grid Mode, then upload. —Jeffrey
Hi Jeff,
I want to make public my CONGRATULATIONS!!!
Yes, the Flickr Plugin worked PERFECTLY, I just tried it!!
WOW!!!!!!!!!!
No more assert problems, it’s a great gift for all of us who enjoy photography.
Thank you very much, you are a Genius.
Cheers.
Have the same problem as Ryan, above – authenticating causes a plugin error. I had to export manually and upload to Flickr – can you image the pain and suffering? Woe, woe is me…
OSX 10.5, Lightroom 2, 20080828.15.
I downloaded 829.18 tonight, and find my previous problem is gone. Uploaded to Flickr smoothly without a hitch. I’ll explore the options now that I can actually start using it.
Ed
The auto-update functionality [download & install] does not create the destination folder with the correct name.
Yep download and install, which seemed to work perfectly for me for one verison (for flickr, picasaweb and facebook) now doesn’t work. 0829.18 say’s it has been installed and needs reloading but still reports 0330.19 is available for dl and installation.
XP LR 2
ok – so I did a manual overwrite of all the files – worked first time. LOVE THIS PLUGIN
Hi Jeffrey, thanks for your nice plug-in.
I had some problems installing the 20080831.19 upgrade. I finally did it manually. Apparently my plug-ins are in the Modules subfolder, I couldn’t find a Plug-ins subfolder. I’m not sure if this was the problem.
Secondly, I ‘m facing the same problem as Joe on August 3rd, 2008 . I have two Flickr accounts. I created two presets, but once I autheticate one of the two, the other preset is also updated. So I always end up with the same Flickr account in the two presets. You know of any work around?
Thanks!
Uploads are pretty reliable now, sorting in LR works well.
The upload seems a little slower than it would be if I did the steps manually, but … it’s more convenient, so that may not be a big deal. I should measure sometime to compare.
I get the following when trying to export to flickr
Whoa, “/var/folders/ug/ugfI-WNtEleQzXw57ztZok+++TI/-Tmp-/FDAFFA05-C748-4E7C-8D62-41E3D11C2879/082908_0272.jpg” does not exist immediately after waitForRender. Please let Jeffrey know.
Then
Couldn’t open 082908_0272.jpg: /var/folders/ug/ugfI-WNtEleQzXw57ztZok+++TI/-Tmp-/FDAFFA05-C748-4E7C-8D62-41E3D11C2879/082908_0272.jpg: No such file or directory
whether I used the temporary folder or assign one.
OS X 10.5.4, lightroom 2.0, plugin 20080831.19 and LR2/Morgrify. Works fine (with lr2/morgrify) if I export to disk instead of flickr.
The above error
Whoa, “/var/folders/ug/ugfI-WNtEleQzXw57ztZok+++TI/-Tmp-/FDAFFA05-C748-4E7C-8D62-41E3D11C2879/082908_0272.jpg” does not exist immediately after waitForRender. Please let Jeffrey know.
happens when I select more than one image to export to flickr. Selecting a single image works fine.
Hi Jeff,
Great job. Your pluggin works fine in LR 2.0. Thanks so much for all of your efforts!
Jan Armor
The newest release works fine in Lightroom 2, great work! The only thing I find irritating is, that the photo which is first on the library grid is the last on flickr display. I think this should be reversed so that that the upmost photo in Lightroom is the upmost photo on flickr.
You can order the images as you like, in the Library’s Grid Mode, then upload. —Jeffrey
Getting this same error: I get the following when trying to export to flickr
Whoa, “…..” does not exist immediately after waitForRender. Please let Jeffrey know.
Then
Couldn’t open 082908_0272.jpg: /var/folders/ug/ugfI-WNtEleQzXw57ztZok+++TI/-Tmp-/FDAFFA05-C748-4E7C-8D62-41E3D11C2879/082908_0272.jpg: No such file or directory
whether I used the temporary folder or assign one.
OS X 10.5.4, lightroom 2.0, plugin 20080831.19 and LR2/Morgrify. Works fine (with lr2/morgrify) if I export to disk instead of flickr.
Except I’m using Windows XP.
It appears to be a Lightroom bug; I’ve added it to the known issues page. —Jeffrey
For me the update on flickr/picasa/facebook is broken again – was fixed but seems stuck on 19 even though 21 appears to be available.
19 was a version with the bug, so the bug remains until you upgrade. Pressing on the “check for update” button might clear it, but if not, you’ll just have to upgrade manually this time. Sorry. —Jeffrey
It would be extremely useful to be able to specify an arbitrary upload date different from the current date. This feature would allow you, for example, to upload old pictures and not have them appear as recent photos in the photostream, burying current photos behind many screens of old photos. The flickr web interface does not provide any way to batch shift the upload date for many photos at once, so this feature would provide a critical workaround.
You said a couple of times above that exporting lens model/id/aperture metadata is simple and can be done with the caption presets. I don’t see any tokens on your template help page that would do this. How do you get this plugin to add that information via the caption/title presets? Thanks.
Added a bunch of new tokens (including lens/exposure/aperture info) as of version .22 —Jeffrey
Another user with “does not exist immediately after waitForRender. Please let Jeffrey know.”
Happens when exporting to Flickr more than one image *in combination with LR2Mogrify*. I exported to local folder and what I see is that LR2Mogrify is exporting files but not necessarily in the same order as expected by “Export to Flickr.”
“Export to Flickr” is complaining about the first file in the list not being there, for instance, and indeed it’s not there but LR2Mogrify is busily working on files, except in what seems to be the reverse order.
Anyway, hope this helps,
Paul
It appears to be a Lightroom bug; I’ve added it to the known issues page. —Jeffrey
I am trying to configure this plugin for two accounts, but I cannot get it to recognize the second one. I logout, then do the “authenticate to flickr” thing, and login to flickr with the other account name, but the plugin is only remembering the first account. How do I purge the info?
The automatic install is not working for me. [...]
This has happened over the past several of your releases, and since others are not complaining I assume I am doing something wrong.
Can you help? Thanks much for a great plugin!!
Finally fixed, I think in .26 (which you’ll have to install by hand, but then should be good to go for subsequent updates). —Jeffrey
First, thanks for doing this great job for us Lightroom and flickr users. It’s an really great help in my workflow!
I’m using 20080914.24 – and I’ve to report a strange behavior in your flickr export plugin. During export, an EXIF-value is changed:
“Scale Factor35efl” should be 1.6 but is changed to 3.1 resulting in a to high value for focal lenght.
This doesn’t show up in flickr, but I’m using this exported JPEG on ipernity.com and they trust on this value. I tried the general export of Lightroom and this produces the right value. If you need any more information or sample files please contact me!
I just attempted to upload using the NEW – Upload those pics not yet exported option.
It would seem this exports any pictures which have had the exported to flickr metadata set manually (ie for the pictures I already had on flick prior to obtaining your plugin)
It appears the plugin is possibly checking the flickr location metadata which is not set by the manual procces rather than the flickr uploaded metadata.
While on the subject, is it possible somehow to manually add the flickr location data for images uploded prior to installing the plugin to allow them to be updated via the plugin after the files are edited? Without this data in place I have to fall back to flickr uploader for older files that I modify
When using the uploader for a while now and with different version I have been getting:
Unable to Export
An internal error has occured: ?:19949: attempt concatenate a field ‘?’ (a nil value)
Image still uploads fine but post processing does not occur (as in setting the Flickr flag to yes in Lightroom).
I have the flickr-log.txt if that helps you.
I will be great if the plugin can cache the flickr data. And not having to download the flickr information each time the plugin is used.
May be it can be solved storing the data locally in a file and including a refresh/synchronize button.
PS: I also have the error commented by Michael [ http://regex.info/blog/lightroom-goodies/flickr/#comment-20475 ]
This is a really useful plugin, but I am having a couple of frustrating problems:
I’m having real problems with the ‘Location’ meta data item. The Country, State, and City meta data items are turning up as tags in Flickr as expected. But not the Location item. I’ve tried added the {Location} template token to the Extra tags field. But this is just taking the location tag for one photos and then applying it to every photos. So it works OK if I am just uploading 1 photos, but uploading photos one-by-one is going to take even longer than manually adding a tag for the location of each photo after the upload!
Another small problem I am having is with the description. I really don’t want the photos caption to be uploaded to Flickr as the description as some of my older photos have automatically generated Photoshop captions which don’t mean very much. I’ve selected ‘None’ as the preset description in the ‘Flickr Upload Management’ section , but I’m still getting that dratted Photoshop auto caption being uploaded in to the Flickr photo description.
If anyone can offer any help at all with these two problem, I’d be very grateful
I just might be able to help. The first is a silly mistake on my part, and the second seems to be a bug in the Flickr API. I’ve just pushed a version that fixes the first and gets around the second. —Jeffrey
Hi!
Just working with your great plugin…
One question. Once i upload a photo to flickr, if i want to add/change a tag from lightroom and reupload (replace) the photo, i cannot
For example i change the copyright info the place the country and i add 2 more keywords from lightroom. When i upload i see ALL the changes except the tags on flickr…
For sure i am doing something wrong, but what?
Elias
Hello, I’ve just tried to install 20080921.30 and lightroom 2 on my xp sp3 box gives me an “error processing schema” and disables the plugin. I’ve tried this with the plugin folder in the lightroom home directory and several other places. I’ve also re-downloaded the zip and unzipped using a different program to make sure nothing was corrupt.
Help please.
Hi Jeffrey, first of all, thank you for your great job with the flickr export plugIn, your work is really appreciated.
However, today I stumbled upon a small bug. I tried to update some of my photos on flickr that got a caption and more keywords in lightroom, that I forgot to add in the first place.
The plugIn worked fine, but neither the captions, nor the titles or keywords have been updated.
I use Windows Vista Ultimate 64, Lightroom2 64bit and your latest plugIn. I also installed the Adobe script for the keyword 1.x->2.0 bug and executed it, though the photos I updated where only added after upgrading to 2.0.
Any idea on that?
Thanks in advance!
That’s actually how Flickr has designed the “replace” feature. I pushed .33 to include a note to the effect that metadata is not replaced. In the future, I’ll add an option to update the metadata as well. —Jeffrey
When I try “Authenticate to Flickr” I recive
“Oops! Flickr can’t find a valid callback URL.”
(flickr-20080923.32.zip)
Hi Jeffrey. First off, this is a great plugin for Lightroom. This makes my publish to flickr workflow so much simpler. While I was using your plugin I had an idea how perhaps a (small?) change might be able to help myself and others get around a limitation with Flickr. You see, I’ve had a request in to Flickr for over a year now to support a user definable maximum viewing size.
You can read the request here.
http://www.flickr.com/groups/flickrideas/discuss/72157600727889685/
As it stands now you can choose to share your full resolution image with everyone, or limit viewing to the medium 500×500 one. I’d rather be able to choose and say, let “large” 1024×1024 be the limit non friends and family can download, and for people I trust let them view the full monty.
Unfortunately, I have no faith this will be implemented anytime soon by Flickr, and the only work around that has been suggested (and people are actually doing this!) is to upload twice, one image for public consumption at the resolution you are comfortable with, and then the same image at full resolution as a “private” or “family” only pic, whatever you choose.
So my RFE and question for you is, could you add this to your lightroom flickr export to have an option at the time of export to upload both a scaled down version and the original? Also adding perhaps an optional tag addition for the full res, and it’s own privacy setting?
Thanks again for the plugin, cheers!
Nordin
Hi Jeffrey. Thanks for the nice plugin, I enjoy using it very much.
I just wanted to ask when can we expect to have the metadata update fuction you mentioned in 20080923.32 update report?
Thanks in advance and keep up the excellent job!
Each time you offer an update for LR2, the Plugin Manager installs an older version??? I saw that you had a 9/25 version, told the Plugin Manager to upgrade and it pulled in the version from 9/14. That’s happened the last couple times for me. Is there anything you can do for it?
I have to come to your website, download the update, extract it and manually move the folder to the right folder in Lightroom. I thought the Plugin Manager was supposed to make things easier???
Thanks for a great tool though!
Feature request to save File Setting, File Naming, Image Sizing alues between exports, at the moment they default to the last export settings used. For example, if you have just done a file export for 10×8 at 402 dpi then when you use your Flickr plugin it uses the setting from this export not those you last used with Flickr. Hope this makes sense.
Thanks for the great plugin.
Hi, Jeffrey, I’ve used an older version of your plugin for a while — it’s awesome, thank you. This the latest version, I can’t find tokens for using the capture time of day in the title. I would expect there to exist {HH}{MM} tokens in addition to {SS}. I’m totally confused by this, I can’t believe seconds are included, but not hours & minutes!
I’m at a loss to explain it myself. I think chipmunks broke into my computer and stole them. The hour/minute items (as {HH} and {MIN}) have been, er, “restored” as of .30. Thanks for the report. —Jeffrey
No bugs to report, no feature requests…just wanted to say thanks! I use flickr a lot, and was using “1001″ as my uploader. But the export from LR/upload to flickr routine was less than ideal. Now you’ve made it all seamless. Thanks so much!!!!
-Matt
P.S. Perhaps I’ll have some bugs/feature requests later…
tag-based pool please!
Awesome plugin! Thanks so much!
Feature request: make the “At Flickr” plug-in field searchable. This way, we can just stick the flickr ID to get back to the photo.
Keep up the good work. =)
Hi Jeffrey,
Thanks to add the refresh tags function !!
In 20080929.36 with LR 2.1 RC1, I see a issue, if I resend more than one photo. All metatadata for exif (
{FocalLengthMM}, {Aperture}, {CameraModel}, {ShutterSpeed}, iso{ISO},…) get the info form the first images.
Other issue, form long time ago I have a bug : If I create a Smart Collection with “uploaded to Flickr” is “yes” for filter all photos send to Flickr, LR is freezing. I can load LR again. Only way is to remove all your plugin. Load LR and delete the Smart Collection.
Fixed the first problem in .37, thanks for the report. I can’t repeat the smart-collection bug you report, so I’m not sure what to suggest…. —Jeffrey
The update doesn’t work for me. I have to manually download the plugin and copy the files over the previous ones.
Do you have any idea why this is so.
Win XP, Service pack 3, Lightroom 2.
As the version history above shows, there were some issues with the automatic update. If you’re were having trouble updating from one where it was fixed, well, then that’s unexpected and I’d like more info, such as the logs from a failed upgrade attempt. —Jeffrey
I uploaded 3 sets of photos using your plug-in and worked well.
I just tried to upload several more photos and I keep getting the message: An internal error has occurred: Access to undefined global: RequestHeaders
Can you help. And thank you for all your work.
Jack
That’s really mysterious, since the Flickr plugin doesn’t have a global named “RequestHeaders”. —Jeffrey
Is there a way one can manually enter data into the Uploaded to Flickr and At Flickr metadata fields? I have a few photographs on my stream which I uploaded with your plugin but later deleted and a number of photographs on my stream which I’d uploaded with other tools and I’d like add the URL for those images into the At Flickr field so I can use Lightroom as a photographic hub.
If version information matters for this sort of thing, I’m using Lightroom 2.1 RC (Release Candidate) and version 20081007.37 of your plugin.
You can clear out the info for a photo in the library by selecting those images and invoking the tools in the “Plugin Extras” dialog (in the File and Library menus). There’s currently no way to tell LR about images uploaded through other means, sorry. It’s on the list. —Jeffrey
How do I upload photos as a set and have the flickr title as bah1 blah 2 blah3 blah4 counting up by itself?
I set what I thought is the jpeg title where it says 1 0f 189 but no effect and the area where you can set the title it wants to pick data from the metadata I think.
Jeffry,
Your plugin is amazing! I only have one request which I’ve seen in several other comments. I have a large number of sets. It would be great if the “don’t add to photoset”, “add to new photoset”, etc. options could be at the top of the list of sets. I am currently using 20081007.37.
Thanks for the effort that you put in to this plugin.
Jeffrey,
I have installed your plugin on Lightroom 2.1 64bit (running on vista 64) all seems fine byt the “Authenticate to Flickr” button is greyed out as is the “check for update” button. I have disabled firewalls and A/V to elimnate that from the mix and reinstalled to default locations etc and still the issue remains. Is this an issue that you are aware of or have a fix for?
Thanks for a great plugin!
The only reason that the Authenticate button would be grayed out is when a the plugin is checking in the background whether you have the latest version. Maybe it (the check) was getting stuck somehow with either your Internet connection or my server having temporary issues? —Jeffrey
First of all, thanks for your work with this plugin and for your support. I’m very pleased with the “Group Polls” section but I’d like to know if it was possible to modify this section to allow the posting at more than one group at the same time.
Thank you very much again!
Yesterday, keywords were being exported to Flickr as tags. Today, I get none.
Changes I made:
1 – new camera, D700 rather than D70s
2 – added a couple of templated keywords to the extra keyword section
I have since taken the templates out and still have the issue, no keywords are being exported.
I tried with an old image from the D70s, worked.
I tried with another new image (NEF rather than PSD), worked.
Gary
I don’t understand the reference to PSD… that pretty much threw me… so perhaps a step or two was omitted from your explanation? Did you perhaps try to export from a PSD that has no keywords? Maybe Lightroom doesn’t support keywords with PSD files???? (I highly doubt that, but since I don’t use keywords, I don’t know)…. —Jeffrey
I’m using Lightroom 64 2.1Rc1 on Vista 64 and plug-in v20081015.38.
The issue I have is that after a few pictures (2-3) exported, the export is stalling. All the picture are exported in the temp folder but only 2-3 get exported to Flickr.
I thought LRmogrify could be the cause, so I deleted it but I still have the issue. No other filter plug-in is installed.
Jeffrey,
I use your plug-in for several weeks now without any problems and it works like a charm.
Until I decided to open a second Flickr account. While I’ve read your recommendations on how to run the plugin for several accounts. It doesn’t work. Only the first Flickr account is logged in and I can’t (whatever I do) export to the second account.
Can you explain in simple English (I’m from Belgium so English is only my third language) how this can be solved?
Kind regards,
Werner
It’s a bit complex, because of how Flickr authentication works. To switch users, you have to logout from Flickr in the plugin and in your browser. Then log into the other account in your browser then authenticate from within the plugin. —Jeffrey
MacOS 10.5.5 and LR 2 481478
Since most recent version, upload doesn’t work anymore. Flickr is operational, don’t see where the “timed out” message could come from.
+141.6: At =(tail call) line -1:
Return header ERROR
—————————————————————-
errorCode = “timedOut”
The error code comes from your operating system. Perhaps your internet connectivity was having some temporary issues (or, perhaps, Flickr was). Nothing has changed in the code since early on that could have any affect on this. My plugins are pretty bad at graceful error handling and reporting, mostly because things normally work and I’d rather put the effort into more features (which is a nice way to say that I’m lazy, I suppose). —Jeffrey
Hello,
First of all I would like to tell that this plugin really rocks! I would like to make a suggesiton toward filtering on keywords.
I’m using a keyword hierarchy which is multilingual. The main language is English but for many English keywords I also include a Dutch and a French keyword as well.
The additional Dutch and French keywords (synonyms!) ends with the suffix _NL and _FR.
So I have something like:
dancing
{dansen_NL}
{dancer_FR}
Would it be possible to add extra functionality to filter on keyword?
If image keyworded [dropdown:contains, startsWith, endsWith] endsWith “_FR”, then [dropdown: remove suffix, do not include keyword or synonym]
You have already added functionality to filter by keyword. Maybe we can add the above as well?
Thank you
Fabian
Hi jeffrey:
I’m trying to install your plugins in LR2, but I don’t see the application folder: C:\Documents and Settings\username\
Replace “username” with your actual user name on the system. —Jeffrey
File naming bug, Just downloaded the latest version and the “File naming” still doesn’t work, I’m choosing “Custom name (x of y), entering some text and below it says “my text 1 of 200) for example but when it upload there all just called custom name with no numbering.
Thank you for this very useful plugin. I’m a real fan.
I just experienced some issue when exporting photos with some keywords. Keywords containing non ascii characters (as éàèç etc..) are not correctly exported to Flickr. It may be a character encoding problem (i think that flickr guesses that all chars are in UTF8).
I could be very great if you could correct this issue : as a french speaking guy, I use a lot of strange characters. If you need help to test a patch, don’t hesitate to ask me.
Mac os X, lightroom 2, last version of the plugin : 20081024
Hello, I find your plugin useful but there’s one annoying thing that has been reported and you don’t have in the known issues list.
As Guillaume Lemoine said all exported information in EXIF that has accented characters is wrong in Flickr. Accented characters in keywords, title and captions disappear. This problem doesn’t seems to appear in Picasa export plugin. This is a problem because you can’t change metadata in Flickr and this information is always wrong.
http://regex.info/blog/lightroom-goodies/flickr/#comment-19082
I’m using Lightroom in Win XP and Mac OS X and this problem is present in both platforms.
I’m sure there are lots of people that uses your plugin and needs support for accented characters.
Thanks.
I’m using this plugin, and i have a lot of friends that use Flickr and are beggining in LR.
But we have just one problem, the english language. I understand everything, and i can write and speak a lot of thing in english, but my big problem is verbs.
Do you want a partner to translate this plugin and after the others?
I can do this just for my friends and the other portuguese speakers users of the plugin, free.
I just want a list of words useds in plugin, and after i can send for you, all translated. So you give us a version in portuguese. Or give the editable archive in wordpad, and teach how to install. If you want, obviously. But i think that would be great.
Congratulations for this plugin and blog!
Send me a e-mail if you prefer.
Thanks!
Thank you for creating this plug-in. It’s exactly what I have been looking for. Excellent work and keep it up!
I’m having an issue with Smart Collections and the Export-to-Flickr Plugin (v 20081104.44, along with previous version) with Lightroom 2.1 on Mac OS X 10.4.11.
If I create a Smart Collection using the “At Flickr” option, the left panel (with folders, collections, etc) freezes. Upon restarting lightroom, the catalog won’t load, giving an “Error changing modules” message. I can get the catalogue working again by deleting entries from the AgLibraryContent table in the SQLite database, but have had the same problem each time I try to recreate a Smart Collection using this field.
Also, I’m guessing the “Uploaded to Flickr” and “At Flickr” metadata is only stored in the Library, as RAW files converted to DNG don’t seem keep this data. Is there any way to write these fields into the XMP files?
Thanks so much for you work on these,
Grant
This is a fantastic set of plug-ins–great work!
I’m having trouble with the metadata wrangler combined with the Picasa plugin. Metadata plugin is v 20081031.23, lightroom 2.1, Windows XP SP3. I get the attached error for every photo exported.
Thanks for your effort on these plugins,
Robert
——————————————–
Execution/debug log for Jeffrey’s metadatawrangler plugin for Lightroom, version 20081031.23
Log started November 7, 2008 12:42PM local
November 8, 2008 05:42AM JST
Plugin folder: C:\Documents and Settings\Robert\My Documents\Adobe\Lightroom 2.1\Plugins\metadatawrangler-jfriedl.lrplugin
Lightroom version 2.1.0 build 512205 for Windows (Locale: en).
———————————————————————————————-
Execute log:
————————————————–
> Undefined subroutine &Digest::MD5::md5 called at C:\Documents and Settings\Robert\My Documents\Adobe\Lightroom 2.1\Plugins\metadatawrangler-jfriedl.lrplugin\lib/Image/ExifTool/IPTC.pm line 946, chunk 3.
————————————————–
I didn’t think this could happen, but have just pushed a new version (.24) that perhaps addresses it. —Jeffrey
Love the “refresh tags” option.
I also have title, description, and set generated from templates. Any chance the “refresh” could include those? That would save the whole image needing to be uploaded again.
Thanks again for the excellent plugin.
Hi,
thank you for the great plugin. One feature Request: Could you make it possible to change the metadata of previously uploaded pictures (Flickr=yes). So i would be able to tag my old uploads i did without your plugin…
(see my response at the end of the comment after this one —Jeffrey)
Tscherno,
I think you can already do this. In the Library Module, select the images you’ve already uploaded, then go to the Library/Plug-in Extras…/Flickr Extras… menu, then use the “Set” button
You can change the yes/no tag, but you can’t modify the url metadata.
Hope this helps,
Grant
or you’ll risk random plugin crashes that are not fixable. It’s a bug that Lightroom allows you to edit that data there. Doing so (editing data that the plugin doesn’t expect you to edit) can put your catalog into a state that the plugin is not capable of handling (because the plugin never creates those states), and hence can lead to crashes or random data corruption. Think about it a bit…. just marking a yes/no variable “yes” doesn’t suddenly inform the plugin which image among the billions on Flickr is the one uploaded from this Lightroom master image. If I could figure out a good way to tie pre-existing images on Flickr with images in your Lightroom library, believe me, I’d do it. —Jeffrey
I understand that the plugin cannot update manually marked picutured wihout the uri. But you could make it simply ignore it if it has the attribute flickr = yes without the url. I’m using the mode “Upload only new”.
PS: Should it work to start two or more upload tasks parallel?
Yes, you should be able to run multiple uploads in parallel. Your bandwidth will remain constant, so LR will generate all the images up front (turning your computer into a space heater for a while), but the uploading itself will continue along until they all get sent out. —Jeffrey
There seems to be an issue with the latest release (flickr-20081111.45)
I had the .44 version installed, so I installed the .45 before doing my first (ever!) flickr export, but it refused to let me choose something in the upload destination drop down menu. I tried clicking on auto-dests, set up a new preset, but I still couldn’t select it in the menu. So i went back to .44 and the problem was solved, the photostream destination was available again, and the new preset I just created with .45 was there too ! I’m back with .44 for now…
Hope it helps…
Thanx and keep it up.
I think this is fixed in .46… —Jeffrey
Hey guy, really love the plugin. I use them to upload to Flickr. However, it would be nice if I can select multiple sets when I export.
cheers.
(ive posted this on the wrong page, sorry!)
Multiple sets? You want to send the same photo to multiple sets? I didn’t even know that was allowed…. —Jeffrey
Love the retry on network issues – but it doesn’t cover all network issues. Last night I set 2802 images to upload to flickr, due to finish this morning at 7am. I woke up to find it had stopped at 850 with a dialog reporting an timeout adding an image to a photoset. I clicked OK and it continued, but now rather than being finished, it still has 2000 images to go and will be busy all day. If you could add retry for timeout when adding to a photoset, it would be appreciated.
By the way, I am using Lightroom 2, not 2.1. I’ve had network issues like these the entire time I’ve used the plugin, so I think it’s a general flickr problem rather than a 2.1 problem.
Thanks for the reply Jeffrey.
I am quite sure this can me done. I do this all the time in my Flickr Uploadr.
I can even create multiple new sets and add them in. And group as well.
Thanks for looking into this, really appreciate it.
Hi,
I’ve been using your plugin to upload my new photos, but like lots of other people, I regret that I can’t get lightroom to know that I already uploaded some pictures before I got lightroom.
I was looking at the flickr api, and it’s fairly easy to get images and their EXIF-data. Since lightroom stores a lot of information in a sqlite database, I think it should be possible to compare the information from both sources, and if they match up, record the id and ‘at flickr’ bits.
You replied somewhere that you didn’t know how to do this. Am I forgetting something obvious? Also the tables in lightrooms catalog don’t make much sense to me yet. Where do you store your flickr-information?
Hi Jeffrey,
Thank you for this wonderful plugin. I was happy to find a privacy control by tag when I switched to LR 2. But I usually tag “friend” for friends and “family” for family access. As they’re tags, I expected a photo which have both tags to be importd to flickr with both accesses but it is not the case. You put a field for “friends/family”, even filling it with “friends,family” does not work. Why ?
Thank you again for your super service.
Hello I am getting this error when I try to upload to Flickr with your latest plugin for Lightroom under Lightroom 2.1, mac os 10.5
+2298.3: At =(tail call) line -1:
Return header ERROR
----------------------------------------------------------------
errorCode = "cannotFindHost"
name = "can’t find host"
nativeCode = -1003
any ideas? thanks
I’m on Lightroom 2.1, new install and I’ve just downloaded and installed 20081117.47 of the Export to Flickr plugin.
The Authenticate to Flickr button appears to have no affect, nor does it write anything to the log file.
The other button (Visit Flickr) loads the website (which I am logged into) as expected.
Sorry about that… fixed in .48. —Jeffrey
Please please please add retry for timeout when adding an image to a photoset. Every time I set off an overnight batch it gets caught with a timeout adding to a photoset – it could happen after 100 images are uploaded or 500, completely unpredictable. Please add retry for this.
I am using flickr plugin version 20081118.50.
I have been uploading along, and now can’t open my catalog. I am getting an error “Access to undefined global: halt”.
I can open my backups fine, but of course they are way off on my flickr status.
Suggestions?
Ron
ps, I think the issue in my previous message was an issue with an update to the firewall at work.
Here’s how to fix it:
The bug you ran into occurs when you exit Lightroom while the Library Grid Filter is attempting to filter on plugin custom metadata. Just make sure you’re not doing that whenver you quit Lightroom, and you’ll be fine. It should be easy, since filtering on custom plugin metadata doesn’t actually work in Lightroom 2.1, so it’s not worth it to even try it. )-: —Jeffrey
“auto dests” not working – get error:
+563.9: At line 20704:
bad state:
+563.9: At line 20704
+563.9: At =(tail call) line -1
+563.9: At line 18583
+563.9: At =[C] line -1
INTERNAL PLUGIN ERROR
?:17540: assertion failed!
I am using WinVista SP1, LR 2.1 512205, Plugin 20081122.51
Thanks, I just pushed .52 that fixes this. —Jeffrey
Plugin 20081123.52 “auto dests” now fails with a different error:
+132.7: At line 20537:
bad state:
+132.7: At line 20537
+132.7: At =[C] line -1
INTERNAL PLUGIN ERROR
?:17555: assertion failed!
One thing I forgot to mention that may be relevant – I have over 454 (and counting) photosets.
Thanks.
” 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 love your plugins but I have been having this authentication error with every update of the plugin since the start of October. I am currently running Ligtroom 2.1 and flickr-20081123.52. Any suggestions would be greatly appreciated. I have not had any problems using you facebook plugin.
Thanks
Jeffrey -
Thank you, thank you, thank you for all the work you put into this export plugin! I’m a heavy user and a big fan, and your continual updates amaze and delight me. I can’t express enough how grateful I am. I left something in the tip jar. It’s not much, but I hope it encourages you to continue on.
Best Regards,
Andrew
Jeffrey,
Thanks for the awesome plugin. I have one problem, though…
No matter what I do, I cannot seem to get the plugin to update metadata for already uploaded pictures on Flickr. I have to re-upload the entire image and, even then, I have to go in and manually delete the original image (with incorrect metadata) because there will be a duplicate. I have the ‘Update’ option set (from All/Update/New selections) and even ‘Delete copies previously uploaded’ selected. Regardless, it always says that I’ve filtered out the selected images in ‘Upload Management’ and nothing happened (also, ‘Upload Management’ is not a grouping in the Export window, either).
Suggestions?
Version no: 20081125.54
Thank you, Jeffrey!!
-Josh
I have plug-in 20080905.21 installed.
I try to upgrade to 20081125.54, but cannot. the update manager downloads and reloads the 20080905.21 version
Then install it by hand, like the notes in the version history (that you didn’t bother reading) says. —Jeffrey
I am unable to authenticate to post to flickr. I am currently running Ligtroom 2.1 with flickr-20081125.54. Whenever I hit the authenticate button in your plugin I get this response:
” 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. ”
Since you didn’t leave an email address for me to contact you with, the best I can do here is to suggest checking your firewall settings. —Jeffrey
Hi Jeffrey, first of all, thank you for your great job with the flickr export plugIn!
Is there an issue with the length oh the keyword-list?
Yes, it seems to be a bug in Flicker. I’ve told Flicker about it in several ways, but have never gotten a reply. They seem to not care. —Jeffrey
If I try to export an image with this keywords
airline, airport, airport zurich, aviation, fliegen, flight, Flug, Flughafen, Flughafen Zürich, flying, geotagged, jet, lszh, plane, planespotting, Schweiz, spotting, suisse, swiss, switzerland, unique, zrh, Zürich, Zürich Airport - Heliport, Zürich-Kloten Airport, Zurich, Zurich Airportflickr doesn’t assign any keywords to the image. – If I shorten the keyword-list to about 1/2 and export a image, flickr assigns the keywords correctly.
As allready mentioned above, german characters are not correctly exported – the “ü” in “Zürich” ends up as “Zürich”.
I use version 20081127.56 with Lightroom 2.1 (german language) on Windows Vista.
I could be very great if you could correct this issues. If you need help for testing don’t hesitate to ask me.
Thank you, Jeffrey!!
– Oliver
Thanks a lot for implementing the “Associate Images” and “Resend Metadata” buttons. That is really great. There seems to be a small issue with the “Resend Metadata” in Version 20081127.56. It doesn’t send the Picture Caption (I hope this is the correct English term that relates to Title).
Best regards
Reini
Added the ability to do this as of version .96. —Jeffrey
I’ve installed the Flickr plug-in and it works however it looks as though there are break points still in the code perhpas for debugging purposes. What happens is when I click export the process start but an info box appears and I have to hit OK to continue. This happens about a dozen or so times before it stops and the picture is exported.
Is this a quiz… am I supposed to guess what’s in the info boxes? —Jeffrey
Export to Flickr – 20081129.57
I’d be happy to send some screen shots if needed.
Thanks again – great plug ins
The Associate Images button is brilliant! This was one of the things that has been in the back of my mind, saving for a really rainy day to sync up. One issue/request: After running it on a batch of photos, the ones that come up as errors due to file names or date/time closeness, could they be somehow tagged as such or displayed? Ideally, they’d come up in the “Error Images” section of the Catalog Browser but that might be inaccessible to plugins. I hesitate to whine about a feature that I’ll probably only use once (I don’t foresee ever uploading to Flickr again outside of LR) but I request for those that haven’t seen the light yet
Shame on you for feeding my metadata addiction!
Could you possibly provide a link to this Google Earth plugin Jeffrey? Thanks.
See the link in the first comment on the page for my Geoencoding plugin. —Jeffrey
What are the instructions for installing Flickr into LR2? Please advise.
This page is linked from every plugin download page: Installation and Management of Lightroom Plugins —Jeffrey
Hi Jeffrey,
Great work with the plugins. I don’t know how I survived without your Flickr Exporting plugin. A few days ago I updated and since uploads to flickr have gotten insanely slow (I just gave up after waiting 1 hour for two 5mb images to be uploaded).
I have run all the necessary tests at my end, and the problem does appear to be inside Lightroom. Have you changed anything in the past week or so which may impact upload speeds to Flickr?
Thanks again for the continued effort!
Regards, Will Boyce
Hello Jeffrey,
Your flickr upload plugin is working wonderfully for me, much appreciated!
One question (that could possibly turn into a feature request) – sometimes when using Flickr as a photo Archive, it is highly convenient to be able to customize the posting date flickr records when a photo is uploaded. This allows people to bury archival uploads farther back in chronology, those of us that also try to keep a coherent stream going in Flickr don’t get swamped with these Archives. I hope this makes sense.
Let me know if there’s any tweak possible to adjust this in the plugin.
Thanks again,
Nathan Siemers
Hello Jeffrey,
I’m using LR 2.1 with flickr plugin 20081209.60 on Windows XP.
I’m encountering a bug – creating custom templates is not persistent across LR sessions. If I alter a basic template or create a new one, the changes are not reflected after restarting lightroom. Where do these persistent things live in filesystem land? I don’t think it’s any permissions problem, etc…
Thanks for your excellent work!
Took a bit to followup from my Dec 1 post… what I meant was the photos that do not get associated due to date/time conflicts. Here’s a screen shot. The question came to me, which are those five? What is the conflict? Are they maybe virtual copies or PSD files that are essentially duplicates date/time wise? If those could be somehow separated out after clicking OK it would be helpful.
Ah, I see. You can filter the selected images on whether they’re uploaded to Flickr or not, and see the five that are not. —Jeffrey
Hi.
This plugin is a godsend.
I am new to Lightroom and to the plugin.
Just a question, does the plugin track images that have already been uploaded to Flickr and will warn me if I try to upload the same image again?
Regards
Christopher
Jeffrey, I’m encountering an error while exporting images to flickr that I’ve never seen before… I’ve tried all sorts of tricks to try isolating it to no avail. When exporting this batch of pics (around 800+), LR gives me this error after finishing the “Preparing to export” routine: “Unable to Export: Couldn’t render image: readNegative: dng_error_bad_format”
It’s killing me! I’ve tried exporting only jpgs, only raws, only dngs, only tifs.. any and all combination results in the error. I tried making them all a quick collection, same. I also emptied 2.8 more Gb of space, optimizing my catalog, and reloading the plugin… same result.
I’m in quite a bind… can you whip out your amazing programming skills to save the day? This plugin is beyond incredible… I’m lost without it!
Thank you for your help!
System info dump from LR:
Lightroom version: 2.0 [481478]
Operating system: Windows Vista Professional Service Pack 1 (Build 6001)
Version: 6.0 [6001]
Application architecture: x86
System architecture: x86
Physical processor count: 2
Processor speed: 1.4 GHz
Built-in memory: 2037.6 MB
Real memory available to Lightroom: 716.8 MB
Real memory used by Lightroom: 362.9 MB (50.6%)
Virtual memory used by Lightroom: 353.7 MB
Memory cache size: 143.3 MB
Plugin Version 20081209.60
Name: Jeffey Friedl’s “Export to Flickr” Plugin
You should probably upgrade to Lightroom 2.1 (and then, Lightroom 2.2 when it comes out “sometime in December”) to see if the problem goes away. I know that there was a major bug in Lightroom 1.4.0 that caused a DNG error like what you see, so perhaps you have some images that were converted to DNG via Lightroom 1.4.0? In any case, this error has nothing to do with the plugin (try exporting to disk and you’ll get it), so either the original DNG is corrupt, or there’s a Lightroom bug. I’m sure that Adobe would like to see the DNG in question, so if you could send them a bug report with the DNG file, I’m sure they’d appreciate it. —Jeffrey
I have been using the Flickr uploader for the last few months using a version I downloaded earlier this year and totally love it. The performance to upload to Flick was fine for me until this past week when I installed the latest ‘Export to Flickr’. After installing the latest version, the performance is 1/10th the speed of transfer to Flickr from what it was before my upgrade a week ago.
I know that you’re aware of this since you posted it in your blog though you made reference that it was possibly due to Flickr being slower. Since I only experienced the slower upload to Flickr after the installation of the more recent Export to Flickr, this would leave me to the conclusion that it is some element of the plugin that is causing the slow issue and not necessarily Flickr being slower than usual.
I’m open to ideas on what to try, but I get the same slow uploads when I use a version of the plugin dating back to August. I think Flickr is just slow, but I haven’t yet ruled out it being a Lightroom 2.0 vs. 2.1 issue. I no longer have a copy of Lightroom 2.0, so I haven’t been able to test that yet. —Jeffrey
BTW:
I’m using Lightroom 2.1 with the Export to Flickr plugin – flickr-20081209.60 on a Mac with OS 10.5.5
Andre.
For the life of me, I cannot figure out how to switch between my 2 Flickr accounts with this, short of always logging out of one and revalidating with the other. Anyone have a simple step by step explanation of how this works?
can’t download the ….60.zip update.
tried numerous times with an error message that the .zip file is damaged or corrupted.
winXP32 with all latest updates.
thanks, H
A thousand others, literally, have it installed and working, so I’m not sure what problem you might be experiencing, but it’s not corrupt on my server’s end… —Jeffrey
Finally worked after a lot of different attempts. May have had something to do with the latest update from MS???
Thanks, H
Great plug in thanks…is there a way to tell easily if i have uploaded a file to flicker?
Hi,
I really love this plugin and so far its working amazingly well for me.
As Flickr are now making a push on Machine tags, do you think it would be possible to add this option to the plugin.
Allowing machine takes to be taken from the exif data lightroom already has?
http://code.flickr.com/blog/2008/12/15/machine-tag-hierarchies/
Thanks for your hard work on the plugin
Hi,
is it possible to somehow call an imagemagick command to add a watermark before uploading?
Thanks for your work!
Chris
LR2/Mogrify —Jeffrey
Hi Jeffrey
I’ve noticed the Flickr Extras dialog has recently stopped appearing: the option is still there under “File, Plug-in Extras…” but nothing happens when I select it. I just checked and it’s exactly the same with the Facebook and PicasaWeb plugins. It may have happened since upgrading to LR2.2, I’m not sure, but they certainly used to work quite recently (under LR2.1).
Details as follows:
Windows Vista Ultimate 32-bit
Lightroom 2.2 523352, Camera Raw 5.2
Flickr plugin v. 20081223.61
Facebook plugin v. 20081223.51
PicasaWeb plugin v. 20081223.51
As you can see I’ve updated all plugins to the latest version. In the case of the Flickr plugin I’ve also tried deleting it altogether from the Modules directory and unzipping a fresh copy.
Big thanks for all the work you do on these amazing products, btw. I do not expect priority tech support for a free product on Christmas Eve!
All the best,
Mark
Sorry ’bout that…. fixed in new versions I just pushed. Thanks for the report. —Jeffrey
Blimey Jeffrey, I said I didn’t expect priority support at Christmas! Thanks a lot, dude. Hope you and the rest of the Friedl’s have a great Christmas.
Hi Jeffrey,
Been using your Flickr plugin for about a year now and absolutely love it. However one thing has always bothered me and that is the loss of a lot of metadata, especially Lens Info. I always assumed this was a Flickr issue but tonight I tried an experiment and downloaded Flickr Uploadr from the Flickr site. The photo I uploaded using this contained a lot more EXIF data (including lens info) on Flickr than the one I uploaded with your plugin.
Is there any way to fix this? Is it being worked on?
Thanks,
Tony
When you upload an out-of-camera image directly, it has a bunch of camera-specific “MakerNotes” data that Flickr tries to decode, including lens data. When Lightroom processes it, it normalizes the data to a maker-neutral format (XMP) that, unfortunately, Flickr ignores. Bummer. —Jeffrey
Hi there!
Perhaps this is a really silly question, but is it at all possible to run a Droplet on images before they’re uploaded to Flickr? If not, do you think it might be added to a future release?
I appreciate all your hard work! Thank you
–
Fred
What is a “droplet”? —Jeffrey
Hi Jeffrey and thanks for all, I list a bug and functionnality yhat I dream for your plugin in Flickr
- BUG : when you choose a templated destination for your images and the set allready exisits, it create a new set with the same name instead of adding the content in the allready created set
- FEATURE : it would be nice to have the capabilitie to use the Collection token in the “templated destination” : so we could have a mirror of our Lightroom’s collection in flick’r set : the only difference with others token, is that one pic could be in more than one collection in lightroom
- FEATURE : capability to suggest groups where to post the photos after uploading : the plugin could search groups related to your keyworks.
Best reegards,
Mac OS 10.5.5
Lightroom 2.2
Flickr plugin 20081224.62
I was uploading several batches of photos simultaneously and got 3 “Network Error” dialogs that said, “Task completed” with a Cancel button on each dialog. Clicking the Cancel button didn’t make the dialog go away, and it locked up Lightroom. I ended up having to force quit Lightroom. Here’s what the dialog looks like: http://flickr.com/photos/veensantmo/3155011816/
BTW thanks for the “auto dests” feature!
A droplet is an exported action from Photoshop. You export the Photoshop action into an .exe file which can then be used from Lightroom.
In the Export dialog in Lightroom (using ‘files on disk’), at the far bottom, there is a post processing tab where you can select the droplet/exported Photoshop action.
Have a look here for a more detailed explanation.
Best regards,
Fred
There is a bug in “Export to Flickr” v2008120960. The plugin won’t upgrade itself. I also had this problem with my previous version (I think that was around version 56, but can’t remember for sure), but I know this has been an ongoing problem, so I didn’t bother to report it then…
I’m running LR 2.2 on Windows Vista Ultimate (64 bit).
I really appreciate all the work you’ve done on your plugins. I use them every day!!
Version: 20081228.63
I figured out that one can enter a hard newline in the Description Preset token dialog by sending ctrl-j (rather than ctrl-enter, etc.). This adds an actual ascii newline character. Unfortunately the code, either Lightroom or the plugin seems to be stripping this out when Lightroom is restarted. Additionally the dialog allows one to update the text section, but it’s not acting as if anything was successfully parsed after hitting “update” (if one then closes the dialog it still uses the changes, however).
Would it be possible to modify the parsing to allow this special character, and/or just add a “newline” token? Thanks.
Version: 20081228.63
Associate images with Flickr doesn’t seem to be working correctly even after clearing the uploaded to flickr flag. It reports “All images are already associated…”. Unfortunately this makes it quite difficult to change the url pointer if one exported the same image (to test out a change for example) and then deleted said upload – as the url pointer now points to a deleted image.
Would it be possible to add a “Modify URL” to the Flickr Extras dialog such that one can just change the url pointer after the fact?
Thanks, plugin is awesome and quite a time and step saver.
I’m building a custom meta panel template and I wonder if you would share your identifier for the flickr and facebook plugin with us?
We want to show if a pic is uploaded or not in this custom template so what I would need is i.e.
com.adobe.filename just for your both plugins.
Would be great if you would share it with us.
Thanks
Hi Jeffrey,
I’d like to thank you for your most excellent plugin. It makes my online photo life so much easier to maintain and stay current with. Brilliant work.
Thanks!
Hey, thanks for the great plugin! I have a question that’s probably in the same vein of what Fred is asking for. I use some Automator actions to add borders around my photos when I export them for upload to Flickr. That works fine if I include the Flickr Uploadr in my Automator action, but your plugin is much better than the Uploadr, and I’d love to use it instead. It would be most welcome to see post-processing support in your plugin. Thanks again!
Hi Jeff,
Running the lightroom flickr export plugin, version 20090110.64, and for this version as well as wih the previous version, I’ve had the plug-in crap out in the middle of an upload. Given the lack of upload bandwidth and the sluggishness of flickr, I’ve start uploads to run at night. But when I return in the mornings, I get this message after only a few (10-15) pictures have been uploaded. Any thoughts?
Error response from Flickr: Filetype was not recognised
Aborting export after X of XX images successfully uploaded
Here’s a screenshot: http://tr.im/flickrerror
I have accumulated a relatively large number of sets on Flickr. This can make it very cumbersome to choose which set I want to export to, because the list is long and extends off the top and bottom of my monitor. The only way to move up and down the list is the small triangles at the top and bottom of the list.
I was thinking that it might be easier if you could add a scroll bar to the side of the list to make it easier to quickly move up and down the list.
I love this plugin!
That scrolling issue is a big across all lightroom plugins that have long lists. If you can fix this and pass it on to the other developers, or tell Adobe how to fix it, that would be awesome!!
Version: 20090110.64
Feature request: Upload images in reverse order of selection.
This is to counteract Flickr’s insistence on reverse chronological sorting. However, the feature’s intent is not really to facilitate an entire stream of this nature but more so for uploading a small set of photos (say 5-10) and having the Flickr order actually come out to the same order as you see them in one’s Lightroom catalog.
For example I usually upload documentary photography in small batches of 3-5, with the uploaded images being contextually related to each other. It doesn’t really make sense to have the images presented in reverse – so I end up having to manually reverse their order in the Lightroom catalog before uploading them with the export plugin so that afterwards they’ll be in the correct order.
Just having a small option “reverse upload order” that would have the plugin process the end of the selected list first would be very useful.
The plugin doesn’t have any control over the ordering of the images, but it could hold off on uploading them until Lightroom renders them all. Hmmm…. —Jeffrey
Oh yeah, that reverse order thing has been on my wishlist for a long time. I would love it if you could tackle that one!
I figured out a suitable work around for the reverse order thing which I kick myself for because I should have done it from the start: the a-z icon in grid view determines the sort order. Clicking it, even when set to User Order will reverse the sort direction – allowing the same outcome as uploading in reverse.
Just a question: how to place a linebreak in the caption field, seems that flickr don’t take the br-tag, neither the /n code. Latest version of the plugin
Lightoom 2.2
Mac OSX 10.5.6
Friedl Flickr Plug-in 20090119.68
Hi Jeffrey–I’m using the Lightroom plug-in (20090119.68) and Lightroom seems to hang when I use the plug-in. The “operation” status bar (upper left hand corner of Lightroom) shows the message “Uploading one image to Flickr” for an extended period of time, 20 minutes. In checking my Flickr Photostream, I do not see the images (thinking that perhaps the export and upload occurred, but didn’t pass “completed” data back to the plug-in/LR).
Doug Cranmer
(PS: I sent you a donation through PayPal earlier today. Thanks for all of your work on this project)
Thank you for this wonderful plugin.
Like Melvin, I would really like to be able to send pictures in more than one set. Would it be difficult to add ?
Until now I used the flickr uploader but their new january version does not handle lightroom titles and never handled accented characters…
Chaleureusement
SB
Hi!
i love your plugin, so i sent 10 bucks to you via paypal!! great job!
but here are two more things to think about?
- wouldn´t it be useful to have the option that the plugin should delete the temp jpegs in the defined folder after the upload? i would like it, becauce now i´m deleting manually every time (i don´t like things on my hdd i don´t need)
The plugin does delete after upload if you export to a temporary folder. If you export to a specific folder, it’s assumed that you’re doing that because you want to keep them. If you don’t care, just pick the “temporary folder” option and you’ll not have to think about it again.
- if I check the option for visiting the photoset after upload the plugins starts firefox to visit flickr. i have installed all browsers on my pc (ie, ff, chrome, opera, safari) and chrome is my default browser. why the plugin is using ff? especally for flickr i like to use chrome, cause it´s really fast. on the other hand i don´t have the piclens addon today, but i like chrome
I would have thought that your default browse would be used…. I have 4 browsers, and it always starts the one registered as my default. In any case, it’s not something that the plugin has control over: the plugin API offers an “open url in browser” call that I use. Is it possible that when you installed FF, it set itself to be the default unbeknown to you? —Jeffrey
ok, not really a big thing, but in my case helpful. however, great and stable plugin!
bye, mike
Version 20090119.68 don’t export all my keywords. Some pictures are placed on the map on flickr, others aren’t.
Version 20090119.69 but irrelevant for my message. I just wanted to say that the problem I reported earlier with broken transfer was actually related to my router. I pluged in my computer directly into the cable modem and no more problems, I could transfer 172 pictures (14.6MP – 3Mb per file) in one batch when I could barely transfer 3 or 4 at once before. The router was a Netgear WGT624 wireless in case someone else has this issue.
This plug-in is great and a huge time saver. Time to send my Paypal contribution! Cheers.
Random Request:
Would it to some how look at the “star rating” given in Lightroom and on export to flickr add this as a tag?
I use the star rating system a lot in Lightroom for sets and editing and would like to be able to use this for sets on Flickr.
Once again thank you for this plugin, its useful everyday
You can already do this by adding something along the lines of Rating:{Rating} to the “extra tags” field. I’d like to be able to suggest “{Rating} stars” but that could result in the tag “1 stars”, and I can’t stand that kind of broken English because when you see it on computers it’s usually a sign of a lazy programmer…. which is the case here. —Jeffrey
20090129.71 The GPS data doesn’t seem to be exported, I have had this issue with the earlier versions too. I use the GPS plugin to geoencode but when exported to Flickr I have to manually add it to the map (I have enabled the incoming EXIF data in Flickr)
Cheers
Not only do you have to manually tell Flickr to allow geoencoding, but you have to explicitly tell it to import the GPS data from the image. It seems fairly moronic to me, since they display the GPS information either way, so it’s not like the requirement for you to jump through a hoop helps privacy or the like. Anyway, be sure you’ve done that… see the bottom of the Metadata Management section. Also, be sure that you haven’t minimized metadata (see the Metadata section), or stripped it with the Metadata Wrangler…. —Jeffrey
I love your plug-in. Ever since I have installed this plug-in, my flickr postings have dramatically improved
It would be wonderful if the plug-in could support multiple logins. I use different flickr accounts to post family, personal, and artistic photos. Re-login every time is a big hassle.
The account credentials are included in export presets, so if you use presets for sending things out, it should all just work…. —Jeffrey
Your plugin is great. Thanks so much for taking the time to develop and actively support it.
1) Is it possible to add a tag in lightroom during the export process? For example I would love to be able to tag all my photo’s that I have uploaded to flickr.
2) Also would it be possible to upload just the metadata and/or replace the photo with the metadata. When on vacation we often quickly upload photo’s with out the titles or descriptions. I would love to be able to re-upload the photo once we have filled in the description. I tried uploading with the delete option selected, but then I loose all the view stats. Maybe there is another way that I’m missing.
Again. Thanks for all your work
>> The account credentials are included in export presets, so if you use presets for sending
>> things out, it should all just work…. —Jeffrey
I created two separate User presets in lightroom 2.2 export dialog. When I change credentials in one preset, they are automatically changed in the other preset.
Thanks for working on that newline thing, Jeffrey. I had tried every hack workaround I could think of and was only able to get it to work per Lightroom session (the ctrl-J trick). I figured it was some kind of LR limitation that was stripping newlines and it looks like you’ve discovered that as well.
Regarding the newline issue: This probably doesn’t have any bearing on the problem of newlines in preset tokens, but Lightroom does allow newlines to be entered into text boxes by using alt-enter.
I’ve had no problem entering new lines in the text boxes using Ctrl+Enter. I’m not sure why you’d do it in most of the text boxes (eg. the title), but I use it all the time in the Caption box. Alt+Enter doesn’t work for me.
I’m currently using Vista Ultimate 64-bit and LR 2.3, but this has also worked for me on XP and at least since LR 1.3.
By the way, my auto-update issues are now fixed, so thanks for that!
Also, just to provide some feedback, I find your scrollable list workaround to be pretty kludgy, and I’m not sure I would continue to work on it in this form if I were you. Maybe it’s better than the crappy drop boxes provided by Adobe, but I’m not sure. Having said that, if you are going to continue to develop this then it also needs to be applied to the popup for the Groups to Upload to.
I really do appreciate all the effort you’ve put into this plugin. It really is awesome!
Hi Jeffrey,
I noticed, that after the last plugin update, the uploaded photos in Flickr and Zenfolio show incorrect “date taken”. When I upload the same photo via webpage (both Flickr or Zenfolio) the “date taken” is correct.
I use Lightroom 2.3 RC and Flickr 20090131.73 and Zenfolio 20090129.56
Thanks in advance.
Hi,
I get this error trying to upload a photoset using the Auto : Title as destination.
Plug-in error log for plug-in at: C:\Program Files\Adobe\Adobe Photoshop Lightroom 2\Modules\flickr-jfriedl.lrplugin
**** Error 1
This plug-in’s post-processing task did not finish successfully.
?:19355: assertion failed!
Hi,
I found the bug (cf, precedent post) : when you doesn’t set any title and use a template to export to destination : {Title} and pics or part of the pics haven’t any Title set it dos’nt work.
PS : Do you project to implement the “Collections” capabilities as destination exportation metatags? (it would be really great, but need you implement the inclusion of a pic in more than one destination)
Best regards,
Hi,
First up let me say that I love the plugin. It is brilliant and makes my flickr life much easier. I have spotted a rather annoying bug in that not all my tags are transfered to flickr. Some are and some aren’t. I can provide example screenshots if required.
I’m using version 20090131.73 of the plugin with LR 2.2
Andy
Flickr has all kinds of bugs related to tags. I’ve never been able to get a reply from them about it. One particular bug is that if you have “too many” tags, none are transferred. I’ve seen other bugs related to non-ASCII tags. If you can send a plugin log (see the upper-right section of the Plugin Manager) along with the result on Flickr, I can take a look to see whether it’s something new. —Jeffrey
Hi Jeffrey,
Many thanks for a great plugin. Just tried it now and works effortlessly so far!
Certainly makes life much easier with one less step in the process.
Cheers
Dirk
The one thing we didn’t think of: When I wiped my disk and had to reinstall Lightroom, I neglected to update it. I was operating version 1.1. I received a message that updates were available, but when I clicked the link, all I got was the Adobe page for 2.2. Today, the link (reluctantly?) took me to the update page, and I’m now running 1.4. Your plugin works brilliantly! Thanks for the time you took, offering me suggestions.
John
I can’t get “Resend Metadata” to work. Although the photo has keywords, nothing gets set on Flickr. Actually, if I do set some tags manually on Flickr, they get erased when uploading from LR. I can see why in the log – the tags field on the api call is empty. Any idea what could go wrong? I can email you the log if that helps.
Great plugin but I think you missed something when creating the newest version: If I set the upload-to-set to “Create new set” when uploaded, and then put in {Folder} as the name I want the set to be, it doesn’t grab the folder name, just names the set {Folder}.
Maybe I just overlooked something but it doesn’t seem to be working for me.
Using version 20090131.72 on Vista Ultimate, 64 bit.
Hello Jeffrey,
I have a request : the Flickr: Group Pools section in the plugin is not very useful when using many groups.
One solution would be to follow the script greasemonkey Flickr – Multi Group Sender http://userscripts.org/scripts/show/1543
1/ possibility of sending photos to multiple groups at the same time
2/ save and choose multiple selections of groups (eg for one photo I choose my selection called “D200+70-200″ with all the groups about D200 & 70-200 and my selection called “Sunrise”)
this is not an essential feature of the plugin but it could be a little more practical
Thank you for the answer even if it is negative
I’ll definitely be looking at this once I get back into feature-addition mode. I’m sort of caught up now with preparing to move over to a “donationware” model… —Jeffrey
Jeffrey,
thanks for all the great plugins. I use Flickr + GPS which both work fine. But today I found one strange thing. After exporting to flickr the GPSDate Time string is different from what is shown in Lightroom. Here’s an example image: http://www.flickr.com/photos/daspaddy/3275389872/
When exporting to jpg and viewing with an EXIF-Viewer it is ok. Any idea? Is that a setting I have to change?
Thank you
Patrick
Plugin: 20090131.73, Lightroom 2.2
Since upgrading to version 20090131.73 I experience wrong characters (especially German umlauts) in uploaded keywords. This must have worked before, as I have updated some pictures on FlickR that now have the same keywords doubled (correct and incorrect umlauts). Those pictures where originally uploaded on Jan, 11th 2009, so I assume it has something todo with your latest plugin version.
What’s interesting is, that I don’t have any problems with the album’s names, that are generated automatically using folder names.
Flickr has all kinds of bugs in its API related to tags, and I can’t get a response out of them. It pulls tags from the image file, and I also send them with the plugin. In some cases, it dorks non-ASCII tags in one but not the other (which is which I don’t recall at the moment… I’ve submitted it all to Flickr, but like I said, no response). Not sure there’s much I can do, but I’m open to suggestions…. —Jeffrey
Jeffrey – wonderful job you are doing with this plugin. I’m using Flickr Export 20090131.73 with LR 2.2 on the Mac. I have observed that the plugin does not observe LR’s “Include on Export” setting for keywords, i.e. it saves all keywords as tags on Flickr, even those that have Include on Export unchecked. If I immediately afterwards do a “Resend Metadata” it works fine, the keywords to be ignored are deleted from Flickr. This is reproducible and happens on every export for me. I do not believe it is related to the keyword bug that was in LR 2.0 since I applied Adobe’s fix and it also happens with new keywords added in LR 2.
I retested everything, and keywords that had “Include on Export” unchecked did not find their way to Flickr. If you’re really seeing something wrong (with the latest version of the plugin, of course), export the offending image into its own catalog and mail it to me, and I’ll check it out. —Jeffrey
20090131.73 – just giving me a ‘not able to load’ & use telling being expired – check for update says nothing available (and date for expiry is set inMarch) – strange …
That is strange. Could you try wiping the current one and downloading/installing from scratch? Sorry for the hassles. —Jeffrey
Btw. – how far is the “Donation Ware” setup grown – already any dates in sight.
Will the new version have the “expiry” removed for “donors” ? If yes – you can count already on my donation.
Thank You – Lutz
Yes, the expiry goes away. Should be releasing the Flickr one within the week. —Jeffrey
Jeff, no chance – even reinstalling still says 20090131.73 has expired
and the new version has already a donation button
I haven’t pushed the donationware version yet…. the donation button on the current Flickr plugin version has quietly been there since Lightroom 2.0 came out, but didn’t see much action. I’ve been working on the new version….. it’s almost ready to go. About the reinstall, are you saying that 20090131.73 is saying that it has already expired? Thousands of people use that version of the plugin so my first thought is to suspect that you’ve not installed the proper version (????) —Jeffrey
I really like your Flickr plug-in. Really thnax for the great effort to further improve it. However there is something very annoying in it. I only export to Flickr every month or so. It turns out that there is always a new version of you plug-in avaible, wich makes the old one unworkable. When just wanting to have that one picture online it is pretty annoying. Some time to get the upgrade hen I have the time, would be seriously helpfull; I really consider this as a bug that eventually could bring me to one of your competitors! Hope this h not the case for other customers, you wouldn’t deserve it.
I’m not a business. I have no customers. I have no competitors. —Jeffrey
Jeffrey, I’m seeing the following error on trying to enable the newly-downloaded 20090221.74:
I didn’t see a note about needing to download and install manually. Am I missing something?
Lightroom has some bugs such that you have to actually restart it for certain changes in a plugin to take effect. I’m not sure why it’s like that or what exactly sets it off other than a change in the plugin file layout. I’ve added a note about the likely need to restart Lightroom to the version history, thanks. —Jeffrey
Whoops, and one more note: It appears you copied the donationware explanation from your geocoding page and forgot to update it for the flickr plugin. (It refers to this plugin being limited to geocoding 10 images at a time until registered)
Oops, indeed I did. Fixed. Thanks. —Jeffrey
Jeffrey, perfect – after restarting and enabling from plugin manager, my plugin is back in action. Donation Code accepted. Perfect.
)
Thank You so much ! Not being able to use it fora few days was painful
Any chance to add the option to upload a photo or photo’s with Multiple “Group Pools” selected instead of just 1?
That’s my main issue is having to go onto flickr later and adding them manually.
If this can be added, or you need someone to test it out let me know!
Thanks for a really helpful plugin, I just started using it and the way it outdo flickrs own upload tool is amazing.
Maybe I’m doing something wrong, but I’d like a possibility to upload a picture to several sets. Is this possible, or is it maybe a future possibility?
But hey, this tool easily gets a 10 anyways. Thanks again!
I hope to get back into “adding features” mode again soon, and that’ll be near the top of the list. —Jeffrey
Flickr Plugin: 20090131.73
System: Vista 64-bit
Non-ASCII characters revisited:
Since I would like to be able to use non-ASCII characters in my tags I have investigated it a bit more.
My test examples use polish and danish characters. You can see the results here:
http://www.student.dtu.dk/~s061361/exif_test.png
What is surprising:
1. when using polish tag: ‘Kępa’ the XMP:Subject contains properly encoded value, IPTC:Keywords contains wrong value and IPTC:Coded Character Set is not set. Flickr shows one tag with proper encoding and a duplicate with wrong encoding.
2. when using polish and danish tag: ‘Kępa’ and ‘Nærum’ the XMP:Subject and IPTC:Keywords data is the same and IPTC:Coded Character Set is set to UTF8. Flickr shows both tags properly.
3. when using danish tag: ‘Nærum’ everything is OK as in 2.
The problem is then in how Lightroom stores the data in the IPTC part of metadata, exactly as described on Lightroom Forums by underbjerg:
http://www.lightroomforums.net/showthread.php?t=2313
Bad metadata is then quite weirdly interpreted by Flickr.
Maybe you could provide us with a quick hack, like adding a tag with danish character “æ” and removing it after upload?
If you cannot add that tag before Lightroom writes out metadata, then maybe we could add it to all our pictures ourselves and you could just strip it after upload?
I would really like to hear your opinion on that.
I’ve tried all kinds of tests using your examples, and have not found any problems with the resulting tags at Flickr. I have seen all kinds of tag-related errors before, so it doesn’t surprise me that you’ve run into some, but I can’t reproduce them on my XP box. Perhaps you could export one image to its own catalog, then try uploading that image to confirm the bug, then send me both the catalog and the log from the upload…. (Via email, please.) —Jeffrey
V20090223.75 Lightroom 2.2 Mac OSX 10.5
“Image visibility at FlickR” doesn’t work for hierarchical tags for me. I have setup a hierarchy like this:
FlickR
- Family
- Friends
- Public
that I want to use to tag my images’ visibility for the export to FlickR with.
I’ve tried various setups like “FlickR>Friends” or “Friends>FlickR” or just “Friends”, but that all doesn’t work. It only works with top-level tags.
It would be great, if you could give me a hint on how to use this, or enhance your plugin to make it possible.
I also would love to see the “Friends and Family” option to be used when the tags for both of them are tied to a photo, not needing an extra tag for it.
It should all just work (using “Friends”… a plugin has no insight into keyword hierarchy). There was a bug in LR2 that caused some keywords to disappear on export if those keywords existed when the catalog was converted from LR1.x –any chance you could be running into that? If so, you have to run some fixup script Adobe published. If not, I’m at a loss to explain it, so perhaps you could send me the log from an export of one image that didn’t get marked the way you expected (along with a description of what you expected). There’s a button in the upper-right section of the Plugin Manager for sending the log. —Jeffrey
Jeffrey… any chance we can add the “Uploaded to Flickr” tag in a user’s Metadata Preset?
(possibly… one created with you great Metadata Viewer Preset builder
thnx!
Soon
—Jeffrey
And if you can make that work with other plugin metadata (eg. Timothy Armes LR2/blog) that would be even sweeter!
Soon
—Jeffrey
Great plugin but I feel like something was taken out of one of the previous updates.. If I set the upload-to-set to “Create new set” when uploaded, and then put in {Folder} as the name I want the set to be, it doesn’t grab the folder name, just names the set “{Folder}”.
Maybe I just overlooked something but it doesn’t seem to be working for me. In the past versions, I swear it did work but not in any of the most recent updates.
Using version 20090302.77 on Vista Ultimate, 64 bit.
I just tested and it seemed to work for me, so please get back to me with more info. If you upload one image with the {Folder} destination, then send the log (via the button in the upper-right section of the Plugin Manager), that’ll help. —Jeffrey
Hi… I really like this plugin but I have a little question .) I’m relativly new to LR so it might be my fault :9
I set up my Keywords in a tree and use the function that all parent keywords are also exported to flickr, and this works fine. (I don’t know the correct option since I use a german LR, but I hope you know what I mean).
I setup the Plugin that it should set all images to “no one else” if the image has the keyword “private” and this works when I actually add the keyword to the image.
Unfortunately it don’t work if the “private” keyword is added when I add a child keyword of it. The “private” keyword still shows up but the image is also visible to everybody.
I used 20090302.77
This was reported by someone else as well, but I could not reproduce the problem on my side. After doing an upload of one image that is not processed correctly, please send the plugin log via the button in the upper-right of the Plugin Manager, and perhaps I’ll be able to figure it out from that. —Jeffrey
Jeffrey… thanks SO much for this plug in!!! It’s a slam dunk utility!
I have a ‘feature request’…. it would be great if in the ‘Flickr Extras…’ menu, one could integrate the functionality from your metadata wrangler plug-in so that more than just tags can be updated. Here’s what I’m doing to illustrate what I mean:
I’m going back thru my LR catalog and associating images to their counterparts already uploaded to flickr. I’ve already geotagged the images in LR and would love to then resend the GPS related metadata, but not the tags (so as not to erase the existing tags @ flickr). I tried adding {GPSCoordinates} as ‘extra tags’, but that just included the GPS data as a tag. What I’d love is for it to be treated as actual geo metadata. That make sense?
Is this already do-able and I’m just missing it or an actual new feature?
Thanks again Jeffrey!
Jeffrey, quick note, I think you need to escape the html tags under the 20090228.76 change history.
Doh! Thanks, fixed. —Jeffrey
Jeffrey, I just updated to version 20090306.81 Flickr plugin on Lightroom 2.3 Windows Vista. I am on yahoo.co.uk not yahoo.com so cannot authenticate. Not had this problem before. Sorry if I have missed this somewhere.
Tony
After you get the authentication failure, could you send a plugin log (via the button in the upper-right section of the Plugin Manager)? —Jeffrey
I seem to have solved the problem by first logging in with my browser from outside your plugin. Thank you.
Hi, now that lightroom (since 2.3) has been translated in several languages, have you considered to localize the plugin too?
I offer myself to translate the “Export to Flickr” plugin in Italian since I’m Italian and I appreciate very much your plugin!
If you’re interested, please contact me
Bye,
Matteo
It’s a lot of work to translate the plugins… almost 2,000 individual text entries to be translated. I have to find the time to prepare them for translation, and when I do, I’ll send you a note, thanks! —Jeffrey
Hi there! The latest plugin version ***.84 is excellent! Especially more so because I can select multiple group pools to post my photos!! Thank you thank you.
-Joseph
flickr.com/photos/sumsinnow
sumsinnow.deviantart.com
I just upgrade the Flickr & Zenfolio plugins, I get an error message and the following is saved:
An error occurred while attempting to run one of the plug-in’s scripts.
No script by the name PluginManager.lua
I’m pretty sure that you just need to restart Lightroom. As mentioned in the release notes, there’s a bug in Lightroom that requires a restart after certain upgrades. I try to limit those kinds of upgrades, but there was once recently. —Jeffrey
Hi there.
Did a quick text search of this page trying to figure out my issue and didn’t get any results. I’m wondering how I go about exporting to flickr if I have multiple snapshots of an image that I’ve created from the RAW (usually b&w/color). Will your plugin do this automatically (I’m about to try, but assuming it won’t). If it won’t how do I go about getting both the versions up there? Is this a case where I have to export to disk and manually upload to flickr (fine if I do, just simpler if I don’t).
I’ve used the plugin a few times already and love it, this is the first issue I’ve had. Thanks for your hard work with it! – Alex in Shanghai
Assuming you have each version of the image in its own virtual copy, it’s treated as a unique photo for upload purposes, so you can have as many as you like. —Jeffrey
… please excuse me, Jeffrey, for a (probably) silly question:
when uploading multiple images… in which order will they appear on Flickr?
ok, ok… I know I should try myself, this one ;-p but… I’m quite “strict” on the order I want them on Flickr so… I never “risked” and always uploaded one picture at a time
thnx!
They’re uploaded in the order you have them in the grid. If you want them uploaded in reverse-chronological order, select reverse-chronological order in the grid before invoking the export. —Jeffrey
… this means, as Flickr shows most recent upload on top, I have to reverse my grid order prior to exporting to… reflect the original grid. right?
thank you very much, Jeffrey
Yup, you have to reverse the order in the grid (click on the “a/z” icon by the sort-order indicator). I’ve been looking into how I might upload in reverse order, so that the order in the stream is the same as in Lightroom, but the only way I can figure out how to do it is to let Lightroom render all the images, then start uploading them in reverse. That has a lot of drawbacks (uploading doesn’t begin until LR renders all the images, for example), but I wonder whether it would be useful anyway… —Jeffrey
Hi jeffrey
Just downloaded Export to Flicker for Lightroom plug-in, excellent, made this so easy. I am from the UK am retired so have time to enjoy my photography, was recommended your site by my son John who now lives in Seattle US, a better photographer than me!
Enjoyed your site very much and am pleased to make a donation for your good work.
Regards
Ken
I am using version 20090319.87 For some reason I am losing my EXIF data that used to be imbeded in my pictures…I upload to flickr and the EXIF shows at Flicker but when I use my EXIF viewer it shows “no exif information in the image” not sure if or what has changed but the EXIF data used to show up in Flickr as well as if I would view it with my external EXIF viewer(OPANDA) and it didnt matter if I viewed it at Flickr or at a forum where I would post pictures.
Thanks
Steve
The plugin uploads some of the metadata to Flickr directly (that is, in addition to whatever metadata might actually be within the image file). If you have the Lightroom-standard “Minimize embedded metadata” option checked, you might see what you’re seeing…. —Jeffrey
This is to answer glen (March 5th 2009) regarding sending the GPS coordinates for images already in Flickr:
If you look at the list of available tokens you’ll find {Latitude} and {Longitude} which can be combined as follows to update your Flickr image with the newly added coordinates as tags:
geotagged, geo:lat={Latitude},geo:lon={Longitude}
After updating the photo, go to this link: http://www.flickr.com/account/geo/import/
to import the geotags.
I already tried it and it works.
Good luck!
Hi Jeff, I’m having the same problem as Elton:
Error response from Flickr: Filetype was not recognised
Aborting export after X of XX images successfully uploaded
I’m currently using version 20090319.87
I’m getting several reports of this. It just suddenly started, so I’m guessing that it’s a problem with Flickr, but I haven’t had a chance to dig deeply. If I can reproduce it on my end, I’ll investigate with Wireshark… &mdash:Jeffrey
version 20090319.87
I do NOT have “Minimize embedded metadata” checked…it is unchecked so that isnt the issue and I am still having the issue that I cant view the EXIF within the picture with an EXIF Viewer(OPANDA or the Firefox Plugin) but the EXIF does upload to flickr…so I am at a loss.
Jeffrey, I want to thank you again for all the work you put into this. I hope you’re getting a lot of donations, because we all owe you a lot. One of these days I’ll throw a little more cash into the hat.
Best regards,
Andrew
Hi !
Just for report the following bug : in 20090324.88 version, when you export to a new photoset (don’t know if it appears for existing photoset), the URL to the photoset has two “//” (slashes) instead of one after the username.
I love your plugin, but am writing because of one thing I find difficult.
In the groups and set sections, the ‘do not add to a group/set’ option should be separate. I always have to scroll down, because for some reason the option turns itself on…
I also find the tags that I put on my picture seem to disappear. Maybe there are just too many options. I was thinking that hiding most of them and just presenting to the user the bottom line – i.e. what will be done to the picture – would be better.
So you see only
- resize to 1200×1000
- tags: harbor, ocean, water
- set: adding to ‘beach lovers’
- Title: “the harbor from the beach”
i.e. the important changes made. Maybe a button next to the change that allows setting it up or making it a default.
I know it’s difficult. Just my 2c.
M
Lightroom UI limitations make this a challenge, but you’re right that it would make more sense to have an overall “don’t add to a set” checkbox. Apparently, you can add a photo to more than one set, so when I move the set stuff over to multiple selection, I’ll add the checkbox. —Jeffrey
Would it be ok to donate beer/sake/wine whenever you happen to be in Tokyo, for the registration fee?
I happen to live in Ikebukuro…
Hello Jeffrey,
To improve the management of Flickr groups in the plugin I have several proposals that I hope interesting
:
1 / Attribute criteria or rules to each group based on the keywords and other metadata (eg GPS data, city …)
eg Flickr group called “geolocated landscape with sea, sand and nobody”
=> Send only the photos with the keyword “landscape AND sea AND sand” and with GPS data and do not have the keywords ‘person OR portrait “.
2/ Save a selection of groups (with the possibility to apply the 1/) and select several previously saved selection of groups when exporting.
eg : a selection called “D200″ with some groups about the Nikon D200″
an another selection “50mm 1.4″ with some groups about the 50mm
…
3/ Do not stop the export picture by picture when adding in a group does not work (“limite reached” for eg) but provide a log file at the end of the global export
4 / add a search box to find a group by title
Kind Regards
Quick token request:
{JobIdentifier}
{Instructions}
{Provider}
{Source} <— already done
I use these tags for tagging Camera, Lens, Film, and Developer respectively and it’d be mighty useful to use them in my Caption template to automate a workflow info line.
Update to the token alternates. The current {Token|”ALT”} setup allows an OR situation. Any chance we can get an AND modifier, e.g.: {Caption&”"} ?
I meant {Caption&”<br>”} (html break-tag)
Hi Jeffrey,
Thanks for your good work with these plugins, they are great.
Between plugins updates and lightroom updates, since some version the exported metadata includes a lot (if not all) of the PP settings from lightroom (like exposure, contrast, etc). Is there any way we can choose, or limit what is exported? Before the metadata that was exported it was only the data from camera settings, lens, etc not the PP settings.
I’m not sure why the difference (or even some setting in lightroom I’m not findding…).
Thanks
Paulo Campos
(Flickr plugin ver. 20090403.89)
The change you’re seeing is at Flickr…. recently, they started to show much more data. Previously, the data was in the image file, but not highlighted by Flickr. If you want to remove almost all the metadata, you can check the “minimize embedded metadata” box in the ‘Metadata’ section of the plugin manager. For more fine-grained control, you’ll want my Metadata Wrangler export filter, which allows you to pick and choose what to include on export. —Jeffrey
Jeffrey, i wonder if multiple photoset can be added to the plugin. Like holding the ctrl button whole selecting the photoset (and creating new ones). Right now I am just using LR and then export them to Flickr Uploadr, would be nice if I can just dismiss that step (export using Flickr Uploadr.)
flickr plugin 20090403.89 with LR 2.3 on Vista 64 SP1: OS freezes when using the export starts – This has happened twice in about three days of using the plugin. As soon as the progress bar for the export appears the machine freezes – no keyboard or mouse movement possible and I have to cold reboot.
That’s seriously unfun, sorry. After rebooting, could you check the log file to see whether it has anything? The log is named “flickr-log.txt” in the OS temp folder. It’s generally flushed whenever the plugin is loaded, so you’ll want to check before running Lightroom. If it doesn’t happen with other plugins, then my first guess would be that it’s something to do with the networking. I’ve had reports of other networking problems on Vista 64, but never system freezes. The other problems were related to IPv6, and disabling that in Vista fixed it. —Jeffrey
Been trying to download the updated flickr and gps plugins but they keep coming back with checksum errors, do you have alternate download sites? Not seeing this problem with anything else, but I’m in Nepal and anythings possible right now…
The files are fine, so perhaps they’re getting corrupted somewhere along the way. Not much I can do except suggest that you try again, sorry. —Jeffrey
Any way to make changes to the meta data (keywording) offline and then syncing the changes, without generating and uploading new images?
I’m not sure exactly what you mean, but you can resend tags for images previously uploaded via the “File > Flickr Extras” dialog. —Jeffrey
I would like to simply install your Export to Flickr for LR 2.3. How do I do it? Your sites are filled with an incredible overload of information. Thanks.
You’ll find all the details at the “installation instructions” link at the top of this page. —Jeffrey
Some versions ago the tags encoding bug showed surprisingly again, now in a weird form. Now I’m on 20090417.90, LR 2.3 for OS X, and the tags with special characters (German Umlauts, Polish ones) are duplicated: they’re send once correctly, and once changed with question marks instead of the character. An example: a LR keyword “Poznań” is send as as two tags, “Poznań” and “Pozna?”, “Mühlgasse” as “Mühlgasse” and duplicated as “M?hlgasse”.
Hi again Jeffrey, I post again with a suggestion: whenever forcing a picture flag to “already exported” should be possible to set manually the picture URL ?
This will save me a lot of work since I’m updating all my pictures (to add a copyright watermark) and some of them don’t sync automatically. So I have to open the web page and use the “substitute” link on flickr inspite of using your plugin.
Then, whenever uploaded, the picture can sync automatically but I have to do it inside of lightroom a second time.
All this is very time consuming, but if I could add the url to the image by myself it will be faster.
Hi Jeffrey, used the plugin for the first time yesterday and works great however I’m not seeing the full metadata import into Flickr as i use a Jobo GPS logger and software to add location info into metadata but once in Flickr can’t see this info. Not sure if this is a lightroom, Lightroom Plugin or Flickr problem – any help much appreciated
This is a Flickr thing. By default, they do not show GPS-related stuff. To get them to show it, you have to enable two different options in your Flickr account. They should be referenced in the Flickr-specific sections of the export dialog, if you can’t find them on your account-options page. —Jeffrey
Have you experienced any issues where connection to the internet is terminated when you use the Flickr plugin? It seems that I lose my connection to the DNS Server every time I get about 10 pictures into my export to flickr. I then have to reset my network hub and cable box for the connection to the DNS server to be reset. I’ve tried rebooting after install and updating my network card driver. Any suggestions?
Thanks… Doug…
I’ve never heard of this, and can’t imagine that it’s anything but coincidental. Has it always been like this, or is it something that started recently? —Jeffrey
Hi. I want to report a bug, and also (for me at least) a solution. I recently was unable to export anything from LR: Both the flickr exporter, and the vanilla “export to disk” exporter would fail after running, with the message “Access to undefined global: prefs”. Very frustrating, as it had worked before.
I realised that I had recently installed LR/Transporter, and turned on its “Keyword Exporter” option in the export dialog. I turned that off, and problems went away. I haven’t really used LRT yet, so it wasn’t a big deal.
flickr exporter 20090429.94, LR/Transporter 3.71
both not (yet) registered, but not yet crippled
Frankfurt, Deutschland
The Lr/Transporter plugin is by Tim Armes, so this has nothing to do with me or my plugins. I’ve passed along your comment to Tim, but it’d be better if you contacted him directly so that he can respond if he needs to. —Jeffrey
Hi,
i am trying to update my already uploaded pictures with geo-information. The geodata shows up properly in LR (thanks to your other great plugin i will donate for soon :=). After that i updated the Flickr data with File->Plugin Tools->Flickr Extra->Resend Metadata, but that didn’t update the geodata. Is there a way to do this (without uploading 4Gb again)?
Added as of version .96 —Jeffrey
Any plans for Proxy support? Would be helpful for us people who want to upload something while at the office. Ideally it would just take the settings from IE or Firefox. Also ideally it would support authenticated Proxy.
I understand if it isn’t worth the effort, but I thought it worth asking.
Thanks for such great products.
It’s my understanding that the network stuff that Lightroom does on the Plugin’s behalf uses the system proxy stuff, so if you set a proxy in IE (even if that’s not your normal browser), it’ll use it. I think. I’ve had reports of uploads failing because people had their IE proxy set wrong. It’s worth a try. —Jeffrey
Hmm…. I’ll give it a try. Maybe I just assumed it wouldn’t work.
Thanks for the quick response Jeffrey!
I found a minor cosmetic issue in the Flickr Extras: Resend Metadata dialog. Near the top of the dialog it says “… associated with the images at ^2″. I’m assuming the “^2″ is a token that should be replace with Flickr in this case.
Your plugins are great.
Oops, thanks. Just pushed a fix as version .97 —Jeffrey
Mac OS 10.5.6
Lightroom 2.3
Export to Flickr Plugin 20090510.97
Not sure if this is a feature request, or a doh! moment for me. In the Flickr plug-in extras, it appears that the Associate Images option inspects only the image capture time. Is there a way to have this feature inspect a combination of file name/flickr image title and image capture time? Nearly all of the images in my LR library that I had uploaded to Flickr before I acquired your plug-in have an image title in Flickr that matches the file name in LR. But because I can get a bit “spammy” on my shutter release, there are many pairs of pictures with the same image capture time.
Thanks!
-Todd, writing from Richmond, Virginia
Yeah, sorry, that’s on the to-do list. —Jeffrey
An error while updating the GPS Metadata (works for most photos):
+4196.5: [x219101f8] line 12486:
couldn’t send
—————————————————————-
“geo-removeLocation failed”
_____ _____ _____ _____ _____ _____ _____ _____ _____
Sorry about that…. it’s an easy fix, but I can’t push it for a day or three. I’ll do so as soon as I can. —Jeffrey
Hello again,
thank you for your fast reply (as always). It would be useful to see the picture (filename) which caused the error in the error message.
I just came up with another feature request: Two new data fields “Date/Time uploaded to Flickr” and “Date/Time of last metadata update”. That would help me to see which photos are up to date on flickr. I’m already using Lightroom to manage all the Tags and Geoinformation for my photos thanks to you and your great plugins!
I just release Flickr version .106 which now has support for new upload-date and upload-time fields (I separated them out so that upload date could be used in the Library Grid Filter). Unfortunately, it’s not possible for a plugin to create something like a “last metadata update time” kind of thing – that would have to be build in. I know that half a solution doesn’t help you, sorry, but there it is. —Jeffrey
Jeffrey, I think I found a bug with the HTML description code. When using things like “&” it issues a warning about not being able to use that description and instead insists on using an empty description. I’ve narrowed it down specifically to ampersands.
Version: 20090510.97
Ah, I see the problem. It doesn’t like & because it’s not XML, and that’s what I’m using to check it. I’ll figure out some fix or other, but won’t be able to push anything for a day or three, as the code is in the midst of a huge upheaval at the moment…. —Jeffrey
Mac OS X 10.5.6
Lightroom 2.3 539407
plugin 20090510.97
The identification to flickr is ver very slow. I can’t use export with previous because of this – the plugin thinks that Internet is down. I need to go to the export menu and then it takes at least a good minute to get the flickr information (My DB and pictures are on a shared network drives).
The shared drive shouldn’t have much to do with how fast it takes to contact Flickr, but I’ve got to point out, just in case you don’t know exactly what you’re doing, that it’s a really really really bad idea to have your catalog on a slow device, and fatal (data-wise) to have it on a shared device and actually share it. An app like Lightroom, by its very nature, is MUCH more resource intense than even a resource-hog like Photoshop. Just think what you’re asking it to do. Fast disk is probably even more important than fast CPU or memory.
Anyway, back to your question. I don’t understand why internet speed would have anything to do with “export to previous”. After it fails next time, send me the log (via the “Send to Jeffrey” button in the upper-right section of the plugin manager) along with a note about what happend and what you expected should happen. —Jeffrey
… I do understand what Ludovis is saying: since a month/a month and a half I have the very same problem. going to “Export” and choosing a preset is a pain
I usually keep Flickr Export as the active preset (is the one I use more often
but everytime it takes… 1 minute + to login into my flickr account. When I need a different export preset… it also takes a long time, with apparently nothing happening, before the selected preset highlights in the list and it’s options appear
I’m on a MacBookPro 2.5 with 4GB of Ram and plenty of free space on my internal hd, where my entire picture collection is.
It’s not even a connection issue as… I’m on a fiber-optic 10MB connection
something is really wrong, on flickr side, with mac safari beta, but this issue is a whole different matter
I think this all started after the LR 2.3 update. not sure though.
Hi,
the authentication in Flickr really takes a long time (but not a whole minute). Also MBP here but with an 50Mbit Internet Connection. The official Flickr Uploadr is authenticated a lot faster. Maybe they have an secret API for that
First of all, thanks for this great plugin.
Lightroom would be a lot less useful without it.
I love the fact that it maintains flickr metadata for pictures that have been uploaded.
It’s pretty common for me to scan my Lightroom catalog to look for specific images that I want to send to somebody. In most cases, I see that the photo has already been uploaded to flickr, and there’s already a link to that photo page on flickr which I can copy and paste in an e-mail.
The only hassle is that I can’t just copy that flickr photo URL. I have to click on it and have the photo open up in the browser, and then I can copy the link from the browser.
It would be great if that metadata field was enabled (but still read-only of course). That way I could just select the URL and copy it right there.
Just a thought.
Thanks again for the plugin.
Yeah, that’d be cool, or a context menu with “copy”, but LR doesn’t allow that yet. )-: —Jeffrey
Hi Jeffrey. I’ve noticed that when the export to flickr dialog opens, a lot of time is spent on fetching the list of sets. I thought to suggest you cache the set list, I don’t think it changes that much. In my case half the times I don’t put it in a set, rather do it later in Flickr’s ‘Organize’ application.
Yeah, it’s a balance…. many want the sets every time, some don’t. Caching them is fraught with danger, so if I ever get around to trying to make this more efficient, it’ll be a bit hairy. It’ll be a while, though, as I already have a long todo of new features I want to add… —Jeffrey
With version 20090518.99 of the Flickr export plugin, any Lightroom preset that uses the plugin disappears from the export preset list. The is true for both pre-existing presets and newly-created ones.
OS X 10.5.7
Lightroom 2.3
Export to Flickr 20090518.99
Do you perhaps have the plugin disabled in the Plugin Manager? —Jeffrey
The plugin is enabled. I can export just fine (as with previous versions), but none of my presets are saved. If I switch to any other export preset, I have to re-enter all of my usual Export to Flickr options.
I’m not sure what’s going on, then. Could you contact me by email, perhaps sending one of the presets? (They’re files on disk; you can option-click and view in Finder) —Jeffrey
Hi Jeffrey, thanks for the great work on your plugin. I noticed a couple of enhancements which would simplify use of the plugin with Lightroom and Flickr.
1. A warning message for oversized images of 20m about to be exported to Flickr that will fail.
2. A metadata update only, example – I want to get pics up fast to Flickr, and thereafter finish metadata, tagging, captions and descriptions later – but don’t want to re-upload images?
I know metadata is embedded inside the images, but it would save allot of time in uploading / synching the metadata into flickr.
Alan Vink
I’m pretty sure both are there already. If the oversized-image check fails, please immediately send a log (via the “Send to Jeffrey” button in the upper-right of the plugin manager). See File > Plugin Extras > Flickr Extras dialog for resending metadata. —Jeffrey
With regards to your comments in the 20090514.98 update – Flickr already offers a calendar view driven by either date taken or date uploaded (It’s the “archives” link on your photostream page), so I’m not sure that doing the same thing via collections is all that useful, at least not to me.
What might be useful is some kind of tag driven set management (kind of like dopiaza set manager, another third party utility, does). In other words, any images keyworded “Macro” should automatically go into my “Macro” set, “Black and White” into “Black and White”, etc.
Though on the other hand there are already utilities that automatically do this (the aforementioned one for example), so it’s still not what I’d call a high priority feature request. That’s my two cents anyway.
Hi Jeffrey!
I bow to the true awesomeness of this plugin! True genius! I thought it was a simple export plugin till I happened to stumble upon the power of tags and templates! I have been trying to use flickr sync to get my entire picture collection on to flickr for backup but have never been successful due to the size of my library and the selective natur of my uploads in the past.
With this, I uploaded all 6000 pictures just the way I wanted them (by date and then folder name of old pictures) and also threw in a few nice to haves during the upload like date of picture, camera settings etc., during the upload. Really awesome!
As far as your question about Collections goes, it would definitely be appreciated and right now I am doing what you described manually so it would be nice to have an automated way of doing that to already uploaded pictures (somehow I feel that is easier said than done due to the fact that Set Names are not stored in the library)
Also, I have two computer and I manage 2 copies of my library on 2 different external drives, I remember you mentioning a text file which stores the upload status of each picture, is it possible for you to point me to it, if its not already in the Catalog? I would like to make sure that both drives are in sync between sessions on the 2 computers that I have.
The “uploaded to…” flag is, indeed, stored in the catalog. —Jeffrey
Twitter support: Way cool. Thanks!
I feel your pain on the Lua stuff. This is another example why every time I try to get started with Lua I never finish… I have a web module design I really would like to see, but I suspect I’ll never implement.
Suggestion for Twitter support: Another special code for the link to my my main photostream page (http://www.flickr.com/photos/mark_sirota/). I’m uploading two photos, one to one photoset and the other to another photoset, so the logical place to point people is to the main page.
About the main photostream page, since that doesn’t change on a per-upload basis, you can just hard code it into the tweet template
But yeah, I’ll add a <home> tag, or something. —Jeffrey
If I hard-code it, will it automatically pass through the URL-shortening mechanism? (I’ll try it, but my first test just now didn’t end up tweeting anything…)
It won’t be shortened by the plugin, but Twitter will shorten it automatically. I was going to do url detection so I could shorten them, but in testing, Twitter let me send tweets 300+ characters long, so I didn’t bother. “140″ seems to be a big myth
—Jeffrey
Love the twitter support. How about some extra tokens so that I can use the Caption and Title as the Twitter message?
That makes sense, I suppose, when you have just one photo, but when there’s more than one, what would you have those tokens do? —Jeffrey
Awesome Twitter support, thanks Jeffrey!
Is there a way to grab the uploaded image’s small/med/large .jprg url (directly to the file) and tweat that instead of the image’s page url? Not in keeping with the social aspect of Twitter/Flickr but I mostly keep the photo page private and just link/embed the actual .jpg image.
Perhaps it’s a step too far or pointless for anyone else
I don’t think that the raw photo url is available to the plugin, but I’ll take a look… —Jeffrey
Direct linking to the image without linking to the photo page is against flickr’s TOS, just in case you didn’t know ,)
Ah, yes, I knew that… should have remembered that. Thanks. —Jeffrey
I typically only upload one photo at a time, so I hadn’t really considered that. I suppose you could tweet them all. Or just use the caption for the first photo. Or set the default for multiple photos differently than for single photos. I guess you’ll have almost as many opinions on this as you have users…
Jeffrey and John: It is a violation of Flickr’s Community Guidelines to link directly to the photo’s URL. They explicitly ask that you link to the photo’s page. This request is also echoed on the download page for the photo, where they give you the HTML to embed.
Those may be Flickr’s guidelines – but whatever we choose to do with our own URLs provided by an external utility is our own business. I don’t think it’s the plugin’s job to enforce policies – it’s to actually use computers for what they were designed for: making our lives easier.
Uh, no. Flickr says you can use their service under such-and-such conditions, and whether you like them or not, those are the conditions you agreed to, so you are bound by them. That doesn’t physically stop you from doing things against the terms, but if you choose to do so, you shouldn’t be surprised if they choose to terminate your account. (My blog is not the place to debate Flickr’s TOS, so further comments on this subject not related directly to the plugin will likely not make it through.) —Jeffrey
Jeffrey-
Had a little trouble with my first Twitter post as it posted “page just uploaded 13 new photos to Flickr : URL” rather than “Photoset_name just uploaded to Flickr : URL”, which is what I expected.
Here’s the verbiage I used:
just uploaded to Flickr :
I’m using version 20090602.104 of the Flickr plugin with Lightroom 2.3 on Mac OS X 10.5.7
Any thoughts?
Cheers,
Randy Stewart
I think my comment-submission form ate some of your text…. could you email it to me? —Jeffrey
Jeffrey, regarding your request for comments about Flickr’s collections (nested sets, sort of): AFAIK the Flickr API does not support collections at all, so don’t bother. Keep up the great work!
Mark, “It is a violation of Flickr’s Community Guidelines to link directly to the photo’s URL.”
Almost right- it’s a violation to link directly to the photo’s url WITHOUT providing a link to it’s page back on flickr. Which is entirely different.
“Do link back to Flickr when you post your Flickr content elsewhere.
The Flickr service makes it possible to post content hosted on Flickr to outside web sites. However, pages on other web sites that display content hosted on flickr.com must provide a link from each photo or video back to its page on Flickr.”
That’s the Guidlines from Flickr re: posting images from flickr to other websites. I wonder how many blogs would die overnight if Flickr could block hotlinking directly to each image which didn’t link directly to the photos page on flickr. I bet almost all photographers using flickr for their image uploads for their site would fail on this (aside from the commercial usage failure.)
I for one post flickr photos using the direct url to my blog, but all are clickably linked to their respective flickr page. This is exactly in accordance with the guidelines and one of the reasons I’d love to see a direct image (small, med, large, original or whatever) link available via this plugin.
Jeffrey,
I have a problem with version 20090604.107, trying uploading to Flickr. I get the following message: Whoa, the exported copy, …, does not exist immediately after WaitForRender. This seems to be a Lightroom bug, tickled when using this plugin along with “post-processing actions” (e.g. LR/Mogrify).
I do use the LR2/Mogrify post-processing, but with the previous version this wasn’t a problem.
Joop
No one has been able to figure out what’s causing this. I hate to say it, but at this point it remains a mystery and I can’t offer more than the suggestion to try it again later and hope it goes away. Sorry! —Jeffrey
John, that’s what I do too, but you originally asked for the ability to tweet the URL of the photo rather than the Flickr page hosting the photo. And Jeffrey, sorry to be continuing this conversation after you asked us not to — this will be my last comment on the subject.
Jeffrey, my earlier problem where no tweet appeared seems to have been caused by a bug that you’ve sinced fixed, where the tweet text didn’t show up by default. All is well now, thanks!
Hello i have a bug report.
I would like to clear the uploaded to flickr tag from the metadata. I select the images, go to library>plugin extras>flickr extras and click clear. Then get the following error message.
Acces to undefined global: LastUploadAt
Great plugin by the way.
Oops, sorry ’bout that. Just pushed .108 that fixes it. —Jeffrey
Hi. I absolutely love your plugin!
Quick question about bandwidth usage, probably LR’s problem and nothing to do with you, but…
I’m looking at how much bandwidth LR is using and it’s fluxuating up and down. It seems to take about 5 seconds to upload a picture then it does absolutely nothing for about 8 seconds. Not a huge deal except that I’m in the process of uploading 18,000 photos to flickr and I’d rather not have my bandwidth sitting idle 60% of the time
Any ideas? Thanks!!
I’d guess it’s rendering the next photo. Photos are rendered separately from upload, so if you have a slow upload link, all the selected photos will get rendered early on then just sit there waiting to be uploaded. On the other hand, if your bandwidth is better than your CPU, you’ll be sitting there waiting for the next rendering to finish before it can be sent on its way. —Jeffrey
Just an FYI to anyone interested in adding machine tags. Simply go to the section where you can add your own tags to photos and add something like:
EXIF:Aperture={Aperture}, Camera:Make={CameraMake}, Camera:Model={CameraModel}, EXIF:DateTaken={YYYY}{MM}{DD}{HH}{MIN}{SS}, EXIF:Height={OriginalHeight}, EXIF:Width={OriginalWidth}, geo:lat={Latitude}, geo:lon={Longitude}, EXIF:FocalLength={FocalLength}, photo:rating={Rating}
Voila, Machine tags for everything! And you can go back and re-update everything you’ve uploaded via the “Resend metadata” in Flickr Extras
That’s what’s weird… it’s not doing -anything- during the downtime. Zero CPU usage, Zero Network usage, Zero disk access. And the time that it sits idle seems to be somewhat random. Sometimes it’s about 1 second, sometimes it’s 30+ seconds.
I almost wonder if it’s not waiting for Flickr to do something? Like waiting to get the ID# or whatnot?
There’s a log that details what’s happening. It’s referenced in the upper-right of the plugin manager. It’s not easy to understand (‘cept for me, I suppose) but you might look at the end to see what you can see….. —Jeffrey
Hi, it’s me again
Another feature request:
Please add a x from y number and the current filename in the progress bar from “Resend Metadata”. The progress dialog would be a lot nicer this way.
Sorry ’bout that… just added it and pushed a new version. —Jeffrey
Thank you again Jeffrey – i think i have to donate again
Another {weird} idea: Reverse Tagging from Flickr. Some photos are tagged/geoencoded/renamed on Flickr after upload (i uploaded it in the past via uploadr). Would be /nice/ if you add a feature to synchronize these data…
Second idea: Change the privacy settings and collection with metadata update (optionally) like on upload via tags. So it should be possible to use LR to completely manage Flickr-Photos.
Can’t do the first one, at least not completely, because LR doesn’t allow a plugin to set LR keywords. Second one makes sense… added it to my todo list. —Jeffrey
Thanks for the great plugin. I love it. I noticed in the recent version that you have Twitter support (Specifically, it is version 20090607.109 running on Lightroom 2.3)
When I try to setup Twitter, it passes off fine to Twitter but when it comes back, I click the Yes button on the dialog that says “Have you finished authorizing the plugin via the Twitter page in your browser?” and another window pops up and says: “?:15315: attempt to index a nil value” and the only option is “OK”.
Any way to get this working?
Sorry about that… I’ve got a fix that I’ll push soon, which will change the cryptic message to the less cryptic (but still frustrating) “couldn’t contact Twitter… Internet connection down?”. (update: Just pushed it, version .110) —Jeffrey
Got the update and the message is a little less cryptic but I still can’t figure out how to get it to authenticate. I am connected to the internet. Otherwise I wouldn’t be able to authenticate on Twitter. Lightroom is connecting cause I just updated the plugin within Lightroom. Why can’t the plugin get access to the internet?
Update: it turns out that this issue is a combination of a sudden and completely incompatible change by Twitter in their authentication method (sigh), and less-than-optimal error reporting on my part. I’ve just pushed a fix. —Jeffrey
… not sure at all it’s related, but… http://www.twitpocalypse.com =:-/
Using Mac OS X 10.4.11, Lightroom 2.3, flickr plugin version 20090614.111, latest now. If I upload more than lets say 100 photo’s at once at some point I’ll get an “out of memory” statement and the upload is cancelled? Any idea? I am happy to do testing and send you test logs. Remco, The Netherlands.
Yes, please send the log, using the “Send to Jeffrey” button in the upper-right section of the Plugin Manager. —Jeffrey
The build from today, 20090614.111 seems to do the trick for fixing the Twitter issue. Thank you so much for your prompt response!
Plugin: Export to Flickr version 20090614.111
Dear Jeffrey,
first of all I want to thank you for the fantastic work you are making with these plugin!
THANK YOU!
I’d like to make a question and a request:
Question) when I upload a batch of pics to flickr and I specify the file name the plugin add a number after the name: NAME-1; NAME-2; NAME-3, …
Is it possibile to have the same NAME for all the pics?
Request) (a bit complicated) It will be wonderful if it was possibile, in a batch upload, to view the preview of the pics and set a differents name for differents image (and, why not, different sets) like the official Flickr uploader …
That’s all!
Thank you,
Raffaele
I don’t quite understand the request… the Lightroom “File Naming” section of the Export Dialog already offers a bazillion ways to name your files, including the way you suggested. —Jeffrey
Are you looking at some kind of a short URL option (eg. TinyURL, or even Flickr’s own flic.kr URL shortening service) for links sent to Twitter??
You mean besides the built-in bit.ly support? No. Why do you ask? —Jeffrey
I dont’ know what you mean by the built-in bit.ly support. My links are going out with the full Flickr URL, and I don’t see any option in the export dialog to use bit.ly. What am I missing? Does it only use bit.ly if the post is too long without it??
Here is my most recent post using the plugin:
“I just uploaded a natural light portrait of Melanie to Flickr: http://www.flickr.com/photos/ssphillips/3649772478/”
You hit on it with Does it only use bit.ly if the post is too long without it??. No need to use an ugly url if there’s space in the tweet, but it’ll aggressively shorten as needed to make it fit. —Jeffrey
OK cool. I didn’t realize that was there. I should have known that you’d have thought of everything!!! Thanks!
Export to Flickr – Version: 20090617.114
Hi Jeffrey,
Somehow i cannot get the plugin to authenticate at my personal page at Flickr, i get this message:
Oops! The API key or signature is invalid.
Flickr seems to be having issues. You’re not the only one. Just have to wait for them to fix it, I guess. —Jeffrey
Love this plugin… Saves me loads of time. Only thing I would like to see added is support for shortening URLs when posting to Twitter. Seems minor, but it would really be the icing on the cake!
Urls are shortened automatically if needed, not if not. —Jeffrey
Hi Jeffrey,
V115 actually did solve the duplicate tag with a ? in place of accented characters.
However there is one case that remains which is when the “City” field of Lightroom is populated with a city name that has accented charaters like “Le Vésinet” in France for instance.
Thanks for your works
Guillaume
Oops, forgot about that. Just pushed a fix. Thanks for the reminder. —Jeffrey
Hi Jeffrey-
I just updated my flickr plugin and now it consistently fails when uploading to my Flickr Pro account. The error message is: Unable to Export: An internal error has occurred: ?:7888: attempt to get length of a nil value.
I’m running Windows XP and your flickr plugin v20090702.116.
I did not find a mention of this error elsewhere.
Thanks
QF
Sorry about that… that’s in some debugging code that gets run only when you’re having connection issues. I’ve pushed a fix for the reporting, so if the connection issue persists, at least the log will have more info. —Jeffrey
Hi Jeffrey,
Lightroom is trying to download 20090705.117 and at the end of the down load it pops up.
The download of the new zip seems to have failed.(expected 659,464 bytes but got 659,833 instead.
Oops, sorry about that…. was a bump in my build process. Fixed. It should work if you try again. Thanks for the report. —Jeffrey
Hi, just a future feature request (from Oakland, CA). Picture Sync allows you to manipulate the upload order of your images. In Flick as things are now using your plugin, the last image from a set is at the top of the photostream. I (and others) like having the first image of a set appear at the top of the stream for chronological viewing purposes. I can’t really find a way to do that with your plug-in. It’d be great to see this feature! Thanks and great plug-in.
-Joey
They upload in the order you select, so if you want them uploaded in reverse order, just toggle the A/Z sort-order icon to Z/A and they’ll go in reverse order. —Jeffrey
Flickr Plug-in ver 20090705.117
As the result of the “Visit destination photoset after upload” checkbox, a browser is opened. My default browser is IE7. The Plugin opens Firefox. Why Firefox? Why not IE7? For that matter Chrome and Safari are feeling neglected. Can I change this to Open IE7?
Lightroom opens URLs in the browser registered on your system as the default browser (which may be different than the one you habitually use). If the browser you want is not registered as the default, check its settings to see whether you can tell it to register itself. —Jeffrey
IE7 IS registered as my default browser. Are you saying that this is a Lightroom bug?
I’m guessing that IE is not your registered browser, despite that you think it is. Perhaps try to reinstall it. Lightroom just tells the OS to display a page (just as when you click on “Lightroom Exchange” in the lower-left of the plugin manager) and leaves it for your OS to figure out how to do so. It’s not impossible that it’s a Lightroom bug, but considering the number of people who use Lightroom (lots) and the number of reports of this bug (1), I’m guessing your IE install has been damaged. (In any case, this has nothing particular to do with any plugin.) —Jeffrey
Dave from SF here, rocking Flickr plugin version 20090705.117. I love the new Twitter support. One tiny detail: the tag, when expanding to a photoset, seems to put two slashes between the username and “sets” rather than just one. See http://twitter.com/glasser/status/2589218649 for example: the link is http://www.flickr.com/photos/glasser//sets/72157621298669242
Thanks for fixing the double-slash-Twitter issue… but you took it a little too far and the double slash after http: is now a single!
Picky Picky! Okay, I’ll meet you halfway…. I just pushed a version that leaves 1.5 slashes.
(sorry… new version should work) —Jeffrey
Hi Jeffrey,
I try to authenticate my twitter account but twitter give me a seven-digit code while the plugin is waiting for a 6-digit code
Best Regards
Sigh, Twitter engineers are either clueless or arrogant beyond belief…. they made an incompatible change to how they talk to external apps like mine, but gave no warning, heads-up, or even announcement. Sigh. I’ve pushed a new version of the plugin that catches up with their latest gettin-jiggy-with-it stunt, but Lord knows what they’ll do tomorrow…. —Jeffrey
That’s a really fast update ! thanks
Enhancement request:
I regularly use your Upload to Flickr plugin with two Flickr accounts. The way it is set up now I have to login completely to the last one I used before I can change accounts to the other one.
On a slow connection from Bangkok that can take a while – I think it’s mostly downloading the groups i have subscribed to.
Could you make it an option that I choose the account before you try to log me on? I think most people use only one Flickr account and like the way it logs you on automatically so I don’t think you should lose that functionality.
Thanks a lot!
Ian
Is it possible to create a “Lite” version that does not change the catalog?
Or, just make “token filters” exporter section into a plugin (or include in Metadata Wrangler) so I can do photo:id={Filename} and I can handle the rest…
Thanks!
I don’t quite understand the second request… could you send me an email with more details? It’s possible to make a read-only version of the plugin, but not much benefit to doing so. —Jeffrey
I have a feature request.
When I export a photograph to Flickr, I often send lots of images to the same set. I almost never send lots of images to a single group. If there were any way of having a configuration option so that the group ticks were unsticky, that would be be a great timesaver (and I get group admins would thank you too
)
I’m not sure what you mean by “unsticky”, but it sounds like I already have a feature that unchecks the group destinations after the export…. is that not what you’re asking for? —Jeffrey
Just wondering if it would be possible to add code that would allow you to choose the file size when exporting. Since I use the free version of flickr I am only allowed 100MB per month of uploads, and when I try to upload everyday I make sure my photos are between 1.5 and 2MB. Such an addition would be greatly appreciated by this user, and I imagine a number of others. Thank you for the wonderful plugin.
floridagizzi
Gainesville, FL, USA
That’s not easy at all, given how Lightroom’s plugin architecture works, but that functionality has been included as part of Tim Armes’ LR/Mogrify plugin, which can be used on its own or in conjunction with other plugins. —Jeffrey
Hello,
I got problem using your Flick’r plugin + LR/Mogrify plugin. I choose a text annotation and this annotation didn’t function. But it was OK with export to disk !? Any idea ?
Thanks.
No idea, other than to ask whether you actually enabled LR/Mogrify in the Flickr export. Other than that, you should probably talk to LR?Mogrify’s author. —Jeffrey
When uploading I choose an “auto destination” based on a template. However, the new set is never created on Flickr’s site. Thanks for the plugin!
andy
Could you send a log after an export that should have created a set? Please use the “Send to Jeffrey” button in the upper-right of the plugin manager. Thanks. —Jeffrey
Jeffrey,
I have a feature request. It would be great if your plugin supported the geoprivacy setttings on Flickr.
Thanks,
Steve
I don’t understand… could you be a bit more verbose in what you want? —Jeffrey
Hi Jeff, great plugin! Unfortunately I’m having the same problem as Elton and Vincent:
Error response from Flickr: Filetype was not recognised
Aborting export after X of XX images successfully uploaded
The error occurs randomly and very often (7 out of 10 attemps)
I’m currently using version 20090716.121 (Vista Ultimate 64, Lightroom 2.4 64bit)
Best, Edi (Switzerland, Berne)
I haven’t found any options like that in Flick’r plugin ? Where are these options ? I think I have see this option one time.
See the lower-left section of the Export Dialog. —Jeffrey
Jeffrey,
Sure, Flickr allows you to specify privacy settings for geotagging information. The allowable settings are:
Only You
Your Friends and/or Family
Your Family
Your Friends
Your Contacts
Anyone
When I take pictures at people’s homes I like to restrict the geotagging info to friends and family.
Steve
Ah, I see… that’s new in the API. I just pushed a new version that handles it. It has quite a few changes in the geoencoding stuff, so please see the release notes and test carefully. —Jeffrey
Hi, great plugin! Just spotted (i think) a bug:
When exporting to flickr and setting a keyword “Family” I have set the visibility to show as “only you – family” but no matter what keyword i set they all appear to default to “Anyone – public”.
Have you any suggestions?
running Windows Vista, plugin 20090716.121
It seems to work in my tests, so if you could upload on photo for which it doesn’t work, then send me the log, I’d appreciate it. Send with the “Send to Jeffrey” button in the upper-right of the plugin manager, adding a note about what you expected to happen and what did happen. Thanks. —Jeffrey
Steve
Jeffrey,
Would it be possible to use the GPS coordinates rather than keywords to manage the Geo Privacy ?
eg : photo taken at home => location visible to Friends and Family
ideally reusing location presets of the “geoencode static location” tab from your geoencoding plugin ?
I’ll add something like that to the todo list, but probably won’t get to it all too soon…. —Jeffrey
Version: .121
I have a request:
I would love to see a function to have more then one Flickr: Group Pools.
This would help with getting the right image to the right group.
Like natural light and strobe light images.
Made something that look like the way we now can do with Descripion Preset.
Thanks, love your plugin and have payed for it. You tha man!!!!!
Best regards,
Tommy
I don’t quite understand… you can now send to multiple pools. You can also encapsulate your settings into export presets…. —Jeffrey
Ok, here goes!!!
BTW I have 2.2 version of lightroom…
As I mark 20 groups, and use ADD preset. It all looks good.
But when I then changes things up, by selecting 15 groups, and the ADD perset, the first saved on now only has the last 15 groups saved. Lightroom does not save this when you add a preset.
Hope this clears things up. Again, thanks.
TommyR
Ah, I see. I’ll check it out…. —Jeffrey
Hello,
I look at all lower-left section and I didn’t any option !
I put a printscreen of the end of my export dialog here My printscreen.
Hope you found why I haven’t any option.
I haven’t yet send you money, but I will do it soon.
Thanks for your support.
I see the LR/Mogrify options right there in the lower-left of the screenshot. I see that you have several of the Mogrify sections selected, so they should appear in the main Export dialog if you scroll up. —Jeffrey
Re…
I think we misunderstood. Yes I really have LR/Mogrify options selected, they appear upper in this long Export dialog. But these LR/Mogrify options are full functional with “export to disk” but with other export (Flick’r, …) Mogrify changed are not visible.
Hope I’have all explained this time.
Contacl me by email, if you haven’t understand.
Many Thanks
Fred (sorry for my bad english)
I don’t know what to say… the Flickr plugin has no interaction with whatever filters you might have installed and enabled (e.g. LR/Mogrify) and is not given something to upload until after the filters have done whatever they’re going to do. If LR/Mogrify is not doing what you expect, you should probably contact its author (Tim Armes). If it works in one situation but not another, as you suggest, it may be a bug in Lightroom, but if so, you’re the first to report it. —Jeffrey
Hi. You didn’t reply to my Enhancement Request at http://regex.info/blog/lightroom-goodies/flickr#comment-36011 so I thought maybe it was a dumb question: too dumb to answer. I asked that for users who upload to more than one Flickr account you don’t have to wait for the first one to logon before you’re able to switch.
I looked at Export Presets and thought that perhaps therein lies my answer. I set everything up for your Plugin to upload to User A and saved that as a Preset: Flickr-A.
Then I logged on as User B and saved that as a second Preset: Flickr-B.
Switching between the two Presets does not log you off as A and back on as B or vice-versa. The drop down box changes from “Logged on as User-A” to “Logged on as User-B” but it doesn’t change anything at the Flickr end.
I think this qualifies as a little bug.
Thanks for listening,
Ian from Bangkok, Thailand.
Hi I was wondering if there are any settings that specifically slow down the plugin? at the moment to upload 5 photos it takes around 3-4 minutes and i’m on a new iMac with a decent broadband connection so maybe there is a bottleneck somewhere?
I’m using version: 20090725.122
I’m sure there must be something i’ve set that slows it down because I can manually export JPGs from my DNGs and use the flickr uploader app in a quarter of the time, which of course kindof defeats the object of this excellent plugin
Any ideas?
Check the JPG size and quality when you export to Flickr…. they are not shared settings with the other export dialogs. Perhaps you’re sending larger files than you thought? —Jeffrey
Hi Jeffrey,
Hope you are having a good vacation
I had a couple of requests to make:
1. Is it possible to specify multiple keywords when setting privacy levels? For example, I might want to use either the keyword Family or Friends to set my privacy level to “Family/Friends”. Right now I have to use either Family or Friends privacy level and then go in and change the level manually.
2. Could the “tweet after upload” functionality be tied to my keywords as well? For example, if I’m posting a photo as private or family/friends only, a tweet isn’t very useful since most people won’t be able to see the photo.
3. This might be tricky to handle given the no. of ways in which an upload can happen, but it would be awesome if the tweet could use the Flic.kr short URLs instead – http://www.flickr.com/services/api/misc.urls.html#short
#2 makes complete sense…. putting on the todo list. I’ll look into #3, and if it allows linking to the photo’s page that’ll be cool, but if it links to the photo image itself, I can’t use it (as per Flickr’s TOS). I’ll have to think about #1 a bit more…. —Jeffrey
Hi Jeffrey,
Another request (sorry about the multiple posts).
Is it possible to add some functionality to change Flickr licensing terms based on keywords? For example, my default Flickr license is “CC-BY” but that isn’t very meaningful on private or “Family/Friends only” photos. My limited understanding of the Flickr API seems to suggest it is possible to set the licensing progamatically – http://www.flickr.com/services/api/flickr.photos.licenses.setLicense.htm , so this would be a nice little tweak to the Flickr metadata panel.
Hey Jeffrey,
I’m using the Flickr Exporter v. 20090725.122, and this is more of a question than a bug report: When I export my photos, it grabs the unedited version of the photo, even if I have made changes in the Develop area of Lightroom. Is there a setting that I need to change so that your Exporter will grab the edited version?
Thanks!
- Cory
From San Francisco, CA.
Yes, change the “Format” option in the File Settings section of the Export Dialog from “Original” to “JPEG”. It’s a standard part of the Lightroom Export Dialog, but fairly poorly named, I think. In this case, “Original” doesn’t mean “same format as the original” as would seem to make sense, but “the original undeveloped master image”. Change to “JPEG” to export a jpg version of the developed image. —Jeffrey
I’m writing to you from the US, and I’m a long-time, satisfied user of your Flickr export plugin and a new user of your Facebook export plugin.
This question is about the most current version of the Flickr export plugin, so here are my stats:
OS: Mac OS 10.5.7
Lightroom: v2.4
Camera Raw: v5.4
Export to Flickr Plugin: v20090725.122
I have a ton of photos, currently on Flickr, that I’ve re-edited as my photography education has gone on, and I’d like to replace those photos on Flickr with the better edited versions in Lightroom.
1) I understand that any photos I did not upload originally with this plugin will simply be added to Flickr, even if they were by another app (like iPhoto or an iPhoto plugin). Is this correct?
2) Once I’ve selected the “Update” radio button, I expect that your plugin will completely replace the existing images (except comments, metadata, order of my photos on Flickr, URLs, favorites, etc.) previously exported to Flickr by this plugin. Is this correct?
3) I don’t understand the “Replace” checkbox underneath the radio buttons. It says to “replace the most-recently, previously-uploaded copy”. If my assumptions in #2 are correct, I’m confused as to what this does. It seems like the “Update” selection should already handle this.
4) I also don’t understand the “Delete” checkbox. It says to “Delete copies previously updated (except the ones replaced)”. Again, if my assumptions for #2 are correct, no deletions are necessary. Thus the confusion. It also seems like the “Update” selection should already handle this.
5) Will this change the order in which Flickr shows those photos? Will they come back up to the top of the queue and hit my front page?
If you’ve already addressed these issues before (I couldn’t find them), I’d be glad to read about it there, but as of now, the text is confusing me, and I don’t want to end up with a completely unexpected result since I did not understand the behavior/consequences of those checkboxes.
Thanks, Jeff! I adore the plugins. I now use your Flickr and Facebook plugins in lieu of iPhoto’s simply b/c they work as advertized, and Apple’s don’t. (For example, try making “Faces” match in iPhoto and Facebook; nightmare.) This helps me keep extra steps out of my photo workflow, and I really appreciate your work!
I should perhaps brush up some of the labels in this area. About #1 you are correct, except that you can use the File > Plugin Extras > Flickr Extras dialog to connect your LR images to those previously imported to Flickr (e.g. via iPhoto). From then, they act as if they were uploaded via the plugin. The radio buttons mentioned in #2 are merely for selecting which of the selected images to actually process and export. #3 chooses how to export a previously-uploaded image (“upload” vs. “replace”), while #4 indicates what the plugin should do with any other copies of the image it knows has been uploaded. About #5, I actually don’t know what will happen to the order on Flickr if you replace… I suspect that the order will not change. —Jeffrey
Hi Jeffrey,
I have the same issue as Balaji Dutt.
I would like that photos with the two tags Family and Friends will be set on level “Family/Friends” in flickr.
many thanks for your useful plugin
regards
Stefano
But what about the Flickr “friends” and “family” levels? I don’t see how you’d like it to work…. —Jeffrey
I simple would like that when I set the tags Family and the tag Friends the private authorization will be set private Friends and private Family.
This is useful for the Sets that has to be shared between Family and Friends.
Don’t know if I explain the “problem”.
regards
Stefano
If I have registered the plugin for the Lightroom version 1.x – will the same work on a Lightroom license for 2.x (the lightroom license key itself is different in both cases and the upgrade from 1.x to 2.x is not within the 6-month window). Or in other words, do you tie the paypal registration code to the lightroom license key (or any other id) ?
Like everybody else before me : Appreciate all your efforts. Thanks much !
My old plugins for Lightroom 1.x had no kind of registration system, and will continue to work in Lightroom 2.x, but they have less features. —Jeffrey
Hi Jeffrey,
Great Job! This Export to Flickr plugin is really great.
I have discovered a great feature of this plugin that is missing when doing a ‘regular’ export to a .jpg file. When I have finished exporting to Flickr, there is metadata available in Lightroom that shows what files have been exported to Flickr! GREAT! Now I can easily select all files that have been uploaded to Flickr.
Do you know if there is a possibility to show something similar when I have exported to a .jpg file (not using your great Flickr upload tool)? I have been using Raw Shooter before I started with Lightroom and I really miss this feature in Lightroom.
I cannot find such info on the Adobe site, so maybe you might know some solution.
Thanks very much.
I am writing you from Barendrecht Holland.
There’s no record in Lightroom of what images you’ve exported, mostly, I think, because one tends to export for a specific use (backup, uploads, give CD to someone…) and one tends to move them away somewhere once done. You can, of course, use the many LR metadata options — keywords, collections and smart collections, metadata fields, star ratings, and color labels — to keep track yourself. —Jeffrey
Hi,
Using Flickr Export v. 20090725.122 with full satisfaction!
I’m writing about the feature request Balaji Dutt originally made. S/he’d like to be able to specify multiple keywords in each “image visibility”/“image safety” field.
My request is actually a little different: I don’t want any photo tagged “family” and/or “private” to appear in search engine results, even though I will sometimes set them to public access. This is so less savvy/lazy friends may access photos on Flickr without registering with the site. I still exclude those images from search engines to somewhat limit public visibility.
The easiest way to do this would be to support multiple tags in these fields.
Thanks!
Bumped it up in priority on the todo list, for after I return to Kyoto in September… —Jeffrey
Question and an “Opportunity for Improvement”
Flickr Export v. 20090725.122
——Background——
I had a need to quickly re-tag photos in Lightroom to honor the memory of a nephew that died last week. Jeffrey kindly pointed out the “Flickr Extras” dialog, where I could upload just metadata. GREAT!!! Saved!!! Should be easy to do.
I came to the realization that much of my Lightroom library that was uploaded with the 1.x plug-in, about 3000 of the 4000 photos, “appeared” to have lost the metadata “link” to Flickr and no longer shows having been exported.
I subsequently discovered on the “Flickr Extras” dialog that the plug-in will re-associate photos based on capture time, which is really GREAT!!! Saved!!! I will not have to reload photos.
——Question——
I also discovered that these “missing data” photos have old 1.x plug-in data that could be imported.
Is it better:
to import that data and call it done?
-OR-
associate photos with Flickr, then import data for what did not associate?
When I import the old data, it has a “now” date and time and does not show the “At Flickr” field at all.
Doing the Associate makes the plug-in data “appear” to be more correct, as all fields show similar to a recent upload, with proper dates from when it really was uploaded.
Need guidance.
——”Opportunity for Improvement”——
I did, however, find a