Jeffrey’s “Export to Flickr” Lightroom Plugin

This plugin for Adobe Lightroom Classic allows you to export images from Lightroom directly to your Flickr account.

This plugin works in Lightroom Classic, and older versions as far back as Lightroom 3, though some features depend on the version of Lightroom.

The same download works for both Windows and Mac. See the box to the upper right for the download link (in orange) and installation instructions.

Please see the FAQ and 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.

When run in Lightroom 3.3 or later, there is support for Lightroom's new Publish feature that goes well beyond what Adobe's built-in plugin provides. See the manual for Publish to Flickr for details.


This plugin is distributed as “donationware”. I have chosen to 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 is done via PayPal, and if you choose to register, it costs the minimum 1-cent PayPal fee; any amount you'd like to add beyond PayPal's sliding fees as a gift to me is completely optional, and completely appreciated.

Note: a Lightroom major upgrade, such as from Lr10 to Lr11 de-registers the plugin in the upgraded version, so if you want to maintain registration, a new ($0.01 if you like) registration code is needed in the upgraded version. It makes for a hassle every couple of years, I know. Sorry. See this note for details.

For details on plugin registration and on how I came into this hobby of Lightroom plugin development, see my Plugin Registration page.

Version History
( Update Log via RSS )


Play wack-a-mole with Flickr's keyword bugs. It seems that if there are 38 or more keywords included with a photo upload, none are actually accepted. But if I have the plugin send them separately after the upload, I get get up to 74 keywords to stick.


Play whack-a-mole with Lightroom's handling of margins in dialogs, trying to avoid having the edge of dialog items cut off.




Work around a bug in Lightroom 11.2 that causes publishing to get stuck. The workaround is to switch the view away from the collection being published. If the user does that switch manually, the bug goes away. This plugin update notices if the bug is being triggered, and if so, momentarily switches the view to the quick collection and back.

Removed a bunch of debug logging that was slowing down the LUA token.Newline


Work around a Lightroom "lua_gettop( L ) == 1" bug.


Added some extra debug logging to try to track down an error.


Added the WEEKNUM token, along with DAYNUM, weeknum, and daynum.

Whack-a-mole with PayPal's random changes.


Increased the album/set list sizes.

Tidied up the UI a bit.


Warn when PayPal seems to have given a bogus code in the web-confirmation page.


Add an option to allow videos to be quietly ignored in republish situations.

Fixed that the Province template token did not respect the plugin-specific geo-privacy settings.

Fixed an issue with the {Newline} token, and added {Comma}, {Hyphen}, and {Space} for good measure.

Fixed a problem with filters on the {Keyword} token.


Added 'separated by' to the People token.

Added the ImageViewDirection and ImageViewBearing tokens.

Reworked the Keywords token to better accept filters.

working around 'constant table overflow' error


Added the PF filter to turn typographic fractions into plain-ASCII fractions.


Updates for Lr10

Added the SpeedKnots token.


Worked around an "unknown key captureTime" error.


Fixed the Auto-Destination dialog.


Added the {PlusCode} and {GeoHash} tokens.


Handle the "All Except Camera & Camera Raw Info" metadata option WRT geoprivacy.


Try to make the create-collection dialog fit more screens, better.

Work around a Windows bug related to canceling out of the registration dialog.

Some of the filename-related tokens could be incorrect in rare situations.

Added some extra debug logging to note whether the plugin is enabled.


Added some debug logging.


Added the LensInfo template token.

Updated the Exposure token to allow customization.

More token work: added {Urls}, and updated {ISO} and {Copyright} to allow customization.

Added the {RelativeFolder} token.


Fixed the SST1 and SST2 tokens.


Updated the PublishCollectionName token (and CollectionNames and CollectionFullNames) to remove the MIRROR: prefix from the name that mirrored collections within my Collection Publisher plugin automatically get.


Added functions uc(), ucFirst(), lc(), and lcFirst() to the LUA token.


When not logged in, make it more clear what you're not logged into, and how to fix it.

Updated the alphabetical sort to be "sorta-smart alphabetical sort", whereby names that differ only by a number are sorted numerically. For example, "album2" properly falls between "album1" and "album3", but "album20" falls after. The former straight-up alphabetical sort put "album20" before "album3", which is ugly and unpractical.

Added the PEOPLE variable to the LUA token.

Fixed a problem with the SpeedKPH token.

Finally figured out the “Assertion failed: packed” error.

Added TempC and TempF to the template tokens that my plugins understand.

Added the TempC and TempF tokens.

Updated the keyword-related tokens to accept standard filters.

Work around a bug that sometimes causes plugins to be disabled when starting Lightroom via clicking on a catalog file.

Fix an "Unknown key: captureTime" crash.

Added the GPSCoords token.

Fixed a problem related to template tokens and photos without capture times.


Created a way to completely disable the fetching of photo comments and ratings from Flickr. Lightroom normally does this for every photo in a publish collection after every publish operation, and that overhead can be significant if you have many photos in your collection. If you never care about photo comments, you can now visit the Plugin Manager to completely disable the fetching and the overhead.


Make the template-editing window a big bigger in the caption editor.


Updates for Lr8 (Lightroom Classic CC Version 8).

Added the special PP() function to the {LUA} token.

Added hierarchical options to the Keywords token.

Try to work around a Lightroom bug related to photo timezones and how Lightroom handles accessing plugin data.


Added the 'nicknames' modifier to the {People} token.


Well, goodness, it seems that Flickr renamed the concept of "sets" to "albums" some years ago, but didn't announce it? All the API documentation still refers to "sets" and makes no mention of "albums". I couldn't find any kind of announcement about it. Weird. I don't use Flickr personally, so I didn't notice as a user. In any case, I think I've updated the plugin to reflect this no-longer-new nomenclature.

Properly handle album names with double quotes in them.


Fixed the problems some folks have been having with Flickr with the previous version. The underlying error was my fault, but it wasn't apparent because Flickr responded with a "we're having technical issues" response..

Added the SST1, SST2, and SS3 tokens to the template tokens that the plugin understands.

Sometimes Lightroom loses the "Visit At... " link for a publish collection; dig harder to come up with it anyway.


Input fields that accept a location can now handle a What3Words code and a Plus Code.

Clicking on the version number in the Plugin Manager now copies version info to the clipboard

Updated the PublishCollectionName token to allow numeric arguments along the lines of the CollectionName token.

Added the folowing template tokens: {home}, {desktop}, {temp}, {pictures}, {documents}, IptcDateTaken

Added the 'PCH' variable to the {LUA} tag.


Fixed a bug when 'Token Examples' invoked in certain situations.

Added a bunch of token filters: F2D F2S F2X B2D B2S B2X S2X A2D A2S A2X


Added the {NonSmartCollectionNames} and {NonSmartCollectionFullNames} tokens to the data templates that my plugins understand.

When encountering catalog corruption, present a better error message.

Added some extra debug logging.

Updated the Keywords token, and added the KWf function to the {LUA} token.


Flickr has been having a lot of technical difficulties lately, so try to report on this better when it happens.


Oops, more Lr7 stuff.


Updates for Lightroom 7


Better handle some character-encoding issues related to template tokens.

Allow the "If Exists" feature of template tokns to work with the PluginProperty token.

Update registration support to handle a stupid bug at PayPal that PayPal refuses to fix )-:


Fixed a bug introuded the other day in template tokens, related to Windows filenames.


Added the "only if it has a value" feature to template tokens.

Updated the {FolderName} token to allow {FolderName=1} (rather than requiring the plus as in {FolderName=+1})


It seems that Flickr now has a pubished limit of 75 tags per photo. It's good that this limit is published, but it brings up the question as to what to do when a photo has more than that limit. For the time being, tags added via the "extra tags to include" have the highest priority. Then image keywords. Then machine tags from the city/state/etc. If there are too many image keywords, the shortest ones are dropped off until the list is under the limit. For the time being, if there are too many keyword, extras are dropped silently.

Added the Newline template token.

Enhanced the FolderName token


Added the following tokens to the template tokens that my plugins understand: Artworks, ArtworkTitle, ArtworkCopyright, ArtworkSource, ArtworkCreator, ArtworkDateCreated, ArtworkInventoryNum


Ratings are no longer fetched for every photo after every publish operation... ratings are now lumped with comments and controlled by the "Importing Comments from Flickr" options.

Added "ISO8601Date" to the template tokens that my plugins understand.


Oops, yesterday's update caused all photos sent to Twitter to be marked as sensitive.


Retooled to use a new Twitter API, allowing photos not to take up any characters in a tweet.


Added some debug logging for the comment-fetch avoidance stuff.

Better dialog real-estate managment for the meatadata section.

Added Weekday, Wday, weekday, and wday to the list of template tokens that my plugins understand.

Fixed a bug with the keyword tables in the LUA token.


Removed the hard limit on pixel size for uploads to Flickr. The limit that used to be there was an undocumented limit due to a bug on their side, but it now seems to be fixed.

Added the following tokens to the templates that my plugins understand: FileModYYYY, FileModYY, FileModMM, FileModDD, FileModHH, FileModMIN, FileModSS, FileYYYY, FileYY, FileMM, FileDD, FileHH, FileMIN, FileSS.

Fix for Lightroom 2. Support for older versions of Lightroom will be stopped soon.

Got around a situation where Lighroom would crash duing an export of large images.


Exclude "Auto Upload" from the list of sets... Flickr doesn't allow manual additions to that set.

Added the {FilenameNumber} token to the templates that my plugins understand.

Some updates to support Lr2. Lr2 is sufficiently old that I will drop support for it soon.


Work around a bug in Lightroom in how dates are computed for shipment to Flickr.


Try to avoid yet another place where Lightroom gets hung because it can't handle certain kinds of dialogs at the same time.

Add some extra debug logging.

Fix to get around a Mac display issue with Lr6 on OSX.

Added Russian-langauge support for the People-Support {People} tag.


Updated for changes Flickr apparently made to the licensing notations, but neglected to document. "Public Domain Dedication" and "Public Domain Mark" are now supported, and "US Government Work" has been removed. Also works in coordination with Creative Commons plugin which has seen similar updates.

Updated Twitter support to better count lengths of tweets that include URLs.

Added ChildOf and DescendantOf filters to the {Keywords} and {KeywordsAll} template tokens that my plugins understand.

Fixed a bug with the 'edit saved credentials' dialog.

Fixed how custom {People} formatting works with people keywords that have no birthday associated with them.


Updated the Caption part of the dialog to show up to three lines of text, and the full text in the tooltip.

Added {SpeedKPH} and {SpeedMPH} to the list of template tokens supported by my plugins.

The {People} token wasn't working properly for some keywords without a registered birthday.

20150712.380 Fix some inefficiencies when creating a new set on the fly in a Publish Service.
20150612.379 Flickr seems to sometimes be returning garbage data in photo group/pool lists, so try to filter that out.

Fixed the "SpecPeople:259: attemt to index al nil value" error.

Clicking on the example caption in the export dialog now brings up a dialog showing the whole example caption, which is useful to see the full thing when it contains multiple lines.


When creating a new set for a Publish Collection, explicitly note if the new-set name conflicts with an exsiting set's name, rather than just silently disallow the creation.

Some metadata updates could be considered failures when they were not.

UI fix for OSX 10.9

20150301.376 Added some debug logging to track down a group-pool issue.

Fixed an assert-failure bug that could happen when editing a collection's settings.


In the POODLE-vunerability dialog, display a raw URL of a page on my site that discusses the issue, so that folks can be independently sure that the dialog is indeed from me and not malware.

20150131.373 Build update.

Added support for the {People} template token, which works in conjunction with my People Support plugin to automatically include in upload captions and the like the names and/or ages of people in a photo.


The location part of the "import metadata from Flickr" feature was broken.

Fix to the date_diff() function supported by the LUA template token.

The Plugin-Extras dialog to resend metadata could allow the [Resend] button to be pressed when no metadata was selected, resulting in confusion.

Updated the camera-name code to try to guess the actual camera model of Hasselblad H5D files, since in their infinite wisdom Hasselblad decided to encode three distinct models with the same internal code, making it impossible to know for sure what camera produced a given image file.

The manual-association dialog didn't recognize Flickr photo URLs that do not end with a '/'. Apparently Flickr sometimes omits the trailing '/'.

Add a note to Flickr's intermittent "Filetype was not recognised" error to let people know that there's not much one can do but wait to try again later and hope for better luck.


If the remote site sends back garbage during the authorization handshake, properly report the error instead of crashing.

20141215.369 Try to work around a display bug on a MBP for the smart-collection edit dialog.
20141210.368 Registration was broken on Lr2

Added an 'Export Location Override' section to the Publishing Manager dialog (when editing an existing publish service) that allows you to change the Export Location. I don't know why Adobe doesn't let you change it.


Use a compressed view on the Plugin Extras dialog if the screen is not very tall.

Experimental: try to avoid networking issues on slow connections with an explicitly long timeout.

When associating a Lr image to a Flickr image manually, incorporate the actual posted time to Flickr as the upload time in the photo history in Lr.

20141127.365 When Flickr is having "issues", as seems to be common these days, they sometimes return huge HTML pages instead of API data, and this sometimes caused huge dialogs that required a force-kill of Lightroom.

Better debug logging of Twitter interaction.

Very long tweet text could break the dialog display.

Don't allow expert when we know ahead of time that the tweet is too long.

