AF Publisher: Chapter Sync

[Rudy Rogalsky]

In Books module, master pages do not synchronize. Other things do.

[bbrother]

This is not a bug. Unfortunately, it is by design that the master pages do not sync.

You can read about it in the help files:

Quote

If a master page of the same name exists in both chapters, the Style Source Chapter's version is copied to the target chapter without affecting the target chapter's version or any applications of it to pages. Both versions' names are unaltered, so consider renaming either or both to help distinguish them.

Here's the link to Publisher's help files → References → Books → Synchronizing chapters

https://affinity.help/publisher2/en-US.lproj/index.html?page=pages/Advanced/syncingChapters.html?title=Synchronizing chapters

[MikeTO]

It's really important that you finalize your master pages before duplicating a chapter as the template for the next chapter.

If you really need to change a master page and it's too tedious to make the same changes manually to all of your other chapters, your only recourse is to sync the masters (which will duplicate them) and then apply the duplicated master to all of the pages - then delete the original unmodified master from each of those chapters.

Cheers

[Rogalsky]

OK, I figured out that syncing does not update content. However, I still have a problem that, when I apply the after-sync master page to  a chapter, the fields at the bottom of the  master page show but the fields at the top do not. Can’t figure it out!

[MikeTO]

On 1/2/2024 at 7:56 PM, Rogalsky said:

OK, I figured out that syncing does not update content. However, I still have a problem that, when I apply the after-sync master page to  a chapter, the fields at the bottom of the  master page show but the fields at the top do not. Can’t figure it out!

Hi @Rogalsky and welcome to the forums. Are you using Running Headers? If so, this is a known bug in 2.3.0 which has already been fixed for the upcoming 2.4 release. I don't think this fix is included in the upcoming 2.3.1. release.

If this isn't what your issue is, could you provide more details?