Jump to content

big smile

Members
  • Posts

    347
  • Joined

  • Last visited

Recent Profile Visitors

4,031 profile views
  1. It only seemed to happen with Publisher 2.5; before that, it was perfect. In the opening post of this thread, posts from other people having the issue are linked to. And they all seem to occur after May 2024, which would suggest the problem was introduced in Publisher 2.5 (which came out in May 2024). All the posts seem to be from Mac users, too. None of the users mentioned OneDrive, so that might not be related (although to be fair, they don’t rule out cloud storage). I have tried running my files from the MacOS downloads folder, which is an offline folder, and the issue does occur, so I don’t think it's connected to cloud storage. Not sure if any of this info helps. Do you have any ideas on what I can do to help you reproduce it? I do appreciate your help, as it seems to be a tricky problem.
  2. @MEB were you able to reproduce and log the error? If not, then can you suggest something else I can provide to help this error be logged? I am using MacOS 12.7.6 if that makes a difference. Thanks!
  3. Hi @MEB I have uploaded the Jpegs. Thanks for continuing to look into this matter.
  4. No, the only thing that fixes it is if you zoom in over 1000%. It also happens with a variety of documents: Linked Affinity Designer files and also linked Jpegs.
  5. Thanks! I have uploaded it. Please let me know if you need any further info. Thanks! Fingers crossed this can be fixed, because it's super annoying!
  6. Hi Yes, please provide the upload link. Thanks!
  7. In my case, the work was created in 2.6.3 from the start, so there's nothing to roll back to.
  8. All my linked files are in Affinity Designer 2.6.3 format. I am not using any PSD. In a separate project, I also find the issue occurs if I import another Affinity Publisher document into an Affinity Publisher file. It looks like switching to a raster format is the only solution (but it's going to be faff!). I so wish Affinity would have the option to down-save formats to older versions. Thanks for your help!
  9. Same issue even when I delete everything but the background. Attached is TEST.pdf which shows the error. I have also attached expected-result.pdf which shows how it should render. Is there any way to save down a 2.6.3 file so it will open 2.5.7? Thanks! TEST.pdf expected-result.pdf
  10. Has this bug been logged by the staff? It's super-annoying that I have to zoom in on every linked artwork before exporting. I am using Affinity Publisher 2.6.3, and it's still a problem!
  11. I am having this same problem, too. My 108-page document is made up of 2-page spreads. On the master page, I have a background that extends the whole of the spread. If I export a single spread, the background renders. If I export a single page, the background renders. However, if I export the whole document as "All Pages", the background on the right-hand side of the page will not render. I cannot share files publicly. My background is an Affinity Designer V2 file created in Affinity 2.6.3 I am using Affinity Publisher 2.6.3 on macOS.
  12. It probably asked for replacement fonts because you don't have Calibri or Arimo installed. It's definitely not a font issue, because I've got the source fonts installed. And there's definitely nothing wrong with the PDF, because I have opened it in multiple PDF apps and it always renders fine. It just seems to be a bug in how Affinity Publisher reads the PDF (which, as I detailed above, has happened in the past).
  13. Yes, I have the exact same font. I actually copied it from the machine where the source file was originally created. I think it's just a bug in how Affinity Publisher reads PDFs. Ages ago, I had a bug with a different PDF and they were able to fix it. So I am hoping that their excellent team can look at the PDF and do the same again.
  14. I have the fonts installed, so that's not an issue. It seems to be a bug in how Publisher interprets the PDF.
×
×
  • Create New...

Important Information

Terms of Use | 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.