If twitter rejects a tweet (e.g. because it's too large), show the tweet and offer to allow the user to edit/resend at


Added extra logging to debug why Lightroom might fail to render for export

20141019.362 Windows Only: Add a one-time check for the POODLE security vulnerability, and alert the user if it exists.
20141017.361 Update to the Flickr remote server to contact for uploads.
20141010.360 Better error reporting with the visit-collection item in Publish.

Added the ability to quietly (or semi-quietly) ignore over-limit group pools in Publish.

Plugin could get confused, not realizing that a photo has been removed from a group

Better reporting when a group-pool submission is rejected due to the nature of the submission (e.g. it's not geoencoded when the pool requires that it be).

20140923.358 Added the LrMD5, LrLocalization, LrSystemInfo, and LrMath packages to the {LUA} template token.
20140922.357 Group Pool dialog UI fix
20140902.356 Allow PNG originals (with any Lightroom changes ignored) to be uploaded.

Made the {GPSAltitude}, {Altitude}, and {GPSCoordinates} tokens subject to the geo-privacy settings like the other geo-related tokens.


Updated the Twitter support to allow my plugins' template tokens in the tweet text.

When on a system with a small screen, try to make the resend-metadata dialog shorter.

20140731.353 Registration fix for Lr5.6
20140729.352 Previous updates broke support on Lightroom 2
20140720.351 More Creative-Cloud support.

Fixed an issue with Creative-Cloud revalidation.


The "Claim" feature in Publish wasn't setting the "View photo at FLickr" URL.


Lr5.5 and later Creative-Cloud installs can now revalidate themselves if needed.

20140710.347 Sigh, had a bug in the Creative-Cloud support.

Now supports Lr5.5+ Creative-Cloud Installs.

20140704.345 Sigh, introduced an error for some folks with the rebuild the other day.
20140630.344 Build-system update
20140617.343 When sending the user's browser to Flickr, do it to the HTTPS version of the page.

Added date_diff() and raw_time_diff() functions to the special {LUA} token understood by the plugin.


Add a note to the Keyword options to highlight that only exportable keywords are considered


Set up the ability to reauthenticate to your Flickr account from the Publishing Manager dialog.

Added the ability to restrict machine tag location items.

Added the geo:location machine tag.

Yikes, the "geo:country" machine tag was misspelled as "geo:countrys".

20140519.339 Added an option to not explicitly send the "Date Taken" info to FLickr.
20140510.338 A missing 'automatic destination' could cause the plugin to crash.

Added new tokens to the template language the plugin understands: LrVersion, LrVersionMajor, LrVersionMinor, LrVersionRevision, LrVersionBuild, CatalogName, CatalogPath, OperatingSystem, OS

Added new token filters: NS and LO


Fixed a bug in the "smoother revalidation" stuff recently added.

20140422.335 Manual url-to-image association didn't work with https urls.

Fixed a sublocation-related bug in the new geo-privacy stuff.

The {Empty} template token wasn't working properly.

Make the revalidation process smoother, especially for folks using Lr5.4 and later.

20140407.333 Fixed an error during catalog upgrade.

Note: updating to/past this version will cause a silly catalog-must-be-updated dialog to pop up once. Just answer "Update Catalog".

Fixed auto-destinations in Publish smart collecitons.

Moved all Flickr API interaction to secure https. Flickr's prior http API was secure against an attacker accessing your account, but not against an attakcer sniffing information exchanged between Lightroom and Flickr. Now, only Flickr, Lightroom, and the NSA can see the data exchanged.

Added the "Recent Flickr Comment" custom metadata item, which holds the date of the most recent comment for a Published photo, in YYYY-MM-DD format. While in the "Published Photos" section of the Library Grid, you can set the Filter to "Recent Flickr Comment" and then scroll down to the end to see the most recent dates, and via that see the most-recently commented photos. It's a bit unelegant, but it's the best I can think of within the severe limits of Lightroom's plugin infrastructure.


The new Location Privacy stuff added recently didn't work properly from the resend-metadata dialog.


Added support for my Creative Commons plugin, to allow that plugin's per-image settings to translate to Flickr license settings.


Added a new "Location Privacy" section to the Exprt/Publish dialogs.

Updated the location-based tokens in the template language the plugin uses — City, State, Country, Location, Latitude, Longitude — to respect new privacy options in the Export/Publish dialogs, and in the resend-metadata dialog. You can override those options on a case-by-case basis with the evenIfPrivate filter.

Added locationIsPrivate variable to the environment available to the LUA token.

Now properly remove location at Flickr during a resend if it's been removed/hidden in Lightroom.

During a normal export that performs an image-replacement at Flickr, you can now choose to replace the image metadata as well.

Auto-destination smart publish collection rules couldn't be edited.


Flickr doesn't allow (no longer allows?) videos to be replaced, so check at the start of an export to see whether we'll run into this, and abort the export if so. This'll save having to wait until you've spent an hour rendering a bunch of videos before being told you can't do it.

Enable a new feature internal to Lr5 for large exports that keeps the CPU from running too far ahead of the upload. Prior to this, Lightroom would go ahead and peg the CPU to pre-render all the images even if they weren't being uploaded at nearly the same speed. Now Lightroom pauses the behind-the-scenes rendering if it has gotten too far ahead of the upload.

20131113.326 Oops, the previous update had a bug.
20131113.325 Enabled the "Visit photoset at Flickr" publish-service collection context-menu item.
20131104.324 Replaced the "check status" code introduced in 20131023.321 with better code I'd already had written for other plugins but had forgotten about... a testament to how complex these plugins have gotten, and how bad my memory has gotten.
20131029.323 Some UI tweaks, and some extra debug logging.
20131025.322 Fix a problem that could pop up with importing GPS data from Flickr.

Added (to File gt; Plugin Extras) the ability to check the remote status to see whether uploaded photos are still there, and clear out data from the catalog when they are not.

Added a way to set the visibility at Flickr via the star rating.

Added keywords to the list of metadata that can be imported back from Flickr.


Gave the Publishing Manager UI some attention on Windows.

Added the “:EMBED” token filter to the template language.

20130926.319 Oops, fix a bug introduced in the previous update

Added a bunch of tokens to the preset templates supported: ExportFormat, ExportColorSpace, ExportBitDepth, ExportQuality, ExportSharpeningLevel, ExportSharpeningMedia, IpernityUrl, GoogleDriveUrl, and TumblrUrl.

The token-examples dialog had been broken. Also deprecated Folder and Path tokens in preference to FolderName and FolderPath tokens.


Work around a Lightroom bug concerning the determination of whether a photo is offline.


Added the ability to import titles, captions, and locations from Flickr back into Lightroom.


Fixed the KW/KWE tables in template tokens; they had been broken when using load for the script.

Better handle very long user account names, so that the [Logout] button doesn't get cut off of the Export dialog.


Made big updates to the "Export with Smart Previews?" section; you can now pick to be asked whether to export via Smart Previews, and can differentiate between when the Smart Previews are "good enough" for an export and when they are not.

Flickr servers have been increasingly flaky for some users, returning empty responses, so try to catch this and report it as such to the user.


Added an "Ask" option to the "Export with Smart Previews?" section, so one can be alerted to the situation at each export.

Moved the "Export with Smart Previews?" dialog section to a more-logical place in the order.

Avert an "FlickrCleanupAndSync:478: bad argument #1" error.


Work around a bug that causes the export-related progress bar to not show up right away.

20130613.311 Better support for plugin revalidation.
20130612.310 Flickr underwent a huge change recently, but they still haven't updated the docs that third-party apps like this plugin use. But it seems that non-Pro accounts can now replace photos, so this update allows for it.
20130611.309 Sigh, previous update for Lr5 broke things for the Lr5 beta.
20130611.308 Yet another Lr5 update
20130605.307 Better logging to try to understand catalog-write-access contention under Lightroom's hood.
20130524.306 Apparently, a recent change broke things on Lr2, which some folks apparently still use.

Added the ability in Lr5 to export images even if the master image file is not available, so long as there's a smart preview available.

20130519.304 Addressing some issues with Publish.
20130501.303 Update for Lr5
20130416.302 In some cases the add-to-new-photoset feature could create multiple sets of the same name.
20130412.301 Fix to the Twitter fix.

Sigh, Twitter yet again made an unannounced undocumented change to their API that immediately breaks apps that have worked for years, and doesn't even bother alerting developers after the fact. Lord knows how many developers wasted how many hours trying to debug something that should have been announced on the developer's blog. Days later, it's still not announced there. Twitter is not worse than Facebook, but seems to be trying.

20130328.299 Fix for the registration system.

Update the endpoint for the after-export "Describe this upload" page at Flickr, to get around a redirection bug on their side.

Some UI cleanup in the export dialog.


Export could crash if a too-big-for-the-remote-service video upload was attempted.

Fixed a possible plugin crash in Lr2 that might happen if the remote site's servers are failing.


Added support for some new template tokens: FlagStatus (requires Lr4.1 or later), and for Lr3 and later, a bunch of IPTC extended metadata: AdditionalModelInfo, CodeOfOrgShown, DigImageGUID, Event, ImageSupplierImageId, MinorModelAge, ModelAge, ModelReleaseID, ModelReleaseStatus, NameOfOrgShown, PersonShown, PlusVersion, PropertyReleaseID, PropertyReleaseStatus, and SourceType.

20130214.295 Small fix for Lr2
20130209.294 Update to handle new Twitter url-length settings.
20130206.293 Update the Twitter-related code to handle their new API. Their old API goes away next month.

Added the ability to use "automatic destinations" (the naming of target galleries based upon image metadata) in Publish. It's been in Export for years (as illustrated in this 2008 article on backing up), and you must create the destination presets from Export, but you can now access them in Publish.

Added the ability to set the caption on a one-off basis by just typing it in, avoiding the need to make a preset each time.


A lot of work on the upload data path, making it more efficient and restoring the ability to retry the attempt on certain errors.

Handle a complex interaction between virtual copies and smart publish collections when deleting.

20121203.290 Add a link to the FAQ for the "missing destination cookies" error.
20121102.289 Handle deleting publish-service sets. Actually remove from sets/groups when requested to when deleting an entire publish collection or set.
20121020.288 A recent optimization for Lr4 broke support for Lr2.
20121017.287 Plugin was blocking export due to DPX-video format in some cases where Lightroom didn't allow the format to be changed.
20121016.286 Worked around the "handle in the wrong state" error... shouldn't see it anymore, I hope. Seems to be some very weird interaction between Windows and Flickr.
20121014.285 Added a help dialog when encountering the mysterious 'handle in the wrong state' error.

Workaround for an "attempt to call field 'getProgressScope'" bug introduced in Lr4.2.

Enhance the {EMPTY} template token so that it interrupts the squelching of superfluous joining characters.

20120905.283 Don't require the selection of a photoset when creating a new publish service, because it's okay to publish just to the photostream.

Updates to the environment in the {LUA} token (in the template tokens in my plugins) to include photoTime() and currentTime(), and other changes to match the updated docs at that link.

20120728.281 Added the ability to create per-set publish collections in bulk from the Publish Services settings dialog.

Flickr seems to have a hard limit of 134,217,728 total pixels (if square, about 11,585×11,585), returning a "Filetype not recognised" error when exceeded. The plugin now watches out for this and aborts such uploads.

Handle more gracefully when the target set of a publish collection has been deleted at Flickr.

Wow, it seems some people using Lr2 are still using very old versions of Lr2 that aren't up to snuff feature/bugfix wise. I don't want to support gratuitously old stuff, so I put a minimum of Lr2.6 to use the plugin.


Fixed an error in how the plugin recreates a photoset that had been deleted at Flickr.

Report in a nicer when when the preset for the image title or description is lost.

20120616.278 The control-via-keyword stuff (e.g. whether an image should be public, etc.) didn't work with non-ASCII keywords.

Very slow uploads in Lr4.1 could cause the new progress bar stuff to blow up.

Twitter support now allows suppressing "Private" geoencoded locations in Lr4.1+


(See my blog post “Hidden Gems in Lightroom 4.1; Hidden Gems in Lightroom Plugin Development” for some details on what's new in this update for Lightroom 4.1.)

Substantial updates to the geolocation privacy stuff. Lr4.1 proper (the actual Lr4.1, not the 4.1RCs) allows the plugin to know whether a photo's location has been marked as private, so the plugin can now respond to that and exclude the geoencoded location in such situations. New options have been added to export and to metadata-resend operations; they default to excluding private locations.

New upload engine in Lr4.1 that greatly increases the efficiency of large uploads. In Lr4.0 and older versions, upload handling is inefficient and large uploads can crash Lightroom, but from Lr4.1 you can easily upload up to Flickr's maximums.

If Flickr requires reauthentication, flush the cached credentials so that the user doesn't keep trying to authenticate with them.

Update to handle the Mac App Store version of Lightroom.

More updates for Flickr's new API... don't try to resend a call that fails due to timeout, since that can end up reusing the call's nonce, and Flickr will reject it if the resend eventually succeeds.

20120514.275 Still working through lingering issues with the move to Flickr's new API on Lr2. I moved on from Lr2 years ago... I wish everyone would.
20120508.274 Yikes, Lr2 registrations were broken again.

Tweak for Lr4.1RC2.

Fixed the “photo too large to tweet” dialog message, which had been all garbled up.


Added options to allow geo-visibility settings to not be explicitly set.


Fixed a potential crash when processing some captions.

Enhanced the send-log dialog to hopefully make reports more meaningful to me, yielding, I hope, the ability to respond more sensibly to more reports.

Added to the template tokens supported by the plugin: {FullMasterFile}, {FullMasterFolder}, {FullExportedFile}, and {FullExportedFolder}.

20120406.270 More graceful handling when a caption preset has gone missing. The various export items controlled by keywording now allow for a comma-separated list of keywords (if any of the listed keywords match, the item matches.)
20120330.269 Update to handle 4.1RC
20120327.268 More graceful handling of videos whose pixel size is not known.
20120321.267 Handle Lightroom internal catalog write contention more gracefully.
20120317.266 Couldn't create a new set in Publish if the set name had no ASCII letters. Doh!
20120312.264 Handle better when Flickr authentication fails. Can now reauthenticate directly from publishing manager. Fix registrations in Lr2.
20120308.263 Update to the debug logging to better track down timing issues that might arise.
20120303.262 The recently-added "Lightroom doesn't handle large uploads well" check/dialog didn't play nice. Does now.

Lots more preparation for Lr4 (but still works in Lr2 and Lr3).

Lightroom's internal infrastructure doesn't handle large uploads well, and will most likely crash when trying to upload huge videos, so I've not added a warning and the ability for the user to decide when it kicks in.

Files that are offline are now detected before an export/publish begins, and if there are any, offers the option to abort the export, or just skip the offline ones. This is a lot more clear than the "dng_error_file_not_found" error you get from Lightroom if you follow through with an export attempt of an offline image.


Beefed up some internal debug logging, and fixed a crash introduced in the previous version.


Total upheaval in the deep-down Flickr code to move to their new authentication method. Unfun.

Discovered why "metadata that triggers a republish" wasn't reliable, and fixed it.

More on the march toward Lr4, including upheaval in the code to handle Lightroom APIs being discontinued in Lr4.

When replacing a photo, update its “date taken” time at Flickr (in case it had been changed locally).

Bumped up the minimum Lr3 version to Lr3.5, to ensure we've got those bug fixes. Lr2 and Lr4 are still supported, of course.

Added the {AspectRatio} token to the token templates understood by the plugin, and added the Length=num filter.

Attempt to prepare for changes Twitter has announced will take place in how they return information about server errors.

20120114.258 More tweaks for Lr4b

Update for Lr4 beta: explain in the plugin manager that the plugin can't be registered in the beta.


Removed the “Re-mark as Published” button from the plugin-extras dialog in Lr4, because Lr4 now supports this natively.

Moved the Twitter code over to a new style of Twitter authentication, in hopes that it cures the authentication problems some people have been having.

Moved all access of Twitter to HTTPS.

Removed an obsolete reference to from the Twitter help dialog.

20120103.255 Seem to have broke group-pool uploads in a recent build; fixed.

Pushing out a new build after updating my build environment


Enabled export snapshot creation in Publish.

Added extra logging to try to debug slowness with remark-for-publish.


Finally figured out why the plugin was not allowing image deletion in some smart-collection situations.

Better error handling for video export, and for when images/videos exceed upload limits.

Warn about the need to update the list of albums if it's not been updated for a long time.

The Lightroom bug referenced in the version note for 20110623.227 was fixed in Lr3.5, so I've removed the special workaround processing for that version and later.


Had issues with the registration button sometimes not showing.

Updated how the Manual-association dialog is sized.


Fix an “attempt to concatenate field 'user_id_string'” error that pops up at rare times.

Added a system-clock check and reports to the user if the system clock is more than a minute out of date. An incorrect system clock can cause problems with various kinds of communication and authentication with some of my plugins, so I've just gone ahead and added this to every plugin.


When doing a plugin upgrade, offer the ability to flush all the old copies of the plugin.

Clarify some info messages about deleting photos from smart collections.

20111025.248 Make some effort to support image update on free (non-Pro) Flickr accounts, turning an “update” option into an “upload a new copy, delete the old copy” operation. Non-pro support won't go much further.

Publish repopulation could fail with write-gate timeouts.

Reporting some errors can create a huge dialog box that can be difficult to close on OSX, so this update adds a [X] button in the upper right of the dialogs.

20111004.246 Plugin would crash in some cases while trying to process Twitter-related settings.
20110904.245 Handle errors more gracefully when attempting to update online comments for photos that no longer exist.
20110903.244 Added {PluginProperty} to the template tokens used by my plugins.

Added the ability to omit city/state/country as keywords when sending Lightroom keywords. Flickr has always had an inexplicable policy of extracting the city/state/country from the image and adding them to the online copy as keywords, and the plugin has long mimicked this, but if you strip these metadata fields from the exported copies, you may not want the plugin to mimic what Flickr would have done, so it's now an option.

Some internal optimizations to handle large gallery sets.

20110830.242 It seems Flickr's API error codes are not consistent across all methods, so the plugin was misinterpreting the results in some error situations.

Gave the Twitter tweet input UI some attention.

Twitter automatically replaces URLs with their own urls, and the tweet-text character-counter now takes that into account, so pasting in urls of any length now “costs” a fixed amount (currently 19 characters for an HTTP url; 20 characters for an HTTPS url). The plugin no longer uses

Made it so that hitting ENTER while entering a tweet does not actually launch the export. This is a maddeningly-frustrating aspect of the Lightroom plugin infrastructure, but I've worked around it in a way that seems to work.


Updates the yesterday's changes to that Lr2 works as well.


Added the ability to include a photo when issuing a tweet via Twitter.

Fixed a problem when fetching comments.

Fixed “attempt to compare nil with number” error that some users might have gotten in Publish.

20110802.238 The upload-destination list was getting cut off again.
20110729.237 The 'refresh list' button was missing from the upload-destination list when it was configured to be a popup menu.
20110712.236 More on the “Missing destination cookies” bug...
20110712.235 Had a minor plugin-crashing boo-boo in the previous update
20110711.234 Really long captions could cause a stack overflow. More on the “Missing destination cookies” bug.
20110710.233 Trying to debug the mysterious “Missing destination cookies” bug...
20110708.232 Fix the “Export:663” error some have gotten.

The manual-association dialog was too big for some screens... now it auto-adjusts depending on the screen size.

20110705.230 Still debugging recent Lr3 changes.
20110703.229 For Lr3, tries to address a similar catalog-access errors that seem to have started popping up in some cases.
20110703.228 For Lr2, fixes a 'must be called inside withReadAccessDo' error I'd recently introduced.

There's a bug in Lightroom that causes it to sometimes include private keywords in exported copies. The plugin now detects these situations and alerts you to them, allowing you to avoid a privacy blunder.


Export presets, when selected in the Export Dialog, didn't handle switching the Flickr account properly if indeed the export preset was for a different user. It should work now, but Lightroom's plugin infrastructure makes this a very fragile operation, so keep your fingers crossed.

More robust publish service stuff. Lightroom's infrastructure is full of bugs in the Publish Service area, but I think I've worked around yet another one that pops up from time to time.


The “do not explicitly send keywords from Lightroom's catalog” option was not being honored in Publish.

Large group-pool names could cause problems with the group-pool section of the export dialog.

Fixed the “Flickr 109” error some users were getting.


Better handle long set/group names by truncating at the beginning with '...', and having the tooltip be the full name.

Try to squeeze the Sync dialog a bit for smaller screens.


Fixing some problems with Lr2 that the comment-refresh thing the other caused.


Fixed a bug that caused the export destination to not properly refresh in response to selecting a preset in the export dialog.


Added a new section to the Publish Service settings dialog, on whether to refresh remote comments (at Flickr back into Lightroom) automatically or only manually.

Be more robust to errors during the gallery-creation process.

20110513.219 Fixed a bug in how some export errors are reported
20110419.218 Wasn't properly issuing an error message when used with Lr3.0 and Lr3.2.

Added the ability to select which metadata items cause a Publish republish.

Fixed some plugin-crash asserts that some new users might get.

20110309.216 The list of upload destinations was sometimes getting cut off.
20110304.215 Added a new dialog (via a button in the Publishing Manager) to sync set/group membership between the Publish Service and Flickr, for photos already in the Publish Service. You can use this, for example, to auto-create publish-service collections for all the sets and/or groups the photos belong to at Flickr. It's exceedingly complex under the hood, so I'll label this “beta”: a catalog backup is suggested before giving it a try.
20110207.214 Added a progress dialog to the “Re-mark as Published” operation, so that it can be canceled, and to make it clear that something is going on under the hood.

Giving a try to a manual option to associate images already at Flickr with catalog photos. See “Associate Images Manually“ in the Plugin-Extras dialog (“File > Plugin Extras > Flickr Extras”).


Added “Re-Mark as Published” to the Plugin-Extras dialog (“File > Plugin Extras > Flickr Extras”). If you have published photos in the “Modified Photos to Re-Publish” grid segment, this moves them back to “Published Photos” without actually uploading anything to Flickr. You might use this after making what you know to be a metadata-only change that won't affect how the image is shown at Flickr. If applied to published photos selected via their presence in a sub collection, it also re-marks the version in the base photostream as published.

Fixed a problem such that long album names caused buttons to become inaccessible in the export dialog.

Not sure what happened to the export dialog since I last checked it in Windows, but it was in need of some UI love.

20110116.211 Added Twitter support to Publish.
20110115.210 The “Import from Adobe's Flickr plugin” would die if some photos added to that plugin's collections had not yet been published.
20110113.209 Added {CroppedWidth} and {CroppedHeight} to the template tokens used by my plugins.

This version no longer works in Lr3.0 and Lr3.2 because many bugs have been fixed in Lr3.3: if you're using Lr3.0 or Lr3.2, please visit Lightroom's Help > Check for Updates to download the free update from Adobe. (The plugin also continues to work in Lr2.)

One of the bug fixes in Lr3.3 allows me to correct a problem when editing a Flickr Publish smart collection. It used to be that you couldn't save it if you only made changes to the smart-collection rules, but now you can.

20101217.207 Updated Twitter support for Twitter's new API endpoints
20101124.206 Fixed a crash sometimes encountered while updating remote-account data in the plugin.
20101107.205 Slowly getting back into the swing of things after September's arm pain and other issues... added the ability to create a set on the fly in Publish (it's been in Export for years, but was much more of a challenge in Publish). Fixed some errors that would pop up when deleting the last image from a set. Other cleanup.

Fixes “Spec:343: attempt to index field '?' (a nil value)” error some were getting.


First update in a while due to my arm-pain issues....

Holy cow, I finally realized that Flickr has conflicting exactly-incompatible ways to specify inclusion or exclusion from public-image search, depending on what API call you're using. It's such a completely-stupid haphazard design that it never even occurred to me that a company as clueful as Flickr would let something like this slip through. I'll add a note of warning here for other Flickr developers: setting “hidden” to “1” during a photo upload marks the photo as explicitly unhidden form public searches, but setting the same value to the same parameter in marks the photo as hidden! Due to the complexities of the plugin (which has four different upload flavors.... initial upload and replacement upload in normal export, and initial/replace in Publish), it took me quite a while to reproduce this bug and figure it out. Sorry for the delay.

Publish was sometimes getting stuck in a 'not logged in' state, if you hadn't refreshed your account data in the plugin for too long a time.

Warn about the loss of metadata if the “resize to megapixels” option is used.

20100829.202 Made the revalidation process much simpler, doing away with the silly need for a revalidation file.
20100824.201 Extra debug logging.
20100823.200 It seems Flickr changed their API on image visibility (?) or I was blind before, but in any case, images should no longer get hidden to public searches unless you ask for it. (Update: actually fixed in 20100930.203; see comment there.)
20100820.199 Discovered a bug in my plugin build system that caused horribly difficult-to-track-down errors in one plugin, so am pushing out rebuilt versions of all plugins just in case.

Added code to allow plugin revalidation after having been locked due to a bad Lightroom serial number.


Fixed a bug that caused a plugin crash if you changed your Flickr username.


Some users were getting errors about withCatalogDo being deprecated in Lr3. Not sure how this could happen, but I've removed the references from some old code so hopefully won't run into them again.

Added the {KeywordsAll} template tag.

A few users found some photos to always be “stuck” as Modified photos in a Publish collection. I'm still not 100% 8 what might be going on and can't replicate the issue myself, but this version of the plugin tries some things to hopefully alleviate the problem.

20100715.195 There was a bug on Windows that caused the warning about potentially-excessive JPEG quality settings to lock up Lightroom for an indeterminate amount of time. Only way I could fix it was to move the warning to the metadata management section (where it doesn't belong as much as it doesn't belong where it was before, but Lightroom doesn't let me put it where it should go, next to the jpeg-quality slider). This also allowed me to put it back into Publish.
20100715.194 Oops, the JPEG-quality thing added in the previous version wasn't bypassable in Publish. Sorry about that. Removed it for Publish for now until I can figure out a better solution.
20100714.193 The plugin-extras stuff was broken in Lr2.

The plugin has long remembered your export settings from Flickr export session to Flickr export session, overriding Lightroom's desire to always bring your recent export settings from non-Flickr exports. However, I had neglected to update the list of settings for Lightroom 3, so this is now corrected, and so the plugin now also remembers watermarking settings, file-renaming and photo-stacking, and DNG compatibility.

Added a warning that blocks export when the JPEG quality is set needlessly high, referring users to my Analysis of Lightroom JPEG Export Quality Settings. You can bypass the warning if you like, and hide it forever, of course.


Fixed a bug introduced in 20100623.177 that caused all images to be hidden from public searches. If you uploaded photos with affected versions and want them to be searchable, you'll have to update the settings at Flickr. Sorry for the hassles.

Fixed a bug with the auto-destination dialog.

Made a squished version of the create-smart-published-collection dialog, for those with tiny screens. Lightroom doesn't give much latitude in this respect, but I took a stab at it.


More auto-login rough edges being smoothed....


Still trying to shake out some rough edges with the login caching stuff necessitated by Publish. Makes my head spin. Hope this update helps.

Be more graceful (and quiet) when Publish is used while there's no Internet connection. My apologies to the airport-lounge road warriors besieged by “no Internet” messages.


Discovered some rare and complex bugs related to collection renaming, and (I hope) fixed them.


Finally pushing the new version out of plugin beta (where it has been for a couple of weeks), after eight months of oft-painful development. It's extremely complex under the hood, so now that it's getting wider user and additional bugs are shaken out, there will likely be frequent updates... please keep an eye on the version history when you update.

Here are the update details from when it was in beta:

20100608.167 — New registration system for Lr3. Registrations in Lr2 continue to work in Lr2, but the plugin reverts to unregistered in Lr3.

Many, many changes under the hood.

Real Publish support in Lr3. Only seasoned Publish plugin developers will possibly appreciate how monumental a task it was to get this working..

Better support for users with multiple Flickr accounts.

Added some options to the Twitter <dest options> special code: add simple as an option to have it become just the name without quotes or other adornment; add short to par down the gallery name to just the leaf name. They can be combined, e.g. <dest short simple>.

Added some stuff to the LUA template token: a version of the standard os table (with date, difftime, getenv, es and time), and the standard Lightroom STK tables LrDate, LrPathUtils, and LrStringUtils). Also added a new functions TBL() (returns an empty table), ne(item) (returns true if the item is not empty), and nb(item) (returns true if the item is not blank; “ ” is blank but not empty, while “” and nil are both blank and empty).

20100609.168 — Fixes the “attempt to compare string with number” error.

20100609.169 — Fixed problems related to the catalog upgrade for the plugin, where it couldn't figure out the Flickr details of some usernames, and couldn't report the usernames properly.

20100609.170 — Learn to spell “aperture” properly.

20100611.171 — Was running into problems in some situations when previously uploaded images had been deleted at Flickr without the plugin knowing. Group-pool stuff wasn't working (doh!).

20100611.172 — More life on the cutting edge... some early adopters may get a dialog asking them to refresh the settings in their export dialog or publish-service settings-edit dialog. Sorry.

20100611.173 — D'oh! Hadn't handled the case of a publish collection going to only groups and no sets. Fixed.

20100613.174 — Found another booboo.

20100614.175 — Broke the build for 32-bit machines sometime yesterday... fixed.

20100620.176 — Fixed and error encountered after publishing a photo that had been part of a collection, deleted, then re-added.

Hah, couldn't use the plugin with a new catalog. D'oh! Fixed.

20100623.177 — When republishing, make sure to refresh the metadata at Flickr. More logging to try to track down bugs reported in the previous version.

20100624.178 — Fixed the issue with renaming the photostream collection.

20100624.179 — More logging to track down some bugs I can't reproduce.

20100624.180 — Couldn't edit caption presets while no photo selected.

20100624.181 — Discovered a nasty build bug; should fix errors many have been seeing.

20100625.182 — Yikes, shaking out some more build issues.

20100628.183 — Working around more bugs... this time with deletion from smart collections.

20100628.184 — Fixing errors with automatic destinations, I think.

20100628.185 — Various fixes, including handling virtual copies (created on images uploaded with this version or later).

20100629.186 — Lots of changes... fixed the “visibility at Flickr” stuff that got broken a few days ago. Bolstered the separation between Publish and non-Publish exports.

20100629.187 — Lots more changes, especially related to auto destinations and replacing images. Identified that “Import Smart Collection Settings” does not work for Publish, and corrupts things. Don't use it.

20100324.166 Figured out a way to make the LUA template token work in LR2 and LR3b1 as well. Internally it's an amazing kludge of inspired proportions, but externally it appears the same as in LR3b2.

Removed some LR3-related debugging stuff that's showing up now that LR3b2 is out. All plugin-related things should work in LR3b2 except Publish, which will likely change drasticly between now and when LR3 is actually released.

New when running LR3b2 is a new “Snapshots on Export” section, which is basically a built-in version of this new plugin.

20100321.164 Oops, introduced a bug that disabled some of the token processing... should be fixed in this one.

Added three new tokens to the templates that my plugins use, IfKeyword, IfExportedKeyword, and (for LR3b and later) the very powerful LUA. See the templates page for details.


Wholesale changes that attempt to honor the user's locale settings for numeric display (e.g. Europeans writing 3,14156 for pi). I've probably missed some spots, so let me know if you find some.

Added three new tokens to the templates that my plugins use, CameraName, IfGeoencoded, and Keywords. See the templates page for details.

20100306.161 Try a bit harder to work around a Lightroom/Flickr bug that causes non-ASCII in tags to create a corrupt version of the tag at Flickr.
20100216.160 More bugs... a fix for one bug tickles another... getting lost in a maze of workarounds...
20100216.159 Wow, ran into an esoteric Lightroom bug tickled in the previous version that caused the plugin to take on a new identity, internally, and so presets that referenced it no longer worked. Took hours to track down... sigh. I've fixed it in this push, but one side effect is that history about any uploads or other changes made with the previous version are lost (so you may want to reupload just to get the history stored properly).
20100214.158 Added <firstphotoid> and <lastphotoid> to the Twitter tweet template.

Yikes, broke exports for LR3b in the previous push, sorry! Fixed.

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

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.


Lots of updates to the Twitter support:

  • Better tweet-size estimates in line with recent processing changes at Twitter.
  • Added <title> and <description> tags to the tweet-text template (they use the title/description from the first image exported).
  • Added the ability to geotag tweets with a static location, or with the geoencoded location of the first image. A static location can be specified with a latitude, longitude pair, a geohash, or a url from a mapping service like Google, Yahoo, or Bing. On the encoded side, geodata embedded in the image can be used, or the geodata maintained by my geoencoding-support plugin).
  • You can now configure the plugin to shorten URLs via your own account, in case you want to track click-throughs yourself.
  • You can now specify that you want all URLs shortened. The default remains to shorten them only when required to get under the 140-character limit. You might, for example, want to forcefully shorten them all in conjunction with your own account, for click-through tracking.
  • The plugin now goes to great lengths to report whether a tweet is accepted by Twitter. In their infinite wisdom, the folks at Twitter suddenly decided to start ignoring long tweets instead of truncating them, but (here's the brilliant part) they still report back to the plugin that the tweet was successful. Sigh.

    Furthermore, they might also ignore (yet report as successful) other kinds of tweets, such as those that are a repeat of a “too recent” tweet. Those crafty folks at Twitter implemented these changes more than three months ago, but in a truly cunning move, they still detail the old behavior in their API documentation, making no mention whatsoever about how their service now actually works.

    Only by doing a bunch of extra work can the plugin detect whether a tweet was accepted or ignored. If ignored, there's no way for the plugin to know why, so at this point it merely reports that the tweet didn't go through.

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 related 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 unintentionally 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.

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.

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.

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

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 &nbsp; 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.

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.


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.

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.

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.


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.

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.

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.

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


    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=''>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=''>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.

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


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="{OnlineID}&amp;size=large">View on

which creates a result at Flickr like this, which then includes a link with this result.


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


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.


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!

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.


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.

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.

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.


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.

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.

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

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 of this rewritten Lr2 version.

All 828 comments so far, oldest first...

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

— comment by Peter Davis on July 29th, 2008 at 4:48pm JST (15 years, 7 months ago) comment permalink

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

— comment by Matt R. on July 29th, 2008 at 11:15pm JST (15 years, 7 months ago) comment permalink

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

— comment by Arturo on July 30th, 2008 at 2:16am JST (15 years, 7 months ago) comment permalink

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

— comment by Daniel on July 30th, 2008 at 5:20am JST (15 years, 7 months ago) comment permalink

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

— comment by Byron on July 30th, 2008 at 7:09am JST (15 years, 7 months ago) comment permalink

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

— comment by George on July 30th, 2008 at 8:10pm JST (15 years, 7 months ago) comment permalink

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

— comment by Chris Kresser on July 31st, 2008 at 1:44am JST (15 years, 7 months ago) comment permalink

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

— comment by Richard on July 31st, 2008 at 7:49am JST (15 years, 7 months ago) comment permalink

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

— comment by Allen on July 31st, 2008 at 10:14am JST (15 years, 7 months ago) comment permalink

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?

— comment by Michael on July 31st, 2008 at 8:49pm JST (15 years, 7 months ago) comment permalink

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

— comment by David on August 1st, 2008 at 4:07am JST (15 years, 7 months ago) comment permalink

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

— comment by César on August 1st, 2008 at 6:16am JST (15 years, 7 months ago) comment permalink

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 ?

— comment by Samy on August 1st, 2008 at 6:31am JST (15 years, 7 months ago) comment permalink

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? :-).

— comment by Orin on August 1st, 2008 at 7:18am JST (15 years, 7 months ago) comment permalink

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.

— comment by Stephen Schwerdfeger on August 1st, 2008 at 10:09am JST (15 years, 7 months ago) comment permalink

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

— comment by Guillaume Lemoine on August 1st, 2008 at 2:46pm JST (15 years, 7 months ago) comment permalink

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 13631

Unable to Export: An internal error has occurred: bad argument #3 (boolean expected, got string)


Fixed in .4 —Jeffrey

— comment by John Labovitz on August 2nd, 2008 at 8:20am JST (15 years, 7 months ago) comment permalink

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

— comment by Joel on August 2nd, 2008 at 11:39am JST (15 years, 7 months ago) comment permalink

Thanks a lot for this great piece of software!!!

— comment by Andrei on August 3rd, 2008 at 1:04am JST (15 years, 7 months ago) comment permalink

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

— comment by Aaron on August 3rd, 2008 at 3:17am JST (15 years, 7 months ago) comment permalink

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

— comment by Enver on August 3rd, 2008 at 6:07am JST (15 years, 7 months ago) comment permalink

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

— comment by TomT on August 3rd, 2008 at 6:59am JST (15 years, 7 months ago) comment permalink

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

— comment by Joe on August 3rd, 2008 at 2:35pm JST (15 years, 7 months ago) comment permalink

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

— comment by Andy Piper on August 3rd, 2008 at 8:33pm JST (15 years, 7 months ago) comment permalink

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

— comment by Thomas on August 3rd, 2008 at 11:05pm JST (15 years, 7 months ago) comment permalink

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

— comment by Jeff Billimek on August 4th, 2008 at 2:03am JST (15 years, 7 months ago) comment permalink

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.

— comment by Andy Piper on August 4th, 2008 at 5:25am JST (15 years, 7 months ago) comment permalink

Hi Jef,
Most of the problems are solved with the latest version

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


— comment by Enver on August 6th, 2008 at 5:33pm JST (15 years, 7 months ago) comment permalink

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.

Fixed in version .15 —Jeffrey

— comment by Juanri on August 7th, 2008 at 5:51am JST (15 years, 7 months ago) comment permalink

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

— comment by Enver on August 8th, 2008 at 4:00am JST (15 years, 7 months ago) comment permalink

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

— comment by Enver on August 8th, 2008 at 6:58am JST (15 years, 7 months ago) comment permalink

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

— comment by John on August 8th, 2008 at 11:56am JST (15 years, 7 months ago) comment permalink

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.

— comment by andy on August 8th, 2008 at 12:22pm JST (15 years, 7 months ago) comment permalink


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

— comment by Dale on August 9th, 2008 at 1:21am JST (15 years, 7 months ago) comment permalink

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.

— comment by Enver on August 9th, 2008 at 6:05am JST (15 years, 7 months ago) comment permalink

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,

— comment by Alex on August 10th, 2008 at 5:22am JST (15 years, 7 months ago) comment permalink

And Again! Thanks Dude!!!

— comment by Flickrfan on August 10th, 2008 at 8:04pm JST (15 years, 7 months ago) comment permalink

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?

— comment by Oren Novotny on August 13th, 2008 at 11:27am JST (15 years, 7 months ago) comment permalink

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.

— comment by Mike on August 14th, 2008 at 4:48pm JST (15 years, 7 months ago) comment permalink

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.

— comment by jorundtm on August 15th, 2008 at 12:34am JST (15 years, 7 months ago) comment permalink

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 ?

— comment by Lucas Janin on August 16th, 2008 at 5:35pm JST (15 years, 7 months ago) comment permalink

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)

— comment by Enver on August 17th, 2008 at 5:12am JST (15 years, 7 months ago) comment permalink


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 🙂

— comment by Marcin on August 19th, 2008 at 1:26pm JST (15 years, 7 months ago) comment permalink


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.

Randy Stewart

— comment by Randy Stewart on August 22nd, 2008 at 2:38am JST (15 years, 6 months ago) comment permalink

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

— comment by Reinhold Stansich on August 24th, 2008 at 5:44pm JST (15 years, 6 months ago) comment permalink

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 !


— comment by David on August 25th, 2008 at 3:39am JST (15 years, 6 months ago) comment permalink

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?

— comment by elton on August 25th, 2008 at 7:14am JST (15 years, 6 months ago) comment permalink

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

— comment by M.Rathmann on August 27th, 2008 at 6:53pm JST (15 years, 6 months ago) comment permalink

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:

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


— comment by Antonio on August 28th, 2008 at 2:32am JST (15 years, 6 months ago) comment permalink

When i authentication flickr i get

Flickr login aborted


An internal error has occurred 17430:attempt to index a nil value

How do i fix that
im runnig wins xp

— comment by Ryan on August 29th, 2008 at 3:44am JST (15 years, 6 months ago) comment permalink

Thank you so much for writing and maintaining this. That’s it! I love it, no problems to speak of.

— comment by Seth on August 29th, 2008 at 11:13am JST (15 years, 6 months ago) comment permalink

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

— comment by Geoffrey Wiseman on August 29th, 2008 at 12:51pm JST (15 years, 6 months ago) comment permalink

Hi Jeff,
I want to make public my CONGRATULATIONS!!!
Yes, the Flickr Plugin worked PERFECTLY, I just tried it!!
No more assert problems, it’s a great gift for all of us who enjoy photography.
Thank you very much, you are a Genius.

— comment by Juanri on August 29th, 2008 at 1:19pm JST (15 years, 6 months ago) comment permalink

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.

— comment by heddy on August 29th, 2008 at 7:08pm JST (15 years, 6 months ago) comment permalink

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.


— comment by E Walker on August 30th, 2008 at 9:45am JST (15 years, 6 months ago) comment permalink

The auto-update functionality [download & install] does not create the destination folder with the correct name.

— comment by Soknet on September 1st, 2008 at 4:15am JST (15 years, 6 months ago) comment permalink

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.


— comment by dan on September 1st, 2008 at 5:18am JST (15 years, 6 months ago) comment permalink

ok – so I did a manual overwrite of all the files – worked first time. LOVE THIS PLUGIN 🙂

— comment by Rich on September 1st, 2008 at 5:20pm JST (15 years, 6 months ago) comment permalink

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?


— comment by bart on September 1st, 2008 at 10:13pm JST (15 years, 6 months ago) comment permalink

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.

— comment by Geoffrey Wiseman on September 2nd, 2008 at 3:30am JST (15 years, 6 months ago) comment permalink

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.


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.

— comment by David Grossman on September 2nd, 2008 at 10:23am JST (15 years, 6 months ago) comment permalink

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.

— comment by David Grossman on September 3rd, 2008 at 7:05am JST (15 years, 6 months ago) comment permalink

Hi Jeff,

Great job. Your pluggin works fine in LR 2.0. Thanks so much for all of your efforts!

Jan Armor

— comment by Jan Armor on September 3rd, 2008 at 1:46pm JST (15 years, 6 months ago) comment permalink

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

— comment by Stefan on September 5th, 2008 at 4:04am JST (15 years, 6 months ago) comment permalink

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.


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

— comment by Ben Mathis on September 5th, 2008 at 11:10pm JST (15 years, 6 months ago) comment permalink

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

— comment by D on September 7th, 2008 at 4:56am JST (15 years, 6 months ago) comment permalink

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.

— comment by David on September 11th, 2008 at 2:47am JST (15 years, 6 months ago) comment permalink

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

— comment by Graham on September 12th, 2008 at 12:18pm JST (15 years, 6 months ago) comment permalink

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,


It appears to be a Lightroom bug; I’ve added it to the known issues page. —Jeffrey

— comment by Paul on September 15th, 2008 at 4:03pm JST (15 years, 6 months ago) comment permalink

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?

— comment by Chester Bullock on September 16th, 2008 at 12:47am JST (15 years, 6 months ago) comment permalink

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

— comment by BettyR on September 16th, 2008 at 7:54am JST (15 years, 6 months ago) comment permalink

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

— comment by jackdornothing on September 16th, 2008 at 4:37pm JST (15 years, 6 months ago) comment permalink

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 🙁

— comment by Louise on September 17th, 2008 at 6:35am JST (15 years, 6 months ago) comment permalink

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.

— comment by Michael on September 17th, 2008 at 8:10am JST (15 years, 6 months ago) comment permalink

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 [ ]

— comment by Soknet on September 21st, 2008 at 12:16am JST (15 years, 5 months ago) comment permalink

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

— comment by Chris Osborne on September 21st, 2008 at 9:23pm JST (15 years, 5 months ago) comment permalink


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?


— comment by Elias Stassinos on September 21st, 2008 at 11:37pm JST (15 years, 5 months ago) comment permalink

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.

— comment by Peter on September 22nd, 2008 at 6:32am JST (15 years, 5 months ago) comment permalink

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

— comment by Ronny on September 23rd, 2008 at 8:02am JST (15 years, 5 months ago) comment permalink

When I try “Authenticate to Flickr” I recive
“Oops! Flickr can’t find a valid callback URL.”

— comment by nikolay on September 24th, 2008 at 12:21am JST (15 years, 5 months ago) comment permalink

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.

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!

— comment by Nordin Rahhali on September 25th, 2008 at 3:05pm JST (15 years, 5 months ago) comment permalink

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!

— comment by John on September 26th, 2008 at 2:29am JST (15 years, 5 months ago) comment permalink

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!

— comment by Stew on September 28th, 2008 at 1:07am JST (15 years, 5 months ago) comment permalink

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.

— comment by Rchard on September 29th, 2008 at 4:47am JST (15 years, 5 months ago) comment permalink

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

— comment by Jasper on September 29th, 2008 at 10:49am JST (15 years, 5 months ago) comment permalink

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


P.S. Perhaps I’ll have some bugs/feature requests later… 🙂

— comment by matt haines on September 29th, 2008 at 11:58am JST (15 years, 5 months ago) comment permalink

tag-based pool please! 😉

— comment by Marcos on September 30th, 2008 at 9:50pm JST (15 years, 5 months ago) comment permalink

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. =)

— comment by Brian on October 1st, 2008 at 12:53pm JST (15 years, 5 months ago) comment permalink

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

— comment by Lucas Janin on October 1st, 2008 at 3:45pm JST (15 years, 5 months ago) comment permalink

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

— comment by John on October 2nd, 2008 at 10:25pm JST (15 years, 5 months ago) comment permalink

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.


That’s really mysterious, since the Flickr plugin doesn’t have a global named “RequestHeaders”. —Jeffrey

— comment by jack on October 6th, 2008 at 10:11pm JST (15 years, 5 months ago) comment permalink

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

— comment by Brooks on October 9th, 2008 at 8:47am JST (15 years, 5 months ago) comment permalink

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.

— comment by Calz on October 13th, 2008 at 6:09am JST (15 years, 5 months ago) comment permalink


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.

— comment by Steve on October 13th, 2008 at 7:29am JST (15 years, 5 months ago) comment permalink


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

— comment by LeoPheonix on October 13th, 2008 at 5:45pm JST (15 years, 5 months ago) comment permalink

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!

— comment by César on October 16th, 2008 at 5:14pm JST (15 years, 5 months ago) comment permalink

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.


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

— comment by Gary on October 16th, 2008 at 7:08pm JST (15 years, 5 months ago) comment permalink

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.

— comment by EnsH on October 19th, 2008 at 3:51am JST (15 years, 5 months ago) comment permalink


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,


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

— comment by Werner on October 19th, 2008 at 4:06pm JST (15 years, 5 months ago) comment permalink


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:

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

— comment by Fabian on October 23rd, 2008 at 4:49am JST (15 years, 4 months ago) comment permalink

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

— comment by Ricardo on October 25th, 2008 at 4:18am JST (15 years, 4 months ago) comment permalink

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.

— comment by Calz on October 26th, 2008 at 11:49pm JST (15 years, 4 months ago) comment permalink

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

— comment by Ghusse on October 28th, 2008 at 9:08pm JST (15 years, 4 months ago) comment permalink

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.

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.


— comment by Oriol Garrote on October 29th, 2008 at 2:20am JST (15 years, 4 months ago) comment permalink

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.


— comment by Leandro on October 30th, 2008 at 9:34pm JST (15 years, 4 months ago) comment permalink

Thank you for creating this plug-in. It’s exactly what I have been looking for. Excellent work and keep it up!

— comment by Sean on November 3rd, 2008 at 11:23pm JST (15 years, 4 months ago) comment permalink

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,

— comment by Grant Kinney on November 5th, 2008 at 4:58am JST (15 years, 4 months ago) comment permalink

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,


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/ line 946, chunk 3.

I didn’t think this could happen, but have just pushed a new version (.24) that perhaps addresses it. —Jeffrey

— comment by Robert Jones on November 8th, 2008 at 5:45am JST (15 years, 4 months ago) comment permalink

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.

— comment by Alan on November 10th, 2008 at 3:54pm JST (15 years, 4 months ago) comment permalink


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)

— comment by Tscherno on November 11th, 2008 at 7:29am JST (15 years, 4 months ago) comment permalink


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,

DO NOT DO THIS 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

— comment by Grant on November 11th, 2008 at 8:52am JST (15 years, 4 months ago) comment permalink

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

— comment by Tscherno on November 11th, 2008 at 2:55pm JST (15 years, 4 months ago) comment permalink

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

— comment by sebchang on November 12th, 2008 at 6:15am JST (15 years, 4 months ago) comment permalink

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.


