Jeffrey’s “Folder Publisher” Lightroom Plugin

This Lightroom “Publish” plugin allows you to export copies of your Lightroom photos to disk in a folder hierarchy that mimics the folder hierarchy in your Lightroom catalog. I've found it very useful in mirroring my Lightroom catalog as small JPGs on my wife's computer.

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

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

This is a sister plugin to my Collection Publisher plugin (which is similar to this plugin, except that plugin mirrors a collection hierarchy instead of a folder hierarchy).

Unlike a normal export, this Publish service allows you to create an ongoing relationship between the photo in Lightroom and the copy on disk. The tree on disk is refreshed for any changes (new images, removed images, and image changes) each time you “Publish”.

The plugin is normally used in the following pattern:

  1. Initial setup of the publish service.
  2. Populate the default collection with image you want to mirror, or create a smart collection that identifies the images you want to mirrors.
  3. “Publish” them, causing copies of the images to be reflected into a hierarchy on disk matching the folder hierarchy in Lightroom.
  4. Going forward, any time changes are made (images updated, added, or removed), “Publish” causes those changes to be reflected on disk.

Publish-Service Setup

When setting up a new publish service, you first assign a name, though you can leave it blank if you'll only have one...

You indicate where published copies are to be placed by specifying the root of the publish tree. When first setting up a new publisher, you'll likely want to pick an empty folder as the root.

The next sections are all part of the standard Lightroom export. In them you decide the size and quality of the published copies...

The next two sections shown in the example aren't included unless you specifically add them:

They're from my crop for iPad and Metadata Wrangler plugins; I use them in my exports to allow me extra control of what metadata is included in each exported copy, and in the case of my iPad portfolio, special iPad-specific crops so that some images better fill the screen.

The next section controls what changes in Lightroom should cause published images to be slated for republish.

Then we have a plugin-specific seciton on file renaming that gives much more flexability than Lightroom's standard “File Naming” section, should you need it:

This allows you to have the files for the exported copies named derived from image matadata using template tokens that are processed on the fly for each image.

The next section provides a way to do an FTP sync of the published copies, should you need it. Photo-viewing iPad apps tend to allow updates via FTP sync, so this section is convenient for that.

It's here as a convenient tool rather than an actual part of the configuration; the FTP sync is never automatic... it happens only when you launch it manually from the Publishing Manager.

The plugin also provides a way to import and export settings, making it easier to set up comparable publish services on multiple catalogs (such as when part of your library is on your desktop, and part on your laptop, as is my case).

When first setting up a service, you'll have the ability to import settings...

... but once it's been set up the first time, after that the section allows for export:

Collection Setup

Once you've got the publish service created, you can drag images into the default collection, or you can create your own collections, including “smart collections” that identify images to include via rules (e.g. “all five-star images”).

The default publish location for any image in any collection is that its folder structure in Lightroom is replicated and placed starting at the root folder chosen when you set up the publish service. However, you can modify aspects of how image locations are mapped when you create/edit a collection:

Availability

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 Lr6 to Lr7 (or the equivalent under the hood for the Lightroom Classic subscription) 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 )

20190708.10020190708.100 --

Newline token.

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

Upgraded to the embedded copy of ExifTool to version 11.50.

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

20190514.99

Added the ability to notice when files have their filename or folder changed.

Fixed an issue with {SequenceFirst}.

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

Fix an "Unknown key: captureTime" crash.

Added the GPSCoords token.

20190308.98

Updated the keyword-related tokens to accept standard filters.

20190307.97

Upgraded to the embedded copy of ExifTool to version 11.30.

20190228.96

Added the {Exiftool=...} template token.

20190114.95

Added some extra debug loging.

If the plugin's attempt to create a folder fails, try again a few times before actually reporting the failure.

Added the PEOPLE variable to the LUA token.

Fixed a problem with the SpeedKPH token.

Added the TempC and TempF tokens.

20181015.94

Updates for Lr8 (Lightroom Classic CC Version 8).

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

Added hierarchical options to the Keywords token.

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

20181004.93

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

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

20180906.92

Try to avoid having unexpectedly-long error messages create too-big a dialog.

20180803.91

Limit the amount of temporary disk used by Lightroom before handing files off to the plugin.

20180608.90

Added some extra debug logging.

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

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

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

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

20180420.89

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

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

20171229.88

