Lightroom Classic: Publish Now fails: The destination folder for this operation is missing

  • 1
  • Problem
  • Updated 7 days ago
  • (Edited)
LR Classic 9.2 Release

Publish Now fails: "Warning Can't update this collection. The destination folder for this operation is missing."

To duplicate:

1. Add Hard Drive Publish Collection:
    - Export to Specific folder
    - Rename to Title [Filename]

2. Add photo with no Title to publish collection

3. Publish Now

4. Add a Title to the published photo

5. Publish Now fails: "Warning Can't update this collection. The destination folder for this operation is missing."
Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes

Posted 2 weeks ago

  • 1
Photo of Laura Shoe

Laura Shoe, Champion

  • 135 Posts
  • 86 Reply Likes
This doesn't produce an error for me. You chose Specific Folder - did you then click on Choose and specify the folder? Please provide a screenshot of the setup dialog.
Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes
Actually, Go to Published Folder fails with "Can't show this published collection" as soon as the untitled photo is published.
Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes

Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes

Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes

Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes

Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes

Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes

Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes

Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes

Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes
Note that when the untitled photo is published, the resulting filename begins with a space.
Photo of Laura Shoe

Laura Shoe, Champion

  • 135 Posts
  • 86 Reply Likes
Regarding the filename, I can't tell for sure, but in the file renaming editor it looks like you have a space between the Title and Filename tokens - in which case images without a title would start out with a space. Based on your third-to-last screenshot of the image in Explorer, the publish/export doesn't actually fail, correct, despite the message?   What are the permissions set to for the folder (Read/Write)? (In Explorer, right-click on the Pictures\Test folder, Properties).

Does file renaming really have anything to do with this - what happens if you don't rename as you publish?
Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes
Based on your third-to-last screenshot of the image in Explorer, the publish/export doesn't actually fail, correct, despite the message?
Correct, but all subsequent publish operations fail with the destination folder missing error.

The folder is on a SAMBA share, R/W by everyone.

The problem is related to publishing photos with no Title field for the rename, which results in a filename that begins with a space.  I just tested a publish service with a Title_[Filename] template instead of Title [Filename], and it does not fail with the folder missing errors.

However, when a photo is added and published with no Title, the output filename is _[Filename].jpg.  If a Title is then added, the photo is marked for update, but when published, the file is not renamed.  Instead, a new file Title_[Filename].jpg is created and the old _[Filename].jpg file is not deleted.

Photo of Sunil Bhaskaran

Sunil Bhaskaran, Official Rep

  • 467 Posts
  • 171 Reply Likes
I tried publishing files with initial space in the file name and later with an added title.
Files were published; as you mentioned, the original files were not deleted.
However, I don't get any error message.

Does it happen if you change the Destination folder too? 

Thanks,
Sunil
Photo of Keith Gorlen

Keith Gorlen

  • 28 Posts
  • 2 Reply Likes
I ran more tests.  The error does not occur when the destination folder is mounted with a drive letter, e.g. a local folder under C: or a network folder mounted on a drive letter.  So the error is related to destination folders with UNC paths.

In all cases the original renamed files are not deleted, but that's an old known problem that Adobe hasn't fixed.