(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

— comment by melvin foong on November 13th, 2008 at 3:49am JST (15 years, 4 months ago) comment permalink

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.

— comment by Alan on November 13th, 2008 at 8:30am JST (15 years, 4 months ago) comment permalink

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.

— comment by melvin foong on November 14th, 2008 at 4:20am JST (15 years, 4 months ago) comment permalink


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?

— comment by Chris Niekel on November 15th, 2008 at 7:48pm JST (15 years, 4 months ago) comment permalink

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.

— comment by Lionel on November 15th, 2008 at 9:32pm JST (15 years, 4 months ago) comment permalink

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

— comment by Sylvia on November 17th, 2008 at 10:19pm JST (15 years, 4 months ago) comment permalink

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.

— comment by Alan on November 18th, 2008 at 8:22am JST (15 years, 4 months ago) comment permalink

“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

?:17540: assertion failed!

I am using WinVista SP1, LR 2.1 512205, Plugin 20081122.51

Thanks, I just pushed .52 that fixes this. —Jeffrey

— comment by Nitin on November 23rd, 2008 at 8:31am JST (15 years, 3 months ago) comment permalink

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

?:17555: assertion failed!

One thing I forgot to mention that may be relevant – I have over 454 (and counting) photosets.


— comment by Nitin on November 24th, 2008 at 8:36am JST (15 years, 3 months ago) comment permalink

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


— comment by A Dubs on November 24th, 2008 at 12:13pm JST (15 years, 3 months ago) comment permalink

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,

— comment by Andrew Shinn on November 25th, 2008 at 4:33am JST (15 years, 3 months ago) comment permalink

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


Version no: 20081125.54

Thank you, Jeffrey!!


— comment by Josh on November 25th, 2008 at 9:05am JST (15 years, 3 months ago) comment permalink

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

— comment by Pablo on November 26th, 2008 at 5:33am JST (15 years, 3 months ago) comment permalink

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

— comment by Filckr8tor on November 27th, 2008 at 9:24am JST (15 years, 3 months ago) comment permalink

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 Airport

flickr 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

— comment by Oliver on November 28th, 2008 at 5:34am JST (15 years, 3 months ago) comment permalink

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

Added the ability to do this as of version .96. —Jeffrey

— comment by Reinhold Stansich on November 29th, 2008 at 7:49pm JST (15 years, 3 months ago) comment permalink

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

— comment by Bob Meyer on November 30th, 2008 at 11:25pm JST (15 years, 3 months ago) comment permalink

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!

— comment by JasonP on December 1st, 2008 at 5:53am JST (15 years, 3 months ago) comment permalink

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

— comment by ElliR on December 4th, 2008 at 7:00pm JST (15 years, 3 months ago) comment permalink

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

— comment by Chris on December 6th, 2008 at 11:00pm JST (15 years, 3 months ago) comment permalink

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

— comment by Will Boyce on December 9th, 2008 at 3:55am JST (15 years, 3 months ago) comment permalink

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

— comment by Nathan Siemers on December 10th, 2008 at 12:02am JST (15 years, 3 months ago) comment permalink

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!

— comment by Nathan Siemers on December 10th, 2008 at 3:56am JST (15 years, 3 months ago) comment permalink

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

— comment by JasonP on December 10th, 2008 at 4:50am JST (15 years, 3 months ago) comment permalink

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?


— comment by ChrisB on December 10th, 2008 at 10:29pm JST (15 years, 3 months ago) comment permalink

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

— comment by Chris on December 11th, 2008 at 4:01pm JST (15 years, 3 months ago) comment permalink

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

— comment by Andre on December 15th, 2008 at 5:55am JST (15 years, 3 months ago) comment permalink


I’m using Lightroom 2.1 with the Export to Flickr plugin – flickr-20081209.60 on a Mac with OS 10.5.5


— comment by Andre on December 15th, 2008 at 5:58am JST (15 years, 3 months ago) comment permalink

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?

— comment by Chester Bullock on December 16th, 2008 at 4:09am JST (15 years, 3 months ago) comment permalink

can’t download the … 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

— comment by Howie on December 16th, 2008 at 11:31am JST (15 years, 3 months ago) comment permalink

Finally worked after a lot of different attempts. May have had something to do with the latest update from MS???
Thanks, H

— comment by Howie on December 21st, 2008 at 11:33am JST (15 years, 2 months ago) comment permalink

Great plug in thanks…is there a way to tell easily if i have uploaded a file to flicker?

— comment by John on December 21st, 2008 at 9:24pm JST (15 years, 2 months ago) comment permalink

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?

Thanks for your hard work on the plugin

— comment by Adrian on December 22nd, 2008 at 8:52pm JST (15 years, 2 months ago) comment permalink


is it possible to somehow call an imagemagick command to add a watermark before uploading?

Thanks for your work!

LR2/Mogrify —Jeffrey

— comment by Chris K on December 23rd, 2008 at 4:53am JST (15 years, 2 months ago) comment permalink

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,

Sorry ’bout that…. fixed in new versions I just pushed. Thanks for the report. —Jeffrey

— comment by Mark on December 24th, 2008 at 5:06pm JST (15 years, 2 months ago) comment permalink

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

— comment by Mark on December 25th, 2008 at 9:23am JST (15 years, 2 months ago) comment permalink

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?


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

— comment by Tony M on December 28th, 2008 at 11:47am JST (15 years, 2 months ago) comment permalink

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 🙂


What is a “droplet”? —Jeffrey

— comment by Fred on December 29th, 2008 at 2:20am JST (15 years, 2 months ago) comment permalink

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,

— comment by Peter E on December 29th, 2008 at 6:08pm JST (15 years, 2 months ago) comment permalink

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:

BTW thanks for the “auto dests” feature!

— comment by Vincent Mo on January 1st, 2009 at 8:41am JST (15 years, 2 months ago) comment permalink

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,

— comment by Fred on January 2nd, 2009 at 6:21pm JST (15 years, 2 months ago) comment permalink

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

— comment by Sean Phillips on January 5th, 2009 at 1:59pm JST (15 years, 2 months ago) comment permalink

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.

— comment by Christopher Layne on January 11th, 2009 at 4:39pm JST (15 years, 2 months ago) comment permalink

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.

— comment by Christopher Layne on January 11th, 2009 at 4:43pm JST (15 years, 2 months ago) comment permalink

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.

— comment by Rolf on January 13th, 2009 at 4:54am JST (15 years, 2 months ago) comment permalink

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.


— comment by Steve on January 14th, 2009 at 8:17am JST (15 years, 2 months ago) comment permalink

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!

— comment by Matthew on January 14th, 2009 at 12:40pm JST (15 years, 2 months ago) comment permalink

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:

— comment by Elton on January 15th, 2009 at 12:43am JST (15 years, 2 months ago) comment permalink

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!

— comment by steve on January 15th, 2009 at 6:15am JST (15 years, 2 months ago) comment permalink

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

— comment by Sean Phillips on January 15th, 2009 at 6:59am JST (15 years, 2 months ago) comment permalink

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

— comment by Christopher Layne on January 17th, 2009 at 4:14pm JST (15 years, 2 months ago) comment permalink

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!

— comment by Sean Phillips on January 17th, 2009 at 4:56pm JST (15 years, 2 months ago) comment permalink

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.

— comment by Christopher Layne on January 17th, 2009 at 6:40pm JST (15 years, 2 months ago) comment permalink

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 🙂

— comment by Caroline on January 17th, 2009 at 7:57pm JST (15 years, 2 months ago) comment permalink

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)

— comment by Doug Cranmer on January 23rd, 2009 at 3:02am JST (15 years, 1 month ago) comment permalink

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…



— comment by Oaksun on January 26th, 2009 at 8:15am JST (15 years, 1 month ago) comment permalink


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

— comment by Mike on January 26th, 2009 at 8:52am JST (15 years, 1 month ago) comment permalink

Version 20090119.68 don’t export all my keywords. Some pictures are placed on the map on flickr, others aren’t.

— comment by Caroline on January 27th, 2009 at 1:22am JST (15 years, 1 month ago) comment permalink

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.

— comment by Emmanuel on January 27th, 2009 at 2:38am JST (15 years, 1 month ago) comment permalink

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

— comment by Adrian on January 28th, 2009 at 10:42pm JST (15 years, 1 month ago) comment permalink

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)

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

— comment by Pat O'Halloran on January 30th, 2009 at 11:30pm JST (15 years, 1 month ago) comment permalink

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

— comment by Zafar on January 31st, 2009 at 1:21pm JST (15 years, 1 month ago) comment permalink

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

— comment by John on February 1st, 2009 at 5:38am JST (15 years, 1 month ago) comment permalink

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

— comment by Zafar on February 1st, 2009 at 5:47am JST (15 years, 1 month ago) comment permalink

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.

— comment by Christopher Layne on February 1st, 2009 at 12:19pm JST (15 years, 1 month ago) comment permalink

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.

— comment by Alan on February 2nd, 2009 at 1:15am JST (15 years, 1 month ago) comment permalink

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!

— comment by Sean Phillips on February 2nd, 2009 at 5:20am JST (15 years, 1 month ago) comment permalink

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.

— comment by Ramunas on February 2nd, 2009 at 5:16pm JST (15 years, 1 month ago) comment permalink


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!

— comment by Peter E on February 3rd, 2009 at 10:58am JST (15 years, 1 month ago) comment permalink


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,

— comment by Peter E on February 3rd, 2009 at 11:06am JST (15 years, 1 month ago) comment permalink


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


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

— comment by Andrew Burrows on February 4th, 2009 at 5:25pm JST (15 years, 1 month ago) comment permalink

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.


— comment by Dirk Lottering on February 4th, 2009 at 10:33pm JST (15 years, 1 month ago) comment permalink

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.


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

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.

— comment by Lucian on February 6th, 2009 at 10:07am JST (15 years ago) comment permalink

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.

— comment by Ben on February 8th, 2009 at 11:27am JST (15 years ago) comment permalink

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

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

— comment by Florent Bouckenooghe on February 10th, 2009 at 7:22am JST (15 years ago) comment permalink

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

— comment by Paddy on February 14th, 2009 at 4:24am JST (15 years ago) comment permalink

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

— comment by Alexander Czernay on February 15th, 2009 at 10:06pm JST (15 years ago) comment permalink

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

— comment by Ole Begemann on February 19th, 2009 at 10:35am JST (15 years ago) comment permalink

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

— comment by Lutz-R. Frank on February 19th, 2009 at 4:28pm JST (15 years ago) comment permalink

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

— comment by Lutz-R. Frank on February 19th, 2009 at 4:36pm JST (15 years ago) comment permalink

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

— comment by Lutz-R. Frank on February 20th, 2009 at 1:02am JST (15 years ago) comment permalink

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

— comment by Ottovelo on February 20th, 2009 at 10:03am JST (15 years ago) comment permalink

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

— comment by Alan on February 21st, 2009 at 11:42pm JST (15 years ago) comment permalink

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

— comment by Lutz-R. Frank on February 22nd, 2009 at 1:12am JST (15 years ago) comment permalink

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!

— comment by James on February 22nd, 2009 at 4:07am JST (15 years ago) comment permalink

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

— comment by Lasse on February 22nd, 2009 at 7:28am JST (15 years ago) comment permalink

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:

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:

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

— comment by kubacu on February 23rd, 2009 at 1:18am JST (15 years ago) comment permalink

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:

– 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

— comment by Alexander Czernay on February 28th, 2009 at 7:13pm JST (15 years ago) comment permalink

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 😉


Soon 😉   —Jeffrey

— comment by paolo savonuzzi on March 2nd, 2009 at 9:16pm JST (15 years ago) comment permalink

And if you can make that work with other plugin metadata (eg. Timothy Armes LR2/blog) that would be even sweeter!

Soon 😉 —Jeffrey

— comment by Sean Phillips on March 2nd, 2009 at 10:46pm JST (15 years ago) comment permalink

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

— comment by BenBen on March 4th, 2009 at 1:48pm JST (15 years ago) comment permalink

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

— comment by Bastian on March 5th, 2009 at 9:03am JST (15 years ago) comment permalink

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!

— comment by glenn on March 5th, 2009 at 12:51pm JST (15 years ago) comment permalink

Jeffrey, quick note, I think you need to escape the html tags under the 20090228.76 change history.

Doh! Thanks, fixed. —Jeffrey

— comment by Christopher Layne on March 6th, 2009 at 1:04pm JST (15 years ago) comment permalink

Jeffrey, I just updated to version 20090306.81 Flickr plugin on Lightroom 2.3 Windows Vista. I am on not so cannot authenticate. Not had this problem before. Sorry if I have missed this somewhere.

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

— comment by Tony Barranco on March 7th, 2009 at 7:43am JST (15 years ago) comment permalink

I seem to have solved the problem by first logging in with my browser from outside your plugin. Thank you.

— comment by Tony Barranco on March 7th, 2009 at 5:03pm JST (15 years ago) comment permalink

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 🙂


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

— comment by Matteo on March 10th, 2009 at 8:22am JST (15 years ago) comment permalink

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.


— comment by Joseph Palmer on March 11th, 2009 at 12:18am JST (15 years ago) comment permalink

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

— comment by Gary Thom on March 17th, 2009 at 7:02pm JST (15 years ago) comment permalink

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

— comment by Alex on March 18th, 2009 at 1:47am JST (15 years ago) comment permalink

… 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

— comment by paolo savonuzzi on March 20th, 2009 at 3:14am JST (15 years ago) comment permalink

… 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

— comment by paolo savonuzzi on March 20th, 2009 at 9:50am JST (15 years ago) comment permalink

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.


— comment by Ken Friar on March 21st, 2009 at 12:43am JST (15 years ago) comment permalink

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.


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

— comment by Steve on March 21st, 2009 at 7:06am JST (15 years ago) comment permalink

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:
to import the geotags.

I already tried it and it works.

Good luck!

— comment by Ahmad on March 22nd, 2009 at 4:06pm JST (14 years, 11 months ago) comment permalink

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

— comment by Vincent Mo on March 23rd, 2009 at 12:43pm JST (14 years, 11 months ago) comment permalink

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.

— comment by steve on March 23rd, 2009 at 1:04pm JST (14 years, 11 months ago) comment permalink

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,

— comment by Andrew on March 27th, 2009 at 10:24am JST (14 years, 11 months ago) comment permalink

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.

— comment by Samy Rabih on March 29th, 2009 at 8:50pm JST (14 years, 11 months ago) comment permalink

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.

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

— comment by Martin on April 2nd, 2009 at 2:25am JST (14 years, 11 months ago) comment permalink

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…

— comment by Tommi on April 4th, 2009 at 6:30pm JST (14 years, 11 months ago) comment permalink

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

— comment by Florent Bouckenooghe on April 4th, 2009 at 9:25pm JST (14 years, 11 months ago) comment permalink

Quick token request:

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

— comment by Christopher Layne on April 5th, 2009 at 11:39am JST (14 years, 11 months ago) comment permalink

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&””} ?

— comment by Christopher Layne on April 5th, 2009 at 11:55am JST (14 years, 11 months ago) comment permalink

I meant {Caption&”<br>”} (html break-tag)

— comment by Christopher Layne on April 5th, 2009 at 11:56am JST (14 years, 11 months ago) comment permalink

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

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

— comment by Paulo Campos on April 8th, 2009 at 5:16am JST (14 years, 11 months ago) comment permalink

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

— comment by melvin foong on April 8th, 2009 at 9:20am JST (14 years, 11 months ago) comment permalink

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

— comment by Jacob on April 10th, 2009 at 12:48pm JST (14 years, 11 months ago) comment permalink

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

— comment by Ian on April 10th, 2009 at 11:28pm JST (14 years, 11 months ago) comment permalink

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

— comment by Ian on April 15th, 2009 at 2:21am JST (14 years, 11 months ago) comment permalink

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

— comment by Jack Larson on April 16th, 2009 at 8:44am JST (14 years, 11 months ago) comment permalink

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

— comment by Krzysztof on April 19th, 2009 at 2:40am JST (14 years, 11 months ago) comment permalink

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.

— comment by Matteo on April 20th, 2009 at 6:17am JST (14 years, 11 months ago) comment permalink

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

— comment by Nigel H on April 20th, 2009 at 9:17pm JST (14 years, 10 months ago) comment permalink

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

— comment by Doug on April 28th, 2009 at 7:40am JST (14 years, 10 months ago) comment permalink

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

— comment by Jasper Teal on May 2nd, 2009 at 10:37pm JST (14 years, 10 months ago) comment permalink


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

— comment by Matthias Zirngibl on May 5th, 2009 at 7:47pm JST (14 years, 10 months ago) comment permalink

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

— comment by Matt Fahrner on May 6th, 2009 at 11:10pm JST (14 years, 10 months ago) comment permalink

Hmm…. I’ll give it a try. Maybe I just assumed it wouldn’t work.

Thanks for the quick response Jeffrey!

— comment by Matt Fahrner on May 7th, 2009 at 12:42am JST (14 years, 10 months ago) comment permalink

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

— comment by Steve L on May 10th, 2009 at 3:28pm JST (14 years, 10 months ago) comment permalink

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.


-Todd, writing from Richmond, Virginia 🙂

Yeah, sorry, that’s on the to-do list. —Jeffrey

— comment by Todd Dixon on May 11th, 2009 at 2:31am JST (14 years, 10 months ago) comment permalink

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

— comment by Matthias Zirngibl on May 12th, 2009 at 6:12am JST (14 years, 10 months ago) comment permalink

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

— comment by Matthias Zirngibl on May 13th, 2009 at 12:09am JST (14 years, 10 months ago) comment permalink

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 &amp; 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

— comment by Christopher Layne on May 13th, 2009 at 3:09pm JST (14 years, 10 months ago) comment permalink

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

— comment by Ludovic on May 13th, 2009 at 9:26pm JST (14 years, 10 months ago) comment permalink

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

— comment by paolo savonuzzi on May 14th, 2009 at 4:17am JST (14 years, 10 months ago) comment permalink


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 😉

— comment by Matthias Zirngibl on May 14th, 2009 at 1:08pm JST (14 years, 10 months ago) comment permalink

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

— comment by John on May 18th, 2009 at 1:44am JST (14 years, 10 months ago) comment permalink

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

— comment by lior shapira on May 18th, 2009 at 2:22am JST (14 years, 10 months ago) comment permalink

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

— comment by Danny Ngan on May 20th, 2009 at 6:08am JST (14 years, 10 months ago) comment permalink

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

— comment by Danny Ngan on May 20th, 2009 at 6:38am JST (14 years, 10 months ago) comment permalink

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

— comment by Alan Vink on May 20th, 2009 at 10:09am JST (14 years, 10 months ago) comment permalink

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.

— comment by Eric on May 26th, 2009 at 10:11pm JST (14 years, 9 months ago) comment permalink

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

— comment by Karan Aggarwal on May 27th, 2009 at 1:41pm JST (14 years, 9 months ago) comment permalink

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

— comment by Mark Sirota on June 2nd, 2009 at 10:51am JST (14 years, 9 months ago) comment permalink

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

— comment by Mark Sirota on June 2nd, 2009 at 11:16am JST (14 years, 9 months ago) comment permalink

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

— comment by Sean Phillips on June 2nd, 2009 at 12:46pm JST (14 years, 9 months ago) comment permalink

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

— comment by John on June 2nd, 2009 at 11:28pm JST (14 years, 9 months ago) comment permalink

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

— comment by Bastian on June 3rd, 2009 at 12:22am JST (14 years, 9 months ago) comment permalink

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…

— comment by Sean Phillips on June 3rd, 2009 at 12:23am JST (14 years, 9 months ago) comment permalink

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.

— comment by Mark Sirota on June 3rd, 2009 at 2:29am JST (14 years, 9 months ago) comment permalink

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

— comment by Christopher Layne on June 3rd, 2009 at 7:23am JST (14 years, 9 months ago) comment permalink


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?

Randy Stewart

I think my comment-submission form ate some of your text…. could you email it to me? —Jeffrey

— comment by Randy Stewart on June 3rd, 2009 at 8:26am JST (14 years, 9 months ago) comment permalink

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!

— comment by Ole Begemann on June 3rd, 2009 at 11:05pm JST (14 years, 9 months ago) comment permalink

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

— comment by John on June 4th, 2009 at 5:02am JST (14 years, 9 months ago) comment permalink


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.


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

— comment by Joop Snijder on June 5th, 2009 at 1:12am JST (14 years, 9 months ago) comment permalink

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!

— comment by Mark Sirota on June 5th, 2009 at 2:46am JST (14 years, 9 months ago) comment permalink

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

— comment by Richard on June 5th, 2009 at 11:06pm JST (14 years, 9 months ago) comment permalink

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

— comment by Mark on June 7th, 2009 at 2:50am JST (14 years, 9 months ago) comment permalink

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

— comment by Mark on June 7th, 2009 at 5:08am JST (14 years, 9 months ago) comment permalink

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

— comment by Mark on June 7th, 2009 at 11:08am JST (14 years, 9 months ago) comment permalink

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

— comment by Matthias Zirngibl on June 7th, 2009 at 6:52pm JST (14 years, 9 months ago) comment permalink

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

— comment by Matthias Zirngibl on June 11th, 2009 at 5:52am JST (14 years, 9 months ago) comment permalink

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

— comment by Brent on June 13th, 2009 at 12:34pm JST (14 years, 9 months ago) comment permalink

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

— comment by Brent on June 13th, 2009 at 10:22pm JST (14 years, 9 months ago) comment permalink

… not sure at all it’s related, but… =:-/

— comment by paolo savonuzzi on June 14th, 2009 at 5:22am JST (14 years, 9 months ago) comment permalink

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

— comment by Remco on June 14th, 2009 at 7:40pm JST (14 years, 9 months ago) comment permalink

The build from today, 20090614.111 seems to do the trick for fixing the Twitter issue. Thank you so much for your prompt response!

— comment by Brent on June 14th, 2009 at 9:18pm JST (14 years, 9 months ago) comment permalink

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!


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,

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

— comment by MadGrin on June 15th, 2009 at 6:50am JST (14 years, 9 months ago) comment permalink

Are you looking at some kind of a short URL option (eg. TinyURL, or even Flickr’s own URL shortening service) for links sent to Twitter??

You mean besides the built-in support? No. Why do you ask? —Jeffrey

— comment by Sean Phillips on June 22nd, 2009 at 2:58pm JST (14 years, 8 months ago) comment permalink

I dont’ know what you mean by the built-in support. My links are going out with the full Flickr URL, and I don’t see any option in the export dialog to use What am I missing? Does it only use 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:

You hit on it with Does it only use 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

— comment by Sean Phillips on June 22nd, 2009 at 3:26pm JST (14 years, 8 months ago) comment permalink

OK cool. I didn’t realize that was there. I should have known that you’d have thought of everything!!! Thanks!

— comment by Sean Phillips on June 22nd, 2009 at 3:38pm JST (14 years, 8 months ago) comment permalink

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

— comment by Lodewijk on June 30th, 2009 at 6:43am JST (14 years, 8 months ago) comment permalink

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

— comment by Andy on July 2nd, 2009 at 2:19am JST (14 years, 8 months ago) comment permalink

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


Oops, forgot about that. Just pushed a fix. Thanks for the reminder. —Jeffrey

— comment by Guillaume Lemoine on July 2nd, 2009 at 10:53pm JST (14 years, 8 months ago) comment permalink

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.


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

— comment by Quentin Fennessy on July 5th, 2009 at 12:47pm JST (14 years, 8 months ago) comment permalink

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

— comment by Michael Watson on July 5th, 2009 at 10:04pm JST (14 years, 8 months ago) comment permalink

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.


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

— comment by Joey Gonzalez on July 12th, 2009 at 11:16am JST (14 years, 8 months ago) comment permalink

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

— comment by Cletus Lee on July 12th, 2009 at 2:04pm JST (14 years, 8 months ago) comment permalink

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

— comment by Cletus Lee on July 13th, 2009 at 12:18am JST (14 years, 8 months ago) comment permalink

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 for example: the link is

— comment by David Glasser on July 13th, 2009 at 6:52am JST (14 years, 8 months ago) comment permalink

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

— comment by David Glasser on July 14th, 2009 at 11:50pm JST (14 years, 8 months ago) comment permalink

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

— comment by Florent Bouckenooghe on July 16th, 2009 at 7:21am JST (14 years, 8 months ago) comment permalink

That’s a really fast update ! thanks

— comment by Florent Bouckenooghe on July 16th, 2009 at 8:14am JST (14 years, 8 months ago) comment permalink

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!


— comment by Ian Fuller on July 18th, 2009 at 12:22am JST (14 years, 8 months ago) comment permalink

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…


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

— comment by Ulrich on July 20th, 2009 at 1:17am JST (14 years, 8 months ago) comment permalink

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

— comment by Sylvia on July 22nd, 2009 at 3:49am JST (14 years, 7 months ago) comment permalink

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.

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

— comment by floridagizzi on July 23rd, 2009 at 7:16am JST (14 years, 7 months ago) comment permalink


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 ?


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

— comment by Fred Klee on July 23rd, 2009 at 10:45pm JST (14 years, 7 months ago) comment permalink

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!


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

— comment by Andy Miller on July 23rd, 2009 at 11:07pm JST (14 years, 7 months ago) comment permalink


I have a feature request. It would be great if your plugin supported the geoprivacy setttings on Flickr.



I don’t understand… could you be a bit more verbose in what you want? —Jeffrey

— comment by Steve on July 24th, 2009 at 2:23am JST (14 years, 7 months ago) comment permalink

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)

— comment by Edi on July 24th, 2009 at 5:07am JST (14 years, 7 months ago) comment permalink

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

— comment by Fred Klee on July 24th, 2009 at 3:56pm JST (14 years, 7 months ago) comment permalink


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

When I take pictures at people’s homes I like to restrict the geotagging info to friends and family.


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

— comment by Steve on July 24th, 2009 at 4:54pm JST (14 years, 7 months ago) comment permalink

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


— comment by Steve on July 24th, 2009 at 6:20pm JST (14 years, 7 months ago) comment permalink


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

— comment by Florent Bouckenooghe on July 25th, 2009 at 1:39am JST (14 years, 7 months ago) comment permalink

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,

I don’t quite understand… you can now send to multiple pools. You can also encapsulate your settings into export presets…. —Jeffrey

— comment by TommyR on July 26th, 2009 at 1:39am JST (14 years, 7 months ago) comment permalink

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.


Ah, I see. I’ll check it out…. —Jeffrey

— comment by TommyR on July 26th, 2009 at 5:54pm JST (14 years, 7 months ago) comment permalink


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

— comment by Fred Klee on July 27th, 2009 at 10:59pm JST (14 years, 7 months ago) comment permalink


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

— comment by Fred Klee on July 28th, 2009 at 4:29am JST (14 years, 7 months ago) comment permalink

Hi. You didn’t reply to my Enhancement Request at 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.

— comment by Ian Fuller on July 28th, 2009 at 10:52pm JST (14 years, 7 months ago) comment permalink

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

— comment by Simon Belcher on July 29th, 2009 at 9:29pm JST (14 years, 7 months ago) comment permalink

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 short URLs instead –

#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

— comment by Balaji Dutt on August 1st, 2009 at 3:50pm JST (14 years, 7 months ago) comment permalink

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 – , so this would be a nice little tweak to the Flickr metadata panel.

— comment by Balaji Dutt on August 1st, 2009 at 4:03pm JST (14 years, 7 months ago) comment permalink

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?


– 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

— comment by Cory O'Brien on August 2nd, 2009 at 4:19am JST (14 years, 7 months ago) comment permalink

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

— comment by Dean Hall on August 2nd, 2009 at 6:17pm JST (14 years, 7 months ago) comment permalink

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

But what about the Flickr “friends” and “family” levels? I don’t see how you’d like it to work…. —Jeffrey

— comment by Stefano Klett on August 3rd, 2009 at 1:46am JST (14 years, 7 months ago) comment permalink

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

— comment by Stefano Klett on August 3rd, 2009 at 2:39am JST (14 years, 7 months ago) comment permalink

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

— comment by zilla on August 4th, 2009 at 1:30am JST (14 years, 7 months ago) comment permalink

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

— comment by fotoHans on August 10th, 2009 at 8:57pm JST (14 years, 7 months ago) comment permalink


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.


Bumped it up in priority on the todo list, for after I return to Kyoto in September… —Jeffrey

— comment by Marco on August 15th, 2009 at 6:46am JST (14 years, 7 months ago) comment permalink

Question and an “Opportunity for Improvement”
Flickr Export v. 20090725.122

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.

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?
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 “opportunity for improvement” in this “Associate” feature…

In a set of 12 photos, 11 were originals and one was a Lightroom “Virtual Copy” of one of the originals, cropped and tweaked. That pair of photos would not re-associate when I tried to do the group.

Upon further investigation, either photo individually then would say that it could be linked to two photos on Flicker, since technically both have exactly the same capture time.

So the “opportunity” is to somehow solve the problem by returning information about each conflicted photo already on Flickr and allowing a subjective match to be made, perhaps a list of radio buttons as you step through the list of photos.

Another variant of the problem is on “rapid succession” photos, like when you hold the trigger to get a “play at the plate”. These photos have the same date and time to the second, so they also have the problem during re-association.

Thanks for any and all help,

— comment by John on August 15th, 2009 at 3:32pm JST (14 years, 7 months ago) comment permalink

Hello. Plug in version 20090723.114 was working great with windows 7 (Final beta) Today I upgraded lightroom, Photoshop and Adobe Camera Raw to their latest versions. Once updated the plug in will not show up in the plug in manager. I try to re-install but I get WARNING “An error has occurred while attempting to load this plug-in” Any idea what would of caused this? I don’t think it is because of Windows 7. I have had windows 7 installed for months with no problems. This same error comes up when I try to install Flickr plug in as well. Any help would be greatly appreciated.

I’m guessing that you somehow deleted some files in the plugin folder during your upgrades. Try downloading freash zips, unzip and put where you want them to be, then tell Lightroom about them by installing into the Plugin Manager (which doesn’t really “install” anything… just tells Lightroom where they are, and refers to them in place). —Jeffrey

— comment by Brian Magee on August 17th, 2009 at 3:23am JST (14 years, 7 months ago) comment permalink

Hi Jeffrey-

Great plugin – it has greatly reduced my workflow time!

If you’re accepting feature requests I’d like to put “license type” on the table. 99% of the imagery I upload is “All Rights Reserved”. Some kind of keyword based or an out-and-out radio button that says “Make is All Rights Reserved” would be fantastic.

Thanks so much for such a great tool!


— comment by Christopher Blunck on August 17th, 2009 at 11:24am JST (14 years, 7 months ago) comment permalink

Using version 20090725.122 of your flickr upload plugin, with lightroom 2.4

Judging by Google, there seems to be regular issues of stripped exif data in the interactions between lightroom and flickr.
I think one of your replies in the comment thread mentionned that flickr wasn’t reading correctly the metadata that lightroom cleans up and standardizes … or something to that effect.
Is this something that has either a workaround or has been corrected? I still can’t get camera make and focal lens to appear in my flickr account (checking / unchecking various combinations of “minimize metadata” …)?
Any thoughts ?
Thank you, and thanks for the plug-ins…

If you modify the Export Location section to export to a specific location, the files will remain even after having been uploaded to Flickr. You can then test them with exiftool (or my online exif viewer) to see whether the data is there. If it is, the problem lies with Flickr. If you check “Minimize Exported Metadata”, the data won’t be there, so, of course, it won’t be possible for Flickr to get it. —

— comment by Paul on August 17th, 2009 at 4:13pm JST (14 years, 7 months ago) comment permalink

Hi Jeffrey
I’m a long-time user of your plugin from France : have you planned to translate your plugin in other languages than English? (I don’t know if LR has support for multilingual plugins).

If yes, I offer you my help to translate your plugin into French 🙂

Lightroom does offer a way for plugins to be localized, and I appreciate your kind offer, but I’ve really got to come up with some kind of system for doing the translations. There are thousands and thousands of text items that need to be translated, and many are not obvious out of context. The head of the main French Lightroom site translated my LR1 plugins, but they’ve grown so large now that I need a multi-user translation system. I’ll work out something eventually…. —Jeffrey

— comment by Samy on August 18th, 2009 at 2:41am JST (14 years, 7 months ago) comment permalink

Re the exif data issue above : thanks for the tip. As in most cases, the human was at fault … no idea what i was doing wrong, but reset all settings and can now proudly display the camera model next to my shiny images.

Now, i have to figure out why the metadata wrangler plugin returns an error message …

Cheers — Paul.

ps: oh and by coincidence with previous poster, am french too and would gladly help in any translation effort …

— comment by Paul on August 20th, 2009 at 3:25pm JST (14 years, 7 months ago) comment permalink

Hello. I’m using the JobIdentifier to keep the target photoset for pictures. And at export time, I use an auto destination preset that includes {JobIdentifier} in the template.

I would be happy if we could store more than one target photoset in JobIdentifier, perhaps separating them with commas, or something similar. I’m sure you’ll have better ideas about this question.

Please, excuse my poor english :-/

Thanks for your sttuning jobs,

Barcelona, Catalonia
(Joan is John in catalan 🙂

— comment by JoanColl on August 22nd, 2009 at 9:52pm JST (14 years, 6 months ago) comment permalink

i have a Quetion to the “Export to Flickr” Plugin VN: 20090725.122

i’m using the extra Tags with Templates ( Camera Exif Data ).
Is there a way to get this Extra Tags in a Row. Now they are listed in Disorder.
There are listed some Tags, created in Lightroom, then some extra Tags, then some Lightroom Tags .. and so on. No alphabetical Order or so.

and one more Problem:
The Input Field ends very suddenly. Shure, i’m using a lot of extra Tags.
But i can’t go to the End of the input field and i can’t increase the Window of the Export Function, to see the whole input field.

I’m using Adobe LR on Mac OS X 10.5.8

Sorry about my bad English

— comment by Boris on August 25th, 2009 at 3:09am JST (14 years, 6 months ago) comment permalink

Hi Jeffrey !
Two features should be very interesting :
– display the photoset list with hierarchy information (like sets in collections, etc)
– a text field to easily set the name of pictures (for exemple, if I want to give the “Photo” name to all my pictures of an export, I need to edit the naming templates)

I’ll take a look at the heirarchy stuff… that’s new from Flickr since I first made this. About the file naming, I agree it’d be useful, but that’s all done via the standard portions of Lightroom’s export. —Jeffrey

— comment by Samy on August 26th, 2009 at 5:51am JST (14 years, 6 months ago) comment permalink

Something drastic changed with tags. Tags are no longer updating in alphabetical order – or Flickr is not presenting them that way. It’s quite difficult to rearrange these after the fact too.

Before, everything was working perfectly. I’m using the latest version.

I’ll look into it next week when I return to Japan. —Jeffrey

— comment by Christopher Layne on August 26th, 2009 at 1:47pm JST (14 years, 6 months ago) comment permalink


I love your development of this plugin and the dedication you have to the Lightroom community. Thank you for all of your efforts, you are appreciated!

I wanted to throw in a suggestion for the Twitter functionality; linking to the slideshow of a set, which follows: I have people complain about small size image viewing (don’t see the All Sizes button), this would help them out!

Thank you again for everything you do for the community!
– Derek Gates (US)

Looks like a nice idea… I’ll add it to the todo list! —Jeffrey

— comment by Derek Gates on September 1st, 2009 at 9:19am JST (14 years, 6 months ago) comment permalink

Great job on the Flickr Plugin I have been using it for a long time and just ran into my first issue. Recently upgraded to Win7 (Final version through my MSDN account). I am running Lightroom 2.4 (572242) and “Export To Flickr” plugin 20090904.123.

Everything works great until I click the last “export” button and it begins exporting the files to my local folder and uploading. Sometimes it crashes immediately and sometimes I can get 5-15 (never more) pictures and my entire system freezes. I do not know if this is a plugin/Lightroom/Win7 bug – but I have not had any other issues with my system. I have not been able to test any previous versions of the plugin either.

I tried exporting to different folders and running Lightroom as administrator but have had no success. If there is anything I can do to help test let me know – I would be glad to help.


I’d have to guess it’s something with your system…. a user program shouldn’t be able to lock up your system, at all, ever, so it sounds like you’re paying the early-adopter price )-: —Jeffrey

