Mr. Dyck

Today I opened all files first, before I opened the book. Opening the files seperately wasnt a problem yet. Having all files opened, the books panel worked fine. The renumbering of the pages worked and even synchronising all files at once worked well. So is that they way the books panel is supossed to work? Do I always have to open alle files before I use renumbering oder synchronization functions of the books panel? But I have still one question: How is the synchronising of the master pages supposed to work? One single change on a masterpage in the masterfile (Or style source chapter - i dont know how its called in english) leads, after synchronizing all chapters, not to a modified masterpage with the same name, but to a new masterpage with the same name. So I have to reaply the new synchronised masterpage to all my Chapters. Is it supposed to work that way? I expected synchronizing will apply the changes in the masterpage of a masterfile to the masterpage with the same name in the chapter files.

I had problems with adding chapters and renumbering in 2.1.1 Because this problems were known and promised to be solved in 2.2, I tried the Beta version. It works better in some way, but it is still very unreliable. Very often when I open an existing book file the program tells: 1 document is being loaded. But there will be no end of loading. adding the fourth chapter very often freezes the program. The renumbering of the three first chapters works well, but the third chapter freezes. I tried it several times, I created new book files, but no change. Could it be connected to the size of the documents? They are between 200MB an 1000MB about 16 pages. I use it on Windows 11. I cannot upload all my files for public because of copyright conditions, but I could send it to someone for troubleshooting. I add some crash reports from the official release version. The beta somehow didn’t save any crash reports. a7b82d03-fdc1-4fd0-9766-5193ef6eb489.dmp 4b8064dc-2882-475a-819e-0b98cbc5d62f.dmp

Can you tell when the next beta is expected to be available? In comparison to former beta releases it actually takes a very long time for the next version. Is it because 2.0 is coming up?

@LibreTraining thank you very much. You really helped me. It works fine with the Gill Sans Nova.

@Pauls So the only solution is to choose another font?

Hello, it is a really odd bug i found on Publisher. I created a template file for worksheets at school. The font for the task description ist Gill Sans MT. My template file has two pages. For the first page I created all textframes manually, for the second page i just copied them from the first page. The Gill Sans MT font is always display correctly. But when I'm printing right from Publisher the Gill Font will be printed correctly on page 1 but not on page 2. On page 2 the the letters are very narrow and stretched on the same time (see attached fotos) We had the same issue with different PCs and also different printers. And even when I'm using the template file for new worksheets, all copied textframes with the gill sans font will be displayed correctly but printed incorrectly. On the other hand exporting to PDF works well. Everything is fine. But because of our workflow I need to print from publisher correctly. Do you have any idea? I attached the template file. AH_Vorlage.afpub

Thank you, that works for the moment.

Where could I upload the file to get it fixed? Is there a chance to rescue the file? The problem is, that I dont get any error information. Publisher just crashes, without saving any recovery files. Update: I attached the crash log file. I hope it will help. It seems, that the same file works properly at other PCs. But im not sure yet. Im using an Asus Zen Book Duo, Windows 10 Home, the latest versions auf Affinity Publisher und Affinity Publisher beta. Publisher Crash logs.zip Beta Crash log.zip

Hi guys i have a large Publisherdocument which I need to get printet as soon as possible. The problem is, i'm not able to finish the work, because Publisher always crashes, when im saving. I already disabled "show exampels" in the studio panel and also the hardware accelaration. But the problem stil exists. It worked fine for several hours today. I saved the document permanently. The main work in the last hours was replacing the pictures in it. But now it doesnt matter which picture Im working on, Publisher will crash while saving. I worked in the 1.10 release Edition und also tried the newest Beta, but no change. Is there somone who can try to fix the document right now. I need the book to get printed. Thanks for help.

I have uploaded the file at the given link. I hope you can fix it.

Hi, I have an specific Affinity Publisher file, which works properly. But when I try to export it to PDF, APub isn´t able to create the PDF. The export works fine with other similar files. I already tried to export with different Publisher Versions (1.9.0, 1.9.1 beta and now the official 1.9.1), but the export always gets stuck at around 40%. While Apub trys to export the file the RAM usage rises up to 11000 MB. It seems to be a bug in the file. Is there anyone who can fix the file? I would send it to you in a private message. Thank you very much in advance

Thank you very much. Im impressed. I didn´t expect you guys can help me with this. Thats great, it saved a lot work for me.

Thank you very much. It works. Awsome. Do you have any idea wich elements are problematic? Would it for example be better to unpin the pinned objects at the master page? Or could it be the connected symbols in Designer (are there problems connected to the symbols function known?)? Should i disconnect the symbols to be safe? In some cases (e.g. the task numbers) i copied the text frame together with the text (shame on me). Do you think that could be a reason to? Would it be better to delete this elements and create new one?

Hi, i created a new document in the beta version and tried to copy all elements of the corrupted document. Therefore i opened the old docment in the retail version und the new document in the beta version. Sometimes, while copying, crashed the old document, sometimes the new one. But afterwards I could work fine with it. But now it seems the document is corruptet again, because it always crashes while saving in the beta version. Its really annoying. Is it possible to find out which element exactly causes the crash? Because i work with connected symbols, with assets and a lot of pinned objects at the master page. Just when im going to rebuild the document it would be great to know which elements i shouldn´t copy from the corrupted document. Here is the crashlog and the document. 19e6f143-1837-4ed2-8ae1-6a7c8b3f03b9.dmp d444f3c7-53e9-4226-a123-e06db6f12e1a.dmp 64bc3027-0b39-41c4-8b87-cf824b2c5039.dmp neuer Versuch.afpub

Thank you for the quick answer. I feared that this is a problem with the document. I will start rebuilding it in the beta version. Is it possible to just copy the elements into a new document or will it lead to the same problem?

I created a document with many pinned objects, symbols und Assets on the master page. After some crashes in the retail version i downloaded the latest beta version of publisher (422). But the document keeps crashing while saving. Every time i want to save the document, publisher crashes, as well the retail version as the beta version. This only happens with this document (see attached file). Is there any possibility to use this document without rebuilding it? Here are the crash reports and the file first time in retail version.dmp last time in retail version.dmp last crash report in beta version.dmp erste_Versuche.afpub

I have the very same question. I tried to reapply a master page because I applied a new text style to an existing text frame at the master page. But it didn't apply the changes of the master page to the document page. But after reapplying it overwrotethe text frames on the document page.