Lightroom: Renaming of file has no effect in Publish Service

  • 11
  • Problem
  • Updated 1 year ago
  • Solved
  • (Edited)
I am running a trial of LR 3.4.1 on Windows 7 Ultimate 64 bit version and have discovered a problem.

If I rename a file that is in a published folder then the name it had when I added it to the published folder will never change on publish. It affects both photos and videos. If I remove the file from the published folder and then add it again then the new filename will take effect.

The steps to reproduce the problem are:

Step 1. Import photos and videos.
Step 2. Create a publish service. Make sure in the export dialog that the renaming of file is not checked.
Step 3. Add photos and videos to a published folder under the new publish service.
Step 4. Publish.
Step 5. Change filename, F2, on some or all of the photos and videos.
Step 6. Mark to Republish
Step 7. Publish. This will result in exported files where the published files on disk gets the original filename and NOT the name set in Step 5.
Step 8. Remove files from the Published Folder.
Step 9. Add files to the Published Folder again.
Step 10. Publish. Now the exported files gets the new filename that was set in Step 5.

Maybe it is designed this way on purpose to be sure that the published folder reflects the names of the files on disk but I consider this as a possible bug because if I set the publish service to rename files, to whatever I choose, it has no effect.

Kind regards
Sten Palmqvist
Photo of stenepalmqvist

stenepalmqvist

  • 1 Post
  • 0 Reply Likes

Posted 7 years ago

  • 11
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4413 Posts
  • 1622 Reply Likes
I can replicate this on Mac OS 1.6.7 too. Is this a bug or as designed?

If I remember correctly the Flickr free account ignores a name change whereas the Flickr Pro account updates with the new name. I'd have expected the hard drive service to update the name, however that would bring up the issue of deleting the previous published file.
Photo of Beat Gossweiler

Beat Gossweiler

  • 238 Posts
  • 38 Reply Likes
There are a few problems associated with naming and published collections, some of which might present a conceptional challenge:

  • Renames on published images are not reflected in published collections, not even when explicitely marked for re-publish.
    Workaround as described by the OP

  • Changing the file renaming scheme in a publish collection setup after it has been created (which is possible to do) does not take effect, although the change in naming (optionally) triggers a mark-to-republish for all images in the collection.
    Workaround is also to manually remove and re-add all images in the collection with re-publish after each step

  • If the published collection in question (for both name changes above) is a published smart folder, the only way to trigger removal and re-addition of the images is either to change the smart collection criteria or the remove and re-add the entire published smart collection


There might be more similar issues in different renaming situations, and as Victoria mentions, solving the issues might involve deletion and re-addition of the affected images.

Beat
Photo of ryanmarti

ryanmarti

  • 1 Post
  • 0 Reply Likes
I am experiencing this too.

Trying to publish a set with a Rename rule using Title metadata field.
Lightroom just keeps on using the original file-name.

I tried removing/reintroducing images, but no luck.

Don't really want to delete/recreate publish set.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 384 Reply Likes
I put renamed photos in a collection, then exclude photos that are in that collection from smart publish collections which need for the photo to be republished using the new name.

Thus whenever photos get renamed (and thus put into the renamed collection), they are marked for deletion on the publish service (since they are no longer included in the smart publish collection).

Thus I can publish / delete them.

Then after removing from the renamed collection, they are marked "to be published" with the new name (since they are once again included in the smart publish collection).

Dunno if that helps y'all, but it's doing what I need.

Cheers,
Rob
Photo of Douglas Bailey

Douglas Bailey

  • 2 Posts
  • 0 Reply Likes
So the work-around works, but this problem takes away a lot of value of the publish service functionality. I use the functionality to create albums of photos for different events. Since I use multiple cameras, and some of the devices I display the photos on only allow sorting by file name, I'm forced to rename the photos with a sequence number to get the photos to display in the correct order. This problem means that if I add a photo to an album I need to blow away the whole album and export it again from scratch. The big problem in my mind is that it's very easy to forget to do this, and of course Lightroom doesn't provide any feedback that it's necessary. As it stands it's little better than manually deleting and re-exporting the entire album after each edit.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 384 Reply Likes
Understood. It's a convenience for me since I don't have any albums riding on the original filename, but I get your point. A true solution would involve renaming the photo at the endpoint. And, how to do that depends on the publish service (there is no standard for it). In my opinion, it is a hole that should filled in no uncertain terms, but also plugin provider could program a solution. So, next question: is there a specific publish service you'd like to see remedied? If so, consider consulting the plugin provider... (if Adobe, then consider whether there is a 3rd party alternative provider that may be quicker to act, or already have the feature implemented).
Photo of Douglas Bailey

Douglas Bailey

  • 2 Posts
  • 0 Reply Likes