— comment by Eric P on September 12th, 2009 at 12:05pm JST (14 years, 6 months ago) comment permalink


Here goes:
When I use the flickr-20090915.124 and tell it that I want to select the photoset as I upload (Select at export time). Everything looks the way it should, but as I select a photoset the “Continue with export” button is still grayed out. Any one know why or how to get it to continue? It works fine is I set it to “Don’t add to photoset”.

Help, please. 🙂

My bad… just pushed a fix (version .125). —Jeffrey

— comment by TommyR on September 16th, 2009 at 1:12am JST (14 years, 6 months ago) comment permalink

Export to Flickr Lightroom Plugin, ver. 20090916.125

Under “Flickr: Metadata Management” subheading “Image Title / Description”

In making a custom preset is there a possibility of adding a few more basic html tags for formatting purposes? I would like to have <em> to italicize one portion and to add space between two lines where two ‘s don’t work.

Otherwise, Jeffery, this is a fine product that I am growing to rely upon!

Thank you!

If you select “HTML”, then you can use whatever HTML that Flickr allows. —Jeffrey

— comment by Ron Kochanowski on September 18th, 2009 at 7:53pm JST (14 years, 6 months ago) comment permalink

ciao jeff
i writing you just to tell thanks, this is te best tools I have found to upload in flickr my pictures. before MAC experience I had use ACDSEE pro for PC to upload picts to flickr, but this is really a good tools. I write from Italy and now i make a donation to be able to have full product.
you make a very good job. if you like this is my set

— comment by antonella on September 23rd, 2009 at 6:08am JST (14 years, 5 months ago) comment permalink

Awesome!!! As all your plugins I’m using and need.

One more idea. Is it possible to add a Post-Processing action like in the “normal” File Export. I use this Post Action to add my watermark, which I think is quite usefull when uploading to the web….

Cheers Chris

A post-processing section wouldn’t help because the “post” means “after”, meaning after they’re already uploaded to Flickr. If you want to add a watermark, several options come to mind: Lightroom’s built-in watermarking (which is pathetic), Tim Armes’ LR2/Mogrify plugin, or my run-any-command plugin. —Jeffrey

— comment by Chris on September 23rd, 2009 at 8:30pm JST (14 years, 5 months ago) comment permalink

I like your awesome plugin.

LR has a nice feature for the slideshow – adding frames and watermarks.

I would like to export these slideshows directly to flickr but my tries were not successful – just the play developed pix were exportet – without the frames and watermarks.

There’s no interaction between export proper and slideshow, so the Flickr plugin can’t do anything with the slideshow. Most people who want frames and watermarks with their exports use Tim Armes’ LR2/Mogrify plugin. —Jeffrey

— comment by JPK on September 29th, 2009 at 1:24am JST (14 years, 5 months ago) comment permalink

When I tried to upload one photo to flickr the bar stays at 50%, later on a notice telling me it’s disconnected from the network which is false. I have try different things, installing, unistalling, etc. but no avail. Please let me know what’s going on. I am using a portable PC Lenovo S10e w/XP home, on my Macbook works perfect.


Luis Gomez
Bogota, Colombia

LR just uses your system networking, so if you’re having networking issues, you’ll need to investigate your system or your ISP. Of course, it could also be Flickr having issues as well, but in any case, it’s not specifically related to the plugin so I couldn’t do anything but speculate. —Jeffrey

— comment by Anonymous on October 1st, 2009 at 3:43am JST (14 years, 5 months ago) comment permalink

When exporting photos to a set in Flickr those photos that have been previously exported do not get added to the set created. Is there an option or method to allow this to occur?

Check the All/Updated/New selector in the Export Dialog, as well as the Replace option. If after checking that out you think the plugin’s not doing something right, please send me the plugin log (via the “Send to Jeffrey” button in the plugin manager) along with a description of what happened vs. what should have happened. —Jeffrey

— comment by MDSchilling on October 1st, 2009 at 9:03am JST (14 years, 5 months ago) comment permalink

Hi Jeffrey, thanks a lot for an awesome plugin that has saved me hours, no, days of manual work!

Since a few weeks I have an issue with the login-process at Flickr. The situation has become really bad as I see up to 20 error messages saying “Attempt #… error “timedOut”, retrying now…” before it is able to login at Flickr. I am not sure, if it relies to Flickr (which I assume) or the plugin, but it is really annoying and takes a lot of time. After a successful login the photo export is working, but sometimes I see timedOut errors here, too, which causes the photo to be uploaded more than once.

I did not find any similar issue in the comments and would like to fix that. Do you have any advice for me?

Thanks in advance and keep up the good work!

It sounds like a networking/Flickr thing, unrelated specifically to the plugin. Flickr occasionally has issues, but I’ve not seen many reports lately, so maybe it’s something with your system, networking, or ISP? —Jeffrey

— comment by Thomas on October 3rd, 2009 at 12:56am JST (14 years, 5 months ago) comment permalink

I used your geo-encoding plug-in and it has worked very well. My problem is when I upload to Flickr.

I made the mistake of uploading from two different folders at the same time. I started uploading from the 11th September folder, then while it was still uploading, started uploading the 12th September folder. Both were headed for the same set on Flickr. All the photos were geocoded and have the correct positions.

When I look at the set on Flickr I find that some of the positions have been flipped. Some of the photos from the 11th have positions of the 12th and vice versa.

Does this surprise you?

Yes, very much…. simultaneous uploads should be fine from the plugin’s point of view, and I’d certainly expect that it would be fine from Flickr’s. I’ll give it a try… —Jeffrey

This has happened using Flickr plugins 20090916.125 and 20091013.126

This photo is in the correct position and was taken on the 11th. It was uploaded as part of one batch.

This photo was taken at the same time (11th) but shows a position where we were on the 12th. It was uploaded simultaneously with photos taken on the 12th.

I thank you for your plugins and in future I will not attempt simultaneous uploads.

You will have worked out that the photos were taken in Nova Scotia, but I am writing from Bristol, UK.

Best Wishes.

— comment by Graeme Churchard on October 16th, 2009 at 12:42am JST (14 years, 5 months ago) comment permalink

Jeffrey… LightRoom 3b is out and I’m considering giving it a try, but…. are your plugins supported?

thnx 🙂

Did you not notice the most recent version history at the time of your comment? Yes, new versions of my plugins seem to work in LR3b, but they haven’t been tested extensively. It doesn’t hurt to try them, though; registration is not required. —Jeffrey

— comment by paolo savonuzzi on October 22nd, 2009 at 7:27pm JST (14 years, 4 months ago) comment permalink

… ooops… sorry , Jeffrey 🙁
as I usually update from PluginManager… didn’t noticed that note 🙁 🙁 🙁

thnx 🙂

— comment by paolo savonuzzi on October 22nd, 2009 at 9:05pm JST (14 years, 4 months ago) comment permalink

first issue with both flickr and facebook plugins in LR 3b: after loading them for the first time, an “Update Catalog” alert pops-up and, after clicking OK, plugin’s window is sent *behind* Plugin Manager’s window so… 😉


Just pushed a fix. —Jeffrey

— comment by paolo savonuzzi on October 23rd, 2009 at 3:41am JST (14 years, 4 months ago) comment permalink

Hi. I’m using version 20091023.128, from LR3beta on Win32.

Thanks for the plugin Jeffrey. Now I’ve read the comments above, and I’ve noticed the question of “ordering” has been asked over and over, but it just seems it doesn’t work with LR3. I just created a Flickr published collection, dropped a few photos there for LR to upload, and the plugin doesn’t upload them in the order they are specified in grid mode. I tried re-ordering some in the grid (User Order), I tried “A/Z”, I tried selecting “Order by Filename”, no success: LR consistently upload them by Capture Time. I guess you can re-order a photoset later on from Flickr’s Organizr, but for many Flickr users the order in the photostream itself matters a great deal. On the other hand, Adobe’s own Flickr plugin in LR3 has the same issue (or maybe I’m mis-using both).


I’d chalk this up to “beta”. I’m pretty sure that the real LR3 will be able to do The Right Thing. It’s been on my SDK request list for a long time. —Jeffrey

— comment by Sebastien on October 26th, 2009 at 12:50pm JST (14 years, 4 months ago) comment permalink

Hi Jeffrey,

Great plugin that I’ve been using happily for a few months. It really makes managing Flickr much easier. However, I was wondering if there is a way to set the license by keyword, similar to the Privacy, etc. settings. Specifically, I’d like to be able to override my default license on Flickr for selected photos on upload, rather than having to do so manually in the Organizr after uploading. Not sure if this is possible, but it would be a great feature to have.

Added in .129 —Jeffrey

— comment by Tim Sackton on October 27th, 2009 at 3:44am JST (14 years, 4 months ago) comment permalink

Feature Request: I’d love to be able to associate certain LR tags with Flickr pools, so that I can automatically have a picture tagged with “Landscape” automatically end up in landscape-related pools I belong to. This would greatly help increase participation in the Flickr communities.

— comment by Scott Hill on October 27th, 2009 at 4:46am JST (14 years, 4 months ago) comment permalink

@Scott Hill : me too see here

Alright, alright… spent all day today on it… version .129 now has it. —Jeffrey

— comment by Florent on October 27th, 2009 at 8:21am JST (14 years, 4 months ago) comment permalink

@Florent: Sorry I missed that. Glad to see someone else wants it too. Maybe that improves chances that it’ll make it in.

— comment by Scott Hill on October 27th, 2009 at 8:59am JST (14 years, 4 months ago) comment permalink

Hi Jeffrey,

I just started using the post to Twitter feature of your plugin, and I have a small request that (hopefully) wouldn’t be too hard to implement.

I see that you use as a URL shortener, which is fine.

Flickr has its own baked in short URL’s, that look prettier if only because it has “flickr” right in there. See their FAQ –

Is there any possibility that you can give us an option to use Flickr’s short URL’s when posting to Twitter, rather than

It turns out that this will be very difficult to implement due to the ridiculously shortsighted design of the Lua language that Lightroom uses for plugins. If someone happens to have a Lua routine that converts an arbitrary-length string of decimal digits into its base-58 representation, I’d like to hear about it. —Jeffrey

— comment by Eric on October 31st, 2009 at 12:27am JST (14 years, 4 months ago) comment permalink

Here’s a feature request (because not enough people pay their money and then demand a feature =) : How about the ability to save your progress on an incomplete Flickr Export dialog so you can go back and fix/change/adjust something you forget in LR (titles, descriptions, tags, etc), but only realize the error after you’ve done the work of preparing to export within the dialog itself? Instead of Export/Cancel as the only two options, maybe a third that would serialize & store the temporary state of the dialog, and reload it the next time the dialog is opened, unless someone completes the operation or cancels it? Make it easier and less “lossy” to jump between LR and the export dialog (and back).

Writing from the great middle west of North America, in the state of Illinois, in a little place called Towanda. Version 20090725.122

It already works like that, at least for LR2 (I’m not sure about LR1). Changes stick until you change them back. If you’re not seeing that, it may be possible that you have a corrupt LR preferences file. —Jeffrey

— comment by EyePulp on November 3rd, 2009 at 6:32am JST (14 years, 4 months ago) comment permalink

Did you know that Flickr is now showing the tool used to upload pictures? Each photo has an “Additional Informaton” panel. My photos say “Jeffrey’s Export-to-Flickr Lightroom Plugin” which links to a page in Flickr’s “App Garden” which in turn links to your site.

That Flickr page could do with a screenshot of the plugin.

Congratulations! But maybe soon you’ll need to hire a support staff to deal with all the questions.

Ah, I didn’t know that the App Garden had gone live. It was in private beta for a while, so I didn’t spent much effort on it. Will give it some attention. Thanks for the heads up. —Jeffrey

— comment by BKKPhotographer on November 7th, 2009 at 2:30am JST (14 years, 4 months ago) comment permalink

Dear Jeffrey,

Thank you for adding the ability to set groups via keywords (I hope this option will be developed in the future with the ability to create sets of groups and write rules).

For the moment I found a little bug in the combolist : I do not have all my groups (220 currently), only about half are displayed (they all appear in the previous section).

Other requests:
Is it possible to have a new keyword giving altitude rounded and formatted? I use the altitude in the legend of some photos but I do not need accuracy below the meter.

eg 2082.2 m => 2 082 m


You can use the Places filter to do this, e.g. {Altitude:Places=0} —Jeffrey

— comment by Florent Bouckenooghe on November 9th, 2009 at 12:47am JST (14 years, 4 months ago) comment permalink

I’m from the west of Scotland 😉

I have some issues with associating photos to ones uploaded.

First matching with criteria other than date created, I know this has been mentioned before but would it be possible to match title/ description instead of date rather than as well as. I have photos on flickr where the local PSD image got deleted. It would be good to be able to associate a new PSD image with the older image on flickr. Could the At Flickr field be made editable?

Second, for some reason the plugin reports that all selected images are associated with uploaded images even when quite clearly not so, I can recreate the issue as follows:-

1: Create a new picture in photoshop, save it and add it to my lightroom cat.
2: Upload the image via flickr uploader or web interface

I now have the image in the catalogue, the meta states uploaded to flickr – No, but the image is also on flickr without exporting from the plugin.

If I now go to plugin extras and click associate the plugin reports that all images are associated with uploaded photos.

I am not sure if this is specific to files created with photoshop as I don’t have any other editing software available.

Finally, when an image is edited externally by selecting edit in photoshop from lightroom context menu the edited image changes in the lightroom view but does not update in the export plugin, I have to synchronise the folder and scan for meta changes before the plugin knows there is a change – Is this normal behaviour?


The whole “associate photos already at Flickr’ thing needs more TLC. Hopefully, I’ll be able to address it more thoroughly while working on the LR3 version, with its more integrated “Publish” functionality. About your final question, I don’t quite understand it. “Edit in…” creates a new file, unless the file is already a PSD and you select to “Edit original”. In the latter case, I would expect all parts of Lightroom to reflect the changes, so if you’re seeing it reflected in one place but not another, that sounds like a LR bug. —Jeffrey

— comment by Louise on November 9th, 2009 at 11:32am JST (14 years, 4 months ago) comment permalink

Hi Jeffrey,

First I want to thank you for your great job on these plug-ins. Are a real time saver and very useful!

With regard to this post, I have the same issue on version 20091027.129. If I select a batch of photos (e.g. 50) and try to associate them with the ones from Flickr, some of them are not associated (Associations not made due to time/name conflicts). If I’m searching for those photos manually and select them individually, I can associate them with success. Is there a way to debug this on my end?

Also, I have some small feature request (sorry if was mentioned before).
I have a bunch of photos already uploaded on Flickr, containing tags, GPS locations (using Flickr interface), titles, descriptions.
It would be nice to have an option to grab this information from Flickr to LR2 on the association process.

Best regards,
Razvan from Vancouver

— comment by Razvan on November 13th, 2009 at 10:58am JST (14 years, 4 months ago) comment permalink

LE on my previous comment (it seems I cannot edit it).

I think I know why some images cannot be associated – some of them have the same timestamp (taken using the continuous mode) with the one from Flickr, so the plug-in doesn’t know which photo to associate.
Another feature request would be to have an option to associate the photos by 2 criteria: timestamp and title (or any other attribute that you consider to be more relevant). If there are more images with the same timestamp, then check the 2nd attribute.

Best regards,

— comment by Razvan on November 13th, 2009 at 11:06am JST (14 years, 4 months ago) comment permalink

Hi Jeffrey,

Firstly thanks for a great plugin, and the Smugmug one also.

Secondly a small feature request, would it be possible to allow the Upload Date to be set as this could really help to organise the front page?

Thanks Louis (UK)

The Upload date at Flickr? I wonder whether that’s even possible…. I’d think that it would be forced to, you know, the date you uploaded… —Jeffrey

— comment by Louis on November 14th, 2009 at 6:50am JST (14 years, 4 months ago) comment permalink

The Upload date at Flickr? I wonder whether that’s even possible…. I’d think that it would be forced to, you know, the date you uploaded… —Jeffrey

Actually it isn’t.

You can certainly change the date posted on the Flickr site, many people use this facility to push new photos they don’t want people to see (uploaded for use in another site for example) to the back of their stream and of course the other way round to bring a photo back to the front of the stream to get more comments.

As to the possibility of doing this through the API I don’t know, I have never used the facility on the site nor in API apps.

— comment by Louise on November 15th, 2009 at 9:05am JST (14 years, 4 months ago) comment permalink

Hello Jeffrey,

Sorry for the delay in responding. I haven’t a token called Altitude and if I try {GSPAltitude:Places=0} it doesn’t work because GPSAltitude is not numeric (unit in meter is included in the token). Another solution ?

Just pushed a new version that gives you a couple of ways to do it… see the version notes for details. —Jeffrey

— comment by Florent on November 15th, 2009 at 8:32pm JST (14 years, 4 months ago) comment permalink

Thanks for the speedy response Jeffrey.

There is an API call that does it, I have used a product recently on the AppGarden which works but is a bit messy, which is why I thought that it might be nice to do it when uploading, or in version 3 of Lightroom it could even be a meta data management thing.


— comment by Louis on November 15th, 2009 at 8:50pm JST (14 years, 4 months ago) comment permalink

Hey Jeffrey.
Just wanted to say ‘thank you’ for adding the option to set the upload date manually. This is very handy because….
A tip for everyone – this is the only way to keep photos from showing up in your photostream!

Thanks again.

— comment by John on November 16th, 2009 at 6:19pm JST (14 years, 4 months ago) comment permalink

Thanks again Jeffrey for such a speedy update to the date settings, have tried it and it works fine.

Just wondered if it might be nice to be able to set the date manually as well?


— comment by Louis on November 16th, 2009 at 11:35pm JST (14 years, 4 months ago) comment permalink


First, thanks for such awesome time-saving plugins.
Second, just used the flickr “Groups via keywords” feature – brilliant idea.
Third, be great to also have a “Sets via keywords” feature

(Berkshire, UK)

— comment by Jim S on November 18th, 2009 at 8:11am JST (14 years, 4 months ago) comment permalink


I must say that you are the best 🙂

Thanks a lot for this update

(Reunion island)

— comment by Florent on November 18th, 2009 at 8:35pm JST (14 years, 4 months ago) comment permalink

I really like the addition of the Posted Date option for setting Flicker’s Posted date. Thanks.

I’d like to suggested an addition for the Posted-Date, to allow the option of typed-in date for more control of the photo stream. This would allow users to push currently taken pictures to the back of the photostream for sorting. This is handy when you want users to view your more arty pictures but also have a large volume of sports pictures from your son/daughter’s team. This would be perfect for organizing them.

Thanks for all the great work.

Added in version #134. —Jeffrey

— comment by Michael on November 25th, 2009 at 12:47am JST (14 years, 3 months ago) comment permalink

Jeffrey, love your flickr plugin! I shoot a lot of action shots that I’ve already uploaded to flickr before I began using your plugin. I’m trying to associate these pictures using the “Associate Images” button in File->Plugins Extras->Flickr Extras, however, many are not able to be associated because the date/time using hh:mm:ss resolution yields many duplicates.

My Canon 40D (and I’m sure many other cameras) include sub-second timing in EXIF data and I see that Flickr also can display sub-second timing (Sub Second Time Original / Sub Second Time Digitized).

Is there any way you could use the sub-second timing as part of the process to associate existing flickr photos?



I’ve spent some time on this, and a solution does not present itself. Neither Lightroom nor Flickr give me access to the sub-second time )-: ) —Jeffrey

— comment by Jeff Thompson on November 28th, 2009 at 7:11am JST (14 years, 3 months ago) comment permalink

Hi Jeffery, I think I found a problem with the geotag “location visibility” setting in the flickr plugin. It doesn’t seem to work with keywords that begin or end with dashes. For example, I use the keyword -nogeo- for photos where I don’t want the location visible. In the geotag “location visibility” setting I added the -nogeo- keyword to the “location visible to no one else” (see screenshot link below). But after uploading to flickr the location is set to “Anyone will be able to see this on the map”. When I change the keyword to nogeo or no-geo it works correctly.

Screenshot of my geotag location visibility settings to reproduce the bug:

Mac OS X Snow Leopard 10.6.2
Lightroom 2.6 release candidate
flickr plugin version: 20091125.134
Geoencoding plugin version: 20091121.101

Thanks in advance!


Sorry about that… just pushed a fix (version 135). —Jeffrey

— comment by Barry on November 29th, 2009 at 12:13pm JST (14 years, 3 months ago) comment permalink

I am testing the last .135 plugin, with LR3b on OS/X 10.6.2 and I’m not sure I understood the destination set logic.

In the LR3 default Flickr publisher, the Publish photoset name is used as Flickr set name.

In your plugin you can select the destination set. I used the ‘Add new photoset” and I thought this is enough, but apparently it isn’t.

Is there any way to automatically select the destination Flickr set based on the Lightroom photoset?

Thank you,


Frankly, I’m not sure what’s going on with LR3b and Publish. “It’s a beta”. Still working on it. —Jeffrey

— comment by Liviu Ionescu on November 30th, 2009 at 8:06pm JST (14 years, 3 months ago) comment permalink

Jeffery, Even with my comments/suggestions below. This is already the best Flicker uploader. Thank you!!!

When uploading a batch of pictures to a set. The pictures are displayed in reverse order.
Could a sorting order option be added?

Also is there a way to change the upload date for a picture that has already been uploaded? It seems the only way would be to replace the picture (not update it) but this would loose all coments and views. Is there a trick or could this option be added?

Thanks for a great tool.

The plugin uploads in the order you have them when the export is invoked, and while there’s no easy way for the plugin to reverse the order for you, it’s a simple matter of chaning the A/Z sort-order icon to Z/A before invoking the export. About the upload date, there’s no way to change that from the plugin after the fact, and I don’t forsee anything like that being added any time soon…. it’d have an extremely limited audience. —Jeffrey

— comment by Michael on November 30th, 2009 at 10:35pm JST (14 years, 3 months ago) comment permalink

Thanks so much for the quick fix, location visibility works perfectly now.

— comment by Barry on December 1st, 2009 at 9:10am JST (14 years, 3 months ago) comment permalink

Jeffrey Friedl’s “Export to Flickr” Plugin
Version 20091209.137

Hi Jeffrey,
First of all, what a great plugin! I just made a Flickr account, and realised I once read about uploading directly from Lightroom.
I normally use the ‘Add copyright watermark’ option under the ‘Metadata’ tab during exporting.
I was happy to see this is also in your plugin, however when I upload the pictures there is no watermark…

Are there more people that experience this problem? I have an Apple Macbook Pro.

Kind regards,

Did you perhaps have the image format set to “Original”? That sends out the original file (as opposed to merely using the original format, which the name might imply). If you want Lightroom changes reflected, you’ll want “JPEG”. —Jeffrey

— comment by Bas on December 11th, 2009 at 6:24pm JST (14 years, 3 months ago) comment permalink

Hi Jeffrey,

Thank you for your quick response.
I checked my export settings, and found out that when exporting a JPEG it does add the watermark, but when I export a CR2 file it doesn’t. (Both with image format set to JPEG)
A workaround would be to first export the images to JPEG, then import those and export to Flickr. But then I guess it’s not really a benefit anymore.

Kind regards,

The source of the image doesn’t matter – if the destination is JPEG, it’s adding the watermark. However, the LR2 watermarking support is pathetic, and if the output image is large, the watermark might be so small that you can’t see it. Try adjusting the sizes of the output image or the watermark. Watermarking is better supported in LR3b, but those who want real watermarking support generally use Tim Armes’ LR2/Mogrify plugin. —Jeffrey

— comment by Bas on December 12th, 2009 at 12:21am JST (14 years, 3 months ago) comment permalink

Hi Jefferey,

Thank you so much for guiding me reset my preferences. Pending any major setbacks, I think I’m set on utilizing LR3 for my post process workflow. However, it would be lovely if you could add the keyword capability to your tokens.

Also, I’m pretty sure it’s been addressed, however, I’m unable to find the answer in the previous posts. I have all your plugins installed on my lr3b and the publish feature shows the url to the pics on flickr/facebook but shows “No” under “Uploaded to flickr/facebook” heading. Ironically, it works just fine when I try to export the same pics via the export menu item. But all the flicr/facebook and picasaweb “extras’ give me the following errors — flickr(?:15354: attempt to call field ‘?’ (a nil value)), facebook(?:14964: attempt to call field ‘?’ (a nil value)), picasaweb(?:14924: attempt to call field ‘?’ (a nil value)).

As always, your contribution to these awesome plugins is greatly appreciated!


Everything is up in the air with LR3b…. it’s a beta, as is support for my plugins on it…. —Jeffrey

— comment by Devender Narang on December 14th, 2009 at 9:56am JST (14 years, 3 months ago) comment permalink

Thank you very much for your great work with this plugin. I like it way more than the flickr upload provided by Adobe in the LR3 beta.

Keep up the good work!
Greetings from Germany,

— comment by gwegner on December 15th, 2009 at 4:10am JST (14 years, 3 months ago) comment permalink

Very minor gripe: I’d like a the “new set” box to be available at all times. Now I have to scroll down through the long list, with would save me a few click everytime 🙂

— comment by Remco on December 17th, 2009 at 3:38am JST (14 years, 3 months ago) comment permalink

I downloaded Flickr and Facebook – fantastic – thanks for all the work. I also registered them immediately.

I can’t find them on the Export page.

Is this because I moved all my work to an external hard drive or am I just being stupid?

Do I need to download them, register and start again?

Happy New Year.


Check the instructions; Adobe didn’t make it very obvious how to select a different exporter. —Jeffrey

— comment by Jonathan on December 27th, 2009 at 9:54am JST (14 years, 2 months ago) comment permalink

Just wanted to say thanks so much for this. Just discovered that I did not title my photos before uploading them to Flickr and the Flickr Extras saved me a mess of time correcting things. Will definitely be renewing my license when LR3 gets out of beta.


— comment by Ken on December 28th, 2009 at 3:10pm JST (14 years, 2 months ago) comment permalink

Flickr Export plugin – 20091223.143

A new bug was introduced with one of the December updates where the plugin no longer captures the URL of the uploaded/exported photo and adds it to the Lightroom metadata for that photo. It does still capture and write the date, time, and uploaded status correctly, but nix on the URL (which has proved to be somewhat problematic).

I believe the field is “At Flickr”

Sorry about that… it seems to have gotten nicked unintentionally by a change elsewhere. Just pushed a fix (that will now include it after subsequent uploads). Thanks for the heads up. —Jeffrey

— comment by Chris Kelley on December 30th, 2009 at 12:47am JST (14 years, 2 months ago) comment permalink

Please state which versions are affected by the bug fixed in v145/146. Thanks.

v142 was the first to be affected, I think. —Jeffrey

— comment by itsnotvalid on January 1st, 2010 at 5:24am JST (14 years, 2 months ago) comment permalink

Hey Jeffrey,

Maybe a small extra feature for your export tool would be great ( maybe it has been asked before? ):

When the export has finished, close down lightroom and pc…
I tend to export to flickr late at night and it takes some time to process, so it would be great if the pc would auto shut down when the export has finished 🙂

— comment by Depechie on January 4th, 2010 at 6:51am JST (14 years, 2 months ago) comment permalink

hey great plugin, I was wondering if there is a way to link directly to an image when tweeting instead of the photoset, it says but it goes to the photoset. Also I noticed that no url shortening is happening, I would like to use flickrs or but I don’t see that its doing it, is there an option? I am using plugin version. 20091230.146

The URL shortening happens only if it’s needed…. I figure that people prefer to see the actual URL if possible. (I’d like to use the Flickr short URLs, but it’s not at all easy to do due to severe limitations in the host language that Lightroom plugins are written in.) You should be able to use the per-photo URL via the <firstphoto>tag. —Jeffrey

— comment by Robert on January 5th, 2010 at 1:41pm JST (14 years, 2 months ago) comment permalink

I noticed that the url isn’t always present, especially if I upload an image using your plugin through lightroom its weird, I would prefer a short url automatically so that I can add more hash tags or something, is that something you may be able to built in, such as Will it detect if I am over the character limit and shorten the url for me? Thanks.

Yes, it will detect when you’re over limit and shorten urls as needed to get you under. Does that not make sense from a user’s perspective? About the per-image url not being present, the next time you notice that, please send the plugin log (using the “Send to Jeffrey” button in the plugin manager) and I’ll check it out. —Jeffrey

— comment by Robert on January 7th, 2010 at 11:53pm JST (14 years, 2 months ago) comment permalink


I really enjoy using your plugins! Thanks for all your work. I had to reformat my computer and reinstall Lightroom. How can I re-register your plugins?


Just reenter your original codes… they should likely still work. They should be in your PayPal history, but if you can’t find them, drop me an email…. —Jeffrey

— comment by Alex Chin on January 8th, 2010 at 10:59pm JST (14 years, 2 months ago) comment permalink


can the plugin (mass) update tags, headlines etc. on Flickr witout resending the picture (which is ever so time consuming)?
Does the Flickr API allow for this at all?


Yup, see File > Plugin Extras > Flickr Extras. —Jeffrey

— comment by Anonymous on January 13th, 2010 at 9:29pm JST (14 years, 2 months ago) comment permalink

Hi Jeffrey
Your “Post to Twitter” feature is great to keep my contacts informed of my new pictures.

Can we imagine having in the future some new special codes, like for the title of the picture ?

(Great job !)

— comment by Samy on January 17th, 2010 at 6:15am JST (14 years, 2 months ago) comment permalink

Hello Jeffery,

I downloaded the latest version of your plug in. Thanks and it works great. I just wanted to know, after uploading pics, in LR3 I just can’t find a way to delete the small collection of photos I just uploaded from the Flickr publishing area.

Is this a LR3 functionality or a plugin functionality?


Mac OS X 10.6.2


The new Publish stuff is only barely supported, and mostly untested, in the LR3 beta. The beta’s plugin-related stuff is sufficiently buggy that I don’t expect I’ll do much with it. Look for real support in the real LR3 when it comes out. —Jeffrey

— comment by Danny on January 20th, 2010 at 9:39am JST (14 years, 2 months ago) comment permalink

“Posted date” option not working?
I have enjoyed the option to change the posted date when uploading from lightroom. Today, I ran into an error with that option and am wondering if the lightroom plugin needs to be updated. The error is
“An internal error has occurred: Access to undefined global: GrokUploadDateSpec”

Sorry about that… just pushed a fixed version. —Jeffrey

— comment by PDo on January 21st, 2010 at 4:59am JST (14 years, 2 months ago) comment permalink

Hi Jeffrey,

I’m trying to use the “Flickr Extra” command to push updated title, caption and tags but am getting the following errors.

Resend Metadata: None of the selected photos had yet been uploaded to the “devendernarang” account at Flickr, so there was nothing to resend.

Associate Images:

?:5173: assertion failed!