Updates to the data templates that my plugins understand: updated the Keywords token, added CollectionNames and CollectionFullNames tokens, and added a bunch of stuff (KWf, CN, CFN, CNf, CFNf) to the {LUA} token.

20171019.87

Oops, more Lr7 stuff.

20171019.86

Updates for Lr7.

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

Allow the "If Exists" feature of Templat Tokens to work with the PluginProperty token.

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

20170705.85

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

Added extra debug-logging to track down a timing issue.

20170621.84

Added the Newline template token.

Enhanced the FolderName token

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

20170309.83

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

20170224.82

Couldn't set the exported-copy file date older than about 50 years ago; fixed.

20170216.81

The rules about what characters are disallowed in a folder name were too aggressive, so relax them.

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

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

Switch the log-sending mechanism to https.

20160905.80

Better support for network shares on Windows.

20160828.79

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

20160430.78

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

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

Added more debug logging to track down some issues.

20160217.77

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

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.

20151115.76

If there's an error exporting one particular image, try to continue with others and merely have Lightroom report a summary of errors at the end.

Added support for sequence numbers on publish. See the "sequence numbers" link in the "Enhanced File Renaming" section of the dialog.

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.

20150831.74

Allowed the Enhanced File Renaming to actually create sub-folders under where an image would normally be placed.

20150517.73

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

20150222.72

If the root folder of the publish tree had a very long name, the view/change buttons would be pushed off the edge of the screen.

20150219.71

In the "Enhanced File Renaming" section, add the ability to override the extension on the exported filename.

20150206.70

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

20150131.69

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.

20150103.68

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

20141215.67 Added a bit more debug-logging for when a file copy can't be done.
20141019.66 Windows Only: Add a one-time check for the POODLE security vulnerability, and alert the user if it exists.
20141005.65 Clicking on the blank area next to the upper-right [Publish] button caused an error dialog to display.
20140923.64 Added the LrMD5, LrLocalization, LrSystemInfo, and LrMath packages to the {LUA} template token.
20140922.63 Workaround for a Lightroom bug that causes the plugin to croak on certain folder names.
20140920.62 Some extra debug logging to track down a problem.
20140902.61 New build system
20140802.60

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

20140731.59 Registration fix for Lr5.6
20140720.58 More Creative-Cloud support.
20140715.57

Fixed an issue with Creative-Cloud revalidation.

20140712.56

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

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

Now supports Lr5.5+ Creative-Cloud Installs.

20140704.53 Sigh, introduced an error for some folks with the rebuild the other day.
20140630.52 Build-system update
20140613.51

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

20140612.50 Under some error conditions plugin would crash instead of presenting the proper error message.
20140509.49

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

20140423.48 Fix a location-related template-token bug introduced in a recent build.
20140422.47

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

20140417.46

Enhancements to the FTP stuff: take care not to work with "." and ".." that some servers return.

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

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

20140410.45

Added an option to limit the overall depth of the publish tree.

20140321.44

Internally track whether exports are via the master image or via a smart preview. In the future this may allow for a "republish those for which a master is now available" feature.

Worked around a mysterious "attempt to get length of a nil value" bug.

20131213.43 Added {PublishCollectionName}, {PublishCollectionDepth}, and {PublishServiceTitle} tokens to the preset templates. See template-token web page for important restrictions.
20131102.42 Update for OS X Mavricks
20131010.41 Yikes, it seems that version 20130905.36 broke the "Metadata that Triggers Republish" section, clearing all items you might have had set (well, all but Caption). Sorry about that. Please visit the "Metadata that Triggers Republish" section to reconfigure to your liking.
20130926.40 Oops, fix a bug introduced in the previous update
20130925.39

The 'Template Examples' dialog had been broken. Deprecated 'Folder' and 'Path' tokens in preference to 'FolderName' and 'FolderPath' tokens.

20130923.38

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

Additional debug logging.

20130909.37

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

20130905.36

Respond more gracefully when enhanced file renaming can't come up with something valid.

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

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

20130708.35 Fixed a crash during certain file-renaming attempts where originals no longer existed.
20130630.34

When "Format" is "ORIGINAL" (meaning to spit out the original image pixels with new metadata, instead of the developed version with new metadata), the plugin didn't handle XMP sidecars properly at all. Now it does.

You now have control over the file time of exported copies (set to the image capture time, or the time of export).

