uwe_hoos's profile

50 Messages

 • 

648 Points

Sat, Jul 2, 2011 9:45 AM

Closed

Solved

Lightroom: Error in deletePhotosfromPublishedCollection: did not call deletedCallback function

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!

Official Solution

50 Messages

 • 

648 Points

10 y ago

I have just installed LR 3.5 RC1 and it seems that the issue has been resolved. Many thanks!

Champion

 • 

6.7K Messages

 • 

112K Points

10 y ago

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?

50 Messages

 • 

648 Points

10 y ago

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.

50 Messages

 • 

648 Points

10 y ago

So it seems nobody from Adobe is actually caring for this problem?

132 Messages

 • 

3K Points

10 y ago

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?

50 Messages

 • 

648 Points

10 y ago

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.

132 Messages

 • 

3K Points

10 y ago

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.

50 Messages

 • 

648 Points

10 y ago

No worries, happens to anyone here and then I think. I appreciate your effort and hope to see it fixed soon - many thanks!

Adobe Administrator

 • 

504 Messages

 • 

10.6K Points

10 y ago

I've confirmed that the # character issue is unique from the deletion error. I've logged a bug for this.