Paul_Finchley's profile

33 Messages

 • 

582 Points

Tue, Nov 17, 2020 7:46 PM

Closed

Lightroom Classic: Enhancements to Publish Services

I love the new features coming through to LrC like Live View for Canon cameras (hooray) but I feel that some love needs to be shown to older features that haven't been shown any attention for a while. I'd like Publish Services to have a bit of a boost as it would really help with my workflows.

I'd like to have a bit more granular control over the actions on an image that cause a re-publish. I use stars and colour labels as part of my work flow in LR. I also have many hundreds of publish collections (both smart and non-smart) I would like to switch off the behaviour of marking an image for re-publish if I change a colour label or star rating as I then can't tell if I've made a real visual edit to the image or just changed something inconsequential (to me). I'm sure other people have other things they do to images that they don't want to trigger a re-publish. It causes a lot of unnecessary republishing for me and drives me a little nuts. Can an extra panel of check box's "ignore re-publish triggers" be added to the Publish Service settings?! 

If possible it would be nice to know what caused the re-publish when LrC changes that flag. A metadata field would be nice and even better if it could be used to create smart collections and filters of images based on what the re-publish trigger was (rating change, label change, keyword change, copyright change, etc).  

An indicator on a collection that has images that need re-publishing would be useful. If that indicator bubbles up from a publish collection to the Publish Service level users would be to quickly see and drill into which collections have images which need re-publishing or maybe just need to be marked as up to date ;-)

Next, anywhere you can right click on a single or selection of images, add to the menu the option to "Republish in All collections" & "Mark as up to date in All Collections". This would allow an image to be edited and then republished in the background without leaving the develop module.

Lastly, when right clicking on a collection or collection set in a Publish Service there are options to "Publish Now" and "Mark to Republish". Please add an option to "Mark as Up To Date" to that right click menu

Hopefully all those suggestions are closely enough related to be allowable for one Idea thread.

Adobe Administrator

 • 

10.9K Messages

 • 

143.5K Points

1 y ago

This article will assist you in making a more effective feature request: 

Notably: One post per each request has much greater impact. 

33 Messages

 • 

582 Points

I already read that article. I didn't consider my request the same as any other I could find. I also felt the ideas were close enough to considered as a single change. i.e. Improve the flexibility, discoverability and consistency of re-publish within Publish Services.

Happy for this idea to be merged if there's a better supported post that covers the same suggestions.

34 Messages

 • 

508 Points

1 y ago

I like these ideas too. Maybe one option would be to "only mark to republish if Develop setting have changed". 

I'm afraid that Publish Services are a very old, and now unloved feature for LR Classic. I think they may have even been deprecated as of a few years ago.

Despite the absolute fits LR Sync has been giving me the past three months, when it did work, it worked well, and was absolutely magical! Perhaps they could merge Publish Services with a revamped LR Sync engine?

33 Messages

 • 

582 Points

I like that first suggestion at a very minimum to prevent endless re-publish flags being set.

The code must have rules which trigger a re-publish so I can't see why those rules couldn't have a few toggles added to them. I know it's not quite so simple as the (I'm an ex database and software developer) but I also know it would take less time to fix than I've spent clicking the "mark as up to date button" or waiting for republishes to happen over the last few years!!!!

I use Publish Services daily and find it one of the great things about LrC as a Digital Asset Manager that really helps my workflow and smooth delivery of images to clients.

101 Messages

 • 

2K Points

1 y ago

I very much like the ability to create published collections that automatically find photos that are edited and need a re-publishing. The problem is that this function seems to be a little too sensitive. Photos that are not edited at all, but just looked at in the develop module, sometimes appear to be "Modified to Re-Publish". The History panel shows no new lines of editing, which I think should be a requirement for re-publishing. 

Note: This comment was created from a merged conversation originally titled Too sensitive re-publishing in Publish Services