Search the Community

I've run into this error many times. Finally caught a screenshot to show. Scenario. Photo book, photo source is Lightroom. Resource Collection folder. In Lightroom I edit the photo and export it to the Collection folder. AFPUB notifies the user that the file has been modified outside the application. The second notice is "Failed to Open File, File Type is not Supported." The photo is not updated in AFPUB document (not replaced with the edited version). However, all you have to do is to "Replace Image" with the very same image (.JPG) and all is fine. So the problem is that the file type is, indeed, supported when you replace the image. The earlier versions of AFPUB would automatically notice the change and apply the newly edited photo into the AFPUB document. No user intervention when the image is Linked, and the preferences are set to "Automatically update linked resources when modified externally" This is no longer working as expected. Something about the File Type.

Hey Affinities, I have a feature request for Publisher: I'm working on a year book project with around 100 pages/each around 4 images. My workflow for the images takes them through Adobe Lightroom from which I export the images to the project's folder. I've set Publisher to "Auto refresh external ressources". So it often happens that I find an image needs an additional tweak when arranged with three other photos, so I make the change and overwrite the existing file (each image is around 10 MB). Here comes the catch/bug/feature request: Publisher correctly recognizes that the file has been changed, but doesn't give the system enough time to finish writing the file: an error pops up "file not readable"... So the FR would be: "Make the software try e.g. three times (with say three seconds inbetween) to auto refresh the file before throwing the error" or if the system can give the information: check if file is still being written, check for refresh afterwards... Cheers, Jan