Jeffrey’s “Export to Zenfolio” Lightroom Plugin

This plugin allows you to export images from Lightroom directly to your Zenfolio account.

This plugin works in Lightroom 6/CC (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 or later, there is full support for Lightroom's new Publish feature. See the manual for Publish to Zenfolio 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 Lr5 to Lr6, 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 )


When running into issues with Zenfolio, present more info that can be passed along to their support staff.


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


When running into errors at Zenfolio, present some info that can be passed along to Zenfolio support.

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


Yikes, previous "fix" made some uploads fail.


Track changes in Zenfolio's third-party API.


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.

Switch the log-sending mechanism to https.


When Zenfolio is having issues, try to report that more clearly.


Publish deletes were getting hung up.


If Zenfolio's servers had a meltdown and returned to the plugin a web page instead of the requested data, displaying the web-page code as the error message could cause Lightroom to crash, so don't do that anymore.

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

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.


Still battling some insidious errors hiding in there.


Try to get around some publish-collection corruption I've seen popping up.


Fixed the album-creation problem.


Added some debug logging to track down an album-creation problem.


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, {FilenameNumber}.

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

Added the ability to repopulate smart collections.

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

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


Allow for username changes at Zenfolio. Also make sure that the "view at Zenfolio" link is correct for each published collection.

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.

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


Update the status messages presented when creating a group from the Tools section of the dialog, to actually use the word "group" instead of "gallery".


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.

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


Added the ability to have collections named just for the leaf album name at Zenfolio, rather than with the full hierarchical name.


Zenfolio changed how some of their back-end stuff works, and so the plugin needs to update Publish Services to match. This one-time change is done automatically the first time you edit a publish service, and should be invisible unless you have a lot of collections, in which case a dialog may pop up letting you know what's going on....

Don't report as an error if the network is down and you're just viewing a Publish Collection. When you view a collection, Lightroom asks the plugin whether the remote service is up, so as to make the comment-input box available or not. The plugin used to report a "retrying..." error if the network was down, but it should just do its check quietly in the background, so now it does.


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

Try harder to detect when Zenfolio is down for maintenance and report that instead of a generic error.


Video upload was broken for some users.

UI fix for OSX 10.9


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


Adding the raw-upgrade option in the previous version caused a side effect of breaking most everything else for certain users. )-:

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.


Add the ability to upload the master original along with an exported copy.

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.


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.


Unlucky timing during an upload could cause an "Unexpected HTTP reply" error.

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... it seems arbitrary.

Add a help dialog to the publish-services edit dialog to make it clear how to delete a publish-services collection.

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

When associating a previously-uploaded image to an entry in Lightroom, note the actual upload time (instead of the time the association was made) in the "Uploaded to Zenfolio" metadata.

Registration was broken on Lr2.


Plugin could block export with a "tweet text too long" even if the Twitter option was disabled.


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.267 Windows Only: Add a one-time check for the POODLE security vulnerability, and alert the user if it exists.
20141010.266 Better error reporting with the visit-collection item in Publish.
20140923.265 Added the LrMD5, LrLocalization, LrSystemInfo, and LrMath packages to the {LUA} template token.
20140922.264 When deleting from a publish collection, properly maintain the 'Uploaded to...' metadata field.
20140917.263 If we've got to bail on an upload due to a too-long title or the like, do so before the pixels are uploaded to avoid leaving an orphan at Zenfolio.
20140902.262 New build system

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

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

20140731.260 Registration fix for Lr5.6
20140731.259 Added some debugging to track down some registration issues.
20140729.258 Previous updates broke support on Lightroom 2
20140720.257 More Creative-Cloud support.

Fixed an issue with Creative-Cloud revalidation.


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

20140710.254 Sigh, had a bug in the Creative-Cloud support.
20140709.253 Oops, restore the create-a-gallery menu item lost in a recent update

Now supports Lr5.5+ Creative-Cloud Installs.

20140704.251 Sigh, introduced an error for some folks with the rebuild the other day.
20140630.250 Build-system update

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 Zenfolio account from the Publishing Manager dialog.

20140510.247 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, Location, CatalogName, CatalogPath, OperatingSystem, OS

Added new token filters: NS and LO


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


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

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.

Added the "Recent Zenfolio 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 Zenfolio 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.

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


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.


A complete overhaul of the "Associate Images Automatically" code (in File > Plugin Extras > Zenfolio Extras). It's still a fragile process, but it might work a bit better now.


Added (to File > 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 keywords to the list of metadata that can be imported back from Zenfolio.

20131011.240 Gave the Publishing Manager UI some attention on Windows.

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

20130926.238 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 and captions from Zenfolio back into Lightroom.


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. Moved to a more logical place in the dialog.

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

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


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

20130629.232 Added an error report to aid in debugging why publish association might fail.
20130613.231 Better support for plugin revalidation.
20130612.230 Creating a new publish album could sometimes fail
20130611.229 Sigh, previous update for Lr5 broke things for the Lr5 beta.
20130611.228 Yet another Lr5 update
20130610.227 Better logging to try to understand catalog-write-access contention under Lighroom's hood
20130524.226 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.

20130511.224 When creating a publish collection from the context menu, respect the publish service's flat vs. hierarchial naming setting.
20130501.223 Update for Lr5
20130412.222 Fix to the Twitter fix.

Can now have Publish collections renamed to match album names changed at Zenfolio.

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.220 Fix for the registration system.

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.

20130311.218 Try to address a gallery-sorting bug.

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.216 Small fix for Lr2
20130209.215 Update to handle new Twitter url-length settings.
20130206.214 Update the Twitter-related code to handle their new API. Their old API goes away next month.

Update to reflect Zenfolio's video-length limit of 20 minutes (it had been 15).

Abort on an attempt to create a gallery with a name more than Zenfolio's limit of 200 characters long.

20130119.211 Added the ability to set the gallery cover photo via Lightroom keyword.

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 to Zenfolio), and you must create the destination presets from Export, but you can now access them in Publish.

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

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.