+1327.7: [x118ad4d48] line 5700:
Assertion failed(!):
+1327.7: [x118ad4d48] line 5700
+1327.7: [x118ad4d48] line 19608
+1327.7: [x118ad4d48] line 15675

Thanks for your help in advance.


Like the warning above the comment-box says, I need the plugin version to be able to do anything. —Jeffrey

— comment by Devender Narang on January 22nd, 2010 at 1:50am JST (14 years, 1 month ago) comment permalink

With Windows XP and all current patches, Lightroom 2.6, trying to use the Flickr Extras to Associate Images, as I do quite often, I’m just now getting

+6.8: [5B698F0] line 5733:
Assertion failed(!):
+6.8: [5B698F0] line 5733
+6.8: [5B698F0] line 19715
+6.8: [5B698F0] line 15782

You’ve had a few updates lately so I applied those, restarted LR, but still the same error.

Like the warning above the comment-box says, I need the plugin version to be able to do anything. —Jeffrey

— comment by Jason Abbott on January 22nd, 2010 at 12:23pm JST (14 years, 1 month ago) comment permalink

This is with version 20100121.149. I had the same problem with the version I just upgraded from. Today’s numbers are a little different, though:

+46.5: [7D70EE0] line 5733:
Assertion failed(!):
+46.5: [7D70EE0] line 5733
+46.5: [7D70EE0] line 19715
+46.5: [7D70EE0] line 15782

Thanks, that’s exactly what I needed. Just pushed a fix. —Jeffrey

— comment by Jason Abbott on January 23rd, 2010 at 8:57am JST (14 years, 1 month ago) comment permalink

Hi Jeffrey,

Thanks for fixing the issue “Flickr Extra” command. However, now when I try to “Associate image” I get the following error repeatedly: “?:14049: attempt to compare two nil values”

Thanks for helping resolve this.


I just pushed a version that might fix this. If it doesn’t and you need to report the bug again, please report the version number… is it really too much to ask? —Jeffrey

— comment by Devender Narang on January 24th, 2010 at 5:27am JST (14 years, 1 month ago) comment permalink

Just did the auto update and now have errors with plugin. Version is 20100123.150 Lightroom 2.5

Error is the following.

Plug-in error log for plug-in at: Y:\DATA_MY DOCUMENTS\JIM\LightroomPlugins\flickr-jfriedl.lrplugin

**** Error 1

Could not create info sections for plug-in.
?:4953: attempt to index upvalue ‘?’ (a boolean value)

I’m hard pressed to understand how this error is happening, but it’s related to some debugging code I put in the other day, so I’ve reverted it… let’s hope that takes care of it! —Jeffrey

— comment by Jim on January 24th, 2010 at 7:25am JST (14 years, 1 month ago) comment permalink

Hi Jeffrey,

My apologies… no, it is not too much to ask — I’m using version, flickr-20100124.151.

The last push fixed it but perhaps introduced another bug. Now when I hit “Clear”, I get the following error “LrCatalog:withWriteAccessDo: must be called from within an LrTask”

Please advise.

Thanks much,

Ah, it seems you’re using the LR3 public beta (the LR version is another tidbit I need with bug reports). LR3 support will remain tenuous at best until the real LR3 comes out, but I’ll patch things up when I run into them; just pushed a new version with a fix for this. Thanks. —Jeffrey

— comment by Devender Narang on January 25th, 2010 at 5:29am JST (14 years, 1 month ago) comment permalink

Hi Jeffrey,

Thanks for the nice Flickr plugin!

I just downloaded 20091230.152 and made some test uploads. There seems to be some issues with the upload date/time metadata:

1. The Flickr Upload Date field in the Metadata panel shows the upload time – and vice versa.
2. In the Library filter bar the filtering for Flickr Upload Date show a list of times (not dates).
3. The date and time formats for the uploads in the Metadata panel is different than what the settings are (12 h clock in stead of 24 h, and dates in YYYY-MM-DD in stead of DD/MM/YYYY.

Any ideas what could be the problem?

Oslo, Norway

Mac OS X, Snow Leopard
Lightroom 2.6
Plugin version: flickr-20100125.152

Hahahaha, I swapped the date and time in one place that the plugin updates the info… how’s that for quality control /-:. Sorry. Fixed in v154…. the first time you load the plugin, it’ll spend a moment or two to fix the entries that are already there. About item #3, there’s nothing I can do about that in LR2, but LR3 gives a plugin insight into the user’s preferred formats, so the first time you load the plugin in the real LR3 (whenever it comes out), it’ll again spend a few moments to update everything to your preferred formats. —Jeffrey

— comment by Jan on January 26th, 2010 at 6:28am JST (14 years, 1 month ago) comment permalink

dear jeffrey!
Your “Post to Twitter” feature is great to keep my contacts informed of my new pictures.
Can we imagine having in the future some new special codes, like for the title of the picture ?

I just pushed v153 with a bunch of new Twitter-related stuff, including tweet-template tags for title and description. —Jeffrey

— comment by haci abbas on February 2nd, 2010 at 7:45pm JST (14 years, 1 month ago) comment permalink

Hi Jeffrey! Plug-in just gets better and better.

I really like the keyword-based group feature… I keep it in my main preset to send pictures tagged “365” to the Project 365 group, eg. It would be great to be able to do the same thing with sets!

— comment by dave glasser on February 3rd, 2010 at 4:08pm JST (14 years, 1 month ago) comment permalink

Like the geotag plugin…. GREAT STUFF!!! I post some geotagged photo’s to flickr. So this flickr plugin and the geotag plugin… were the ones for me.

Compensate this guys’ work like I did… and if you can not the 1 eurocent!

— comment by Marco on February 6th, 2010 at 6:28pm JST (14 years ago) comment permalink

I updated to the latest Flickr export plugin and for some reason am now getting an error on all my exports:

“Unable to export

The preset for ‘DESCRIPTION_SPEC’ no longer exists”

Not sure if it’s a coincidence and I did something inadvertently in my configuration or something is wrong with the latest plugin.

Anyone else experiencing this?

That message is saying, fairly poorly (sorry), that the description preset encapsulated in an Export Preset some time ago can not be found now when you’re trying to use the Export Preset. Did you perhaps edit your set of description presets and delete one? Or bring the Export Preset from another system? Or reinstall your LR? This is one of those areas where I put in a simple check for something that doesn’t happen often, and never got around to actually look reasonable… must look into that. —Jeffrey

— comment by TC on February 7th, 2010 at 6:45am JST (14 years ago) comment permalink

I just upgraded to 20100102.105 and did the catalog update (all in 2.6) and now my smart collection with a “Uploaded to Flickr is No” includes all sorts of things that have been uploaded to Flickr.

LR2 has some issues with custom metadata, so first I want to try to differentiate between that and a bug in the plugin…. does restarting LR fix the problem? When you select an image you know you’ve uploaded to Flickr and view the “All Plug-in Metadata”, does it show “Uploaded to Flickr: Yes” and a url? —Jeffrey

— comment by dave glasser on February 7th, 2010 at 2:10pm JST (14 years ago) comment permalink

Restarting Lightroom did the trick. Thanks!

— comment by dave glasser on February 7th, 2010 at 2:20pm JST (14 years ago) comment permalink

Hello Jeffrey. First, this is a WONDERFUL tool.

I’d like to be able to set the title/description “on the fly” at the time of export, regardless of the amount of pictures in the batch (i.e., one or fifty)… so adding to the existing presets, there could be a text field where I could define a title just for that export…

Keep doing this great job! Thanks a lot, Eduardo

— comment by Eduardo Green on February 13th, 2010 at 2:38pm JST (14 years ago) comment permalink

Jeffrey, these have been some impressive updates to an already robust plugin. You’ll be happy to know after several months of owning a twitter account and never having actually tweeted, I let your plugin post my first tweet. Tweet by proxy, we’ll call it.

My one request would be to add another variable placeholder in the Twitter string – – to get the actual photoset id being created at flickr (instead of the full flickr url). My use case is that my flickr stuff is available via my personal site under the same photoset id value, so it would be really nice to Tweet “Hey, look at my new junk @

Using version 20100210.157

thanks for all the work…

v158 now has this… see the dialog about special codes above the tweet-text input box. —Jeffrey

— comment by Andrew Hughes on February 14th, 2010 at 2:47pm JST (14 years ago) comment permalink

Hi Jeffrey !
I use your great plugin everyday !
But, is it possible to imagine to have some “predefinable” tags template ? In fact, I am part of photo project with everyday-posted photo, with same tags each time : so if, between theses photos, I change my tags, I need to retype them after. (I don’t know if you see what I mean 🙂

Thanks for all !

You can create an export preset (upper-left of the Export Window)…. that encapsulates all the settings, including tags. You can then use it as the basis for later exports by selecting it, then making any changes you like before launching the export. —Jeffrey

— comment by Samy on February 21st, 2010 at 7:24pm JST (14 years ago) comment permalink

Version: 20100205.154
LR: 2.5
Win7 64bit

I’m using this plugin along with your metadata wrangler, and I have set to remove a lot of things, but leave camera information in there.

But the flickr plugin seems to be removing all metadata. Once it’s in flickr, there is no metadata attached to the images. It used to work some time ago last year, but I have noticed that recently none of my uploaded photos do have that metadata.

Do you know what’s going on?


Are you sure Lightroom is not removing it all (via the option in the Metadata section of the export)? You can have the export go to a local folder (rather than temporary folder) and the images will be left there after the upload, so you can see exactly what was sent to Flickr. If you see the data in the files but not on Flickr, you’ll have to bring it up with them. If it’s not in the files, then something in Lightroom, such as my plugins, is removing it. —Jeffrey

— comment by talsit on March 5th, 2010 at 6:21am JST (14 years ago) comment permalink

Just wondering (couldn’t find this documented in the templates), is it possible to conditionally add a keyword? To be more specific, I’d like to add the geotag coordinates and the “geotagged” tag, but only if the picture actually is geotagged.

I have a slight feeling that something like “geo:lat=” and “geo:lon=” would only be added if the picture has GPS coordinates (or at least this is how it should work – I wouldn’t see the point in getting blank lat/lon — haven’t tested it though), but for the “geotagged” tag I can’t seem to find a way to restrict it to just the right pictures. Of course I could do this manually in LR, but was wondering if there is a way to automate the process.

Otherwise, many thanks for the excellent work!

— comment by Lucian on March 6th, 2010 at 1:04am JST (14 years ago) comment permalink

Your plugin seems like a great idea, but can’t seem to get it to work. It won’t connect to flickr when I try to authenticate the plugin, nor will it connect to your server when I attempt to register the product or search for updates.

When authenticating I get the error “connectConnectToHost”.

Is this for windows only?

No, it should work on any system that LR can run on. Sounds like Lightroom can’t can’t connect to the Internet… do you perhaps have some kind of security thing blocking Lightroom? —Jeffrey
Jay Preston

— comment by Jay on March 9th, 2010 at 7:42am JST (14 years ago) comment permalink

… not at all sure it’s related to your great plugin but… my contacts are telling me they can’t comment anymore on my pics (those uploaded in these last two weeks. sorry I’m travelling and, as my internet connections are “sporadic”, I don’t remember when v160, the one I’m still using, was released)

I’m using the same laptop I was using at home and I’ve checked my settings on Flickr but everything seems ok there so I wonder if…

thnx, Jeffrey 🙂

If everything seems okay at Flickr but people can’t comment, it sounds like a problem at Flickr. My plugin does not maintain some kind of long-distance mental hold on photos you upload with it. 🙂 —Jeffrey

— comment by paolo savonuzzi on March 9th, 2010 at 10:19pm JST (14 years ago) comment permalink


Does the LR API allow to differentiate between ‘image edit time’ and ‘metadata edit time’?

No. it’s a longstanding request that I hope will make it into LR4. —Jeffrey

I noticed the Export window counts as ‘updated’ also the photos that were not really updated, more precisely the image was not edited, but the metadata was.

Since metadata is best updated with the Plug-in Extras, in the Export window it would be great to know which images were changed, to publish only those.



Mac OS X, Snow Leopard 10.6.2
Lightroom 2.6
Plugin version: flickr-20100209.156

— comment by Liviu Ionescu on March 15th, 2010 at 3:08am JST (14 years ago) comment permalink


Your export plug-ins are a real workflow time saver. Currently using Zenfolio, Flickr, and FaceBook and was wondering if a Tumblr export might possibly be in the works. I’ve done some checking on the Internet, but have found nothing.


Have never heard of Tumblr, nor a plugin, but the spot to check is Adobe’s Lightroom Exchange. —Jeffrey

— comment by Clayhaus on March 17th, 2010 at 1:51pm JST (14 years ago) comment permalink

Mac OS X 10.6.2
LR 2.6


In my previous slideshows format I used to have a field displaying “airborne” for photos taken from the air (I’m also a private pilot). In LR I cannot use the same custom configuration, and all I can do is to define an “airborne” keyword.

I would appreciate a way to pass this keyword as a token in the template I use to generate the caption Flickr field.

If you do not have a better solution, we can use {keyword=name}, for example {keyword=airborne} will output “airborne” if the keyword is defined, and nothing otherwise.

Thank you,


Take a look at the release notes for v163 —Jeffrey

— comment by Liviu Ionescu on March 18th, 2010 at 7:42pm JST (14 years ago) comment permalink

About my previous comment re. conditionally adding keywords – I see you added the {IfGeoencoded=} template now (156), which works perfectly for the “geotagged” keyword – so I can now use {IfGeoencoded=geotagged} to only add “geotagged” when relevant. But is there a way to have nested templates, i.e. use a construct like {IfGeoencoded=geo:lat={Latitude:Places=3}} ?


Take a look at the release notes for v163 —Jeffrey

— comment by Lucian on March 19th, 2010 at 2:05am JST (14 years ago) comment permalink

Hi Jeffrey
I’ve just donate for your excellent Flickr plugin.
I was struggling to transfer my 284 photos from a trip in Australia as the Flickr’s tool is not handy at all.
I tried your plugin without big expectation and I was delighted to see all my pictures exported in one shot ! Amazing ! It changes my life ! It took the night to do this export as we don’t have a powerful connection in Ireland but this plugin works great without any bug, a real pleasure to use it.

Thank you for all this hard job you share with us and congratulations for your blog !


— comment by Patrice on March 21st, 2010 at 11:58am JST (13 years, 11 months ago) comment permalink

Hey Jeffrey,

i really love this plugin. so i decided to bought the plugin and this was not a mistake 😉

i have an idea:
Its really boring to click the checkboxes in the group list. nearly each photo i must set new checkboxes. Is it possible to create “group list favorites”? So i can save a list on a button and another list on a other button and when i click the button the list loads?

I know this can be solved by the keywords, but it is very much and boring work.

is this a good idea?

greetings from Germany/berlin

It’s on the todo list, but until it gets done, you can create export presets that incorporate the groups you want. And thanks for your kind gift! —Jeffrey

— comment by Nils on April 4th, 2010 at 4:00am JST (13 years, 11 months ago) comment permalink

At first thank you for this plugin — you’re saved months of my life, which is valuable at least for me 😉 I hope you’ll continue this God-blessed thing.

The ideas of future improvements:
* keyword-based photoset autoselection, just like in groups;
* basic logical operations with keywords for groups autoselection;
* some kind of BIG keywords assignment editor — perhaps in Extras. I have hundreds of keyword-group pairs and it’s hard to recheck each in tiny 20-lines frame.

Good luck!

— comment by aKry on April 13th, 2010 at 2:07pm JST (13 years, 11 months ago) comment permalink

Hi, I am trying this plugin in LR3b2 and it seems to work except removal of photos: I delete photos from a collection, publish (to synch with Fkickr) but nothing is deleted on the Flickr site. The original adobe flickr plugin works with deletion (but does not have so many option as yours!)


Publish support is not ready yet… any Publish stuff you do in the Lr3 betas won’t carry over to Lr3. —Jeffrey

— comment by Giuse on April 18th, 2010 at 3:47am JST (13 years, 11 months ago) comment permalink

from Canada….will your export to SmugMug plugin for Lightroom 3 be available with Lightroom 3 releases?


Yes, the current version works for Export in Lr3. However, the new Publish stuff does not work yet, but I hope to have that in time for Lr3’s release. —Jeffrey

— comment by Steve Aho on April 18th, 2010 at 2:00pm JST (13 years, 11 months ago) comment permalink

Hi! (system: Mac OS X 10.6, plugin version: 20100324.166)

thanks for this amazing plug-in. Question: Let’s say I published an image to flickr, then it get automatically flagged as
Upoaded to Flickr = “Yes”
At Flickr =
Flickr Upload Date/Time

Is there a way to delete an image or set of images on Flickr such that these flaggs are reset?


You can manually reset the flags via the File > Plugin Extras > Flickr Extras dialog. —Jeffrey

— comment by Frank Chr on April 20th, 2010 at 1:55pm JST (13 years, 10 months ago) comment permalink

The list of groups sometimes expanded over the window width:

I’m finding export preset file and patching it manually, but maybe you can install some kind of automatic group name truncation?

— comment by aKry on April 22nd, 2010 at 7:06pm JST (13 years, 10 months ago) comment permalink

I am dealing with RAW and JPG images at the same time. For RAW images to be uploaded they need to be converted in JPG. However I think this also causes JPG images to be reprocessed and there for losing image quality. Is it possible, or can an option be created, so that only the RAW images get converted to JPG and not reprocessing for existing JPG.

This way I would be able to upload them in one go instead of 2 (first JPG without processing) and then RAW with JPG conversions.

Thank you!

Can’t do them both at once like that… if you have SmugVault the plugin will upload the raw file as is, but if you want conversion on some files and no conversion on others, you’ll have to upload them separately. You can make export presets that will make it easier, though. —Jeffrey

— comment by Remco on April 27th, 2010 at 5:14pm JST (13 years, 10 months ago) comment permalink

I recently upgraded to the latest version of your LR_Flickr Plug-in and now (or at least I notice it now) I am unable to the “remove” button to delete user Presets.
I am using:
Mac OS SnowLepoard
LR v 2.7 sub-version 666138 Camera raw 5.7
And you Flickr Plugin # 20100324.166

After I select one on my presets using your Flickr Plugin, the preset settings are displayed on the right, but the focus is lost on the selection pane on the left, and the ‘Remove” button becomes greyed out.

Other Presets, e.g. Jpeg ir tiff export the focus is not lost after I select the pre-set and I am able to use the remove button. Strange, Right?!

Has anyone else reported this? Can you confirm this behavior?
Not preventing me from enjoying your wonderful plug-in, just annoying and need an eventual fix.


Very strange indeed… it’s not something that the plugin should be able to influence. The presets are just files on disk (in ~/Library/Application Support/Adobe/Lightroom/Export Presets). Could you give it a try in Lr3b2 to see whether it’s happening there? —Jeffrey

— comment by Kevin D. Clarke on April 27th, 2010 at 8:30pm JST (13 years, 10 months ago) comment permalink

The flickr plugin is awesome. You simply did make uploading rock’n’roll. Greetings from Dresden, Germany

— comment by Al on May 2nd, 2010 at 10:23pm JST (13 years, 10 months ago) comment permalink

(A duplication of my original message that was posted in the wrong forum)

Thanks for your contributions. Your professionalism, expertise and images are very pleasing.

My query concerns the ability of multiple keywords (tags) when combining LR2.6 and your “Export to Flickr” plugin V 20 100324.166 trial.
In the “Image visibility at Flickr” section, my wish is to list several keywords in a single field using an ‘or’ operator between keywords. I do not know if this is even possible and if it were possible what seperators to use.
My end result would be to tag images in LR, upload a bunch of images to Flickr with your plug-in restricting the images that were key worded with certain people’s names, to a higher level of Flickr privacy.

Apologies for posting this originally in your Facebook area !
Melbourne, Australia

It’s not currently possible, but it’s on the list… it’ll likely get added once Lr3 is out (even for the Lr2 version)…. —Jeffrey

— comment by Marcel Peeters on May 3rd, 2010 at 9:23am JST (13 years, 10 months ago) comment permalink

LR3B2, Flickr plugin 20100324.166

During initial setup, I changed the description and then went to change the JPEG quality by clicking on the slider. The focus jumped back to the Description field. If I click anywhere else on the form or in any other edit box, I can grab that slider.

Very strange. That’s part of the standard Publish setup dialog, so perhaps report to Adobe. Be warned, BTW, that Publish will change completely when Lr3 comes out, so any Publish collections you set up now will go away when you upgrade to the real Lr3…. —Jeffrey

— comment by Ken on May 19th, 2010 at 2:40am JST (13 years, 10 months ago) comment permalink

Keyword-based group assignement doesnot work for me (plugin version 20100324.166 & LR3b2 but also with LR2 and previous versions of the plugin)
For instance I have set the following pairing : Keyword ‘NIKON D700’ to the ‘Nikon D700’ group
The NIKON D700 keyword is added by the plugin itself thanks to the {CameraModel} template token.

As a matter of fact, those photos with the NIKON D700 tag are never sent to the NikonD700 group!

Am I missing something?


The plugin doesn’t actually add Lightroom keywords… it adds tags at Flickr. The group stuff uses real keywords in Lightroom’s database. —Jeffrey

— comment by Guillaume Lemoine on May 20th, 2010 at 6:01pm JST (13 years, 10 months ago) comment permalink

Hi Jeffrey,

Running LR2.7, Export to Flickr plugin 20100324.166, OS X 10.6.3

I have an image that is 2896 x 2048 (cropped size) in LR. I upload to Flickr with the intent of resizing the image to 1500 x something. I use the Image Sizing option where Long Edge is 1500 pixels. When I go to the Flickr page where the image has been uploaded, it shows that the biggest size is 1024 x 731. Am I doing something wrong? I also tried “Width and Height” option with both set to 1500, but got the same results.

Thanks for the great plugin!

When you export to local disk, to the size settings work as you expect? On Flickr, are you sure you’re logged in with your browser and looking at “original” rather than the largest size made public? I’m just grasping at straws here… —Jeffrey

— comment by Paul Waldo on May 21st, 2010 at 11:40am JST (13 years, 9 months ago) comment permalink

Hi Jeffrey! Really great plugin.
I’m using the .166 version and LR3b2 on windows os
I used for a while without any problem, but couple of day ago for a power supply leakage I had my LR catalog spoiled.
So I rebuild another one and started again with your plugin.
This time during the publishing in a Flickr collection I can see the task bar saying “updating collection” and an error due to an unknown keywords “apeture” (yes apeture not a mispelling of aperture).
Actually I don’t have this keyword in the picture metadata, I tried also to upload a never published picture with the same result…
Any suggestion?


Sounds like you’re using the Publish export… that’s not ready for real use yet…. won’t be until new plugin versions are pushed after Lr3 comes out. I’ve been working on it for six months and it’s still a work in progress…. it’s quite challenging. —Jeffrey

— comment by Androxstudio on May 21st, 2010 at 11:15pm JST (13 years, 9 months ago) comment permalink

Yes, it is the publish export that in general is consider a great improvement in the plugin.
I also found the error has been caused by the activation of the MACHINE TAGS option (probably due to a mistake in code in the apeture instead of aperture text string somewhere).
In general I suggest you to add also some tag used for managing better the flickr set and collection, maybe a FLICKRSET tag in the photometadata, other than the actual tokens.

Thank you really much for your efforts that it is really appreciated


— comment by Androxstudio on May 23rd, 2010 at 6:29pm JST (13 years, 9 months ago) comment permalink

Whenever I upload to Flickr straight from Lightroom, the pictures permissions default to not allowing others to leave comments. I can’t figure out how to change this to allow commenting. Can you please help me? Or is this not available? Otherwise, this is an amazing plugin!!!

Flickr’s permissions are smattered here and there on the account screens… I’m sure it’s there somewhere… the plugin doesn’t doesn’t have any controls about comments at Flickr. —Jeffrey

— comment by Alan on May 29th, 2010 at 5:56am JST (13 years, 9 months ago) comment permalink


Fantastic plugin to start with, however I have a problem…
I updated both Ligthroom and your plugin at the same time, the result is now that all pics I upload are both stored in the last set I created before update and also into a new set that I have to name manually instead of having the plugin to do it.

Upload destination is set to “*** Auto: To new folder ***” and name template for the new folder is {YY}{MM}{DD}

Plugin was updated from 2009something to version 20100324.166, now running Lightroom 2.7.666138


I’m not sure I quite understand what you’re reporting, but it certainly seems odd. Could you try with the version of the plugin on this page (the page is about Lr3, but the plugin you can download there works in Lr2) and send a log if it’s still happening? Thanks. —Jeffrey

— comment by Torkel on June 7th, 2010 at 9:57pm JST (13 years, 9 months ago) comment permalink


LR3 released earlier today. Any news or plans for the plugin release?

And congrats for your work.. it is great. I´m supporting it..

Best regards,

Uh, did you perhaps miss the big green box at the top of this page? 🙂 —Jeffrey

— comment by du.r.Maciel on June 8th, 2010 at 10:52pm JST (13 years, 9 months ago) comment permalink

plugin does not work. every time I ‘authorize’ it to flickr, I complete the dialog on the web page and when I come back to lightroom, it’s stuck at “Awaiting Dialog” and never returns. what’s more, at this point I cannot cancel the dialog, as it has made lightroom *completely* unresponsive. I.e. I cannot even force quit, I have to do a kill -9 from the command line.

OS X 10.6
Lightroom 2.5
your plugin version 20100324.166

Yikes. I’m guessing that the Lr “let me know when you’re done with the browser” dialog is somehow stuck behind Lr itself. Use expose to show all app windows to see if it’s there. (BTW, if you option-click on the dock icon, the “Quit” menu item turns into “Force Quit”… very useful, but you shouldn’t be needing it for Lr!) —Jeffrey

— comment by Chris on June 9th, 2010 at 1:47am JST (13 years, 9 months ago) comment permalink

I can’t see any mention of this on the site, but in practice I’m finding that the export plugin is limited to only working with two accounts. Is there a way of supporting more than two accounts? I’m evaluating the plugin, so maybe this limitation is due to it being an eval version.

Melbourne, Australia

No, there’s no limit. To add another, just unauthenticate in the plugin, log in to the new target Flickr account in your browser, then invoke the authenticate action from the plugin. Personally, I have only two test accounts so I’ve never actually tested it with more, but in theory it should work. —Jeffrey

— comment by Drew on June 23rd, 2010 at 8:12pm JST (13 years, 8 months ago) comment permalink

Hi Jeffrey,

I’ve installed the Lightroom 3 and updated the latest version of Flickr. However, once I start to export the image, a error message pops out to say, “LrCatalog:withCatalogDo was marked deprecated…..”. Do you know what happens to this issue?


Sounds like you’re using a very old version of the plugin… the Lr3 version is in beta here. —Jeffrey

— comment by Lucas Liu on June 24th, 2010 at 9:26am JST (13 years, 8 months ago) comment permalink

Hi Jeffrey.

Thought I’d try the twitr alter thing. Bad mistake. Pops up the dialog box, OK to open the browser to get the pin, back to LR, already got the “a pin is 7 numbs” error message up. OK to dismiss, reappears immediately. Rinse & repeat. Cancel LR, Make note not to use that feature again…

Sounds like you accidentally bumped the OK on the “enter the pin” dialog before you actually entered the number from Twitter. Not a big deal… just try again, no? —Jeffrey

— comment by Ian Worthington on June 24th, 2010 at 10:11am JST (13 years, 8 months ago) comment permalink

Hi Jeffrey,

I use publish collections to publish my photos to flickr. The problem I’ve found is that when I’ve reached the publish limit in one group, the proccess stops and doesn’t continue. The photo is published at flickr but remains unpublished at the publish collenction in LR.

Mac OS X 10.6.4
Lightroom 3
Flickr plugin 20100611.173


How is this different from your expectation? If you create a collection for including photos in a group, would you not want them to be considered published to the collection only when published to the group? If not, what’s the point of having the collection to begin with? —Jeffrey

— comment by César on June 27th, 2010 at 7:14pm JST (13 years, 8 months ago) comment permalink

Hi Jeffrey, a follow-up to Cesar’s post…

The functionality as you’ve stated is desirable, but what I’ve found is that when the plugin tries to publish to an overlimit group, the entire publish process ends. Then, from within LR3, you have to unselect that group and publish again with the remaining groups. Your Export plugin offers an option to warn and continue when this circumstance is presented.


— comment by Ron Kochanowski on June 27th, 2010 at 9:28pm JST (13 years, 8 months ago) comment permalink

Hi Jeffrey,

Yes and no :). I’ll try to explain me.

When I create a publish collection for including photos in a group (only one) I think that the photo has been published if it has been published in the group. (anyway the picture itself has been published in flickr but not listed as published in ‘Flickr photostream’ collection)

But when I create a collection for including photos in more than one group. I think the photo has been published if it has been published in any of the selected group. imho.

I’ll continue thinking about this.


— comment by César on June 27th, 2010 at 9:39pm JST (13 years, 8 months ago) comment permalink


I am using Lightroom version 3.0. This is regarding your Zenfolio plug-in version 20100323.106.

I just upgraded to Lightroom 3 and I had your plug-ins in the previous version. I am trying to upgrade to the new plug-ins. I have made my donation and I have the confirmation number but I don’t know how to enter that into the plug-in itself. How do I do that? The message says that I have 33 hours before it expires and I don’t want to wait until then to correct this matter.

Nat Carter

The Lr3 version had been in beta, but it’s pushed out now, so a normal upgrade should pick it up. —Jeffrey

— comment by Nat Carter on June 30th, 2010 at 4:32am JST (13 years, 8 months ago) comment permalink

Finally support for 3.0 Yay! 🙂

Just one thing I didn’t get so far… Is it somehow possible to manually “claim” photos? Deep Scan missed about 30 of my photos and I would like to add them. Simply dragging these photos to the Publishing Service want’s to upload them as new.

Thanks for your great work!

Not yet, sorry… it’s on the todo list. It was a Herculean effort just to get this far.. —Jeffrey

— comment by Chris on June 30th, 2010 at 4:56pm JST (13 years, 8 months ago) comment permalink

Hi Jeffrey, Craig here from Australia

Thanks again for a fantastic plugin.

I have just bought Lightroom 3 and reregistered my plugin. So far everything is working fine, except for the following, which could be intentional.

I am using Windows 7 with Lightroom 3.0 (Camera Raw 6.1) and flickr-20100630.188

Because with the 5DMkII, the exported jpeg files can sometimes be larger than the 20MB flickr limit, I have enabled the setting to limit file size (to 19000KB inmy case). I have been keen to use the new ability to upload video, but because the video file are a lot larger than the 19000KB limit, I get a message that the video cannot be rendered. If I disable the limitation, the video uploads fine.

I suppose I could create a separate collection for video, but was just wondering if the behaviour is intentional, considering that Lightroom doesn’t have the ability to render video (apparently).

Thanks again

None of the file settings have any effect with video in Lightroom… it just passes the raw bytes of the video file, just as if you had set the format to “ORIGINAL” for images, so I wouldn’t expect it to work unless the original video is within limits. But frankly, I haven’t really tested video much yet… many rough edges yet to smooth with these things… —Jeffrey

— comment by Craig Jewell on July 1st, 2010 at 10:14pm JST (13 years, 8 months ago) comment permalink

When for instance adding keywords to a previously uploaded image, and running Publish in the plugin, it insists on re-uploading the whole image. This in turn changes the URL to the image on Flickr, breaking uses of it on other sites. This is a big inconvenience to me, and I’m wondering if it’s something you think you will be able to solve.

/Björn, Uppsala, Sweden

It shouldn’t change the Url, unless you’re not a paid Flickr user, I guess. Flickr doesn’t allow image replacements for free accounts, and as such, Publish is a lot less useful for non-paid Flickr accounts. The plugin doesn’t know what changes have been made, so it can’t decide to send only metadata updates, so it’s probably best to just stick with normal exports and manually resend metadata (via the Plugin-Extras menu) when you want. —Jeffrey

— comment by Björn Lindström on July 2nd, 2010 at 12:36am JST (13 years, 8 months ago) comment permalink

Hi Jeffrey,

I just updated the JF Flickr plugin to version 20100703.190. The earlier messages have disappeared.
(— comment by Karel on July 1st, 2010 at 12:36am JST or

Now I get the following messages when starting up LR3, or when reloading the plugin, the plugin now does not load correct anymore. Is there a way to revert back to the .188 version?

Messagebox 1:
We can only wait from within a task

attempting login aborted

Mac OS X 10.6.4
LR3.0, CR6.1
JF Flickr Plugin version 20100703.190



I’d sure like to get a log if you get that error again. —Jeffrey

— comment by Karel on July 3rd, 2010 at 8:11pm JST (13 years, 8 months ago) comment permalink

Hi Jeffrey,

Sorry, I asked you how to revert back to an older version, as the .190 version of JF Flickr plugin doesn’t work for me. See earlier comment.
I just removed and reinstalled the older version. Easy as that!

Kind regards,


— comment by Karel on July 3rd, 2010 at 8:17pm JST (13 years, 8 months ago) comment permalink

Hi Jeffrey,

Is that available to export automate folder location on hard-drive when Flickr Export to online set? (automated Folder rename and replace/ file rename. At moment the [export location] only have few options that [specific folder]/ [choose folder later]/[temporary folder] none of them have the ability to create a new Sub-folder with different photo set)
It would be wonderful to keep all the photo I export to online Sync with my iPhone/ iPad if I edit/add photos.

That section in the export/publish dialogs is part of standard Lightroom, and I don’t have control over it, so you get what you get. I might be able to add something extra to the plugin in the future, to maintain a local mapping of files, but it’d be behind a lot of other stuff on the todo list…. —Jeffrey

— comment by Ryan on July 4th, 2010 at 12:58pm JST (13 years, 8 months ago) comment permalink

Hi Jeffrey,

My issues are solved with the 20100704.191 version. Starting up and reloading the plugin does not give any errormessages anymore. Publish services work!

In answer to comment

Thanks for all the work!

Kind regards,


— comment by Karel on July 4th, 2010 at 5:03pm JST (13 years, 8 months ago) comment permalink

I downloaded your plug in over a month ago, but now it has vanished from my Llightroom. What’s up with that?

How do i get it back?

You probably deleted it yourself by accident. Just reinstall, taking care to first place in a location you’re not likely to delete it from. —Jeffrey

— comment by M. I. Droz on July 6th, 2010 at 6:31am JST (13 years, 8 months ago) comment permalink


Since upgrading to Lightroom 3 I can no longer use, upgrade or re-install the plugin.
I see the message “Could not read the metadata spec for this plugin” and under that “bad argument #1 to ‘gsub’ (string expected, got function), then the plugin is disabled.
Plugin version is 20100706.192
Windows 7
LR 64-bit v3.0

FYI, I’m an Australian living in Saigon, Vietnam.

Sounds like you might have a bad download. Try downloading with a different browser…. —Jeffrey

— comment by Stephen McGrath on July 12th, 2010 at 1:40am JST (13 years, 8 months ago) comment permalink

Flickr Export Plugin for Lightroom
Version 20100706.192

Hello, I keep geting this strange error/code thingy when trying to publish to flickr. I created a smart collection for this plugin.

flickr +75839.4: [x13c0b1cf8] @Flickr line 3423:
unexpected result from addToPhotoset

args = table: 0x159715080:
| api_key=x
| api_sig=x
| auth_token=x
| method = “flickr.photosets.addPhoto”
| photo_id = “4766376571”
| photoset_id = “72157624341269361”
result = “”

I’d appreciate a log for errors like this. —Jeffrey

— comment by Sam Freeman on July 12th, 2010 at 3:29am JST (13 years, 8 months ago) comment permalink


I’m using the following:
Jeffrey’s flickr plugin for Lightroom, version 20100706.192
Lightroom version 3.0.0 build 677000 for Windows Microsoft Windows XP Professional Service Pack 3

I’ve noticed that when in the publish collection, and I hit the refresh comments button on the right hand tools, it isn’t doing what I would expect – It doesn’t seem to be getting the comments.

I had a quick look with wireshark to see what it was up to – it seems to be doing an api call to rather than a call to the method I was expecting – – I was hoping you could take a look at this when you get time. I have a photo with no favourites, but a comment, so I thought that would show up in the comments section in LR.

Many thanks,

The getFavorites thing is because Lightroom tries to get both the comments and the favorites for every photo, every time. You probably don’t see the comments due to the bug mentioned here, but if that’s not it, please send a log. —Jeffrey

— comment by Guy on July 13th, 2010 at 4:54am JST (13 years, 8 months ago) comment permalink

First, great plugin! Finally I can use lightroom as my publishing tool!

I’m trying to stop publishing the location metada as tags, for instance the City, State/Province, and Country fields. However, I’m not finding any reason in my plugin settings for why they are converted to tags in the first place. I see you have plenty of options for adding extra tags, but I can’t figure out how to remove them.

Thanks again!

Flickr does that, pulling them from the image. As far as I can tell, they always forcefully add those fields as tags and give no option not to. The only thing I can suggest is to strip the metadata from the image (via the “minimize” option in the “Metadata” section) so that they have nothing to pull from. —Jeffrey

— comment by Guillaume on July 16th, 2010 at 11:36am JST (13 years, 8 months ago) comment permalink

Dear Jeffrey,
I think the “all images are hidden from public searches” issue is still here … 🙁

Flickr export plugin v 20100715.195

Have a nice week-end,

My weekend will be anything but nice… I’m going to be sitting in a tin-can of an airplane for much of it, which also explains why it’ll be a few days before I can look into the public-search thing again, sorry. —Jeffrey

— comment by MadGrin on July 18th, 2010 at 12:18am JST (13 years, 8 months ago) comment permalink

Just a heads up if you hadn’t noticed this bug (?) yourself, related to the Flickr “Deep Scan”. (Or the Claim process?)

(Export to Flick Plug-in 20100715.195, LR3, Win 7.)

If I have two photos in my library taken within the same second, and only one of them is on Flickr, your plugin will connect both those images in the local photostream to the single image on Flickr.

I was under the impression that the plugin, when in doubt, would not make any connection at all. Perhaps I misunderstood something?

“Visit photo at Flickr” will only work with the correctly matched photo though. (Which to me seems strange since both photos show the same, working URL when viewing “All Plug-in Metadata”. By working I mean leading to the one same photo that was uploaded to Flickr.)

Anyway, thanks for a great plugin. I know how tough this kind of development can be when users start demanding stuff, having dabbled with Firefox themes.

Best regards,
David Naylor (Eskilstuna, Sweden)

It seems to work properly in my tests… maybe send a log if you can reproduce it —Jeffrey

— comment by David Naylor on July 18th, 2010 at 2:52pm JST (13 years, 8 months ago) comment permalink

I’d just like to add a vote for the ability to manually assign Flickr photos. Your plug-in is probably the most useful add-on I’ve ever come across for easing the management of images on Flickr, so much so that I’d jump ship from Aperture to Lightroom just so I could use this plug-in (Aperture has “FlickrExport” by ConnectedFlow but it doesn’t allow you to update metadata on Flickr images).

This has really hit home this morning as I’ve noticed that I mis-typed a place name on 500 odd photo’s. This would be easy to correct with your plug-in if I could let if know about images already uploaded. I’ve tried the “Deep Scan” option but unfortunately it doesn’t work with scanned images (from old slides) as I would assume there isn’t enough EXIF data to do the match.

Even if it’s just the ability to manually enter the “UploadedtoFlickr” and “AtFlickr” fields then that would be fine. I know you’ve commented on this earlier but frankly this would be so useful that I’d take the risk and if it cocks up my catalogue then it’s my own fault.

Keep up the good work!


It’s not merely a matter of turning on a flag, but of also associating the appropriate data with the flag (data about the image location at Flickr). I’ll eventually figure out something, even if it’s just a dialog where you cut-n-paste a Flickr url, but I’ve been so completely overwhelmed with plugin development since December that I need to let things settle a bit, for my own sanity, before trying to tackle this. Sorry for the selfishness, but mentally I’m close to an edge I really don’t want to fall over. —Jeffrey

— comment by Ken Davies on July 19th, 2010 at 6:35pm JST (13 years, 8 months ago) comment permalink

… btw… I’m migrating my LR3 catalogs (and pictures) to a new iMac , so… what *exactly* should I carry over to ensure all your plugin (Flickr, Geoencoding and MetadataWrangler) preserve all settings and “flags”?

thnx 🙂

The catalog and the Lightroom preferences file. The former is where all per-image data is saved, and the latter where all the overall settings are saved (such as dialog settings). Also, if you have export presets, those are files you can copy over as well. —Jeffrey

— comment by paolo savonuzzi on July 20th, 2010 at 10:16pm JST (13 years, 8 months ago) comment permalink

Hi there. First, thank you for this amazing plugin.

I’ve seen you included a “Post to Twitter” feature at the export module. I was thinking why this doesn’t exist in the Publish Services… That would make a great feature as well! And Flickr already have a “Blog it” feature to twitter and a short URL service you could use.

Just something to think about..

— comment by Felipe on July 23rd, 2010 at 9:38am JST (13 years, 7 months ago) comment permalink

… anything you can do so the “deep scan” (when claiming already uploaded pictures to “Publish”) is aware of timezones? I tried it and all the pictures uploaded from a different timezone ended up duplicated (theose already in “Publish”)
my catalog was so messed-up I had to go to recover from a backup one :-/

what I was trying to do is… how can I add the missing ones (uploaded, mostly, directly from my iPhone)?


Timezones are just one of many possible derivations from a good match. It’s unfortunately complex, and I doubt I’ll ever be able to cover them all, and I think timezone adjustments (which should be done at the Lightroom level prior to uploading) will make it any time soon. Sorry. —Jeffrey

— comment by paolo savonuzzi on July 26th, 2010 at 9:03am JST (13 years, 7 months ago) comment permalink

Hi Jeffrey,

I might be being a bit dumb here but could you tell me how to set groups via keywords? I’m trying to reduce the number of collections to publish and this looks like it would be a great help. For example I have a “smart” collection of about 100 images, most of which could be published in a “landscape” group I’m a member of but about 10 of which could also go into a “coast” group. I want to avoid – if possible 0 needing two separate collections to achieve this.

Many thanks.

I’m not sure what to say… it’s in the Flickr: Group Pools section of the dialog, and pretty self-explanatory. Send email with a more specific question if you have one…. —Jeffrey

— comment by Ken Davies on July 26th, 2010 at 5:45pm JST (13 years, 7 months ago) comment permalink

ok, Jeffrey: thanks

so, as “Associate Images” in “Plugin Extras/Flickr Extras” (first method I tried) fails, how can I manually add to “Publish” the missing ones?

At this point, you can’t. Adobe designed Publish for new photos, not for managing old, so my “Associate Image” stuff is an attempt to extend the feature. It doens’t work well yet for some. —Jeffrey

— comment by paolo savonuzzi on July 26th, 2010 at 6:00pm JST (13 years, 7 months ago) comment permalink

ok :’-(

last request: could you, please, at least let the “Flickr Extras” also work “the old way” and just flag the picture as uploaded even when the corresponding one, at Flickr, is not found and associated?

this way I could, at least, create (also) a smart collection to track *all* my Flickr uploads 😉

thank you once more 🙂

I’d rather not, because it’ll create a lot of confusion about why such photos are marked uploaded, but the plugin doesn’t know where they are, etc., If you want to track things yourself, consider using a smart collection that does the union of UploadedToFlicker and some “I know it’s at Flickr” keyword that you manually add to those images. —Jeffrey

— comment by paolo savonuzzi on July 26th, 2010 at 8:37pm JST (13 years, 7 months ago) comment permalink

I had already paid for the Lightroom plugin with the last version and was all up-in-arms that my registration code didn’t work for Lightroom 3. As soon as I realized that you weren’t making people pay anything more than $.01 for a new registration code, I sent you another $5.

— comment by Josh G on July 28th, 2010 at 9:18am JST (13 years, 7 months ago) comment permalink

I just upgraded to LR 3 and got your latest flickr plugin and paid via paypal.

now I have 3 jeffrey plugins in my lightroom plug-in manager.

Flickr (installed and running)

Flickr (Jeffereys (disabled) message – this version has expired

jf flickr (disabled) – probably duplicate of the jf flickr (enabled)

jf flickr (installed and running)

I just need one(1) plugin – how do I delete the others???
Lightroom manager will not let me remove them – the ‘remove’ is greyed out.

most frustrated

If the plugin manager won’t let you remove them, they weren’t installed with the plugin manager, but rather, they appear by virtue of being in the location that plugins were added in Lightroom 1. If you want to manage plugins with the Plugin Manger, install them elsewhere. —Jeffrey

— comment by inge weidmann on July 29th, 2010 at 10:03am JST (13 years, 7 months ago) comment permalink

As I take may pictures of birds, bees, etc., that move rather fast-I was having quite a few problems with date and time stamp issues-maybe your users know this and maybe they don’t, but thought I’d put it out there. The “capture time” field in Library/Metadata is editable-you can change it there for pix posted in the same minute. For pix already on flickr you can change the time there as well. A kludge is better than no kludge, I’m learning to say!

— comment by Lisadawn Schram on July 30th, 2010 at 8:32am JST (13 years, 7 months ago) comment permalink

Running latest release 20100727.196 in LR3 on mac OS 10.6.4.

I seem to remember that previous versions for LR2 had the option to assign photos to your flickr sets.
Has this option been scrapped or have I just overlooked it?

btw still enjoying your plug-in!

kind regards


it’s all set and group based, so I can’t imagine what you’re looking at if you don’t see it. Are you sure you’re looking at my plugin? —Jeffrey

— comment by Martin on July 31st, 2010 at 10:50pm JST (13 years, 7 months ago) comment permalink

Running latest release 20100727.196 in LR3 on mac OS 10.6.4.

My bad. Was looking in the settings for the publish service and not the export settings. Found what I was looking for in “Flickr upload destination”.


— comment by Martin on August 1st, 2010 at 5:29pm JST (13 years, 7 months ago) comment permalink

Thanks for the plugin, I have one issue that is currently spoiling my flickr upload experience. Many of my tens of thousands of keywords are not enabled with ‘Will export’, and thus they are not coming through the export process.

When I used to do manual exports, ‘Writing keywords as lightroom heirarchy’ used to work, and even the non-exporting keywords would show up. But the same is not true when using this plugin. Is there a way to force all keywords to export, or do you know of a script to change all of my keywords to ‘Will export’ without me right-clicking on every single one?

Many thanks

There had been a bug that caused keywords to export improperly, but that was fixed in Lr3, so it’s not just the plugin. You might look to see whether Tim Armes’ Keyword Master can help… I know he was considering something along these lines. —Jeffrey

— comment by Timo on August 4th, 2010 at 7:38pm JST (13 years, 7 months ago) comment permalink

Hey Jeffrey, I just upgraded to Lightroom 3 and used the Publish services with your plugin.
Everything seems to be working, except the “Retrieving comments from Flickr” just won’t continue…

It just stays at the top as the current action and the progress indicator stays blank ( no continuation ).

Any thoughts?

No sure why it wouldn’t continue, but if you have a lot of photos, it could take a while… it tries to get all comments for every photo every time. )-:. If it really seems stuck, please send a log. —Jeffrey

— comment by Depechie on August 7th, 2010 at 12:15am JST (13 years, 7 months ago) comment permalink

Sorry if this has already been asked…

LR3 Win7

Does the structure of the Flickr sets get passed back to the published service? i.e. I would like to see the folder structure that I set up under flickr mapped back to a folder structure under the photostream in the published services.

Or, can you look at some metadata to see the flickr set?


No, sorry, currently there’s no folder structure maintained by the plugin in Publish. You’re free to do it manually, but the plugin doesn’t do it for you. —Jeffrey

— comment by Brendan on August 9th, 2010 at 4:05am JST (13 years, 7 months ago) comment permalink

I also do have those “stuck” photos that were reported for version 20100727.196. But I must admit that I already had the very same problem with the native LR3 FlickR plugin. So I suspect LR3’s publish feature to be broken. I also saw some postings regarding that in the beta forums for LR3.

This is the first version with Publish, and it shows… it’s a minefield of bugs. Once Lr3.2 is out for real, I will push my plugins to use some of the better support it offers, but I don’t think that will fix this bug, but we’ll see… —Jeffrey

— comment by Alexander Czernay on August 12th, 2010 at 2:53am JST (13 years, 7 months ago) comment permalink

I changed my Flickr screen name from ‘ilg-ul’ to ‘Liviu Ionescu (ilg-ul)’ and the Flickr Extra -> Resend Metadata failed with an error telling the user ‘Liviu Ionescu (ilg-ul)’ has no photos uploaded.

Reverting the screen name to ‘ilg-ul’ allowed me to update the metadata.

Probably you validate the user with the screen name, instead of the login name.



20100419.167, LR 2.7, Mac OS X 10.6.4.

That version of the plugin is ancient… you should always test with the latest version before submitting a bug report. This bug was fixed around June…. when you upgrade, the plugin will map all your photos to an internal Flickr ID that doesn’t change when you change your screen name. (To be safe, leave it at the working screen name until after upgrading, and then it’ll be fine and you can change your screen name as you like…) —Jeffrey

— comment by Liviu Ionescu on August 18th, 2010 at 4:04am JST (13 years, 7 months ago) comment permalink

Hi Jeffrey !
It seems that pictures uploaded to flickr continue to be set as hidden from public search. I check the settings and confirm that I chose that if no special keyword match, I want pictures to be searchable.
Is this a bug ?

Version : 20100814.198

Thanks for your great job !

Grrrr, I thought I fixed that. I’ll check it out again… —Jeffrey

— comment by Johan on August 18th, 2010 at 6:23am JST (13 years, 7 months ago) comment permalink

Jeffrey… if I also “re-create” in LR3’s Publish service (still got to figure ou how, though 😉 ) my Flickr sets and collections… will those populate with already uploaded pictures or…


— comment by paolo savonuzzi on August 19th, 2010 at 7:18pm JST (13 years, 7 months ago) comment permalink

Hi, Jeffrey.

I upgraded my hard drive, and moved all my original pictures and export locations to it – Flickr Export now complains that it can’t find the old Export Location, and it won’t let me enter a new one.

I would re-create the Publish Service from scratch, but I’d rather not go through the Deep Scan again, since all the information is already available. Is it possible to edit manually a configuration file somewhere to change the Export Location? Thanks!

The Deep Scan is not specific to a publish service… just tries to match up images in Lightroom and in Flickr, so no need to do that again. If you want to recreate the publish service, a simple repopulate should suffice. However, perhaps you can just at a shortcut link from the old target to the new, so that the plugin thinks it hasn’t moved. Most people use “temporary” for this, so I’ve gotten little feedback on what happens when it’s not. Frankly, I made it so that you couldn’t change the local destination simply because that’s what the Adobe one did early on, but now that I think about it, I should let you do what you want so long as you’re willing to take responsibility for the change. I’ll see what I can do… —Jeffrey

— comment by David Navarro on August 31st, 2010 at 6:29am JST (13 years, 6 months ago) comment permalink

Using the latest 20100829.202 but still all my photos end up being hidden from public search in Flickr. Which BTW also causes them not to sent updates to Facebook via Flickr’s FB-integration, which is how I actually noticed the bug – just took quite a while to realize what was the real issue here.

And to clarify: keyword filters for search in export settings are empty, and “included in Flickr’s public image search” is ON.

Just pushed 20100930.203 which should finally fix this problem. —Jeffrey

— comment by Miemo Penttinen on September 26th, 2010 at 3:54am JST (13 years, 5 months ago) comment permalink

When I was using Lightroom (through Version 2), I held this plugin and one of the most important features I could possibly have. Since then, I migrated to Aperture 3 (and love it). Unfortunately, Connected Flow’s plugin is pathetic, overpriced, and only works when it wants to.

I yearn for a “port” of “Export to Flickr” for Aperture. Any chance you are enticed to release an even stripped down version of your plugin for Aperture? Connected Flow sets a very low bar.

No, sorry, they use completely different technology for the plugins, so there’s absolutely no overlap in code. Plus, I’ve never used Aperture. —Jeffrey

— comment by CKelley on October 2nd, 2010 at 3:35am JST (13 years, 5 months ago) comment permalink

I’m using this great plug-in for maintaing my Flickr appearence and its a very helpful tool. I just registered today and will continue with other publishing plug-ins.

There is one aspect I havnt found in all these tools out there for Flickr and just thought Jeffrey’s plug-in might help. Yes, this is a feature proposal: I would like to have a way to publish just one or two pictures at a time. Which is the case when I prepare a complete series for a Flickr collection on one day but want to publish step by step over the next weeks.

Its just a proposal, but I know people would love it.

Keep up the good work!

If you want to publish a subset of photos waiting to be published, select them, then hold down the option/alt key, and the “Publish” button becomes “Publish Selected”. —Jeffrey

— comment by Chris de Vida on November 28th, 2010 at 3:23am JST (13 years, 3 months ago) comment permalink

please, Jeffrey: where are plugins data stored (on a Mac)?

I’m setting up a new computer, moved my old one’s “Lightroom folder” and plugins but… Flickr’s collection, the boring one to setup from scratch, is now empty 🙁

thanks 🙂

All collection info is in the catalog… if you copy your catalog over, it should be there. If you export-then-import, though, you lose all Publish data… this is a (major, if you run into it) Lightroom shortcoming. —Jeffrey

— comment by pl_svn on December 12th, 2010 at 9:31pm JST (13 years, 3 months ago) comment permalink

Plugin version in Lightroom 3

Even though watermark on export is checked my pics are not being watermarked once in flickr. Anyone know why? Thanks for your time

Lightroom’s built-in watermarking puts the watermark in the actual photo pixels, so it certainly should be there when uploaded. If you do a vanilla to-disk export with the same settings, do you see the watermark? —Jeffrey

— comment by Lee Mousseau on December 13th, 2010 at 10:59am JST (13 years, 3 months ago) comment permalink

Version 20101217.207

I am now getting an error ’The preset for “DESCRIPTION_SPEC” no longer exists. The plugin page refers to Last Message: The plugin’s post-processing task did not finish successfully
I had to reload my catalog after doing some maintenance on computer files as directed by adobe support and this caused me to have to reload plugin, now I receive this error when it was working fine before. Any ideas on how to fix?

You had used a preset for describing how the Flicker “description” was to be derived for each photo, but that preset is now gone. Revisit the export dialog and reset the description setting to what you want (perhaps creating a preset if you like), and you should be fine. If you have export presets, you’ll need to do this for each preset, re-saving the preset so that it has the new description setting. —Jeffrey

— comment by Michael on December 18th, 2010 at 10:15pm JST (13 years, 3 months ago) comment permalink

When editing a Smart Flickr Public Collection, the Save button remains disabled unless you change your Set selection. That is, I can change which photos are selected using the rules, but unless I change the Set, I can’t save my update.

Using 20101217.207, which is telling me it’s the latest.

This was due to a bug that got fixed in Lr3.3, so I just pushed 20110103.208 that takes advantage of the fix in 3.3 to allow the smart collection to be saved. If you’re using Lr3.0 or Lr3.2, the plugin now won’t work until you apply the free update from Adobe to Lr3.3 or later. —Jeffrey

— comment by Graham charles on December 24th, 2010 at 4:54pm JST (13 years, 2 months ago) comment permalink

Hi Jeffrey,

I’m running Flickr Export Plugin 20101217.207 against a non-pro Flickr account. Mac OSX 10.6.5, Lightroom 3.3. I have 2 images I have modified since the initial Flickr upload and one that is brand-new to be uploaded.

When I try to publish, I get the following message: “Error response from Flickr Not a pro account Aborting export after 0 of 3 images successfully upload”

I’m stopped dead in my tracks, as new images won’t upload. Any help would be greatly appreciated!!!


Flickr doesn’t allow image replacement in non-pro accounts, so it can’t really be used very well with Publish. I would have thought the plugin would be a bit more graceful in letting you know, though…. I’ll look into that. —Jeffrey

— comment by Paul W Waldo on December 30th, 2010 at 10:00am JST (13 years, 2 months ago) comment permalink


I currently use your plugin to publish to Flickr, and it works pretty well to upload easily my pictures.
However, with publish services, lightroom tried to introduced some sync principles and is supposed to detect when a photo changed for it to be republished to flickr.
For some reason, I don’t get, Lightroom finds picture to republish even when I don’t change them at all. I upload a collection and some pictures gets immediatly marked as republished even though I don’t change anything. Do you have any idea of what triggers this behaviour ?

Thanks for your help



There are bugs in Lightroom with the republish stuff… it doesn’t affect most people most of the time, but appears from time to time. Hopefully they’ve gotten better in Lr3.3, but I haven’t yet checked in detail. It’s frustrating. —Jeffrey

— comment by Thibaud on January 2nd, 2011 at 12:04am JST (13 years, 2 months ago) comment permalink

There is a problem with Export to Flickr Lightroom Plugin download……..
Can you verify?

Best regards

Seems fine to me… —Jeffrey

— comment by Alleo on January 5th, 2011 at 12:25am JST (13 years, 2 months ago) comment permalink

Hi Jeffrey,

I have been using the your plug ins for quite some time and I think they are really great. When I was working yesterday with the Flickr plugin I thought of the following suggestion (which I am not even sure if it is possible or not):

Would it be possible to update the metadata of the files in both ways? By this I mean:
– During my workflow, I publish to Flickr before I write the title of the photo and I add the geolocation (I like Flickr’s interface better for these tasks).
– Would it be possible to sync the current uploaded pictures so that the metadata from the ones in Flickr updates the metadata of the pictures in my computer?

Just a thought, looking forward to your new updates, thank you.

It’s not really possible, no, because neither Lightroom nor Flickr track when a bit of metadata changed. —Jeffrey

— comment by Julio Aprea on February 7th, 2011 at 5:33pm JST (13 years ago) comment permalink

The manual linking to Flickr is working awesomely! I just re-linked ~90 of the 500 or so it wasn’t able to automatically link. It correctly added the uploaded flag, and the URL, and when I re-published some of them they did a proper replace on Flickr, rather than as a new upload.

Brilliant, sir! Brilliant.

— comment by Jay on February 7th, 2011 at 5:54pm JST (13 years ago) comment permalink

A hopefully quick and question:

Is there any way when republishing a photo to specify to update the title but to leave the caption/description on Flickr in tact? I’ve experimented a bit with leaving it blank and using {none}, but in all cases it seems to wipe out what’s on Flickr. I’d like to be able to preserve it.


No, the whole point of Publish is that Flickr becomes a reflection of your Lr catalog. —Jeffrey

— comment by Eric on February 11th, 2011 at 11:47pm JST (13 years ago) comment permalink

In the Export Plugin for Lightroom, the token {FocalLenght} or {FocalLenghtMM} are not accepted!!
regards, Henrique

Try swapping the ‘h’ and ‘t’. —Jeffrey

— comment by Henrique on February 16th, 2011 at 8:50pm JST (13 years ago) comment permalink

Hi Jeffrey,

I have some images that I geoencoded on Flickr that are matched to images in Lightroom with no geo data. If I use the Flickr publish service to update Flickr for these images, will the geo data already on Flickr be over written (i.e. cleared)?

Yes, it should be removed. Publish means that the presence in Lightroom is the master copy from which the view at Flickr is derived. Just as if you removed geoencoding within Lightroom and republished, the lack of geoencoding will be reflected at Flickr. —Jeffrey

— comment by Clarence Holmes on February 22nd, 2011 at 11:43am JST (13 years ago) comment permalink

I just downloaded the plug-in and am very happy with it except I have a question about the “Claim” feature. I’d like to do it because I want all my past photos that were connected with my built-in Flickr plug-in to be part of the new one (as opposed to starting at 0 photos in the new plug-in). I know if I claim them, it will apply all of my settings (such as quality, etc.) to those photos retroactively and re-publish them. This is all fine with me as long as it doesn’t erase all of my titles, descriptions, comments, and favorites on those photos. The “Claim” feature is exactly the opposite… it does not re-publish them… it shoves them into the collection as if they were already published. You have to explicitly update them or “Mark for Republish” if you want them to go out with the Publish-Service settings.

Under “File Naming” in the plug-in preferences, I do NOT have the “Rename to” box checked, which leads me to believe that it wouldn’t rename my photos if it claimed them, but I’d really like some assurance before I hit the switch.

Also, along those lines:
I know you want to maintain a constantly updating relationship b/w LR and Flickr, so if I publish a picture to Flickr then subsequently alter it, that alteration will automatically be uploaded to Flickr and the online picture updated.

Now as I understand things with Flickr, when you “replace” an uploaded photo, the new photo actually gets a new URL from Flickr so if you have a link to the original photo from an external site, that link will be broken when you replace the online image.

My question is does the JF plug-in sync function do the same thing (break links)?

Thank you so much,

Yes, apparently the url is changed. The plugin has no control over Flickr urls, but it seems that they change the url when you replace the image. It boggles the mind how they can think this is appropriate, but it’s their service. /-: —Jeffrey

— comment by Nora on February 25th, 2011 at 6:35am JST (13 years ago) comment permalink


I think that this application is essential for Lightroom users. The fact is that I want to remark the great use that amateurs photgraphers make about this application.

Nevertheless, I want to point out one question. I use this API since 2008, and from mid 2010 the EXIF data begun to not be uploaded within my flickr images. I give you some example of that:

You can check my EXIF data and its not detailed (I have checked both Flickr and Jeffrey configuration so as enable this data). So, my question is the following, how can I repair or fix that issue? I don’t think it is a bug, but I don’t know how to patch it

Thank you for your time

You might have the “Minimize embedded metadata” option selected for export, or maybe Flickr is stripping it. If the option is not set in export, do a text export where you set the “Export Location” (2nd section from the top of the export dialog) to something other than a temporary folder. That way, the exact file uploaded to Flickr will be left on disk, and you can inspect it (e.g. with my online exif viewer) to see exactly what data it has. If it doesn’t have your metadata, look to your Lr settings. If it does, look to your Flickr settings. —Jeffrey

— comment by Sergio on February 25th, 2011 at 10:19pm JST (13 years ago) comment permalink

The changing URL when you replace an image on Flickr is one of the big reasons I’m seriously considering switching over to SmugMug (and sending Jeffrey some more money 🙂 )

— comment by Jay on February 26th, 2011 at 12:54am JST (13 years ago) comment permalink

Hi Jeffrey!

Thanks for the information, it was me that had the minimize embedded metadata activated! How could I pass this checkbox?


Thank you very much!

— comment by Sergio on February 26th, 2011 at 4:21pm JST (13 years ago) comment permalink

Great plugin!

Some feature ideas…

If you mark a photo for deletion from the collection, and later change your mind, there is no way to reverse it. You cannot ‘unmark’ the photo for publishing.

Just drag the thumbnail back to the published-collection name, and it’ll silently move back to “Published”. This is not specific to my plugin; all Publish works this way.

It would be nice to be able to apply post-processing actions (such as watermarking or actions pulled in from other plugins, ie mogrify) on a per-collection or per-set basis. Or, if nothing else, allowing for an easy way to temporarily disable these actions.

Lightroom doesn’t give a plugin any leeway here, so the best approach I can think of is to create separate publish services, e.g. “Flickr with Mogrify”, for each kind of output you want. —Jeffrey

— comment by Gary on April 20th, 2011 at 11:00am JST (12 years, 10 months ago) comment permalink

Your plugin is great. It makes Flickr so much easier to manage. Would it be possible to add controls to override visibility and safety to the Flickr Publish Collections so that every image doesn’t need to be tagged beforehand? You could resolve conflicts when an image is in two publish collections with different settings by providing a global option to select “least permissions” or “greatest permissions” by default.

I’m not sure what exactly you’re asking, but if you don’t want to think about visibility until later, you can just keyword every photo so that it’ll marked private upon upload, then change those keywords for subsequent uploads. It’s not very efficient because Lightroom will want to regenerate the entire photo, but that’s how Publish was designed. —Jeffrey

— comment by Henry on April 22nd, 2011 at 8:03pm JST (12 years, 10 months ago) comment permalink

To rephrase, it would be nice if I could say “All photos added to this publish collection should be friends/family only by default instead of whatever I have set the default for the publish service to be.”

I’m not sure how that would be expressed in the UI. You can set the publish service to respond to tags, and it seems fairly undemanding to click an “add keyword” button before dragging to a publish-service collection, so I’m not sure that anything short of an ESP module would make something that’s already easy much easier…. (?) —Jeffrey

— comment by Henry on April 22nd, 2011 at 10:45pm JST (12 years, 10 months ago) comment permalink

I’m having an issue with your “Explort to flickr” plugin (Version 20110419.218) in LR 3.4 running on OS X 10.6.7. When I try to publish a collection in which there are some photos which have been modified since they were previously uploaded, I get the following errors in three subsequent dialog boxes:

Error response from Flickr
Photo is temporarily unmodifiable
Aborting export after 0 of 95 images successfully uploaded

Aborting export

Can’t update this collection
Aborting export

However, if I create a new collection and put photos in it which haven’t yet been uploaded, that seems to export just fine. Maybe there’s some kind of maintenance going on at flickr preventing new files from being swapped in… but I’ve never seen that happen before, so it seems odd.

Judging from a web search of the error message, it’s likely an internal error at Flickr (that hopefully doesn’t last long)…. —Jeffrey

— comment by Zane Selvans on May 2nd, 2011 at 6:26pm JST (12 years, 10 months ago) comment permalink

Still trying to get to know your LR goodies – which so far are great!

An issue I’ve just discovered with the LR export to Flickr plugin (Version 20110419.218) running with LR 3.4, Vista Ultimate 32bit SP 2:
After having done a deep scan and claimed pictures for the jf Flickr Service there appears an option with right-click “Visit photo at Flickr” – when clicking on it, I get an error message saying something like (freely translated from German) “This published photo cannot be shown. The URL for this published photo could not be found”. Nevertheless I can access the photo through the link in the all “All Plug-in Metadata” Tab.

The right-click action seems to be working for pictures uploaded with your uploader (but not the claimed ones).

That’s unexpected…. it should have the URL registered with the plugin service. I’ll have to take another look at it… thanks for the heads up. —Jeffrey

— comment by Roman on May 2nd, 2011 at 11:43pm JST (12 years, 10 months ago) comment permalink

A question on your lightroom export to flickr plugin.

I am using LR v3.3 and your plugin version 20110419.218.

I have recently tidied up the number of flickr groups I am a member of, however groups I have left still appear in the export dialogue. If I ever accidentally select a group I have left for export, I get a ‘group not availalbe error’.

Is it possible to refresh the group listing in the export dialogue box?

Love your work, very usefel,

The list should be updated when you refresh the list of sets (there’s a button for that near the list of sets). I should have a button near the groups, too, I guess…. —Jeffrey

— comment by Dave on May 7th, 2011 at 8:38pm JST (12 years, 10 months ago) comment permalink

flickrplugin 20110419.218
LR 3.4

(1) I manually uploaded an avi (with flickr uplodr) to flickr (because LR and even your plugin has some problems with AVIs)
(2) To have the correct metadata in LR I added the avi to a publish collection – now I is listed as “new”
(3) I did “Associate images Manually” – the avi is still listed as “new”
(4) I did “Re-mark as Published” to get rid of the status “new” – but then I got the error message “Nothing needed to be updated”?!

How can I move the avi to status “published?

This is a sloppy area of the plugin, because the whole “associate” thing is so fragile, but in general you’d want to follow the steps as outlined in the docs, which means to first “associate”, then have the plugin add it to the publish collection via the “populate” function. As for the “nothing needed to be updated” error, could you send a log after you get it again? —Jeffrey

— comment by Gernot on May 9th, 2011 at 2:30am JST (12 years, 10 months ago) comment permalink

Plugin is shown as enabled in Plugin Manager, but is grayed out in Plugin Extras (the sub-category of Flickr Extra’s is available). What am I missing / doing wrong??

The only thing from this plubin available in the Plugin Extras menu is “Flickr Extras”… the grayed-out “jf Flickr” is just a header under which all (one) plugin menu items are listed. If you have my geoenoding plugin, for example, there will be a dozen items under the grayed out “jf Geoencoding Support” header. Most things the plugin offers are in the Export Dialog and the Publish Services section. —Jeffrey

— comment by Wes Neuenschwander on May 17th, 2011 at 1:36am JST (12 years, 10 months ago) comment permalink

Is there any way to disable the automatic “Downloading Flickr comments” whenever you publish something? As I have 3,000+ photos on Flickr which have accrued somewhere on the order of 20,000 comments in total, having the plugin attempt to fetch them all with every publish is a little extreme. At least that’s what I believe it’s doing. I’d rather invoke it manually from time to time when I don’t mind letting it run for a good long while.

Another thought concerning the feature, is there any way to make this metadata available for searching and filtering within Lightroom? Being able to find my most popular photos my number of faves and comments (and maybe interestingness score?) would be fairly useful to me.

As always your work is much appreciated.

Lightroom really doesn’t give much flexibility here, but I figure that I can at least short-circuit the comment fetching before it its the network, if you want to do it manually. So, I’ve just pushed v.220 that includes a new section in the publish-service settings dialog that allows you to control this. It also allows you to fetch comments in the versions of the photos in the non-Photostream collections, if you like. —Jeffrey

— comment by Eric on May 19th, 2011 at 12:11am JST (12 years, 10 months ago) comment permalink

Awesome plugins. Question re: Flicker and Facebook plugins – do they optimize for the web (like Photoshop does when you Save for Web)? Thanks!

“Optimize for the web” for the most part means, AFAIK, that most metadata is stripped, so you can mimic that by selecting “Minimize Embedded Metadata” in the export dialog. —Jeffrey

— comment by Paula on May 21st, 2011 at 12:17pm JST (12 years, 9 months ago) comment permalink

Hi Jeffrey — thanks for all of your work on all of your plugins. I couldn’t live without them.

Would it be possible to hook up some kind of field in LR to export to flickr’s “People in this photo” (in some form, even if it only worked for direct real name matches?) I’ve gone through and tagged a lot of people in my photos, and would like a way to tag them in a flickr-friendly way more than just having their names show up as tags.

This is more difficult than it might seem at first because when talking to Flickr, you need not the name, but the Flickr internal code for the person. It’s not impossible, but the plugin would have to build a lot of infrastructure to support it. —Jeffrey

— comment by Stuart Parmenter on May 25th, 2011 at 1:07am JST (12 years, 9 months ago) comment permalink

Good day from Chicago! First off, thank you so much for all of your hard work on your plugins. I will be making a “gift” as soon as money is transferred into my PayPal. Now on to the question:

When trying to populate some images into a set in the Flickr Publish service, almost half of them did not show up. I moved the missing ones into the collection, and they show up as “New Photos to Publish”. I associated them manually, but they will not change to “Published Photos”. They still say they are new. Any suggestions on how to get them marked as published?

jf Flickr “Export to Flickr” Plugin Version # 20110521.222

To go directly into “Published”, they’ve got to be put there by the plugin, either via “Re-mark as Published” (in Flickr Extras), or by doing the “populate” action after the associate action. It only really matters for the “Photostream” collection, since that’s the only one that deals with pixels. The others are just set/group inclusion, which is relatively fast and painless to repeat. —Jeffrey

— comment by John M. on May 26th, 2011 at 6:34am JST (12 years, 9 months ago) comment permalink

I’m using version 20110531.224.

Can I control the ordering of photos in my sets on from the lightroom plugin? I’ve tried reordering photos manually in the Lightroom plugin, but that doesn’t trigger the photos to be republished, and even if I mark the photos for republication, and then click publish, the order of the photos on do not change. Is there a way to do this, or do I have to manually order the photos at Thanks.

No, Lightroom doesn’t allow for it. I find it very frustrating. —Jeffrey

— comment by Andreas on June 3rd, 2011 at 1:58pm JST (12 years, 9 months ago) comment permalink


I don’t have a Pro Flickr account, and thus I never want to “re-publish” my pics. I’ve un-checked all the metadata re-publish triggers, but LR still insists on republishing photos sometimes (I’m not yet sure why). Is there any way to ensure this doesn’t happen?


jf Flickr 20110603.225
LR 3.4.1

I’ve never understood completely why Lightroom suddenly considers some images in need of a republish, so I can’t answer your question. The best I can suggest is to not use Publish, but rather, use normal Export along with making a bunch of export presets for the various sets and groups you most often use. —Jeffrey

— comment by Alex Shenkin on June 12th, 2011 at 11:58pm JST (12 years, 9 months ago) comment permalink

Just wanted to post up and say thanks for a fantastic plugin!

— comment by Lurch on June 14th, 2011 at 11:04am JST (12 years, 9 months ago) comment permalink

Have mostly had great luck with your plugin until recently when it stopped publishing to flickr….got a not saying the plugin could not be found. Ok, so I’ve reinstalled it. Now all my old published photos 155 of them, are in the “modified photos to repub. file. I don’t want to touch them on flickr. Any way to leave them alone. I do like having the file of published photos to see which shots have been uploaded in LR. Also, I’d love turn off the download comments, but don’t see where to do that. Thank you.
Dan Freund

Merely reinstalling the plugin shouldn’t have had any impact on whether the photos were considered “published”, so there’s something else going on there. You can re-mark them as published from the “File > Plugin Extras > Flickr Extras” menu. Lightroom always trys to grab the comments, though I’ve got some ideas on how to head it off. But it sounds as if you don’t really want Publish… rather, just use normal exports, but create a Smart Collection with an “UploadedToFlickr=Yes” rule. Then you’ll have them at your fingertips without the baggage of Publish. —Jeffrey

— comment by Dan Freund on June 30th, 2011 at 9:29am JST (12 years, 8 months ago) comment permalink

Flickr Uploader Version 20110623.227
Lightroom Version 3.4

Is there any possibility the the uploader will post the photo to a set but not the photostream? Uploads performed prior to upgrading to the current version were working fine, now uploads seem to work but do not reflect in the photostream. Any thoughts?

The way Flickr is designed, it’s not possible for a photo to be in a set but not in your photostream… photos “live” only in your photostream at Flickr, while Flickr sets merely contain references to the photostream photos. —Jeffrey

— comment by Ron Kochanowski on June 30th, 2011 at 5:54pm JST (12 years, 8 months ago) comment permalink

This is for the flickr plugin version 20110712.236 for lr3 when attempting to view my photostream or collection I get an error can’t find url for this published collection even for the default photostream. Thanks

I’m working on this… it turns out to be a surprisingly difficult problem due to how Publish is designed internally. —Jeffrey

— comment by Fred on July 15th, 2011 at 2:41am JST (12 years, 8 months ago) comment permalink

Is it possible to have the zenfolio/flickr etc plugins remove the file names so I do not have to do it manually on each image after I have synced with flickr or zenfolio?

One can set the source for the title/caption in the upload. Set it to nothing if that’s what you want. —Jeffrey

— comment by Fred on July 15th, 2011 at 4:39am JST (12 years, 8 months ago) comment permalink

Plugin version: Export to Flickr, 20110712.236

I have chosen to “Download photo comments from Flickr: Manually”, but every time I upload a few photos Lightroom will continue to download comments for ages and ages.

I know that it should show up “momentarily”, it seems to go on for ever. I can’t remember ever seeing it be cancelled automatically.

Any tips on how I can get it to work the way I want it? Thx in advance.

Publish gives no option here… it’s a huge design problem, I think. The best I’ve been able to do is to not actually fetch comments from Flickr when Lightroom tells me to, if you’ve chosen Manual downloads. But Lightroom doesn’t know this, so goes through all the motions internally, which is a lot of wasted work if you have a lot of photos in the Publish Service. Until Lightroom is updated to be reasonable, this is the best I can do. —Jeffrey

— comment by David Naylor on July 27th, 2011 at 5:50pm JST (12 years, 7 months ago) comment permalink

Hi Jeffrey.

About a year ago another user asked for a feature to manually claim photos that are already on flickr (
You said this is/was a to do. Are there any news to it? Is there a way to manually claim photos? Or will there be a way in near future?
I’ve got several photos that are not recognized by the deep scan an the claiming feature of the latest version.

BTW: I don’t how my photo would make it to flickr without your plugin – it’s just great!!!


It’s been there since February. —Jeffrey

— comment by André on July 31st, 2011 at 9:11pm JST (12 years, 7 months ago) comment permalink

I have the latest version of the Flickr plugin (20110802.238) and noticed that the “Group Pools” list isn’t to date. It’s missing some groups that I’m a member of and I see no way of “refreshing” the list.

Is this a known bug or am I missing some method for refreshing/resyncing the list?

Ah, good point. They update with the list of sets… there’s a “refresh list” button near the set list. —Jeffrey

— comment by T. Chow on August 8th, 2011 at 5:10am JST (12 years, 7 months ago) comment permalink

Hi Jeffrey,

Are there any known issues related to uploading HD videos to Flickr with this plugin? I like to manage short video clips (under 90 seconds, per Flickr limits) taken with my Canon 7D alongside all my other photos. As an example, if I try to upload a 63 second video (375 MB at 1080p), LR locks up, my whole computer grinds to a slow crawl, and LR seems to eat up memory (I have 4 GB RAM on this laptop) until it starts eating into virtual memory as well (disk usage drops by a few GB until the disk fills up, and then usually LR freezes up completely). I tried a shorter video (40 seconds, 240 MB) and it didn’t seem to cause problems like larger ones.

Any thoughts?

Flickr Uploader Version 20110802.238
Lightroom Version 3.4.1
Mac OS X 10.6.8

I’m going to guess that the file size is the problem… the way Lightroom interacts with plugins requires that the entire image/video be loaded into memory before starting the upload, and the attempt to do so is probably what’s causing the apparent lockup as your OS memory allocator goes crazy. I don’t see any way around this (other than exporting outside of Lightroom) until Adobe updates Lightroom. —Jeffrey

— comment by Chris on August 15th, 2011 at 1:56pm JST (12 years, 7 months ago) comment permalink

Flickr Uploader Version 20110819.241
Lightroom Version 3.4.1

Tried the flickr plugin, it seems to work fine. But I am missing the “Privacy and Safety” section that the default flickr plugin has. Am I missing something?
I want all my pictures to be private. I changed the default privacy setting in flickr too, and that does not solve my problem.

Thanks and keep up the good work…


The plugin offers full control of privacy… there are a lot of sections to the dialog… please see them all to familiarize yourself with what’s available. —Jeffrey

— comment by Daved on August 22nd, 2011 at 11:47pm JST (12 years, 6 months ago) comment permalink

I’m going to upgrade to OS X Lion this weekend and completely reinstall everything. When I reinstall Lightroom and your Flickr plugin will that trigger a republish to Flickr? I would rather not have that.

It’ll be fine if you backup your catalog and Lightroom preferences file. The catalog and images you have to handle yourself, but for all the various preferences and preset files, check out the LR/Backup plugin for backups. —Jeffrey

— comment by Marc on August 26th, 2011 at 4:17am JST (12 years, 6 months ago) comment permalink

The Lightroom Publish/republish flags are stored exclusively in the Lightroom catalog. Just copying the catalog from the old computer to the new computer will keep the Flickr Publish Service happy.

Cletus Lee – Bellaire, TX USA

Some plugin-specific items are kept in Lightroom’s preferences file; I’d be weary of copying just the catalog without the preferences file… —Jeffrey

— comment by Cletus on August 27th, 2011 at 1:00am JST (12 years, 6 months ago) comment permalink

Hi Jeffrey,

please: any easy way to replace a picture already on Flickr (with a different edit of the same one) using your plugin in “Publish mode”?

thanks 🙂

If you have a Flickr Pro account, Publish does it automatically: just make your changes and republish. If you don’t have a Pro account, photos can’t be replaced. —Jeffrey

— comment by pl_svn on October 7th, 2011 at 2:33am JST (12 years, 5 months ago) comment permalink

yes I do have a Pro account but unfortunately it’s not that easy: I’d like to replace a picture with an externally edited copy and LR’s Publish treats it as a separate image :-/

Ah, I see. You can do that, but it’s kludgy: remove the photo from the Publish Collection (leaving it untouched on Flickr), then clear the association (via “Clear” on the Flickr Extras dialog). Then do a manual association of the Flickr url to the new copy in Lightroom (via the same Flickr Extras dialog), then get the photo back into the Publish Collection not by adding it directly, but by the “Claim for this Photostream” function. Easy as pie! /-: —Jeffrey

— comment by pl_svn on October 7th, 2011 at 7:34am JST (12 years, 5 months ago) comment permalink

How do I remove the “Uploaded using Jeffrey’s Lightroom Exporter” additional info that gets added by default? I looked through all the options and your docs and don’t see it. Thanks.

That’s something Flickr adds… I have no control over whether they add it. —Jeffrey

— comment by Mark on October 23rd, 2011 at 4:53am JST (12 years, 4 months ago) comment permalink

I also thought many of your readers would appreciate this plugin, to “unmark for flickr republish:”

I used it and it works. 🙂

I suppose, but the Flickr plugin itself has the same feature, in the “Flickr Extras” dialog. —Jeffrey

— comment by Eric on October 23rd, 2011 at 5:42am JST (12 years, 4 months ago) comment permalink

@Mark : to remove the “Uploaded using Jeffrey’s Lightroom Exporter” go in your Flickr account and “Show which application you used for uploading” to no

— comment by Florent Bouckenooghe on October 23rd, 2011 at 6:57pm JST (12 years, 4 months ago) comment permalink

… but I believe it is nothing else than just fair to aknowledge, and possibly advertise, the great work Jeffrey has and is devoting to us all!

— comment by pl_svn on October 24th, 2011 at 12:18am JST (12 years, 4 months ago) comment permalink

I’m a newcomer to Lightroom and Flickr.
So far I have used the Flickr upload function that came with LR.
However – this utility has one major weakness:
While you can organize your photos in sets and collections – even collections nested 5 levels deep in Flickr. There is no such thing in LR.
Taking a lot of bird photos and organizing them i sets sorted under orders, families and species/subspecies it is relatively easy to find my. In LR – all my sets are in one very long list.

I am searching for a utility that let me do this sorting already in LR.
To make an easy example:
If I wanted to sort my pictures in sets on geographical location I would first make a main folder on Continent, then on Country, then municipality and finaly local places.

I would be very happy to buy or support economically a plugin that would let me do this!

With effort, you can do this with my plugin… bring up the context menu for the Publish Collection and choose “Create Publish Collection Set” and name it “Europe”, for example, then in its context menu do the same to create “Norway”, etc. At the final level, create a Publish Collection that refers to the set you want. It’s a manual process, but at least you can do it. —Jeffrey

— comment by Stein Arne Jensen on October 28th, 2011 at 4:05am JST (12 years, 4 months ago) comment permalink

Though if I’m not mistaken, creating a publish collection set in LR will not create a collection in Flickr, so you’d have doubled your work trying to organize it the same way in LR as in Flickr…

Yup. —Jeffrey

— comment by Roman on October 30th, 2011 at 5:09pm JST (12 years, 4 months ago) comment permalink

… any idea on a *painless* way to replace all my pictures already on Flickr, and in a “Publish” collection, with larger ones?

thanks 🙂

Edit the publish-service settings to set the size you want, answer “yes” when it asks whether you want to republish, then publish. —Jeffrey

— comment by pl_svn on November 7th, 2011 at 11:32pm JST (12 years, 4 months ago) comment permalink

With respect to the above comment by pl_svn – it’s not *entirely* painless.

Replacing photos on Flickr will change all static URL’s to the photos, so if you’ve ever blogged your photos those links will break. Also the magic donkey doesn’t seem to particularly like when a photo is replaced, so it might negatively impact interestingness by a small amount.

Of course neither of those things are anything that Jeffrey has any control over, but they might be a concern to you so I figured I’d mention them.

— comment by Eric on November 7th, 2011 at 11:55pm JST (12 years, 4 months ago) comment permalink

… *that* painful and easy? 🙂

thanks, Jeffrey

— comment by pl_svn on November 8th, 2011 at 12:13am JST (12 years, 4 months ago) comment permalink


well… I don’t give “interestingness” a damn… you know what :-p … but thanks for reminding me about URL change: that’s a real dealbreaker issue 🙁

thank you very much

— comment by pl_svn on November 8th, 2011 at 7:51am JST (12 years, 4 months ago) comment permalink

If you have a pro flickr account, you *can* republish images under the same name. Jeff’s plugin also allows you to resend metadata (such as a gps tag or more keywords) without republishing the image.

That’s the idea of the publish manager, the relationship idea, that LR and this plugin track the location of the photos after they’re uploaded and information can be updated to the same web address. But only with a pro account. I’m JF has verified this somewhere else on his site.

— comment by Eric M on November 8th, 2011 at 3:09pm JST (12 years, 4 months ago) comment permalink

Ok, I goofed. I accidentally did a “mark for republish”, but I do not actually want to do that. Can i “unmark for publish” somehow?

“Undo” should work, as well as “unmark for publish” in the “File > Plugin Extras > Flickr Extras” dialog. —Jeffrey

— comment by Janne on November 10th, 2011 at 8:16am JST (12 years, 4 months ago) comment permalink

I suspect that this is an issue on Flickr’s end, and not something fixable within the plugin, but I thought I’d mention it just in case.

Whenever I change the metadata (or anything else) on photo and want to update the version at Flickr to match, it results in the real URL of the images on the web getting changed (despite the fact that the photo’s “home” URL at Flickr remains the same). This means that any prior references to that image URL, such as those generated by the oEmbed calls that happen when a Flickr URL is used to embed a photo in a blog post, become invalid, and broken images end up appearing in older posts. Is there any way that a Flickr photo can be updated without a new image URL being generated at Flickr? It seems especially odd that this is the case even when it’s just a metadata update.

It’s a combination of really unfortunate designs at Flickr and in Lightroom. For reasons I don’t know but assume are related to limitations with their underlying data-distribution infrastructure, Flickr urls change whenever you update the image pixels, even with Pro accounts. This is really really unfortunate, but that’s the way it is with Flickr. The plugin has the ability to update only the metadata (File > Plugin Extras > Flickr Extras) and in that case no urls change at Flickr, but with an update in a Publish Service, the plugin has no idea what has changed, so can’t know that it’s a metadata-only update, so must do a full refresh. It’s a bummer. The best I can suggest is to not us a Publish Service for the kind of photos that you’ll like to externally, but another (but really fragile) approach would be to invoke the resend-metadata in the Flickr Extras on images that you know it applies, to, then invoke the “unmark republish”, also in Flickr Extras. —Jeffrey

— comment by Zane Selvans on November 12th, 2011 at 5:38am JST (12 years, 4 months ago) comment permalink

Is the intended behavior that subsequent uploads (after modifying the image) will change the permissions on the uploaded image?

by default, I upload images as private into Flickr, and then from there, I may make changes taking some of the images public. This allows me to use Flickr to share photos with the people in the photos first, and then use flickr to make the ones they approve of, public.

However, if I later touch up something in LR, it looks like the permissions are getting reset, and I don’t have a way in LR to know what the permissions in Flickr are.

Is there a way to support this workflow?

If you’re talking about Publish, then yes, it’s intended that the permissions are set with each export to the settings that you define for the publish service. You could consider having the permissions defined via keyword, then instead of making photos public at Flickr, make them public via keyword in Lightroom, then republish. —Jeffrey

— comment by Stuart on November 14th, 2011 at 5:47am JST (12 years, 4 months ago) comment permalink

For what it’s worth, the reason Flickr gives for the URL change on replace is to prevent mischief. Say if I uploaded a photo of a cat, you blogged that photo, and then I replaced that photo with porn, there’d be porn on your blog. Stupid if you ask me but that’s the reason I was given.

But that does bring to mind a tiny request – can we get a “Resend metadata and re-mark as published button”? Since I wind up doing this process a lot, cutting it from a two step process to a one step process would be helpful.

— comment by Eric on November 15th, 2011 at 1:31am JST (12 years, 4 months ago) comment permalink

@permissions (comment by Stuart and Jeffrey)

I use keywords to control permissions. Sometimes I like/have to change permissions – so I change the specific keyword(s) – is there a way to change permissions on flickr with “resend metatdata” without “republish”? This would be a great performance boost.

Yes it would, but unfortunately not easy to do under the hood —Jeffrey

— comment by Gernot on November 17th, 2011 at 9:52pm JST (12 years, 4 months ago) comment permalink

Yes, I was referring to publish. Something to consider for an update is an option that allows re-publishing of updated images, where the permissions are taken from the permissions of the current image as published in the service. Basically a way to let me us the plugin to set permissions when I initially publish an image, but to allow flickr to then manage permissions even when I re-publish a modified form of the image.

In the current state, I have to essentially remember any changes I made in flickr to permisions whenever I update an image and republish, or I need to just use the plugin keyword approach to always manage permissions. While the keyword approach is a nice feature, it isn’t really an optimal interface for this, at least in my humble opinion.

Thanks for the consideration, and an awesome plugin.

The whole point of Publish is that it is the “master source” for all information about an image (at least as far as info that comes from you… comments from others are different). So if you’re changing stuff at Flickr, you’re going against what Publish is about, and so perhaps Publish isn’t the best tool for you in this case. —Jeffrey

— comment by Stuart on November 17th, 2011 at 10:51pm JST (12 years, 4 months ago) comment permalink

Hi Jeff, Ken from Chicago here … just to let you know that your plug-ins are time saviors and very much part of my workflow. Thank you for your generous heart. Any chance of developing a plug-in for Photoshelter? Thanks.

No plans for me to make one, but a web search will find that someone else has. —Jeffrey

— comment by Ken on November 18th, 2011 at 7:52am JST (12 years, 4 months ago) comment permalink

Hi Jeff,

I’ve hit an annoying bug (is there any other type?!). I use your Flickr Publish Services functionality. I lost the association between an image in LR and of that on Flickr. I re-associated and it found it. If I use the Flickr extras to update metadata (tags for instance) it works fine, but if I edit the actual photo and publish, then it uploads a brand new version and changes the association to that version. It’s driving me nutty!

Thanks in advance,

Windows7 64-bit
LR 3.5 (current version)
Flickr plugin version (current version)

It’s the point of Publish that it uploads a new version when you change things, but two gotchas to watch out for: Flickr doesn’t allow non-Pro users to do an in-place update, and even with Pro users, an “in-place” update still changes the URL of the JPGs, though comments and ratings are maintained. These are both Flickr issues. —Jeffrey

— comment by Gavin Owen on November 21st, 2011 at 6:48pm JST (12 years, 3 months ago) comment permalink

Hi Jeffrey –

First off, thank you for an amazing set of plug-ins. They make Lightroom ‘sing’.

One question; using the Flickr plug-in, how can I search for all of the photos I have uploaded using it? I see the meta data under “Uploaded to Flickr” = yes, but cannot find a way to search/filter on that.

You can filter on it in the Library Grid Filter (under the Metadata dropdown), or via a Smart Collection. —Jeffrey

— comment by Dean on December 5th, 2011 at 10:37am JST (12 years, 3 months ago) comment permalink


I just moved from one Mac to another and everything seems ok now, except I can’t find the custom definitions I made for the Flickr plugin. I mean the Title and Description presets.

Can you remind us where these presets are stored?

I’m currently still using LR2.7, on Mac OS X, plugin 20110710.233.



They’re all stored in the Lr preferences file, which means that you have to recreate them on the new system. It’s a hassle, sorry. —Jeffrey

— comment by Liviu Ionescu on December 11th, 2011 at 5:57pm JST (12 years, 3 months ago) comment permalink

How can I move photos from one (jf flickr) publish service to another (different) (jf flickr) publish service?

You’d want to delete the photos from the service (but not from Flickr), then “claim” them in the other service. —Jeffrey

— comment by Gernot on December 23rd, 2011 at 6:21am JST (12 years, 2 months ago) comment permalink

Just upgraded the Flickr plugin to 20111229.254 and having issues with the group settings. I’ve tried setting both the keyword to group as well as the explicit group settings but for some reason it won’t auto-assign the photo to any of the groups specified (8 total). I’ve used these settings before (not recently) but it used to work so I’m relatively sure I configured it correctly. Running LR 2.7 on Windows 7 64

I had a bug with the groups stuff in recent builds, sorry; it’s now fixed in the 20120103 build. —Jeffrey

— comment by Troy Ward on January 1st, 2012 at 1:25am JST (12 years, 2 months ago) comment permalink

I’m writing from Denver, CO. I’m using version 20120114.258. I love the option to ‘Set each photo’s “posted date” to the time…’ Is it supposed to also work with videos that are uploaded? I just uploaded a mix of photos and videos taken on the same day, and the photos show the correct posted date, while the videos show today’s date.

The plugin treats them the same (or at least it should), so it could be a limitation at Flickr. I’ll take a look. —Jeffrey

— comment by David Bump on January 25th, 2012 at 2:49pm JST (12 years, 1 month ago) comment permalink

Yet another update on the video time/date! I think the problem is that video files (or at least the ones my two Canon cameras produce) do not contain EXIF data. I’m guessing Lightroom is pulling the date/time from the file’s datestamp, to sort it? When I upload video manually to flickr, both the taken and posted dates are set to when I uploaded, wheras with pictures, I think the taken time is read correctly from EXIF? So this may not be something that’s easy to address. Apparently, if you really want to get the info, you can rename the .THM file that acts as a thumbnail for in-camera use to .JPG, and import that into LR, and then can viewthe date/time from the EXIF embedded in that file, but I don’t need it that badly. Thanks again for this awesome plugin!

— comment by David Bump on January 27th, 2012 at 1:59pm JST (12 years, 1 month ago) comment permalink

I’ve got a small problem: I have some pictures that I’ve deleted from flickr after being uploaded with your excellent plugins.
Then I re-uploaded some of them on flickr.
The ones that I didn’t re-upload still reference a missing page on flickr from the lightroom metadata.
How can I remove flickr metadata from those ones in lightroom?


Select, them, then choose “clear” in the “File > Plugin Extras > Flickr Extras” dialog. —Jeffrey

— comment by Matteo on February 2nd, 2012 at 7:14am JST (12 years, 1 month ago) comment permalink

Any chance of an Export to 500px plugin?. I’m starting to upload photos there and it would streamline the process greatly. Thanks.

Answer is here —Jeffrey

— comment by Patricio Suarez on February 25th, 2012 at 5:02am JST (12 years ago) comment permalink

Upgraded to the final version of LR4 released today and then it tells me your plugin is not compatible. I tried the latest version available on this page but nope. Any idea of when you plan to update it? Thanks.

Version .268 should definately work in Lr4. If not, please email a screenshot or the like…. —Jeffrey

— comment by Pratik on March 7th, 2012 at 5:34am JST (12 years ago) comment permalink

Hi Jeffrey

updated to LR4 and made a new *cumulative* donation for the four plugins I use but… sorry: didn’t remember I had, instead, to make four separate donations as each plugin requires a different PayPal transaction ID

no big issue but… pretty annoying :-/

sorry: just a rant and… I’m already proceeding with three more 1c donations ;-p

Sorry for the hassles. It’ll come up every couple of years. As always, one-cent transactions are okay for them all, so hopefully the annoyance is short lived. —Jeffrey

— comment by pl_svn on March 7th, 2012 at 10:40am JST (12 years ago) comment permalink

Installed LR4 on Windows 7 64-bit today and played around adding some of my photos to the map. Your plugin correctly spotted the updated GPS data and marked them as needing a republish. I republished them which happened very quickly but flickr still doesn’t see the new GPS data. Using 20120229.185.

Are you sure that you’ve got your Flickr account set up to allow geoencoded photos? It’s disallowed by default. —Jeffrey

— comment by Dave Townsend on March 7th, 2012 at 2:33pm JST (12 years ago) comment permalink

Jeffrey, been using your flickr plugin for a long time (need to pay for it, for that I’m sorry).

I used to manage GPS visibility using tags, but flickr rolled out geofences (, and those work really well. Essentially, you tell flickr the default visibility for a circle, and flickr sets that visibility. It can be overrulled, however.

Unfortunately for me, your plugin does just that. Would it be possible to add a new option to the Geo Visibility “flickr default” that sets it to whatever we told flickr to set? I suspect this would allow the geofences to work on pictures uploaded by your plugin.

It sounds like it’s a bug at Flickr… if you tell them not to reveal the location and they do, it shouldn’t matter how they learned of the location in the first place. I’d definitely report it as a bug to them. But FWIW, I see no API access to anything about geofences, so there’s nothing the plugin could do anyway. —Jeffrey

— comment by Aaron Whiteman on March 7th, 2012 at 2:42pm JST (12 years ago) comment permalink

Hi Jeffrey,

I have problem with Smart photosets.

I have a picture inside a smart photoset i can not deleted from my disk.
and i have no clue how to remove from the smart photoset without having to set the data to do not fit with a smart photoset includes filters.

Could you please help me?


What you mention — setting the data to not fit with the smart photoset’s filters — is exactly the way and the only way to exclude a photo. That’s the whole point. If you want to include most items but exclude a few, perhaps consider adding a rule along the lines of “Keywords don’t contain OMIT_FROM_FLICKR”, and add that keyword to photos you want to exclude. —Jeffrey

— comment by Carlos Alies on March 7th, 2012 at 8:10pm JST (12 years ago) comment permalink

A feature request:

I recently noticed that at some point, my Flickr publish collection and Flickr account got out of sync. My Flickr account has 20 more photos than the publish collection. I’m not sure how/when/why this happened, but I’d like to track down the un-matched photos and match them up.

The problem is that I currently have about 4,000 photos on Flickr – so manually figuring out which of those 20 aren’t in my publish collection would be fairly tedious.

Is there any way I might get the plug in to spit out a list of Flickr URL’s or ID’s or whatever in my Flickr account that aren’t matched by Lightroom?

You might try the “Automatic Association” feature in “File > Plugin Extras > Flickr Extras”. It’s pretty fragile, but you might get lucky. Other than that, I don’t have any good ideas. —Jeffrey

— comment by Eric on March 8th, 2012 at 12:02am JST (12 years ago) comment permalink

Hi Jeffrey,
same issue with geoencoding and flickr. Republishing a picture where I’ve just added the GPS information with the map module seems not to have an effect. But changes in the development module re-uploads the complete image and the geolocation appears in flickr.

Yes, it’s an unfortunate byproduct of a how things work under the hood with Lightroom and with the plugin… there must be actual develop changes. I’m going to have to think of some way around this… —Jeffrey

— comment by Frank Joas on March 10th, 2012 at 4:53pm JST (12 years ago) comment permalink

Hi Jeffrey,

In the post just below mine, I noticed that adding GPS coordinates in lightroom does not count as changing a develop setting. The only change I made to the picture in question was add GPS info. That might answer the question…

Best regards from Winnipeg,


— comment by Henk on March 11th, 2012 at 11:56pm JST (12 years ago) comment permalink


In my LR4 the “register here” is missing 🙁
What could help as now the plugins are in trial?
I have them working fine in LR3.

br. Hannu

The “register here” button should appear once you have Lightroom itself registered, and a “register-here will show up here” note otherwise. If not, make sure you’re using the latest version of the plugin, and perhaps send a screenshot. —Jeffrey

— comment by Hannu on March 19th, 2012 at 12:15am JST (12 years ago) comment permalink

Finally discovered the “Update Metadata” option in Flickr Extras, that allowed me to push the new tags and GPS for my photos. Shame I had to remember which ones had changed manually but at least there is a workaround for now

— comment by Dave Townsend on March 19th, 2012 at 10:55am JST (12 years ago) comment permalink

Hiya —

I’ve just done a fresh install to a new disk and want to transfer over the Flickr group mappings from the old version – but I can’t for the life of me find out where they’re stored! Can you give me a hint where to look please? It’d be a serious pain to set up all the groups and tag mapping again as there’s a few hundred in that list.

Thanks 🙂 joel.x

Your best bet would be to copy over the old catalog lrcat file (renaming it to whatever you want it to be on the new system), then on the new system delete all the “images” (catalog entries) leaving a catalog that’s empty, but with all the publish services set up as you had them before. —Jeffrey

— comment by Joel Rowbottom on March 19th, 2012 at 7:21pm JST (12 years ago) comment permalink

The problem with geofences might be that the plugin is explicitly telling Flickr to make the location visibility “all” rather than just letting flickr work it out based on my preferences at flickr (at least that is what the settings UI suggests). That would override the default location visibility for the photo so the geofence wouldn’t apply.

They’re aware of a need to update their API (see this thread). We’ll see. —Jeffrey

— comment by Dave Townsend on March 25th, 2012 at 12:31pm JST (11 years, 11 months ago) comment permalink

Maybe you’re better at interpreting their responses but to me it sounds like they are considering adding an API that will tell you for a given photo that it falls within a geofence. That doesn’t sound useful to the uploader at all. I think if you didn’t call at all then the geofences would work just fine, but I don’t see anything in the settings that suggests a way to stop your uploader from doing that.

— comment by Dave Townsend on March 26th, 2012 at 2:32am JST (11 years, 11 months ago) comment permalink

Hi Jeffrey. Quick question: is there a way for me to create a smart collection or otherwise filter images on Flickr that have comments?

Unfortunately, no, Lightroom doesn’t supply that info to the plugin. —Jeffrey

— comment by Jack James on April 7th, 2012 at 8:55pm JST (11 years, 11 months ago) comment permalink

Ah ok, so it seems like simply tagging a photo with a GPS loc isn’t enough. It’ll display some auto populated reverse name look up in the appropriate fields (Sublocation, City, State, Country) but since they’re grayed out it seems like they don’t stick with the photo, at least as far as your Flickr exporter cares when populating the geo: machine tags (and actually just adds them blank, which is ugly). What is extremely interesting is that the actual IPTC tags still get exported with that grayed out data.

I can use the bulk reverse name look up tab to force populate all those fields, but I either get a very specific (Sub)location or it blanks it out, which kind of sucks as I generally like the value that’s returned when the fields are populated with the grayed out data (something more like neighborhood than street address).

Anyhow, I really don’t know how this is designed in your head, but I do feel like there’s at least 1 bug here.

A. If the fields are blank, whatever the prepopulated grayed out data is Flickr upload should use to populate {Location} {City} {State} {Country}, and also use with the Mimic Flickr’s practice of including the city/state/country as keywords option.

B. Don’t let Flickr upload default to applying the grayed out data to IPTC on export, all together.

And lastly, it would be nice if the bulk reverse name look up in the geotagging plugin would have an option to use the slightly more generalized location data that is autopopulated as gray data when doing a simply single location tag.

Let me know if a log would help and I’ll throw one up somewhere.

Unfortunately, the plugin not only has no access to the grayed-out data, but doesn’t even know whether it’s even there. While grayed out, it’s completely invisible to plugins. Hopefully Adobe will address this sometime, but that’s how it is in this first implementation. This is just one of many nooks and crannies of Lightroom’s mapping implementation that could use some attention. —Jeffrey

— comment by rubin110 on April 13th, 2012 at 12:59pm JST (11 years, 11 months ago) comment permalink

FWIW, I agree with Dave Townsend’s interpretation of the geofence issue and Flickr’s response. All the uploader needs is an option to upload the GPS tags without explicitly setting the Flickr location permissions. That should allow the Flickr defaults, including geofences, to take effect.

I’m at a loss to explain what page on I was on when I first replied to this comment, but my mental logjam has cleared and I finally understand what I should have understood long ago, and I just pushed a new version of the plugin that addresses this properly. Thanks for your patience. —Jeffrey

— comment by Matthew Hunt on April 26th, 2012 at 11:24pm JST (11 years, 10 months ago) comment permalink

I’m at a loss to explain what page on I was on when I first replied to this comment, but my mental logjam has cleared and I finally understand what I should have understood long ago, and I just pushed a new version of the plugin that addresses this properly. Thanks for your patience. —Jeffrey

Thank you Jeffrey, I just updated the plugin and verified that the new “don’t set” setting works perfectly for the geofence I have set up around my parents’ home.

— comment by Aaron Whiteman on April 29th, 2012 at 11:03pm JST (11 years, 10 months ago) comment permalink

Thanks, Jeffrey! I tried 20120429.272 with “don’t set any specific location visibility” and it works great for me. I tested it with photos inside and outside my geofences, and with GPS data in the photos at the time of upload and with it added later via “Resend Metadata”, and it worked correctly in each case. Strangers could see the location of photos outside my geofence, but not inside.

— comment by Matthew Hunt on April 30th, 2012 at 12:10am JST (11 years, 10 months ago) comment permalink


First off great plugin that despite what I’m about to say is invaluable.
The issue I’m having is that I use lots of smart groups so that I can keep track of not only the image content but also the lens and body so that I can easily offer advice to others online and point them to my flickr (just back history to explain i use lots of smart groups and why)

Anyway after I’ve published an image I will sometimes alter the metadata – just name the type of insect, that sort of thing – no actual adjustment to image, which will rightly mark it to be re-published, the problem comes now that sometimes it just flies through the images updating the tags, but often it uploads the whole image again and that breaks the naming of the files as used on forums and so forth, which as I’m running a 365 project (take a photo a day and upload) breaks the images quite a lot.

Also worth noting is that publishing via multiple groups seems to do the same thing too even if metadata has not changed.

I had this before with lightroom three but it seems much worse under lightroom 4.0 – I have just now upgraded to the very latest version (20120429.272) and just saw the same thing an a re-publish I was half way through but stopped to test the latest version.

Sorry that was so long and thanks again.

Unfortunately, that’s how Lightroom is designed.. it doesn’t give the plugin insight into what has changed. There may be light on the horizon, but for now this is how it works. You can handle the metadata upload manually (via the Plugin-extras dialog), and then mark the images as unchanged. It’s a hassle, but that’s the best I can suggest at the moment. (However, tangentially, you can use the Library Grid Filter to isolate upload-to-Flickr images by lens, body, etc., on the fly, which may eliminate your need for so many groups.) —Jeffrey

— comment by John on April 30th, 2012 at 6:34pm JST (11 years, 10 months ago) comment permalink

Thanks very much for the quick reply, I’ll look at the Library Grid Filter and see how that works and look forward to the light on the horizon 😉

— comment by John on April 30th, 2012 at 7:10pm JST (11 years, 10 months ago) comment permalink

… not only Lightroom “doesn’t give the plugin insight into what has changed”, it doesn’t give *the user* any insight!!!

I recently reinstalled the OS (thanks, Lion :-/ ) and now almost every picture has the exclamation mark stating that metadata are out of synch between my catalog and my files but… how can I check which are the right ones? :-/

not a question: just a rant! ;-(

— comment by pl_svn on April 30th, 2012 at 10:00pm JST (11 years, 10 months ago) comment permalink

Would it be possible for jdflickr to detect a keyword with a user-specified “{namespace}:” and then block that keyword from being upload?

I’ve started making use of the feature to update the flickr privacy and very useful it is too. However, it not alway practical to use my existing keywords and I so I’ve ended up with a small set dedicate keywords for the purpose: In my case I’m using “flickr:friends” and “flickr:family”. I’ve used namespace/machine-tag format here since it is in effect a control keyword rather than descriptive of the image. No only does the namespace help isolate it from other descriptive keywords but has the added benefit of keeping the keywords close to each other in the list. For me these ‘machine tags’ have no purpose apart from controlling jd Flickr but of course they end up on my flickr page. Would be just perfect if jdFlickr make them dissappear.
Lightroom lets you set any keyword to not export… visit a keyword’s “Edit” page via the context menu for the keyword in the “Keyword List” panel, and deselect “Include on Export”. —Jeffrey

— comment by Phil Blackburn on May 13th, 2012 at 3:34am JST (11 years, 10 months ago) comment permalink

I’ve used these deselected “Include on Export” keywords to populate Smart Publish Service collections for some time. My internal keyword “@flickr” gets the image included in a jfFlickr Publish Collection. Another Keyword determines which Flickr set will get the assignment.

— comment by Cletus Lee on May 13th, 2012 at 11:19am JST (11 years, 10 months ago) comment permalink

I had already tried deselecting “Include on Export” however this then prevents the Image visibility rules from working – I guess that’s because your publish service only gets to see what Lightroom has exported rather than what is in the catalog? On the off-chance that this is a bug, I’m using version 20120508.274; LR4.0; Win 7.

The plugin should be checking all keywords, not just exportable ones, so indeed it may be a bug. Try a small test, when it doesn’t work as you expect, send a log along with a note about how what did happen differs from what you expected. Thanks. —Jeffrey

— comment by Phil Blackburn on May 13th, 2012 at 4:43pm JST (11 years, 10 months ago) comment permalink

Wow, I am truly impressed that you still support Lr2. I can’t even remember what it was in those days!

To whoever is still using Lr2: It is time to move on. Lr4 has so many new features and the new process version 2012 is great! You can get so much more out of your images.

— comment by Daniel on May 14th, 2012 at 3:17pm JST (11 years, 10 months ago) comment permalink

Using flickr publisher plugin 20120514.275 on LR4
I found that retrieving the comments for my photo’s from flickr does, indeed, take a looong time – as is mentioned in the plugin configuration screen. So, I switched retrieval of comments to manual, and also changed to retrieve comments only for the main photostream.
However, the plugin still says it is retrieving the comments for all publish collections. It doesn’t really do anything, as far as I can tell, but it does still take a looong time.
If the automatic retrieval of comments is switched off, does the plugin still go through the motions of faking it? It even feels as if it does that for every single photo I have in flickr. The more pictures I have published, the longer the comment retrieval operation seems to take, even though it doesn’t seem to do anything.
Would it be possible to skip the entire step of retrieving comments when the option is switched off in the plugin configuration? Or am I doing something silly and can this looong operation be avoided by doing something I overlooked?

Many thanks!

Lightroom always trys to get every comment every time. I think that’s ridiculous, but that’s how it works. When you switch to “manual”, it’s just telling the plugin to not actually contact Flickr (to fake it, as you put it) and lie to Lightroom that there are no new comments. As I said, it seems ridiculous that it’s not an option, but apparently my take on things doesn’t match Adobe’s reality. If you agree that you’d prefer it to be optional, submit a feature request to Adobe. If enough people do, maybe they’ll agree. —Jeffrey

— comment by Marjo on May 28th, 2012 at 11:58pm JST (11 years, 9 months ago) comment permalink

Hi Jeffrey,

Still can’t use the Flickr Plugin Version: with LR4 and I’ve removed LR3 from my computer so I’m out of luck trying to upload from LR.

System: W7 64bit. LR4.0 (just downloading the 4.1 version now and it will update when finished)

Can’t use Plug-in “Flickr”
This plugin is not installed or functioning properly

Yet when I go to File/Plug-in Manager it shows the plug in and the path to it and if I view in Windows Explorer it shows up right where it is supposed to be:
Path: C:\Program FIles\Adobe\Adobe Photoshop Lightroom 4\Flickr.lrplugin

Status: This Plug-in is enabled

I’ve tried deleting and reloading etc. etc. but to no avail …I just can’t seem to get LR4 to recognize it.

I’m not sure what trouble you’re having, but that’s not my plugin, that’s the one that comes with Adobe, so you should contact them with more details. Or, perhaps, try mine, via the download link in the upper-right corner of this page. —Jeffrey

— comment by jay on May 31st, 2012 at 2:44pm JST (11 years, 9 months ago) comment permalink

I’m running 20120531.276 on MacOS Lion with LR4.1, and have run into what may be a burp between the Export to Flickr plugin and the new Flickr API that you have written about.

In chatting with a friend today, he told me that he really liked my recent images and was wondering why I disabled comments. My response was “Oh, really?!” and then the lightbulb went on and I realized why no one had commented on my last three or four uploads. Gee, and I thought nobody liked those images. 😉

So I went to Flickr, pulled up my latest upload, and after navigating to Owner settings, I clicked on the “(show more)” link – and lo and behold, the Permissions settings were such that no one could comment or add a note, tag, or person to the image.

By way of explanation, my Flickr privacy setting is set so that new uploads default to “View: Only you (private)” so that I can do a mass upload, and then add a caption, notes, or whatever else I might want to do before making the newly uploaded images public.

However, in terms of permissions on comments, etc., my other Flickr settings use the recommended values:

Any Flickr member can add comments (edit)
Only your Contacts can add notes/tags/people (edit)

In my settings for the Export to Flickr plugin in the “Flickr Metadata Management” settings, I do not specify any keywords that control visibility, safety level, etc. The plugin does not appear to offer any control on who may comment or place a note/tag/people on a photo, and that’s fine –my settings on the Flickr site set those the way I want.

It thus seems that the Export to Flickr plugin and/or the new Flickr API may be setting a per-upload privacy setting that winds up overriding my Flickr default. This started happening within the last couple weeks; my older uploads have the proper settings for “add comments” and “add notes/tags/people” that I’ve set on the Flickr site.

Thank you for producing this wonderful plugin.

I just did a test… uploaded a private image, then checked the owner settings, and they’re at the defaults (anyone can comment). I then tried setting the Flickr default-upload-privacy to “Only you” and repeated the test, with the same results. So perhaps it’s a bug with Flicker and/or the plugin, or perhaps some kind of account setting or interaction we’re not thinking of. Perhaps try futzing around with things to see whether you can’t understand it? It seems to be working for me. —Jeffrey

— comment by Jon R on June 8th, 2012 at 1:22pm JST (11 years, 9 months ago) comment permalink


How do I add photos to groups via keywords? I can’t find it documented anywhere. Thanks. I tried simply adding keywords matching the group names before publishing, but that didn’t work.

I know you can specify groups in in the “Edit Flickr Publish Collection…” dialogue but that would assume that all photos in a collection should be added to a group, and in my case I only want to add a few. How would you recommend accomplishing that? Thanks.


Via a smart collection in the publish service. —Jeffrey

— comment by Andreas on June 9th, 2012 at 6:06am JST (11 years, 9 months ago) comment permalink

very great plugin !

just synced mt flickr account with lightroom and all my 1728 pics are ok in the flickr photostream of Jf Flickr Plugin.

But is there some way to get them right back in their album names without having to create each albums one by one ? I would like to get the Flickr Sets/Albums structure in Lightroom after the sync.

Now i just have a bunch of 1728 pics unordered 🙂

any idea ? 🙂


I didn’t (yet) build a full replication thing because the “association” stuff is so fragile. I figured most people create collections for their sets/groups going forward, but I suppose that should be revisited. —Jeffrey

— comment by eric ramahatra on June 12th, 2012 at 1:09am JST (11 years, 9 months ago) comment permalink


I love this plugin and have been using it for quite a while. I recently picked up a 5D MKII and I can’t seem to figure out how to strip some of the EXIF data like my camera’s serial # (I’m paranoid, I don’t want to go posting my serial # all over flickr) without also stripping necessary info like camera orientation so flickr can rotate photos properly. Both of these, along with a ton of other data I don’t think needs to be exposed, seem to be under “MakerNotes block”. Is there a way to further drill into this and selectively choose what to export?

No, ExifTool doesn’t allow breaking up the MakerNotes section. However, you certainly don’t need the camera orientation data for stuff exported from Lightroom… Lightroom spits it out correctly (assuming you see it in Lightroom correctly, of course). I always strip the MakerNotes section when I export for upload. —Jeffrey

— comment by Mark on June 15th, 2012 at 5:02pm JST (11 years, 9 months ago) comment permalink

Dear Jeffrey, thank you very much for everything you do! You – the best! A low bow to you. Special thanks for the update 20120616,278. I wish you health!

— comment by Newsky on June 19th, 2012 at 2:54am JST (11 years, 9 months ago) comment permalink

Hum, I have all my flickr albums and groups mapped to export collections in the flickr exporter, and when I change things, I just go to the root collection group and click “publish” which will see for all published collections if there are things to do.
Now, some groups I joined to limit the number of pictures I can upload every day, and when I put more pictures in one that I’m allowed for the day, the plugin borks out with an error (which is understandable). It would be nice if the plugin would treat it as a soft error when doing batch publishing and continue to the next collection instead of stoping the whole process. That is, if you can find out wether you’re only publishing this collection or a group of them.
Thanks 🙂

Mathieu, from Paris, France…

— comment by Mathieu Arnold on July 4th, 2012 at 5:22pm JST (11 years, 8 months ago) comment permalink

Is there a way that JUST a metadata change in LR can force an update of JUST metadata on flickr rather than an entire republish? Or is that a limitation of the flickr API?

When updating the meta data on a photo such as adding a new caption after it was already published it triggers a re-publish. However, when it republishes it ends up changing the img src location on flickr’s side (the direct image URL for embedding in other sites) while keeping the photo URL the same.

Using LR4.1

You can update only metadata via File > Plugin Extras > Flickr Extras. —Jeffrey

— comment by Chris on July 20th, 2012 at 11:28pm JST (11 years, 8 months ago) comment permalink

I’ve tried changing the resize settings for flickr publishing but when I marked a couple of photos to republish and published it completed almost immediately and didn’t upload the new sized image. How can I fix this?

This is an unfortunate side effect of how I shoehorned the Flickr experience into the horribly-rigid Lightroom Publish infrastructure… you actually have to make a develop change in an image to get it to republish. Even the most minute change (e.g. Color noise reduction from 25 to 26) will work, but something is required. It’s really unnatural, and I’m still trying to think of a way around it. —Jeffrey

— comment by Dave Townsend on July 24th, 2012 at 4:18am JST (11 years, 7 months ago) comment permalink

Where are the custom Title and Caption presets stored please? I store Lightroom on a removable drive so I can share between my desktop and laptop, but my laptop doesn’t see the Title and Caption as configured on the desktop. Thanks.

They’re stored in your Lightroom preferences file. This FAQ has a link that mentions where they are. —Jeffrey

— comment by mallchin on August 6th, 2012 at 6:16pm JST (11 years, 7 months ago) comment permalink

Hi Jeffrey! Writing from Los Angeles…big fan of your Lightroom plugins! I prefer them over the Adobe publishing services. Anyway, I recently upgraded to LR4 and re-registered some of your plug ins. My question has to do with the Flickr plug in. I created a smart publish collection under your flick plug in. The collection is an existing album on flickr with 242 photos. When I created the parameters of the collection it loaded the 242 images into the smart collection as “new photos to publish”. I do not want to publish these photos as they are already on flickr and I cannot find the “mark as published” command in LR4…any help would be appreciated.

“Mark as published” appears only once it’s already been published once, as far as the publish service is concerned. This is a fairly fragile/kludgy area, but in general, once the images are in the publish service, you’ll want to claim the Flickr versions for the publish service (if they’re already associated; if not, you’ll have to associate them first, also covered at that link). This will get them into the “Photostream” collection under “Modified Photos to Re-Publish” where you can then “Mark as published”. Finally, you can then do a normal “Publish” of the smart collection, which will end doing the minor action of confirming set/group membership of the images as per the collection settings. Phew! Much more complex than it needs to be, but there are unfortunate limits to Lightroom’s publish infrastructure. —Jeffrey

— comment by Noel Kleinman on August 8th, 2012 at 2:20am JST (11 years, 7 months ago) comment permalink

Hi Jeff:

Sometimes I need to upload a large number of photos, and some of them have encoding or other errors (my new D800 is producing a few of them), and the plugin stops when it encounters an error in the photo file. Is there a way to “skip” such files and report them at the end with an option to save to file (just as LightRoom does un imports)?



I don’t think so… it sounds like those error are coming from Lightroom itself, and if it’s a substantially-unexpected error, it’ll just bail. The plugin does the same for really unexpected things. —Jeffrey

— comment by Ravi Dattatreya on August 10th, 2012 at 10:48pm JST (11 years, 7 months ago) comment permalink


The plugin (most of the time) works fine . I have a few suggestions though:
* On error the complete upload stops, it would be nice if only the current photo’s is skipped and the upload continues; a retry after the upload is finished would be nice.

* Import sets and collections already present on Flickr into lightroom which are uploaded to flicker with a programm other than lightroom.



It depends on what kind of error it hits… some errors cause a retry, but other errors it makes no sense to retry (such as, for example, the lack of authorization at Flickr). Yet other errors are sufficiently unexpected that Lightroom or the plugin just throws its hands up and bails. I can work to have the plugin handle some of those more gracefully, but it’s already a challenge just trying to keep the plugin working reasonable when everything else is working reasonable, so bailing on unexpected errors is the easy way out, one I usually have to take. —Jeffrey

— comment by Ad on August 12th, 2012 at 3:10am JST (11 years, 7 months ago) comment permalink

Would it be possible to just add an option to the flickr extras dialog to re-send the image, like you already have for re-send metadata in order to force upload images after you make changes to scaling or something?

Not easily. Publish is a huge can of worms, made all the worse by how inappropriate the initial approach I took with the plugin was to how the Publish infrastructure worked out. )-: —Jeffrey

— comment by Dave Townsend on August 16th, 2012 at 4:53am JST (11 years, 7 months ago) comment permalink

I decided to try experimenting with using export to flick to update the image of something already published. In the export settings I chose “Replace the most-recent previously-uploaded copy”. Although that setting claimed to ignore the upload destination, it still added it to the set selected, but no big deal. This seemed to work and allow me to change the image sizes at will! Sort of.

For some reason for a lot of the older photos I tried it out on it worked perfectly, a newly-sized version of the picture showed up in place of the old one at flickr. For newer photos however it just uploaded a new photo at flickr leaving the old one there (and of course not carrying over comments etc.).

I’m not sure why this happened, in both cases they were photos already published using this plugin, both have “yes” in the “Uploaded to Flickr” metadata. Even when looking in the export settings for one of the new photos it looks like it knows it has been uploaded before (the “New” radio said 0).

Could this be to do with me using the built-in LR publish service in the past for my older photos? I imported them all to your plugin but I wonder if those published with LR re the ones behaving differently to the newer ones. Unfortunately I can’t remember when I switched to be able to test that.

I’m at a loss to explain that, though your idea about a difference between “imported into Publish” and “originally Published” may bear fruit, but the two *should* work together just fine. I’ll have to dig. —Jeffrey

— comment by Dave Townsend on August 16th, 2012 at 6:16am JST (11 years, 7 months ago) comment permalink

Silly me. I can indeed find which ones were uploaded by your publish service and which by something else by looking at the “Uploaded by” on the flickr page. And it looks like I was right, the last photo I have on flickr that wasn’t uploaded by this publish service gets replaced just fine by my export preset, the next one gets duplicated. Sounds like an odd bug to me, I’m sure very few people try to do this.

Don’t know if it is any use, but in the metadata for Flickr Upload Date, stuff uploaded before I switched has an abbreviated month, stuff after has the full month.

— comment by Dave Townsend on August 16th, 2012 at 6:26am JST (11 years, 7 months ago) comment permalink

Getting a lot of timeouts trying to upload large batches of photos, any way you could make the plugin wait a bit and just try again automatically? I normally average around 10 uploads before it fails and when you’re trying to upload a few hundred that means a lot of babysitting.

Also as far as I can tell when the upload batch fails it leaves rendered copies of the photos in the temp folder that never go away, my hard disk ran out of space last night because of it.

The plugin should retry on a timeout, up to 10 times… is it not? As for the temp folder, I’ve been asking Adobe about that since Lr1… there’s nothing the plugin can do about that. )-: —Jeffrey

— comment by Dave Townsend on August 19th, 2012 at 12:50am JST (11 years, 7 months ago) comment permalink

Hi Jeffrey,
Thanks for the great plugins!
Question re the Flickr plugin. I’m using v20120723.208 with LR 4.1 and a Flickr Pro account.
I have a number of JPG images in a Flickr collection within the plugin.
I’ve revisited my post production on some of these, and wish to republish the updated images. No problem. In some cases, my post-production has involved Topaz Adjust where that plugin creates a TIF copy of my LR edited JPG and applies the Topaz effects to this TIF. Is there a way that I can tell the plugin that I want it to replace file X.JPG with the latest version which is now X.TIF?

Not easily, but this might work: visit the Flickr Extras dialog to “Clear” the JPG from any Flickr association, then “Manually Associate” the TIF with the same Flickr URL that the JPG had. Then back in the Publish Service dialog, try the “claim” step to incorporate the TIF back into Publish. —Jeffrey

— comment by Steve Oldham on August 24th, 2012 at 3:36am JST (11 years, 6 months ago) comment permalink

hi, nice nice plugin but my english is terrible. i get not work the watermark in the plugin-settings. the watermark will not appear in the images, that i uploaded to flickr (pro account). i hope you understand me. 🙁


Check the File Format… make sure it’s not “Original”. —Jeffrey

— comment by Pandrag on September 7th, 2012 at 12:09am JST (11 years, 6 months ago) comment permalink

Amazing plugins, Jeffrey. Just amazing. And much appreciated.

My question is about image privacy. I generally publish without privacy, but sometimes I want to restrict and image to family or family and friends only. Is there a way to set this by image before I export, and if not, is there a way, once I have exported the image with the plugin and then manually changed privacy on Flickr, to prevent Flickr from changing it back to public when the image is otherwise updated using the plugin?

The keyword-based settings in the “Flickr: Metadata Management” section of the dialog were created just for this kind of situation. —Jeffrey

— comment by Rob Hyndman on September 22nd, 2012 at 7:31pm JST (11 years, 5 months ago) comment permalink

Hi Jeffrey. First, your plugin is just Great ; many thanks for it !

I am now using the LR 4.2 Watermark tool. It works fine for the new photos but not for the ones already on Flickr when I ask to republish them. Is it normal?

Second question, I would be interested in a feature that could allow to disable the watermarking when there is a specific keyword in the metadata. I would use it to not watermarking my private photos I share with family/friends. Do you think such an evolution would be possible?


There’s an “issue” with my plugin such that photos require actual pixel changes before a republish actually republishes. It’s an unfortunate side effect of shoehorning the Flickr stream/sets/group paradigm into Lightroom’s inflexible category Publish paradigm. As for the the second item, that’s not something that Lightroom allows plugins to do. —Jeffrey

— comment by Greg on October 7th, 2012 at 1:26am JST (11 years, 5 months ago) comment permalink

Is there a way to identify photos in the Lightroom catalog that are not also at flickr? I recently matched up my LR with my flickr set, but I realise now I want to clean out a lot of dud images that I have never published. A Library Filter that excludes published pics would be great place to start but I can’t see how to do that easily.

Choose “Uploaded to Flickr” in the Metadata section of the Library Filter, then choose “No”. —Jeffrey

— comment by Stefan M on October 9th, 2012 at 5:03pm JST (11 years, 5 months ago) comment permalink

Hi Jeffrey,

Out of the blue, I started to get an error with uploading to Flickr. It starts preparing for export and a dialog box pops up that says: “Error during export. No reply from Flickr.” This was happening with Lightroom 4.1 but I upgraded to Lightroom 4.2 and also the latest version of your plug-in manager 20121009.284 and the problem persists. The regular flickr plug-in still seems to operate fine.

Any ideas? Thanks.

— comment by Gordon Haff on October 13th, 2012 at 1:00pm JST (11 years, 5 months ago) comment permalink

I appear to have found the cause of the issue I reported earlier. I was renaming the filename to the file’s title during publishing. It appears as if Flickr’s API has decided to intermittently fail if the filename has an apostrophe in it.

Thanks for sending the log… it helped. I don’t know what causes the error, but I have been able to work around it, so if you upgrade to v.286 or later, it should work. —Jeffrey

— comment by Gordon Haff on October 16th, 2012 at 6:24am JST (11 years, 5 months ago) comment permalink

Possible new feature: Stripping keywords that set parameters. For example, I add the keyword #LOC to photos when I want geotag info (location) to be public. It doesn’t mean anything else to the photo, and it’s not important to Flickr or its search engines. I’d just as soon it not be displayed, if possible.

Lightroom allows you to mark each keyword for export or not. Right click on the name in the “Keyword List” in Library and edit its properties to remove “include on export”. —Jeffrey

— comment by Brent on October 17th, 2012 at 1:24am JST (11 years, 5 months ago) comment permalink

This is really more a suggestion for a feature rather than a bug report and I think it would apply to all export plugins. I like to tag my images with “Flickr”, “Tumblr”, Website”, etc when I’ve exported them to those locations. I would love it if a user defined tag (or even a fixed one) could be automatically added on export. If this could be done, adding the tag after export rather than before means the tag will not show up on the list of tags on that particular site. Hmm, or maybe it would be easy to exclude this set of tags using the Metadata Wrangler?

The plugin already sets metdata for the image indicating whether the image has been uploaded… you can see this in the Library Grid Filter (under Metadata), and in the “All Plugin Metadata” selection in Library’s Metadata Panel. But if you really do want to add keywords, you can do so through my snapshot-on-export plugin (though the Flickr plugin already includes the snapshot functionality). You can mark keywords to not be exported… see this comment. —Jeffrey

— comment by Larry Williamson on October 17th, 2012 at 5:32am JST (11 years, 5 months ago) comment permalink

Hi Jeffrey – quick question. IR