MikeTO Posted July 16, 2023 Posted July 16, 2023 This isn't new but it is serious - there's no way to add a page before page 1 if its story is in a master text frame. frames on page.afpub frames on master.afpub With these test documents: With "frames on page.afpub", add 2 pages based on Master A before page 1. It works well. With "frames on master.afpub", add 2 pages based on Master A before page 1. The story on the three existing pages will be lost. The new page 1 has a frame not linked to page 2. I think that it should be linked to page 2 but this is okay. The new page 2 has a frame linked to page 3 which was previously page 1 - this is okay. But the story from old page 1 (now page 3) should now start on page 2 but instead it is lost. Or maybe it's orphaned and not attached to a frame but it's in accessible with Find and Replace. With "frames on master.afpub", add 2 pages based on master Blank before 1 page. The story will be lost again. The new page 1 is blank as expected. The new page 2 is blank as expected. But the story from old age 1 (now page 3) should still be there but it is lost. I imagined that in the previous scenario the story was lost when merging the stories for new page 2 and old page 1 but no, the story is just being lost even if a blank page is added before it. With "frames on master.afpub", add 1 or 2 pages based on master Blank after page 3. This works fine but then drag those new pages before page 1 and the story will be lost again. There's just no way to avoid losing the story in a master frame if pages are added before it. Screen Recording 2023-07-16 at 12.40.08 PM.mov razorpig 1 Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
MikeTO Posted July 16, 2023 Author Posted July 16, 2023 BTW for anybody struggling with this, there's an easy workaround. You need to make the story that would be lost the second story. Break the link between the frames on pages 1 and 2. Click in the frame on page 1, which contains the entire story now and is overset (overflowing) and choose Select All and then Cut. Click in the frame on page 2 and paste the story in. Now you can safely add pages before page 1. When you're done, you can re-link that empty frame on what used to be page 1 to the frame on what used to be page 2 and the story will move back to where it used to be. razorpig and Oufti 2 Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.5, MacBook Pro (M4 Pro) and iPad Air (M2)
walt.farrell Posted July 16, 2023 Posted July 16, 2023 Happens on Windows, too, for what it's worth. MikeTO 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.5, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.5
Dan C Posted July 17, 2023 Posted July 17, 2023 Hi @MikeTO, Thanks for your report! I can confirm that a member of our QA team spotted this issue recently and therefore it is already logged with our developers as a High severity issue. I'll be sure to 'bump' this report with your post now - I hope this helps MikeTO 1 Quote
razorpig Posted August 2, 2023 Posted August 2, 2023 Thanks MikeTO ! That's fantastic. Very relieved I don't have to do it all again. Hope they can fix it soon Quote
Staff Affinity Info Bot Posted November 15, 2023 Staff Posted November 15, 2023 The issue "Adding a spread prior to Page 1 in a document is causing all text to disappear" (REF: AF-458) has been fixed by the developers in internal build "2.3.0.2139". This fix should soon be available as a customer beta and is planned for inclusion in the next customer release. Customer beta builds are announced here and you can participate by following these instructions. If you still experience this problem once you are using that build version (or later) please reply to this thread including @Serif Info Bot to notify us. MikeTO 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.