20130620.33 Allow published copies to remain on disk even if a photo is deleted from Lightroom.
20130613.32 Better support for plugin revalidation.
20130612.31 A failure for the plugin to copy a file on disk resulted in a plugin crash instead of the appropriate error message display.
20130612.30

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.

20130611.29 Yet another Lr5 update
20130610.28 Final update for Lr5
20130513.27 More changes for the root-selection problem... really seems to be a bug in Lightroom, but it's hard to tell because I can't replicate the bug myself.
20130501.26 Update for Lr5
20130412.25 Build system update.
20130329.24

More with with the code that handles changing the root of the publish tree.

20130220.23

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.

20130209.22 More build-system maintenance
20130206.21 Tweak for my registration system
20121210.19 Added some extra debug logging.
20121024.18 Allow Video to be FTP'd as well.
20121009.17

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

Disallow DPX video export because it breaks things.

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

20121004.16 Oops, the file-extension thing got worse, not better... reverting that change.
20121003.15

Work around a "situation" (likely Lr bug) where exported video loses its file extension.

More debug logging for the elusive "no root folder" problem.

20120821.14

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.

.
20120810.13 Added some debug logging to try to track down an error
20120722.12 More debugging for the "choose a root folder" bug that seems to still affect a few folks.
20120531.11 Oops, I was moving the original XMP file (when the Publish format was "Original" instead of copying it. Fixed.
20120529.10

Finally tracked down why the plugin had problem with Windows network shares. Ended up filing three separate bug reports with Adobe, but in the end was able to work around the bugs, so hopefully it's working now.

Update to handle the Mac App Store version of Lightroom.

20120510.9

Tweak for Lr4.1RC2.

Added the ability to move/reset the root folder. As a byproduct, this should allow the "choose a root folder" situation to be repaired.

In some crazy file-renaming situations, the plugin could get confused about the file extension.

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}

20120330.8 Update to handle 4.1RC
20120315.7 Add some extra debug logging to try to track down some network-folder errors.
20120309.6

Update to the debug logging to better track down timing issues that might arise.

20120228.5

Wasn't handling some kind of file-rename templates properly.

Now handles things much more gracefully when some files are offline when the publish is started.

Better support for video in Lr4.

20120224.4 A few bug and Lr4 fixes, and some extra debug logging.
20120217.3 Didn't handle XMP sidecars correctly when publishing original raw files.
20120217.2 Discovered why "metadata that triggers a republish" wasn't reliable, and fixed it.
20120213.1 Initial release, evolving from my earlier tree-publisher plugin, which dated back to the summer of 2010.

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

Hi, the new version of Lightroom Classic (7.2) is incompatibile with Folder Publisher. Do you plan to upgrade it? Thanks

Davide

Perhaps you have a (very) old version…. any recent version should work fine. —Jeffrey

— comment by Davide on March 19th, 2018 at 2:16am JST (1 year, 4 months ago) comment permalink

(UK). I’m having problems with folder publishing missing output files when virtual copies are involved. Within Lightroom everything looks fine, but when I look at the actual output files, I find some are missing, all ones which are virtual copies or have virtual copies.

I’ve tried some simple tests with just one master file and two virtual copies, and the first thing I notice is, the master version output file seems to get appended with “-3”, with one of the virtual copies getting the bare name, which seems the wrong way around. The other virtual copy gets “-2” which is fine.

I then delete the output files, “mark to republish” and publish again. Now in one of my smart collections, this produces same output files as before. But for another smart collection, seemingly identical but with a different output folder, I get just two output files, the “-3” one corresponding to the master file, and one with an odd “-2-2” suffix corresponding to one of the virtual copies. And when I watch the files being generated, I can see the missing virtual copy is actually generated first, with the “-3” suffix, but is apparently then replaced by the master version with the identical name when that is generated.

So it looks to me as if there is a semi-random problem arising from output naming with virtual copies, resulting in some output files getting overwritten when they should be retained.

Incidentally I am using a newly downloaded plugin, windows 10/64bit, lightrooom 6.14, and mostly using plugin defaults (with no renaming of output files).

All a bit frustrating ..

