folder-publisher-20120510.9.zip
· FAQ
· Version History
· Update Log via RSS
· Installation instructions
· “Donationware” Registration Info
· More Lightroom Goodies
· All-Plugin Update Log via RSS
· My Photo-Tech Posts
· My Blog
This Lightroom “Publish” plugin allows you to export copies of your Lightroom photos to local 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 4 and Lightroom 3 (though you must have at least version 3.5 for the latter).
The same download works for both Windows and Mac. See the box to the upper right for the download link link (in orange) and installation instructions.
Note: a Lightroom major upgrade, such as from Lr3 to Lr4, de-registers the plugin in the upgraded version, thus requiring a new (1-cent if you like) registration code in the upgraded version. It makes for a hassle every couple of years, I know. Sorry. See this note for details.
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:
- Initial setup of the publish service.
- Populate the default collection with image you want to mirror, or create a smart collection that identifies the images you want to mirrors.
- “Publish” them, causing copies of the images to be reflected into a hierarchy on disk matching the folder hierarchy in Lightroom.
- 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:
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 comperable 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.
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
)
| 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. |
Thank you Jeffrey!
Hi Jeffrey,
I just switched over to this plugin from tree published and I was wondering if there is some way to “mark as published” so that I don’t have to republish many thousands of files which have not technically changed.
No, sorry, there’s no easy way to back in old stuff. I’m facing the same thing with 100k photos, but I’ll just let it run overnight. —Jeffrey
Hi Jeffrey,
can you relocate the root folder? There’s only a visit button now while the old plugin let you change it.
Not at the moment, but it will… that’s the last big thing to add. I wanted to get the plugin out for a bit, though, before I tackle root relocation. I’ve moved back over to updating plugins for Lr4 for the time being, but I’ll probably get to the relocation thing within a month. —Jeffrey
Hi Jeffrey,
last week I found your new FolderPubisher Plugin. It would be very helpfull for me.
I just tried it the but hadn’t sucess.
I get the the warning window ” TreePublisher_FolderLocal:161: ‘for’ limit must be a number” and the plugin stopped working.
Woul’d you pleas help me
Thank’s Herbert
Sorry ’bout that… I’ve pushed a new version of the plugin that should fix it. —Jeffrey
I’m using Lightroom for many years and it serves my purpose perfectly! On the other hand I use the iPad more and more for presentations. The main problem I am facing is about the order/sequence of pictures within a folder. Whenever I synchronize a new “picture folder” with my iPad, the Apple software copies the photos in a “ramdom order” on the iPad, which sometimes makes to presentation “useless” (I have tried with renaming; changing the dates in the exif data, etc.). Is your plugin able to make sure that the sequence of pictures stays the same on the iPad (as in Lightroom)? That would be a great help!!
Thanks for your answer
Markus
You’re running into a problem that I talked about and tried to solve on this post, but in the end iTunes is just too unpredictable. The workflow becomes predictable and smoother when you abandon Apple’s “Photos” app for a third-party app. I talk about that and this plugin in this post. —Jeffrey
Hi Jeffery,
I would love to use your plugin but it does not work for me. All my images are placed in the root folder of the export. Exmple:
\\DISKSTATION\photo\image\test\test.nef
is exported to
\\DISKSTATION\photo\
(both leading and trailing path to ‘None’)
I’m using Windows and Lr4. Am I doing something wrong or is the network share I use a problem?
Hi Jeffery,
I did some testing and it seems that filenames on network shares are not handled correctly (see last message). E.g. for “D:\Images\a\b\c\img.jpg” everything works fine but for “\\MYSHARE\Images\a\b\c\img.jpg all” exports are transferred to the output root without any subfolders. The output root is also set to a network share. (Windows, LR4)
With kind regards
Tobias
I can’t reproduce this bug on my side, but I’ve just pushed a new version of the plugin that has more debug logging, so if you could try it, then if it doesn’t work, send the log with a description of what went wrong, I’ll take a look. —Jeffrey
Jeffrey,
I just registered this plug-in and while doing the initial setup I realized I can’t save the changes because the save button is disabled. On the bottom of the plug-in dialog there’s a message saying “Can’t save changes: Choose a root folder for the publish tree”. The publish tree root is filled in, in my case with E:\Dropbox\iPad, but no matter what I put there the error stays the same. I believe it’s an error related only to Windows, which is my platform.
Any advice of how to go around this issue?
Thanks,
Gabriel
After getting into that situation, could you visit the plugin manager and send the log, along with a short recap of the problem? Thanks. —Jeffrey
Hi,
I had the same problem as Gabriel, “Save” button inactive, I just restarted Lightroom and the button became active and worked ever since. Hope it helps.
Hi, I don’t know if it’s a bug or made on purpose but if I have folder with pictures with no ratings at all is published with no problems. Then, if I put some ratings, 4,5 stars to some pictures, in “Folder Publisher” those pictures will show in “deleted photos to remove” category and of course will be deleted from the “root of publish tree”.
Thanks,
Ion
It sounds as if you’ve got them in a smart collection where a rule excludes ratings of 4+ stars. —Jeffrey
Spot on. It was a smart collection with the rule of any with no stars, when I created it I thought was a good idea to include all photos but when I started to give stars I forgot about the rule in collection.
Thanks for the quick reply
Ion
Thanks to your folder publisher and your pointer to photomgr pro, i no longer need to maintain a publish collection for every collection i have in a flat hierarchy to get photos onto my ipad nicely ( i organized by -> year > month -> photos and itunes doesn’t like that but photomgr deals very nicely with it.
I have found one problem but i’m not certain it’s specific to this plugin. When I rename the source files in lightroom, the plugin doesn’t by default move them to be republished. I can’t find anything in the plugin config to tell it to republish based on file name change. Is this the expected behavior? If so, any idea why and anything I can do to change it?
It’s an oversight (or inexplicable decision) on Adobe’s part. I submitted a bug about it, asking for folder/filename to be included in the list of things that can trigger republish. We’ll see. —Jeffrey
Is the plugin supposed to be “Processing Updated Publish Criteria” on every LR4 restart? This seems to have started a few updates ago.
It’s fairly annoying because it takes about a minute on my largest catalog. Even on my smallest catalog, it’s about 10 seconds.
This is something on Lightroom’s side, and I don’t understand it. I saw it in the Lr4 trial, but thought it was fixed in the real Lr4, so didn’t peruse it further. If you’re getting it in the real Lr4, I’d be interested in a copy of your catalog (sans photos) to test with and to send to Adobe. But before that, perhaps give the Lr4.1RC a try? —Jeffrey
Hi, the download link http://regex.info/LightroomPlugins2/releases/folder-publisher-20120330.8.zip doesn’t work. Can you please check that?
It seems to be working when I test it, though you must try to download it via the link on the plugin page, or via the plugin itself. If it’s not working for you in those situations, I’d appreciate it if you could follow up with more details… —Jeffrey
Thanks for your reply Jeffrey. I’m using Firefox with RefControl which blocks referrers. After disabling this for your site it does work.
Ah, that makes sense. Unless the referrer is from my site, it forwards you to the plugin’s home page, so that folks following a hard link will always be presented with the latest version. —Jeffrey
Jeffrey,
Have now found a corrupt file and a few missing links so have managed to babysit all the files through now.
Great plugin, thank you.
Peter
I also have the “Processing Updated Publish Criteria” on startup. I´m using 4.1RC. Where can I send a copy of the catalogue?
Adobe has already been sent a way to reproduce the problem, so there’s no benefit to sending additional catalogs…. just send hope.
—Jeffrey
For me the “Processing Updated Publish Criteria” has stopped with 4.1RC2
Thanks!