No baseline grid when drawing a new connected text frame

[rubeekon]

Hello all,

this is more to draw attention to a possible problem; I solved it by using an earlier document version via Apples Time Machine (System: Catalina 10.15.3, Affinity Publisher 1.7.3, Macbook Pro 16 inch).

I am producing a 100 page magazine on chemistry and biology, for the first time in Publisher (come from InDesign). As the magazine layout is to be re-invented, I worked with new paragraph styles and so on, also using the search function. Unfortunately "search" does not allow to search only in a text selection... Short to say: I cant explain exactly what I was doing when the malfunction occured.

The malfunction was: After a time I wanted to draw a connected text frame, starting from an existing one, formatted in the right way with baseline grid, and hiding some additional text. But whatever I did: Every new textframe did not align to the baseline grid. I tried to press all necessary buttons  

CLB01-02-2020parfum.afpub

[Patrick Connor]

Sorry.

Thank you for reporting a problem using 1.7.x . It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script.

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the current 1.8.3 release build.