I’m going to guess that there are multiple issues at play here. During any particular publish operation for new photos, Lightroom comes up with some filenames, and the plugin preserves those names unless they conflict with filenames already in use (having been assigned to photos published earlier in the publish service). Lightroom itself doesn’t notice nor care about what filenames might have been used for other files… it cares only about the set of photos being published right now, and depending on what’s in that mix and the order they happen to be published, Lightroom appends these sometimes-weird suffixes. To avoid this, consider the “Enhanced File Renaming” section, whereby the plugin ignores the filename generated by Lightroom and uses one that you decide. In any case, once the files are handed over to the plugin, it has to make sure that there are no conflicts among any of the photos in the publish service, and no unexpected conflicts on disk, so it’ll add its own suffixes as needed to keep data consistent. If your enhanced renaming ensures that filenames will never collide, you’ll have perfect control over the names and there will be none of these issues. Consider using the virtual-copy name (“Copy Name”) as part of the filename. —Jeffrey

— comment by derek langley on May 1st, 2018 at 4:30am JST (1 year, 3 months ago) comment permalink

Hi Jeffrey, greetings from Italy.

I have a collection of 18100 photos dating from 1960, so publishing them with the desired hierarchy is a big task. I cannot thank you enough for this gem, that has saved me tenths of hours of tedious work.

Great job!

Ivano

— comment by Ivano on May 6th, 2018 at 7:34pm JST (1 year, 2 months ago) comment permalink

I seem to have a problem with Folder Publisher. It’s fairly easy to set up, but I am unable to publish my rather modest 9000+ pictures to a folder on the local disc. It goes fine (although rather slow, but that’s LR’s fault) for about 3000-4000 pictures, but then it invariably aborts with an error saying something like “Unable to move …. does not seem to exist” or something to that effect. The first part of the message is the name of some temporary folder, and if I look into that I see some of the pictures that I’m publishing.
I hope there’s a cure for this problem, because Folder Publisher fills a large hole of missing functionality in LR.

Best regards,
/Steen
(writing this from the city of Skanderborg in Denmark 🙂

Next time you encounter this, please send a plugin log. —Jeffrey

— comment by Steen Kroyer on June 28th, 2018 at 5:49am JST (1 year ago) comment permalink

Hi Jeffrey,
I am a big fan of your plugin but there’s something that doesn’t seem right. I have a single Smart Collection defined for the Publisher, which holds every raw photo in my collection. Every time I hit Publish, the plugin exports again EVERY single photo, regardless if it’s been modified since last time or not. It takes hours, each time. Any idea what I might be doing wrong?
Thanks,
Stefan

Please see this FAQ —Jeffrey

— comment by Stefan on July 17th, 2018 at 3:47am JST (1 year ago) comment permalink

Hi Jeffrey

Very happy with your plugin, which I use extensively. A question:

My “Published Photos” Collection is now quite big and I would like to get rid of the photos it contains since I do not have to rework them.

Is there a way reset the “Published Photos” collection (i.e. bring their number to zero) when they have all been published ?

I tried “Removing from collection”, but it actually deletes the corresponding photos completely from the target folder, not just from the collection of published photos.

“Deleting” does of course the same thing.

Cheers,

Pierre

There’s a “Delete Options” section in the Publishing Manager that controls whether they’re deleted from the target folder; adjust that and you’ll be fine. —Jeffrey

— comment by Pierre-Yves Bely on July 30th, 2018 at 4:13pm JST (11 months, 18 days ago) comment permalink

I used this plugin to create DNG and TIFF archives on external hard drives. It worked fine. I am intending to update such archives maybe on a yearly basis (by connecting them and hitting Publish). Unfortunately, after moving the hard drives to a safe location, I am no longer able to delete photos from my catalog. As soon as I attempt to delete a photo from a folder, I am seeing an error: “Can’t update this collection. Error with your “jf Folder Publisher” Publish Service (…); the root of the publish tree does not exist”.

This is fine. I know I have disconnected the hard drives. But I would like to delete some photos. Is there a workaround?

The plugin should give you the option to proceed, so I’ll work on that, but please realize that if you completely remove a photo from Lightroom without first letting the plugin “Publish” the removal from the publish service, the previously-published DNG/TIFF remains, so you’ll end up with orphan files. —Jeffrey

Update: hah, I forgot that the option is already there. See the “Delete Options” section in the Publishing Manager. —Jeffrey

— comment by Tom on July 31st, 2018 at 5:28am JST (11 months, 17 days ago) comment permalink

Hi Jeffrey, thank you for pointing me in the right direction. The selected option was “Yes, delete published copies from disk when originals are removed from Lightroom”. With the Root of Publish Tree disconnected this was acting just like the last option: “Don’t allow photos in this collection to be removed from Lightroom; abort the delete operation”.

The option which lets me delete source images from Lightroom when the Root of Publish Tree is disconnected is “No, leave published copies on disk”. I am fine with the resulting orphan files in the archive. This approach should protect from accidental deletion of originals (which would propagate to backup drives), as long as the originals have been published to the archive drives.

— comment by Tom on August 1st, 2018 at 6:38am JST (11 months, 16 days ago) comment permalink

Can the plugin be updated to cleanup the TEMP directory as it publishes files? Right now, it retains all of the temporary files until the complete publish is done which is problematic for very large libraries, in particular Video libraries.

Alternative, can you at least add the ability to set the TEMP folder to the folder/collection publisher plugins like the Smugmug plugin has.

The default temp Directory of the folder/collection publishers is where the OS is which is typically a small drive and compounds the problem above.

Lightroom should take care of keeping it clean as files are exported, but on top of that just in case I do have the plugin delete the copy the moment the export has completed. At least for the normal exporter plugins… which plugin are you speaking of? —Jeffrey

— comment by Andrew on August 2nd, 2018 at 11:56pm JST (11 months, 14 days ago) comment permalink

I’m using the folder publisher when the TEMP drive fills up. If lightroom/the plugin are cleaning up after each file is published then I think the problem must be that every single filed is put in the TEMP directory before a single file is published because in order to publish i need the same amount of temp space available as all of the files i’m trying to publish in the folder publisher.

There is an option within Lightroom that the plugin can use to tell Lightroom to not render too far ahead of what the plugin has handled. It really shouldn’t matter for this plugin because the plugin “handling” is just moving a file, but let’s give it a try. I just enabled that option in version 20180803.91. Let me know how it goes…. —Jeffrey

— comment by Andrew on August 3rd, 2018 at 10:24am JST (11 months, 14 days ago) comment permalink

Is it possible to trigger republishing of images if the Foldername has changed. I tried „source“ in the “metadata that triggers republish“ menu but that doesn’t work.

If its not possible now, that would be a nice Feature for the Future, in the best case the plugin would simply rename the published Folder instead of republishing all images again…

Unfortunately, Lightroom doesn’t allow for this. )-: —Jeffrey

