Lightroom: Error in deletePhotosfromPublishedCollection: did not call deletedCallback function

  • 1
  • Problem
  • Updated 8 years ago
  • Solved
  • (Edited)
Hi, in a LR publishing service, when it comes to the deletion of images that were removed from the collection, it halts with the following error message:



I have found several reports of this happening when the file to be removed from the collection had already been removed manually outside of LR. But this is not the case with me - the file still exists on the hard drive.

I rather believe that it can't handle the # character in file names properly, because the file's name is e.g. 2011-03-27_00-51-50_#165.jpg, but when I right-click on the image in LR and select "show published file in Explorer" it telles me it can't find the image but with the name "S:\\165.jpg, so the part of the file name until the # is missing! This happens to all the files that have the # in their name.

I am using Windows 7 64 bit, if that matters.

# is an allowed character in filenames in any modern OS, so please fix this annoying bug as soon as possible.

It seems to have been introduced in LR 3.4 or 3.4.1, as I haven't encountered it before, and the # is in almost all my images as it is important for my workflow.

Any ideas for workarounds (other than renaming the files!!!) are also very welcome!
Photo of DarkVater

DarkVater

  • 48 Posts
  • 1 Reply Like
  • annoyed

Posted 8 years ago

  • 1
Photo of Victoria Bampton - Lightroom Queen

Victoria Bampton - Lightroom Queen, Champion

  • 4970 Posts
  • 1931 Reply Likes
Hi DarkVater, can you please confirm which publish service you see this in? And do you see it anywhere else in the program, other than that publish service?
Photo of DarkVater

DarkVater

  • 48 Posts
  • 1 Reply Like
Hello Victoria, thanks for the speedy reply!

I'm using the hard drive publish service. As said, I haven't encountered this problem anywhere else yet in Lightroom, and I'm using it regularly for two years now; almost all of my 25,000+ photos have that # in their name.
Photo of DarkVater

DarkVater

  • 48 Posts
  • 1 Reply Like
So it seems nobody from Adobe is actually caring for this problem?
Photo of Julie Kmoch

Julie Kmoch, Sr. Development Manager

  • 109 Posts
  • 42 Reply Likes
We are investigating. Can you tell us which publish service this is happening on - is it a server, or a publish to your hard drive?
Photo of DarkVater

DarkVater

  • 48 Posts
  • 1 Reply Like
Hi Julie, thanks for your reply. Quote from my post above: "I'm using the hard drive publish service." :-) It doesn't matter whether I publish it to my Unix server (connected as a network drive) or onto my internal hard drive (Windows NTFS), the same error occurs with both.
Photo of Julie Kmoch

Julie Kmoch, Sr. Development Manager

  • 109 Posts
  • 42 Reply Likes
Doh! I should've read the comments more carefully, sorry. We'll have a fix for the deletion error in the next dot release, but we need to see whether the # character in filenames is a separate problem.
Photo of DarkVater

DarkVater

  • 48 Posts
  • 1 Reply Like
No worries, happens to anyone here and then I think. I appreciate your effort and hope to see it fixed soon - many thanks!
Photo of Becky Sowada

Becky Sowada, Adobe Employee

  • 510 Posts
  • 107 Reply Likes
I've confirmed that the # character issue is unique from the deletion error. I've logged a bug for this.
Photo of DarkVater

DarkVater

  • 48 Posts
  • 1 Reply Like
Official Response
I have just installed LR 3.5 RC1 and it seems that the issue has been resolved. Many thanks!