In my case it's the hard drive service I care about. Renaming files is trivial, but as you say some services can't support rename.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 384 Reply Likes
I may add a generic rename capability to PublishServiceAssistant, or add a non-generic rename capability to TreeSync-Publisher (not yet released), along with the ability to have non-tree format output, so it covers normal flat-folder hard-disk publishing too. That might solve your problem. Do standby, and ping me if I grow quiet...

http://forums.adobe.com/people/areohbee

But I'm still not sure about this "album" you mention - what type is it? If the filenames change will this album "get the memo"? Or is that part of the functionality you need, to "notify" this "album"?
Photo of Steve Harris

Steve Harris

  • 8 Posts
  • 1 Reply Like
I agree with Douglas, this almost completely negates the benefits of a published service.
If you can't keep it in sync it has no value. I spend more time trying to keep them in sync than I just exported them every time. :(
Photo of rachel channon

rachel channon

  • 14 Posts
  • 2 Reply Likes
my problem is similar to op. i set up new publish to hard drive. edit settings. either leave settings with no filename change, or include a name change. publish photos. now edit settings and change rule for filename. absolutely no effect when republishing regardless of whether i actually delete files from folder or not. note that if i change the rule about file size, this behaves correctly and alters file size appropriately.
Photo of Andreas Prantl

Andreas Prantl

  • 13 Posts
  • 0 Reply Likes
Obviously the publish services still need some work. This issue has been reported three years ago and it still persists (Lightroom 5.7). I have also experienced some other weird bugs.
It could be such a useful tool. However for the time being I apparently have to look for another tool that allows me to publish my RAW images and movies as JPGs to my NAS for presentation purposes.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 384 Reply Likes
A couple work-around solutions for now:

1. Don't rename. Sorry, but for the sake of completeness it had to be mentioned, and hopefully once you have a solid naming convention, you'll never rename again. But if you must rename:

2. Before renaming, remove from publish collection, and publish (so photo is removed from remote location..).

3. After renaming, add back to publish collection, and republish.

To be clear: I agree renaming intelligence would be optimal, but the work-around is not too bad, unless of course you rename frequently (you don't rename frequently, do you?).
Photo of Andreas Prantl

Andreas Prantl

  • 13 Posts
  • 0 Reply Likes
Thanks, this work-around solves my problem. In the end I am only using smart collections so that I can easily add and remove a rule to republish the entire collection.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 384 Reply Likes
Good to hear! (thanks). R
Photo of Steve Harris

Steve Harris

  • 8 Posts
  • 1 Reply Like
Don't rename files???
Wow I can understand not renaming them in the filing system but to not be able to rename them in LR is not good. 
Hiving just spent an hour with the work around on 30 published services, I am not a happy camper.
Photo of Luis Faustino

Luis Faustino

  • 2 Posts
  • 0 Reply Likes
+1 fix this.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
How often are you renaming your photos?

Anyway, make sure you know how to work around for the mean time (see above).

Don't get me wrong - I'm all for making Lr better, but no telling how many features/bugs are ahead of this one - could be Lr7 or 8 before it's fixed, if ever..
Photo of Luis Faustino

Luis Faustino

  • 2 Posts
  • 0 Reply Likes
It doesnt matter how many times really. If you are midway on processing the photos and realise something is wrong and files need be renamed then,
even if its just one time or once in a project, the work around explained by the OP means I still have to re-export all files. On 1000 RAW images it takes a good 4h to 5h to complete.
It's good to have a workaround but think this a bug - at the least because you dont get a warning explaining the current behaviour, which is misleading.

Yeah, lots other things to do in LR...

Thanks anyway.
Photo of Rob Cole

Rob Cole

  • 4831 Posts
  • 382 Reply Likes
I agree - even if not "fixed" in robust fashion, a word of warning would be very helpful..
Photo of Mediha Ayub

Mediha Ayub

  • 1 Post
  • 1 Reply Like
wow, this is such an old problem, and it STILL has not been fixed. i just experienced this and my solution was to publish from lightroom, and batch rename using Bridge.
this should not be an issue anymore :(
Photo of PAUL ROOKES

PAUL ROOKES

  • 2 Posts
  • 0 Reply Likes
And its still an issue, obviously ignored by Adobe.
big headache for me as I'm using it for my stock portfolios......ie so I don't upload the same image twice........not being able to rename say after a period of time is a pain.
the work around of removing all the files and then putting them back in works but as previously mentions the functionality of the service is lost.
if I change the file quality it works, the file will save from then on at he new quality and I have the option to also change all the existing file in this publishing service to the newly entered quality, that's the functionality I need and is implied by adobe, so why not the rename function ?
Photo of Josée Sévigny

Josée Sévigny

  • 2 Posts
  • 0 Reply Likes
Same here and using LR CC 2015.
Photo of Thommy Andersen

Thommy Andersen

  • 6 Posts
  • 0 Reply Likes
And same here and using LR CC 2015.12 and Windows 10.
Rename not working..