— comment by Timo on September 25th, 2018 at 1:51am JST (9 months, 22 days ago) comment permalink

Thank you for this great tool. I have a question about the best setup:

I’m using a MacBook with limited disk space. So I move older pictures to a NAS. I use the publisher to create low res images on the Mac for the screen saver from images on disk and from the NAS. So I regularly move images from the Mac to the NAS.

If I keep the directory structure on NAS and Mac the same, eq. Foto as the highest level, would this cause problems if I move a picture from Mac to NAS and edit it later? Name conflicts are not possible, as I move whole directories.

Or what would be the best setup for this use case?
Best regards Peter

I don’t quite understand what you’ve described, but what you face is a common problem. The usual way to solve it is to generate Smart Previews for the photos before moving them to the NAS (and off your local disk). In such a case, you can still edit and export within Lightroom, but you’re dealing with a low-resolution Smart Preview, and have to re-load the master file from the NAS if you want to work with the original. Another option is to change the root of your library from your local disk to the NAS and back, as needed, but this can be quite dangerous if you’re not careful to keep things straight. —Jeffrey

— comment by Peter Heuchert on September 25th, 2018 at 7:47pm JST (9 months, 21 days ago) comment permalink

This looks like one good tool to have.

— comment by Roston Chase on October 27th, 2018 at 3:57pm JST (8 months, 21 days ago) comment permalink

Thank you for this awesome tool. I upgraded to the latest version, but it seems I did something wrong. Whenever I publish some new photos, all existing file structure and files in the target folder are being deleted. I actually want the target folder structure to increase over time since I mirror this into the cloud. I tried the different “delete” options but hat did not change anything on this end. Thank you for helping.
Best Regards, Thomas

It’s difficult to guess the issue based on the limited info here, but the intent of the plugin is to make, after a publish operation, the target folder hierarchy exactly match the publish service. Random unrelated files in the target will be deleted. —Jeffrey

— comment by Thomas on November 26th, 2018 at 9:27pm JST (7 months, 20 days ago) comment permalink

Hi Jeffery,

Thanks for this plugin which i had been running with lightroom 6.8 for years happily.

I’ve recently moved to a different computer which runs another version of lightroom (classic cc 7.5) and started to experience some problem. The publishing is very slow, and at some point got stuck.