20121203.208 Add a link to the FAQ for the "missing destination cookies" error.
20121109.207 Note when Zenfolio is down for system maintenance.
20121030.206 Could run into catalog contention while fetching new comments.
20121020.205 A recent optimization for Lr4 broke support for Lr2.
20121017.204 Plugin was blocking export due to DPX-video format in some cases where Lightroom didn't allow the format to be changed.
20121014.203 Added a help dialog when encountering the mysterious 'handle in the wrong state' error.
20121010.202 Fixed Twitter authentication.

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

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

Disallow DPX-format video export, since that totally breaks things.

20121002.200 Fixed some UI-cuttoff in the Publish upload-destination dialog section, on Windows.

Added the ability to create new galleries directly from the Publish Service context menu.

Disable the "Also automatically add as collection" checkbox in the Publish-Dialog "Zenfolio Tools" section, when the type of thing being created is a group instead of a gallery. You can't publish to groups.


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.


Responding to further Zenfolio error-message changes.


Fixed a resend-keyword bug.


Zenfolio seems to be changing how they report errors, so this update tries to respond in kind, as far as I can tell.


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.

Oops, a side-effect of recent changes caused the log to bloat with a binary dump of exported images. Fixed.


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

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

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 your Zenfolio account maximum.

With Lr4.1 and later, you also get an upload percent-complete report in the task progress bar, and the ability for upload cancels to take effect immediately.

Update to handle the Mac App Store version of Lightroom.

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


Fixed a potential crash when processing some captions.


Handle a change to Zenfolio's API. According to Zenfolio, earlier versions of the plugin will cease to work on July 1, 2012.

Add the ability to reauthenticate Zenfolio credentials from within a publish service.

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

