Jump to content
You must now use your email address to sign in [click for more info] ×

marbel

Members
  • Posts

    7
  • Joined

  • Last visited

  1. @natecombsmedia In fact, that solves the issue! This means, copying an existing document sets a fix start page number for that document? I wouldn't expect that to happen! That's why I didn't check that numbering option... Once I change it as per your video, it is working fine. Thanks for the hint!
  2. @Lee D I just tried the beta 2.2 (1954). With newly created documents it is working now. But: I copied a document of my book and added the copy to the end of the book. For that document, Publisher won't update the numbering. The numbers from the original document remain in the copy. I now removed all content from the document, you can find it attached. Its a book with 2 chapter documents, which both are binary identical. Would be great if this can also be fixed soon. Thanks! Markus Book.afbook Chapter 1.afpub Chapter 2.afpub
  3. For the system spec, see below. After updating to 2.1.0, publisher won't update page numbering for books anymore. I can reproduce it with new documents. Here's how: Create new document (I used A4, no changes) Save it (e.g. "A4_1") Create another new document (A4) Save it (e.g. "A4_2") Create a new book Add both new documents You will see both chapter files with their page numbers First: 1-10 Second: 11-20 Now drag&drop the second to first place, they won't get the page numbers renewed: First: 11-20 Second: 1-10 You can click the renew numbering button, but nothing will happen I also attached the created docs and book for your reference. BTW: It was working in 2.0.4. ---------- Using latest released version 2.1.0 of Publisher OS: Windows 10 22H2 Hardware acceleration: On book.afbook A4_1.afpub A4_2.afpub
  4. You are right, there was some formatting issue, whereever that came from. I now also managed to have the frame where I want it to be. Just for anyone who may have the same challenge: Do not move the notes frame in the document. Instead, create a new text frame at the place where you want it to be, connect the notes frame with the new text frame and resized the notes frame so that no text fits in 🙂 Many thanks for your support!
  5. I now managed to repair the document by going one-by-one through each connected text frames, copying the text, deleting the frames, creating them newly and finally paste the text in again. After that, setting a note works. But I now have a mis-placing of the notes. Any ideas how to align the notes and title again? And I now know how the document breaks: The frame for the notes must reside at the end of the document (or maybe at least after the last frame containing a note). Once you move it up in the document, it will break. Unfortunately I have to re-think my approach then (I wanted the frame at the beginning to fill some spare space)...
  6. This document was newly created from scratch and I was able to reproduce it. By using Document wide instead of Custom (as proposed by Old Bruce) I managed to get a valid numbering in a new document. The weird thing is, that it is now also working with Custom set in a new document. I can confirm what MikeTO wrote: Notes being added to a broken document are somehow "disconnected", navigation does not work. I've once seen this strange page adding also. Sadly, it seems that a once broken document is not fixable. My main document (not the sample I uploaded) is broken and I did not yet manage to recover it 😞 I guess there is no way to "reset" (wipe) any notes in an existing document somehow?
  7. Hi, I am using Affinity Publisher in version 2.0.4 on Windows 10 (22H2) on a desktop PC. When I use document wide endnotes and a common document frame, the numbering within the frame is broken. Only the first endnote gets the correct value 1, but all others get a 0. Anyhow, in the text the numbering is just fine. To reproduce, just create a new dosument, place some text frames, configure the endnotes as described (Document wide, one common document frame) and set some endnotes in the text frames. I assume this is a bug, or am I doing something wrong? BTW: Just tested with the BETA version (2.1.0.1730) and it behaves the same. Endnotes.afpub
×
×
  • 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.