I have about 27000 images (including about 600 videos) to export. It used to take a few hours to export which is bearable. Now, on an AMD 8-core process and 32GB RAM, it only managed to publish 15000 pictures after 30 hours, and the process is now stuck with the number of published picture doesn’t move further.

I tried changing a few settings like skipping videos, adjusting JPEG compression ratio etc; none helped.

I tried using lightroom’s builtin export feature on the same machine and it works just fine, which seems to indicate the problem is with the plugin itself.

Could you please shed some light? Many thanks.

My first thought was video files getting stuck, but you then ruled that out. Leaving video out of it, could I ask you to send a plugin log once you think it’s stuck? —Jeffrey

— comment by Calvin on December 15th, 2018 at 5:35pm JST (7 months, 1 day ago) comment permalink

Hi,

in the last time I can’t update one folder. I always got the error message that folder publisher can’t write into that network directory. But that wasn’t rue, I tested it. Now I get the error message when I reconnected the root “RobustCopy 184 attemt to compare number with nil”.
What do I have to do to solve this? Thanks

Please send a plugin log when encountering either error. —Jeffrey

— comment by Claus on December 15th, 2018 at 6:10pm JST (7 months, 1 day ago) comment permalink

Hi Jeffrey,

I’m having trouble in publishing folder from Win10 to a NAS
During the publish process a Warnig message is displayed: jf Folder Publisher: Can’t create target folder

The NAS is mounted as a network drive in WIN10, with NAS user login saved (different from WIN user, but stored in OS credential), and perfectly working from Windows Explorer, it’s possibile to write file and create folder on the destination folder on NAS.
In fact, if I create in advance the destination folder tree, the publishing process is correctly performed.

I suspect it can be an access rights problem occurring, but why Lightroom file management is not using the access right provided by WIN OS? is it running with different credentials?

Thanks
Daniele from Italy

I’ve pushed out a new version of the plugin that has more debug logging… give it a try, and send a plugin log if you encounter a failure. Do note that if there’s already a file of the same name where the plugin needs to create a folder, there’s no way the plugin can resolve that conflict and you’ll have to either delete the file, or change the folders of the photos you’re trying to publish. —Jeffrey

— comment by Daniele Capizzi on January 15th, 2019 at 7:23am JST (6 months, 2 days ago) comment permalink

Hi Jeffrey. Thanks so much for the Folder Publisher. A question please. I use the publisher to create a second copy of all my DNG and RAF raw files to DNG. When doing my Publish, I have noticed that the DNG files (to DNG) “come out” around half the original file size, and the RAF (to DNG) files around 70% of the original file size. It may be that the efficiency of the export is doing it, but just wondering if I am “losing” anything in the export?
I have, in file settings, Image format DNG, JPEG Preview Medium size, Embed Fast Load Data ticked, and unticked are Use Lossy and Embed Original +RAW file.

Thanks.

The plugin doesn’t have any impact on how Lightroom creates the DNGs, so your question is more a generic Lightroom question. I don’t know the answer, but if your master DNGs have the original raw file embedded, the resulting DNG will of course be much smaller (about half), so that sounds likely. Perhaps use my online Exif viewer to inspect the before and after files, looking for big changes? —Jeffrey

— comment by Richard Histon on January 24th, 2019 at 7:03am JST (5 months, 24 days ago) comment permalink

Hi, great plugin

I use for publishing all my favourites to my phone via GoogleDrive.

However, I’d also like to publish everything (15000 photos) in relatively low quality (1000×1000 px) to GoogleDrive for sharing with my PCs and browsing from anywhere. I set this up and it ran quite successfully.

However, I Then noticed that my previews folder Lightroom Catalog-2 Previews.lrdata had grown to 11GB and my C: drive almost ran out of space.

presumably as the plugin accesses each picture it will cause lightroom to generate a preview.

Is this avoidable?

Lightroom needs the previews cache for displaying thumbnails, and all other non-Develop sizes. You can flush previews with my Bag-o-Goodies plugin, but then you’ll lose thumbnails, and Lightroom will need to rebuild them as you scroll around in the Library Grid. As you move around in Library with the full view, it’ll make bigger previews, so the cache will continue to grow back over time. (You can get some great performance benefits to put the catalog and its previews on a big SSD.) —Jeffrey

— comment by David Roberts on February 2nd, 2019 at 3:17am JST (5 months, 15 days ago) comment permalink

