I like your Tree Publisher service. However, I am having a small problem. As the iPad has limited sort functions, I export the images with sequence numbers (Image-10.jpg and so on) with suppressed Exif, so it sorts by name. If I publish multiple subfolders in a batch, I get for each folder an error message (multiple files with same name).

First I do not understand, why it sees multiple files with same name, as each image has a different name (there is some explanation in the message box, but the text is truncated).
Second the error message comes up with each subfolder, so batch does not really work. Can the check not be disabled?

Thanks and regards

Rudolf

Sequence numbers make no sense in the context of Publish (this publish plugin, or any)… sequence numbers make sense only in a one-time “here are all the images, spit them out in order” export. Publish is a back-and-forth over time, so sequence numbers just shouldn’t be used. —Jeffrey

The plugin has two modes, locked in on a Publish Service basis. One is where it mirrors the folder structure as seen in Lightroom (and on disk), and the other where it mirrors whatever collection hierarchy you create within it. —Jeffrey

2011/09/image01.jpeg … imagexxx.jpeg
2011/10/image01.jpeg … imagexxx.jpeg

and then I remove all the images in the 2011/09 folder from the collection, the images are deleted, buy the folder remains. Again, this may be by design, but I occasionally find myself deleting empty folders.

Brian

It’s not so much “by design”, but “not really thought about”. But thinking about it, if the empty folder is wanted for some reason, deleting it is much worse a problem than leaving one that’s unwanted, so the plugin should probably not delete folders. —Jeffrey

At the moment it looks like a folder can only contain either more folders or pictures but not both. Is that the case?

(an example being that I want the root folder to contain several folders, but also an image that will be used by my website software as the background to the rest and this needs to be held at the top level)

many thanks,

Chris

When you create a non-leaf folder, it gives the option to have another folder represent the root of the non-leaf folder. If you didn’t make it at the time, you can do so by naming a leaf folder “root”. it’s a horrible kludge, but the best I could come up with given the severe limitations imposed by Lightroom. —Jeffrey

thank you for your great plugin! I recently upgraded to the latest version, but i also reinstalled my pc. So I don’t know where this issue comes from, also I didn’t find a possibility to downgrade.

This is my issue:
If i click on publish it takes very long before publishing even starts (more than a minute) the progress bar just stays empty and logging doesn’t even start either. As soon as publish starts its fast. This didn’t happen before my new pc or before this new version.

Any hints?

Thank you!

Where is the target folder? Is it on a network disk that needs to be re-established, or something like that, before the export can actually proceed? —Jeffrey

Thanks in advance.

Not easily possible. The ordering in the folder is up to the OS, but is usually a name sort, and there’s no reasonable way to force Publish to pick names that will sort in the order you want. Even worse, if you reordered photos, the plugin would have to rename all the affected files. There’s no easy solution here, sorry. —Jeffrey

Is there anyway for the plugin to only publish the first photo of a “stack” of photos? Thanks Jason

Well, I’d think you’d accomplish this by not putting the not-first photos into the publish service… (?) —Jeffrey

Thanks,

Bob Siegel

I don’t understand what you’re asking abut changing a name below the root… with a folder-structure tree, the name comes from the folders that the master images are in. With the collection tree, the names come from the collections you create, so you can just change them there. About the “license”, I’d actually forgotten that I hadn’t moved this plugin over to my “donationware” model. I’ll probably do that soon… it’ll remain free, but optional registration will require a (1-cent, if you like) transaction at PayPal. —Jeffrey

Let me start by saying amazing plugins and excellent work! Although you must already know that by now!!!

Now on to my “problem/question”!

I gave the plugin a try but did not manage to accomplish what I needed, maybe I did not understand the post very well. I have my lightroom folder structure based on pic creation date(YYYY/YYYY-MM) and have sorted the “albums/events” through collections e.g. (Collection Root/2009/Sister’s Birthday).

What I would like to do, is to export/publish my images on an external hdd with the current collection tree structure as a folder structure on the external hdd. e.g. (My Pictures/2009/Sister’s Birthday)

I thought I could set the tree publisher’s ‘root’ folder to “sync” with my ‘Collections Root’ collection set and it would automatically make the underlying subcollections as folders on my destination.

Can this be done or must I make a leaf folder for each of my subcollections and manually move my images from my regular subcollections to the leaf folders?

Thank you for your time! And bravo once again for your excellent work!

Prokopis

It doesn’t automatically replicate the collections… Lightroom doesn’t really provide a way to do it. I could have the plugin move the collection tree, I suppose, into the Publish service, but a mirroring is not currently reasonably possible in Lightroom as it stands now. —Jeffrey