20120418.186 (this version had an assert in Publish)
20120417.185 (this version had a "This file format is not supported or the file is corrupt." bug")
20120330.184 Update to handle 4.1RC
20120327.183 More graceful handling of videos whose pixel size is not known.
20120309.182 Had broken registrations in Lr2; Update to the debug logging to better track down timing issues that might arise.
20120303.181 One more update with the large-upload thing.
20120302.180 The recently-added "Lightroom doesn't handle large uploads well" check/dialog didn't play nice. Does now.
20120301.179 Oops, broke new logins in the previous big update... doh! Sorry. Fixed.

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.

20120218.177 Zenfolio seems to have changed how they handle image deletion... not sure whether they're having issues or it's an intentional change, but the plugin now handles it gracefully.

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

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

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

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.

20120114.175 More tweaks for Lr4b

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.

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


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

Enabled export snapshot creation in Publish.


Zenfolio added video-upload support today, so I've updated the plugin to allow video.

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.


Updated how the Manual-association dialog is sized.

Had issues with the registration button sometimes not showing.


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.

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

Added some debug logging to try to track down a sizing problem with the manual-association dialog.


Include the account id (in addition to the full name that's already there) in the Publishing Manager login section, to allow multiple accounts associated with the same real name to be easily differentiated.

Also report how much storage quota is remaining, if on exists.

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.

Gracefully report when Zenfolio replies with a "storage quota exceeded" error.

20111010.169 Added the ability to resend copyright when resending metadata.
20111008.168 Publish repopulation could fail with write-gate timeouts.
20111004.167 Plugin would crash in some cases while trying to process Twitter-related settings.
20110918.166 Now I'm seeing "Server Error" responses, so trying to handle that more gracefully as well.
20110914.165 Zenfolio seems to be having a spate of "service is unavailable" errors, which the plugin wasn't handling well. Now these errors are reported more clearly when the plugin encounters them.

Handle errors more gracefully when attempting to update online comments for photos that no longer exist.

Better general debug logging to help track down errors when reported.

20110903.163 Added {PluginProperty} to the template tokens used by my plugins.

Some internal optimizations to handle large number of sets.


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.

Gracefully handle when Zenfolio rejects HTML captions with a non-validation error.

20110814.158 The "resend metadata" operation, if not resending all data, could cause unsent fields to be wiped out at Zenfolio.
20110807.157 Fixed "attempt to compare nil with number" error that some users might have gotten in Publish.

Better reporting of networking timeouts.

The 'refresh list' button was missing from the upload-destination list when it was configured to be a popup menu.

20110712.155 Had a minor plugin-crashing boo-boo in the previous update
20110711.154 Really long captions could cause a stack overflow.
20110708.153 Fix the "Export:663" error some have gotten.
20110706.152 Still struggling with catalog-access issues that seemed to have materialized out of the blue (with a bug in Lr3.4??). This update addresses creating a new publish collection.

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

More on the catalog-access errors that some are getting with Lr3.

20110703.150 For Lr2, fixes a 'must be called inside withReadAccessDo' error I'd recently introduced. For Lr3, tries to address a similar error that seems to pop up in rare cases.
20110624.149 Present a better error message if image metadata (title, caption, etc.) exceeds Zenfolio limits.

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.

20110614.147 Fixed the “Associate Images Manually“ functionality. Tweaked the authentication stuff to avoid having to re-upload the first image after a long absence by pre-testing the cached authentication token, and refreshing it if need be.
20110611.146 Workaround for a problem one user experienced.
20110607.144 Due to a mistake on my part, the plugin started building invalid urls for galleries at Zenfolio. This version of the plugin fixes it, but to make it manifest, you've got to click the "refresh list" button next to the list of galleries (in either the Export Dialog or the Publishing-Manager Dialog).

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


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 Zenfolio back into Lightroom) automatically or only manually.

Fixed an obscure bug that caused new album creation to fail if it's your first interaction with the plugin in more than a day.


It seems Zenfolio dropped (or never had?) support for Width-related gallery sorting, so I've dropped that option.

Be more robust to errors during the gallery-creation process. Added more logging to try to debug a gallery-creation error.

20110511.139 Yikes, when I upgraded to a new Zenfolio API in March, I broke the image-association feature. Sorry. Fixed.
20110426.138 Fixed a bug in how some export errors are reported.
20110419.137 Wasn't properly issuing an error message when used with Lr3.0 and Lr3.2.

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

Added "select all" button to Publish collection list.

20110329.135 Oops, the button to refresh the list of galleries had inadvertently disappeared.

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

Added the ability to sort the album list in the Publishing Manger

Previous build was broken under Lr2, and some Lr3 installs.


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

Added the ability to create new Zenfolio galleries from within the publish manager.

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.

Fixed a bug whereby one couldn't export via preset to an account different from the currently-logged in account.

The list of upload destinations was sometimes getting cut off.

Internally, upgraded to the latest Zenfolio API.

20110125.132 Some ares of the code that talked to Zenfolio didn't properly handle reauthentication requests, but I think I've caught them all now.

Added “Re-Mark as Published” to the Plugin-Extras dialog (“File > Plugin Extras > Zenfolio 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 Zenfolio. 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 Zenfolio.

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.130 Added Twitter support to Publish.

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

Added {CroppedWidth} and {CroppedHeight} to the template tokens used by my plugins.

Add a note of instruction to handle a (rare) situation where one needs to reauthenticate in the normal Export Dialog in order to get a Publish Service working again.

20101217.128 Updated Twitter support for Twitter's new API endpoints

Fixed a crash sometimes encountered while updating remote-account data in the plugin, fixing correctly the fix I added incorrectly in 20101112.125.


Check whether galleries at Zenfolio have been renamed from when publish-service collections were created, and prompt the user with a note that the renaming can be incorporated into Lightroom by enabling the “Forcefully rename current collections” option.

Replaced an ugly debug message that popped up when the plugin detected that a publish-service collection's related gallery at Zenfolio has been removed from Zenfolio, with a more user-friendly message.

20101112.125 Some users were suddenly getting an “Assertion failed(!)” error (it would happen in some situations when the internal Zenfolio access token would time out and the plugin would need to reauthenticate on your behalf). I haven't been able to reproduce the error myself, but this should fix it.

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. Not sure why I might have built it that way, but I took off the time limit so now it shouldn't get stuck anymore. Wish I understood why I'd put it in in the first place, though. )-:

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

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

20100829.123 Made the revalidation process much simpler, doing away with the silly need for a revalidation file.
20100820.122 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 an interactive filter to the gallery list in Publish; it'll show up if there are more than 10 galleries. Only galleries whose names match all the (space-separated) terms in the filter are shown.

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


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% 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.119 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.118 Yikes, the JPEG-quality thing I added didn't play well with Publish. Removing it from Publish 'till I figure out a better way.

Egads, the list of albums in the Publish Service dialog was not sorted.

Did a lot of work to revamp the ability to tie in photos already at Zenfolio into your Lightroom catalog (and hence to populate a Zenfolio publish service), working around bugs in Lightroom. See the new publish docs for details.

The plugin has long remembered your export settings from Zenfolio export session to Zenfolio export session, overriding Lightroom's desire to always bring your recent export settings from non-Zenfolio 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.

Clarified that the “delete all copies previously uploaded” option applies to, well, all copies previously uploaded, as opposed to some magic subset of copies previously uploaded that you might have fixed in mind.

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.


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:

20100614.107 — This version can be registered in Lightroom 3. It can run in Lightroom 2 or Lightroom 3; it does not work in the Lr3 betas.

It uses my new registration system when run on Lightroom 3, which avoids some of the silly issues of the old one. Please take care to note the details on the registration page: use of this version (or later) of the plugin in Lightroom 3 requires a new registration code, even if you had registered some older version of the plugin.

This version has no Publish support... I hope to push that out soon, but I wanted to get out something that works in Lr3 ASAP.

Many, many changes under the hood.

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

20100624.108 — Discovered a nasty build bug; pushing a new version in case it affects this plugin.

20100625.109 — Yikes, shaking out some more build issues.

20100627.110 — Giving publish for Zenfolio a try.

20100628.111 — Had broken auto destinations.

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

20100629.113 — Lots of changes. Bolstered the separation between Publish and non-Publish exports. You can now publish comments.

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


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.

Added new tokens to the templates used in my plugins: IfKeyword and IfExportedKeyword are supported for LR2 and later. For LR3b1 and later the very powerful LUA token, and for LR3b2 and later, a bunch of new localized date/time tokens. 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.


Title presets weren't getting saved across LR restarts in some cases (for definitions of “some” meaning “all”, sorry).

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.


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.

Caught a few more LR3b issues.

Fixed the {GPSAltitude} template token so that it should now actually work.

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.

Lots of updates to the Twitter support:

  • Better tweet-size estimates in line with recent processing changes at Twitter.
  • Added <title> and <caption> tags to the tweet-text template (they use the title/caption from the first image exported).
  • Added the ability to control whether to send a Twitter tweet with photo keywords.
  • 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.

20100118.102 Added two new template tokens, {DaysSince} and {PhotoDaysSince}. They're a bit tricky, but could be useful.
20091230.101 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.100 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 Zenfolio' item) a few versions back. This should fix it, at least for images uploaded from now. There are some more updates for Publish in LR3b, but it's very much a work in progress.
20091222.99 Fixed some issues with the metadata resend (in the Plugin-Extras dialog) when images had been exported to multiple Zenfolio accounts.
20091216.98 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.97 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.
20091215.96 Debugging-log tweak.
20091214.95 Added the special {NOJOINERS} token to the Template Language understood by my plugins.
20091209.94 A few small fixes for LR3b, and tweaks to the extra-keywords stuff do tidy up repeated keywords in the display.
20091205.93 Minor internal debugging tweaks.
20091118.92 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.
20091118.91 Added the ability to resend keywords/captions/titles via the File > Plugin Extras > Zenfolio Extras dialog.
20091023.90 A bunch of UI fixes for LR3b, such as fixing the scrollbar and the token-examples dialog.
20091022.89 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.
20090916.88 Some UI tweaks earlier in the month had an unintended side effect of breaking the “choose destination at export time” feature. Sorry... fixed! Also, added some prose to make it more clear that the “create gallery” part of the choose-destination-at-export-time dialog is not part of the export process, but merely a tool placed there for the convenience of those wishing to create a new gallery just prior to exporting.
20090915.87 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.)
20090716.86 Sigh, Twitter engineers treat developers like a bunch of twits. Twitter just made a sudden, unannounced, and 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... are there kids 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.

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.

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.