Hey, thanks for the amazing feature-rich plugin. I’m trying to use it in automated back-up solution to external disk – copy the originals with correct folder structure, but only these worth keeping (using star rating). Unfortunately – as written in “Metadata that triggers republish” section in settings – Develop always triggers republish. This is undesired because Developing does not change the originals.

Would it be possible to add settings to disable this behavior? Or maybe it should always be disabled if the folder is set up to publish the originals?

FYI, even when you set the image format to “Original”, it’s not actually just copying the original file… for reasons I can’t fathom, it actually means “original pixels with current updated metadata”. So this is probably not the solution for you. I could probably try to work out something to copy the original files behind Lightroom’s back, but it’s not currently possible with the plugin. There’s no way for a plugin to disable the republish-on-update stuff, but it may be possible to effect the same thing by working around it. I’ll give it some thought. —Jeffrey

— comment by Marek on February 2nd, 2019 at 9:00am JST (5 months, 15 days ago) comment permalink

Hi Jeffrey, reporting from China (Czech guy living in China).
I have this Folder publisher and publishing around 28000 photos to L drive and having the photo 5mpix size limit. Problem is that this plugin also creates photos on my C drive and filling all the free space there. Why is that? If I delete the temp files in c:\Users\Coudy\AppData\Local\Temp\E9B9514A-EBD1-4DAD-B9A2-15AC1F328347 the plugin stops with an error. Another problem is that in that temp folder it creates photos that are not publish to my L drive as per settings of the folder publisher. What information do you need from me to find the problem?

Lightroom creates the rendered copies for the plugin, and places them in a temp folder, then hands them off to the plugin to move to wherever you wanted them. The plugin work in moving the rendered copies should be relatively quick, so Lightroom shouldn’t be building up a bunch of waiting-to-be-processed items… but even if it were to, the plugin tells Lightroom not to build up too many. So I’m at a loss to explain where the temporary files are coming from. Perhaps you can investigate the exact contents and timing of the files, to get an idea of what is creating them, and for what purpose? —Jeffrey

— comment by Pavel Desort on February 25th, 2019 at 3:02am JST (4 months, 20 days ago) comment permalink

Hi, it’s really a great and very helpful tool!

I need some help: I moved my LR to a new computer. In the new setup I imported a backup of the catalog from the old computer. So far so good. Now the folder publisher has lost all it’s previous state about already published photos and want’s to publish the full catalog again. And that are really many (90,000) pics. So it’s not possible to just let it happen and sit and wait.

Is there a way to just mark all pics as already published?

No. )-: In this case, it would have been better to simply use the moved-over catalog, rather than importing it. (Lightroom excludes all Publish info when importing or exporting catalogs). —Jeffrey

— comment by Riccardo on March 21st, 2019 at 4:36am JST (3 months, 27 days ago) comment permalink

I’m running LR CC…does your plugin work with it?
I need something that will export my files from LR and keep the creation date/time as the file date/time.
Thanks,
Rob

Adobe has made the naming stuff so egregiously complicated I’m not sure what to call it. If your “Lightroom” product can use plugins, it can use my plugins. All other “Lightroom” products can’t use plugins. You can use Rob Perrin on May 8th, 2019 at 1:35am JST (2 months, 9 days ago) comment permalink

Hi Jeffrey,

thanks a lot for your plugin, which I use to keep ~100,000 photos synchronized to a Dropbox folder.
Recently, I have run into problems:
I moved several 100s of already published photos to other folders within LR 6.0, but the move was not reflected in the published files. Also renaming an already published folder is not reflected in the published version.
I cannot (and don’t want to) undo the changes I’ve made in my lightroom catalog, but now I’m left with the LR structure not synchronized to the published version. What should I do?
I’m hesitating to delete all exported files on Dropbox and publish everything again, since it will take days…

Thanks,
Elmar

Lightroom doesn’t consider filename or folder changes with Publish, so this aspect is inconvenient. I just realized, after all these years, that I can have the plugin scan for changes, so I just added that. The plugin hadn’t kept quite enough data to make the first scan reliable — it might be overzealous and dirty photos whose filename hasn’t changed — but from then on, each scan will be reliable and should cause photos whose filename or folder has changed to be republished. —Jeffrey

— comment by Elmar on May 13th, 2019 at 6:02pm JST (2 months, 3 days ago) comment permalink

Hi Jeffrey,

