Bookends trashed my folders containing references

A place for users to ask each other questions, make suggestions, and discuss Bookends.
Post Reply
alarob
Posts: 9
Joined: Sun Aug 08, 2010 6:46 pm
Location: Birmingham AL US
Contact:

Bookends trashed my folders containing references

Post by alarob »

In Bookends 11.1.1, I try to attach a folder to a reference. The folder is not attached but is placed in the Trash. Here are the steps:

1. Select Attach > Attach a folder…
2. Select the folder to be attached to the reference.
3. The "Attach to Ref…" dialog appears, asking "Do you want to attach the folder [foldername]?" Click "Attach".
4. An error dialog appears: "The file your are [sic] attaching has no content":
Bookends_attach_error.png
Bookends_attach_error.png (25.13 KiB) Viewed 3410 times
5. Notice that the folder you selected is no longer where you last saw it.
6. Recover the folder from the Trash.

If these steps cannot be reproduced, try this:

1. Create a PDF named "Latrobe 1905".
2. In a separate location, create a folder named "Latrobe 1905".
3. In Bookends, create a new reference to a work by someone named Latrobe, published in 1905.
4. Attach the PDF to the reference. (Do not select the option to rename the file.)
5. Now try to attach the folder to the reference.

FWIW I did open Adobe Reader and disable the "Internet" preference to display PDFs in a browser using Adobe Reader. I quit and relaunched Bookends. The problem persists.
Jon
Site Admin
Posts: 10291
Joined: Tue Jul 13, 2004 6:27 pm
Location: Bethesda, MD
Contact:

Re: Bookends trashed my folders containing references

Post by Jon »

Hi,

This is actually an unanticipated side effect of the malformed pdf warning (and also affects attachment of Mellel documents). It was fixed a day or so after 11.1.1 was released. Please download Bookends 11.1.1 again.

Jon
Sonny Software
alarob
Posts: 9
Joined: Sun Aug 08, 2010 6:46 pm
Location: Birmingham AL US
Contact:

Re: Bookends trashed my folders containing references

Post by alarob »

Thanks, I'll do that. Glad it's a known prob that's already fixed.
Post Reply