20090616.83 Sigh, this upload-destination fiasco is a real pain. Maybe have it nailed down this time.
20090615.82 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.

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.

20090605.80 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-Zenfolio data via the Zenfolio-Extras menu.

Fixed the urls in Twitter tweets to be the public version of the url, not the private owner's version.

Added a couple of new custom metadata fields, “Zenfolio 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 Zenfolio.

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”). Then a progress bar will show up and, if you have a lot of photos in your catalog that had been uploaded to Zenfolio, will just sit there for potentially several minutes, looking stuck. Just let it work. For my catalog with 48,000 photos, it took about 5 minutes.

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.zenfolio2.uploadDate and ....uploadTime.


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

Fixed a “loadstring” error some users got.

You can now use the scroll wheel with the scrollable lists (such as for the gallery list)... 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.

20090519.75 Fixed an album-creation bug I introduced in a previous version.
20090518.74 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.
20090510.73 Added a link in the Plugin Manager to the plugin's update-log RSS feed.

Added items to the title/description presets: SmugMugUrl, FlickrUrl, 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. {FlickrUrl}, 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 {FlickrUrl=photo at Flickr}.


    See the <a href='...'>photo at Flickr</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 {FlickrUrl=photo at Flickr|"photo at <a href=''>my Flickr 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 Flickr 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 Flickr site</a>.
20090429.71 Fixed a bug that could potentially crashed the plugin while editing caption/title and auto-destination presets.
20090425.70 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.69 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.68 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.

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


Turns out that there's a bug in Lightroom that causes login names to be rejected if they can't actually fit in the input box that's presented when trying to log into a second account. To get around this bug for the few who run into it, I've made the box as wide as I can... I hope it's sufficient.


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.

It now reports a proper error if you try to upload an image with a copyright that's longer than Zenfolio's 100-character limit. I really should do this in a pre-export scan so that it's issued right away (prior to LR rendering all the images), but I doubt many will actually run into this, so I'll not bother with it for the time being.


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.

20090310.62 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.
20090305.61 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.
20090303.60 If there's an error calculating the automatic destination for a photo, now actually reports that error instead of just crashing
20090302.59 Fixed a bug that could cause the plugin to crash when using the File > Plugin Extras
20090228.58 Updated the caption stuff to handle newlines and <br> better. Also fixed a bug that caused a plugin crash if my server couldn't be reached during registration.

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 Zenfolio logins, 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. Also, caption handling has been fixed... it use to break when there were ampersands in the caption.

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

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.

20090116.53 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.52 Added more debugging-log stuff to the 'Upgrade Now' button action, to try to understand why it doesn't work for some people.
20090115.51 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.50 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.49 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.48 The “Extras” item in the File menu had stopped working. Works now.
20081223.47 Bumping back the expiration date.
20081208.46 Fixed a problem that sometimes caused errors during login/authentication, or after logging out.
20081204.45 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.
20081127.44 The counting of previous uploads (for the All/Update/New of the Upload Destination section) was not working right.
20081125.43 Another fix for a bug that had disabled plugin presets (for captions, etc.)
20081124.42 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.41 Fixed a plugin crash when using the plugin's built-in preset system.
20081122.40 No problems from the upheaval recently, so pushing back the expiration a bit.
20081117.39 Oops, wouldn't let you log in / authenticate if you weren't already. Doh. Fixed.
20081117.38 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.37 Fixed yet another list-of-upload-destinations bug. There are sure a lot of edge cases here.
20081111.36 Fixed a crash that happened sometimes when there are not yet any preexisting destinations at Zenfolio.
20081104.35 Perhaps squelch a spurious error dialog
20081103.34 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.33 Now works properly with the shadow GPS data maintained by my geoencoding plugin.
20081024.32 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.31 Addressed (and perhaps even fixed) a bug introduced in the previous build.
20081021.30 Small update so that a stuck background version check does not disable the plugin. 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.29 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(?)

I created a “Metadata Management” section in the dialog, and moved some things into that from other sections.

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 Zenfolio was no longer present at Zenfolio. 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.27 Sigh, just realized that the “check for new version” stuff did break in 2.1. Totally my fault, sorry. Fixed.
20080921.26 Oops, the ability to use my template tokens in the 'extra keyword/tags' area, that I added last week, didn't actually recompute the tags on a per-image basis, applying the tags computed for the first image to all the others. That's now fixed, and tags are recomputed with each image.
20080920.25 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.24 Added the ability to use template tokens like {Filename} in the “extra tags” input box.
20080916.23 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.22 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.21 Added a few more descriptive tooltips to the example-token dialog
20080914.20 Oops, fixed a boo-boo introduced in the previous version.
20080914.19 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.18 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.17 Fixed an “undefined global: DestinationSynopsis” error that could happen when using a preset with a “select at export time” upload-destination setting
20080831.16 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.15 Added a bunch of new items to the template language.
20080829.14 Oops, left some debugging cruft that results in an “empty” dialog if the logged-in-user has no galleries or the like. Fixed.
20080828.13 Minor tweaks
20080828.12 A few more tweaks to report a failed upgrade attempt a bit more clearly
20080828.11 Whoo-hoo, finally figured out the “assert” problem that some people without galleries 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.10 Fixed the Caption {Filetype} token (was broken for DNGs). Made some Layout tweaks in my preset dialogs. Added titles to the tools sections (were missing on OSX)
20080817.9 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.8 Fixed infinite cycle of 'assert' messages one might get in odd situations
20080812.7 Fixes (I hope) a “bad argument #1 to '?' (table expected, got nil)” error
20080811.6 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.5 Fixed {State} and {Rating} in preset templates.
20080805.4 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.3 Fixed “Access to undefined global: LrError” error that happens when trying to report a login-related problem.
20080804.2 Fixed a couple of internal errors related to the “choose destination at time of export” feature
20080729.1 Initial public release. (The version of this plugin for Lr1 is here; its initial release was “20071121.1”)

The 30 most-recent comments (out of 369; see all), most recent last...

Greetings from North Carolina. My Zenfolio plugin stopped working so I downloaded and installed the new version 20160307.282. When I try to use it, either by publishing new photos, adding a new gallery , removing photos…anything that requires connection between Lightroom and Zenfolio, I get the error that I can’t log in to Zenfolio:invalid credentials. I can login to Zenfolio through their website. I checked the status and the plugin is enabled, but has encountered some problems. I have deleted and removed prior versions and reinstalled and can’t get it working.

Help please. Thanks,
Matthew Kraus

Try logging out from Zenfolio within the plugin (near the top of the Export dialog), then logging back in. —Jeffrey

— comment by Matthew Kraus on June 4th, 2016 at 8:24pm JST (10 months, 21 days ago) comment permalink

My Zenfolio plugin stopped working so I downloaded and installed new version 20160307282. But whenever I try and use it I get the error”can’t log in to Zenfolio:invalid credentials”. I checked the status and “plugin is enabled, but has encountered some problems”.

I have deleted and removed prior versions and reinstalled and still can’t get it working.

When I look at the plugin manager, on the left it lists the Zenfolio plugin and says it is installed, but may mot work.

In the diagnostic message, it says “this plugins post processing task did not finish successfully.”

What am I doing wrong. Please help.


Matthew Kraus

It sounds like you changed your password at Zenfolio. Log out from Zenfolio (in the plugin, at the top of the Export Dialog), then log back in at the same place. —Jeffrey

— comment by Matthew Kraus on June 14th, 2016 at 3:15am JST (10 months, 12 days ago) comment permalink

have not used for a while. Uploaded about 2,000 images and they all published. about 300 had changes so went to section to update. when I click Publish to update photos, i get the following error:

Unexpected HTTP reply from 503

any ideas?



That seems to be what we see when Zenfolio has temporary “issues” with their servers. —Jeffrey

— comment by Clark on June 16th, 2016 at 1:11pm JST (10 months, 9 days ago) comment permalink

Tom from Florida USA. I downloaded the the latest zenfoilio plugin from your website: version 20160715.283 and when I go to install it in Lightroom, I get the message “this Plugin does not work in Lightroom 6 please download the latest version” I run Lightroom CC and just downloaded it from the CC app last night. Please advise why it is not working.


The best I can guess is that after downloading the plugin, you actually tried to install a really old version that was lying around on your system? —Jeffrey

— comment by Tom Mesick on July 22nd, 2016 at 7:25am JST (9 months, 3 days ago) comment permalink

Re Nesting Groups (Collection Sets):

I cannot create a new Collection Set within a Collection Set from within the Zenfolio Publish Service.

I can nest Groups at the Zenfolio site. After Refresh, I get the desired nested Collection Sets in the Publish Service.

Is this normal? Is this OK? Won’t corrupt things down the road?

Your plug-in is fantastic. Thanks so much,

Saul Taylor
Minneapolis, USA

Yes, it’s fine… that’s the way to do it. —Jeffrey

— comment by Saul Taylor on August 7th, 2016 at 9:44am JST (8 months, 18 days ago) comment permalink

Hey Jeffrey,

After years of happy use of your ZF publish collection, it’s become indispensable to my workflow. And right now it’s sadly failing me. I’ve done all the I can think to do, reloading plugin, forcing local gallery renaming, etc., but the publish always fails with “Upload failed: Error 50072”.

Any tips?

Thank you for all your hard work!

It’s probably Zenfolio just having “issues”, but if it continues, try reporting it to them (a message like “Error 50072” almost certainly comes from them, which makes it harder for them to ignore you and tell you to contact me). At the same time, you can send a log for me to look at. —Jeffrey

— comment by Steve on August 23rd, 2016 at 3:17pm JST (8 months, 2 days ago) comment permalink

Yes you where right problem at Zenfolio end now resolved ! 🙂
Thanks for your quick responce

— comment by Alan on August 24th, 2016 at 8:04am JST (8 months, 1 day ago) comment permalink


When I try to upload from Lightroom to my Zenfolio web page I get this message.

“The destination folder for this operation is missing”

I upgraded to the latest version and I still get this message. I have located the “missing” folder on my hard drive with all of the previously loaded pics. Is there an easy way to “reconnect”?

MacBook Pro (Retina, Mid 2012) OS10.11.6 (15G1004)

Plugin: 20160730.288

Lightroom most current CC version

That’s a message from Lightroom. You apparently set things up so that copies created for upload are saved on your system (most folks leave it at the default of “temporary folder” so that the copies created for upload are discarded after upload), and the folder you told Lightroom to use is no longer there. So, you have to either change that setting (to choose “temporary” or pick a new location), or re-place a folder at the original spot. —Jeffrey

— comment by Ed Dunn on September 13th, 2016 at 5:12am JST (7 months, 12 days ago) comment permalink

Jeffrey, can’t find a place to choose “temporary” in the Plug-in Manager window you suggested, above.

It’s in the top section of the Export dialog. —Jeffrey

— comment by Ed Dunn on September 16th, 2016 at 4:05am JST (7 months, 9 days ago) comment permalink

Your plugin is great and I contributed when I downloaded and will so again as it is a real time saver. I am a high end hobbyist and still learning. If I want the jpeg pics that I have in LR to upload to Zenfolio in the highest quality, what settings should I ensure I set? I saw one place where it was set to max of 240 dpi and I changed that to 600. Is that a good number or any other recommendations on settings?

Thank You,
Bret Mason

The DPI setting is irrelevant… just leave the JPEGs un-resized and set the JPEG quality to 80 or 90 (or whatever you want, though see this writeup on JPEG quality settings) before pushing it to 100. —Jeffrey

— comment by Bret Mason on September 30th, 2016 at 1:37am JST (6 months, 26 days ago) comment permalink

How can I delete the Zenfolio plug-in and ALL preferences. I want to reinstall it and make the connection to Zenfolio again from scratch. I have tried removing and reinstalling the module, but some preferences must be elsewhere, because my Zenfolio account name sill shows up when I start to enter my Zenfolio credentials in the plug-in.

I have had all sorts of problems associating/re-associating my Publish collections with Lightroom, perhaps because I changed both my login name (email) AND my Zenfolio page/URLs are now my custom domain, and not [name]

In one gallery, I even manually reassociated the URLs for 53 files and this did not correct the associations in Lightroom. The corresponding gallery in the Publish collection will only show 10 of the 53 images.


Your login data are in the Lightroom preferences file, so clearing them out would do it, though that’s a very big hammer for this small nail. If you want to remove all the upload history as well, select all photos and “File > Plugin Extras > Zenfolio Extras > Clear”, and also delete all the Publish Services. —Jeffrey

— comment by Brett Wickens on October 6th, 2016 at 2:10pm JST (6 months, 19 days ago) comment permalink

Hobart, Tasmania, Australia.

Hi Mate – How do I make a “Smart Collection” in lightroom that only shows images that are currently published onto my Zen Website?

I want a collection that lets me see all published images so I can easily update Caption and title and then republish…

Is there a Metadata field that is only set when the image is on the Zen site, and removed when its no longer published??

Thanks in advance..

Among the smart-collection rules (scroll toward the bottom) is an “Uploaded to Zenfolio” item that’s exactly what you want. —Jeffrey

— comment by Adriaan on October 22nd, 2016 at 10:28am JST (6 months, 3 days ago) comment permalink


Using version 20160730.288. I am now seeing an error message when uploading to Zenfolio.

“Error during export

File size of xxxxx exceeds your Zenfolio subscription plan.

Aborting export before any image was successfully uploaded.”

I don’t understand why I am now seeing this error? I have the Premium plan and have never seen this error before?


That’s an error apparently returned directly from Zenfolio and the plugin is just passing it along. Perhaps it’s due to a momentary hiccup on their side. If it persists, send them a note to inquire. —Jeffrey

— comment by Warren on October 23rd, 2016 at 11:47pm JST (6 months, 2 days ago) comment permalink

Hi Jeff,

In your “Smart Collection” answer, can you indicate what the difference is between “Uploaded to Zenfolio” and “At Zenfolio”?

Secondly, I have several iterations of your Zenfolio Publish Service established in a LR catalog (e.g., Public Galleries and Private Galleries) and within each I have folder structures that are at times 3 or more levels deep (eg, Location -> North America -> Western States -> California -> San Francisco). In a Smart Collection, what is the best way to specify which of the several Zenfolio Publish Services instances it relates to and then within that Publish Service which folder or subfolder it’s in? In some cases the same image appears in several of the PS instances and may also have been uploaded to more than one gallery within that PS instance (e.g., an image may be in the “San Francisco” Gallery but may also be in the “boats” gallery in the same Zf publish service.

So, let’s say I want a Smart Collection to show me images in the “Public Galleries” jf-Zenfolio PS that are in the California folder (or any of it’s subfolders) and were uploaded to that folder more than 1 year ago. How would I do that?

Thanks –Dan

“Uploaded to Zenfolio” is a simple yes/no item. “At Zenfolio” is the URL at Zenfolio of the most-recently uploaded version. About the other question, I don’t think you can do it. Lightroom’s smart-collection rules are woefully deficient in this area, and I don’t know of a way to refer to a collection except by name, and if the name is the same for two collections, both match. One way around it all is to use keywords for everything — Lightroom’s keyword rules are more rich and so you can then use keyword rules to define collections in pretty specific ways. —Jeffrey

— comment by Dan (California) on October 24th, 2016 at 1:06am JST (6 months, 2 days ago) comment permalink

I am writing again as I have not heard back and the problem has gotten worse. Now whenever I am doing exports to Zenfolio, I constantly get “TimedOut” errors. This is causing much frustration. Any insight? Thank you!

If the problem is with Zenfolio, it seems to come and go. Since it’s not doing that with you, I wonder whether there’s something
about your system (your computer, your router, your security apps, your ISP) that might be causing it? The plugin is just reporting the timeout error that it gets from Lightroom, which itself gets it from your OS. —Jeffrey

— comment by David on November 29th, 2016 at 12:12pm JST (4 months, 26 days ago) comment permalink

I believe that David’s problem with timeout errors is a Zenfolio problem. I get it from time to time. Generally, if i upload at night, the upload goes quickly, if it is mid-day, it can be a lot slower and will occasionally time out. Zenfolio’s bandwidth is just too narrow to handle heavy traffic.

— comment by Shirley on November 29th, 2016 at 2:01pm JST (4 months, 26 days ago) comment permalink

Hi Jeffrey,

I made a small mistake yesterday and I’m just wondering whether there’s a simpler way to remedy my goof…

I set up a new publish service and put in that the files should be limited to 1000 pixels in either direction. Then I put 43 pictures in there and published them. Then I realized that I didn’t want to limit the resolution at Zenfolio, so I edited the puvlish service accordingly. But the images remain in the “Published” group. Is there a simple way to fix this? Could I just go to Zenfolio and delete them there (would that cause a hiccup at my end leading to the need to puiblish)? I suppose there’s a workaround that involves taking all the pictures back out of the publish services list and then reinserting them, but that seems ugly. Or I could perform tirivial edits on each one, but that adds up with 43 images.

Looking for advice, ideas….

Thanks for a great tool!!


Just select them in the “Published Photos” grid, right click, and “Mark to Republish”. —Jeffrey

— comment by Richard Kain on December 1st, 2016 at 1:59pm JST (4 months, 24 days ago) comment permalink

Thanks for the response. The issues have gotten so bad that I can no longer use your plugin at all. Nothing has changed regarding my system (your computer, your router, your security apps, your ISP) . The only thing I would say is that it seemed to have started once I upgraded to Lightroom’s 2017 Update. If I upload directly to zenfolio via their website, so far I seem to have no issue. I have written to zenfolio for any insight. Also, I saw someone suggested it happened to them as well but only mid day, however all my uploads happen later in the night. I am very confused and disappointed at the moment as your plugin was the best thing that ever happened for zenfolio. Any more insight would help greatly. Thanks.

— comment by David on December 6th, 2016 at 11:05am JST (4 months, 19 days ago) comment permalink

The problem is definitely on Zenfolio’s end, or between you and ZF. I have sporadic problems as well, but often a retry is successful. The failures I saw last night were clearly on the server side (it gave me information that would only be found on the server, and it was definitely a server issue). The third time I got my two images uploaded.

I think they get hacked, which causes problems with their stability and bandwidth, and they periodically have to go clean it up. Just a working theory.

That said, we should all be complaining to ZF, but I think it’s such a small-time operation that little would be accomplished. I think their technical staff is no more than a few people, or contractors, evidenced by their clear inability to address even signficant, pervasive problems on their site, or clearly needed fixes/features that their customers want.

— comment by Gary R Hook on December 7th, 2016 at 8:05am JST (4 months, 18 days ago) comment permalink

LR 6.7/Win10
I’m having a lot of trouble in re-populating pictures from Zenfolio into Lightroom. I check marked “Populate newly added collections from Zenfolio account” but none of the new ones are coming in.
The description says: You may want to invoke Zenfolio in the “File > Zenfolio Extras” dialog prior to doing this the first time in your Lightroom catalog” but I have no idea where to find this feature.

I’m not sure where you saw that reference, but it should be “File > Plugin Extras > Zenfolio Extras”, which means to visit Lightroom’s File menu and select “Plugin Extras”, then within that “Zenfolio Extras”. —Jeffrey

— comment by Werner on December 30th, 2016 at 7:45am JST (3 months, 26 days ago) comment permalink

Hi Jeff, love your work and have used your plugin on my MACs for a long time and love them to upload to Zenfolio. About two weeks ago trying to upload I started receiving an upload error on all my computers and could not upload to our marine photo library. I contacted Zenfolio, but no help as they didn’t even want to comient on it or even respond about the error. This is what I sent to them. Hello, we are having trouble uploading our images to our photo library. After about 30 seconds we receive and error banner (please see attached screen grab) we noticed it about two weeks ago. We have tried from different locations from the office to out on site. Average internet upload speed we have is 12 mb we are using 27 iMacs along with macbook pro latest OS on it. do you have any suggestions or can you please help us?
The error message is 2120512769. I just wondered if you might be able to help?
Best regards Paul.

Actually, they reached out to me today to talk about some of the errors that plugin users have been experiencing, and one of them was my bug. I pushed out a new version of the plugin a few hours ago, and it sounds like it might help your situation. Give it a try, and if it doesn’t help, send me a log and I’ll take a look. —Jeffrey

— comment by Paul Todd on January 17th, 2017 at 11:22am JST (3 months, 8 days ago) comment permalink

Have been using the plugin successfully for quite some time. However, something happened and now whenever I try to publish a collection to Zenfolio (new or updated) I get an error that says

Error during export
Unexpected reply from Zenfolio

Aborting export before any image was successfully uploaded.

Any ideas??

Yea, I screwed up the plugin with the version from earlier today. I’ve just pushed another one out that should fix it. Sorry for the hassles. —Jeffrey

— comment by Gretchen on January 17th, 2017 at 1:58pm JST (3 months, 8 days ago) comment permalink

Hi Jeff just wondered if there has been any reports of this error still coming up when uploading to Zenfolio from the latest Lightroom on an apple machine. It is happening on my iMac as well as my two macbook pro laptops. this is the error message when trying to upload:
Unexpected reply from Zenfolio. The plugin expected a data reply, but received a web page instead, so perhaps Zenfolio is having “issues” at the moment. For reference, in case there are any hints to the problem, the web page reply is:

There is no such user.

I know that they had a specific issue for a short while the other day, but if you’re still getting this, definitely touch base with them on it. Maybe log out of Zenfolio and log back in, just to make sure your account is in good standing? If they ask for more info than you have, send me a plugin log and I’ll see what I can figure out. —Jeffrey

— comment by Paul Todd on January 24th, 2017 at 10:19am JST (3 months, 1 day ago) comment permalink

Hello Jeff hope you are well. The zenfolio plugin has been working fine for a couple of months and today started getting this error message on my iMac and macbook pro running OS 10.11.6 Unexpected reply from Zenfolio. The plugin expected a data reply, but received a web page instead, so perhaps Zenfolio is having “issues” at the moment. For reference, in case there are any hints to the problem, the web page reply is:

There is no such user.

Additional information to pass along to Zenfolio support in case you contact them:
Target url:
Unix timestamp of call start: 1488914625.4378
Unix timestamp of call end: 1488914626.187

Please contact Zenfolio with this. —Jeffrey

— comment by Paul Todd on March 8th, 2017 at 4:28am JST (1 month, 17 days ago) comment permalink

Hi Jeffrey, Trying to export photos to Zenfolio. Getting this error message. Error during export 2058550564 Unexpected reply from Zenfolio.

Any suggestions?


Are you using the latest version of the plugin? It should also be giving you information that you can pass along to Zenfolio support. —Jeffrey

— comment by John Munno on March 12th, 2017 at 10:54am JST (1 month, 13 days ago) comment permalink

I’m also getting the no such user error

Please report it to Zenfolio, with the additional data that modern versions of the plugin presents along with the error. —Jeffrey

— comment by shawn on March 20th, 2017 at 11:59pm JST (1 month, 5 days ago) comment permalink

Hi Jeffrey. I am writing from Los Angeles. You live in one of my favorite places! Kyoto!! I am on a 27″ iMac 5k Late 2015. I am on OS 10.11.6 I am using Adobe Lightroom 4.4 I have been successfully using your plugins publishing to my Zenfolio account for several years. Then yesterday I had a problem while trying to publish to a new gallery in Zenfolio. First I noticed before I tried to publish that many of my previously published galleries showed empty in the LR lower left panel. I didn’t know what to make of this. But then when I tried to set up and publish the new gallery, other strange things started. I opened the setup panel (by clicking + in Publish Services in left panel on LR. This opened the regular window that I had always used. But then another window opened titled Loading Publish Collections. It showed a progress bar and the bar eventually went to far right, but it never completed it just froze onscreen and froze all LR. I eventually clicked Cancel button on this window, but nothing happened still frozen and still lots of published galleries (listed in far left panel) are still showing 0 or empty. I don’t know where to turn now as I don’t know if this is a LR or a plugin problem or even a zenfolio problem I assume its a plugin or LR issue though as the galleries are showing on zenfolio when I access it via safari. Please give me your thoughts on what to do next. Thanks Tom

When you mention that the previously-published collections show up as empty, only two things come to mind: one is that you’re accidentally using an old catalog, or your catalog has somehow gone corrupt. If it’s not the former, perhaps go to a recent backup of the catalog, check its integrity, and also reset your Lightroom preferences. Maybe try the preference-reset first, as that can often fix “weird” things in Lightroom. —Jeffrey

— comment by Tom Carmichael on March 25th, 2017 at 4:12pm JST (1 month ago) comment permalink

When using the Facebook plugin…I cannot see my business page as an album option to be published to…I am not sure if I am setting it up wrong. Thank you.

Please see this FAQ —Jeffrey

— comment by Mia van der Paardt on April 15th, 2017 at 1:43am JST (1 week, 4 days ago) comment permalink

hey there

I’ve come back to doing some work within lightroom and use your plugins. today i noticed something odd and its probably nothing to do with your plugin, but maybe you’ve seen or heard about it.

all of my zenfolio publishes in lightroom show ZERO photos. when i last used LR there were populated will all the photos that are on my website. any idea why this is or how to resync?

thanks! keep up the good work. love what you do.

I can only imagine that you’ve opened the wrong catalog (or perhaps an old version of Lightroom)? I’ve never even heard of catalog corruption causing this. —Jeffrey

— comment by brett isaacs on April 19th, 2017 at 3:11am JST (1 week ago) comment permalink

Im trying to use the plugin extras to see if that will fix my errors with no published data showing up from yesterday. i keep getting Assertion failed: packed.

LR 2015.6.1 windows. current plugin

Please see this FAQ. —Jeffrey

— comment by brett isaacs on April 20th, 2017 at 1:39am JST (5 days, 14 hours ago) comment permalink
Leave a comment...

See the known issues before reporting bugs. Also, when reporting bugs, please include the OS, the version number of Lightroom, and the version number of the plugin. PLEASE REPORT THE NAME AND FULL VERSION NUMBER OF THE PLUGIN WITH EVERY REPORT. Seriously. I need the full version number or I likely can't do anything but ignore the message.

All comments are invisible to others until Jeffrey approves them.

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

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

Subscribe without commenting