wow – that’s quite impressive that you have integrated my comment so quickly and released a new version. Thanks a lot!
Just one more question: do I have to do a new Publish of all files with that version now, so that it will be able to detect filename or folder changes in the future?

Thanks, Elmar
(from Austria, since you asked)

Performing the scan the first time will accomplish the same thing, while it marks to republish items that it thinks might have had filename changes. —Jeffrey

— comment by Elmar on May 14th, 2019 at 10:35pm JST (2 months, 2 days ago) comment permalink

I’m very happy to learn about detecting filename changes. I was bothered by that as well, but was assuming it’s not possible to do this given Lightroom limitations. Very happy, thanks!

— comment by Iustin Pop on May 30th, 2019 at 4:19am JST (1 month, 18 days ago) comment permalink

Hi Jeffrey,

Using latest version of this plugin (20190514.99) I see some pictures being exported with some directories missing. E.g. instead of final path being drive:\a\b\c\d\e.jpg, it will be drive:\d\e.jpg. However, only some pictures get this “treatment”.

I can confirm that editing the smart collection, the preview shows the path simplified, even though leading path components/trailing path components and overall depth limit are all set to none.

If I quit Lightroom and then restart it, the bug dissapears. And it seems related to pictures that have been renamed, or that are no longer part of a stack.

Does this all ring a bell?

Not at all, unfortunately. If you can identify a specific failure before restarting Lightroom, send a plugin log with specific info about it (which image, exactly when where, exactly, and where you thought it should go, exactly). Thanks. —Jeffrey

— comment by Iustin Pop on May 30th, 2019 at 7:33am JST (1 month, 18 days ago) comment permalink

From the UK

I like Folder publisher a lot but what it doesn’t seem to handle is when I have new folders created as a result of importing new pictures, it doesn’t pick them up. So I have Dave’s Pictures\2015, … Dave’s Pictures\2018 (with subfolders). Which I published using Folder Publisher. Now I’ve got some pix from 2019 which I imported into LR so I now have a new subfolder under Dave’s Pictures called 2019 (and subfolders thereof). Surely FolderPublisher ought to detect that (as after all I selected “Dave’s Pictures” as the thing I wanted published …

Cheers and thanks for the plugin
Dave

I’m not sure what you mean, by “I selected ‘Dave’s Pictures’ as the thing I wanted published”. Any Lightroom Publish Service, including Folder Publisher, includes one or more collections of photos that are populated either by you dragging specific photos into them, or via smart-collection rules that are computed on the fly. Whatever photos are there, however they get there, is what the plugin works with during a Publish operation, and the folders that those master images are in are what’s replicated at the Publish target. If you import new photos, and they’re not included via one of smart collections you set up in the publish service, you have to manually drag them in. —Jeffrey

— comment by David Partridge on June 8th, 2019 at 2:03am JST (1 month, 9 days ago) comment permalink

Just recently updated to the latest folder publisher plugin and I am having something happen that I’ve never experienced before. As my photos are publishing they are sending copies to C:\Users\rob\AppData\Local\Temp. The problem is as the temp folder fills up my computer eventually runs out of storage and the lightroom process shuts down. Then I have to delete all the temp files and start the publisher process from where it failed. In all my years of using Folder Publisher I’ve never had this happen. Any idea what might be available for a solution.

Lightroom has a mechanism specifically meant to stop a publish operation from doing that, but it becomes disabled if the plugin takes “too long” to process files. The plugin normally should be very quick, as it’s just moving files around, but if you have some other plugins as part of the publish stack, and they take a long time, then perhaps this is enough to trigger things? —Jeffrey

— comment by Robert Norman on June 12th, 2019 at 8:16am JST (1 month, 5 days ago) comment permalink

Hi Jeffrey,

I have been using Folder Publisher for about 7 years in my old LR 4.4.
Somehow today it told me that I have to register and will continue working with limited functionality.

I am pretty sure I registered years ago, but cannot find the registration code.
What do you recommend, should I (re-)register or is there a way to retrieve my code again?

Best regards
Georg

You can easily create a new code with a one-cent transaction, but my worry is why did the registration disappear to begin with. I worry that your Lightroom preferences file has started to go corrupt… please see this FAQ if it disappears again. —Jeffrey

— comment by Georg on June 23rd, 2019 at 9:04pm JST (3 weeks, 2 days ago) comment permalink
Leave a comment...


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