Jump to content

Search the Community

Showing results for tags 'afb-4000'.

More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...

Date Created

  • Start


Last Updated

  • Start


Filter by number of...


  • Start





Website URL







Found 2 results

  1. 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.
  2. 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
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.