Hangman

Hi @Jenium,
That's no trouble at all, glad it resolved your issue...

Thanks for verifying, I've noted this in the development log

Hi Kuba,
Thanks for confirming...
This is unfortunately a known bug in the release version of Publisher 2.2 which appears specific to the Euroscale Coated v2 ICC profile, logged as AF-370 and currently being investigated by @Dan C.
It's interesting that you're experiencing the issue on Windows as I believe all other reports to date have been on macOS Ventura (though I could be wrong here)...
Could you let us know:
Which version of Windows you are running? What language is the Affinity app set to under Affinity Publisher 2 > Settings > General? What language is your PC set to, through Start > Settings > Time & language > Language & region? I'm going to link this thread to the main thread so @Dan C can reference your post as part of the testing process.

Welcome to the Forums @LambdaRed & thanks for your report!
As mentioned above, this is an issue our team have identified and are currently working to resolve - this is the first report I've seen from a Windows user, however we believe the cause of this issue may be due to an update to the PDF Library Affinity uses when exporting files, which would mean the issue can be experienced by Affinity users on any platform.
I'll be sure to update the development log with the details provided above now, and our team hope to have this issue fixed ASAP.
I hope this helps  

Hi @K_T and welcome to the forums,
With a text frame selected go to Layer > Convert to Curves. Equally, you can leave the text editable and convert it to curves on export if exporting to a PDF file. The option appears in the Advanced section of the PDF export dialog under Embed Fonts > Text as Curves.

Thanks @Hangman!  I'll give that a shot...

Just to add, the additional ÿ with diaeresis character at the start of the profile name is unique to 2.2.0 (both Beta and Retail) in both Designer and Publisher. Using the identical profile in 1.10.6 and 2.0.4, again in both Designer and Publisher, displays the profile name correctly. I'm using English for both my system and Affinity languages.

Nothing to apologize for and I agree, this does look like a bug, I think it may actually already have been logged as a bug a while ago... The 'issue' appears to be when you have nested adjustments.
When an adjustment is nested to a group as per your file then this seems to prevent the group with the nested adjustment from being partially marquee selected.
  When an adjustment is nested to an object this seems to prevent the object with the nested adjustment from being partially marquee selected even when 'objects' is the Auto-select option.
  When the adjustment appears above the object within the group then 'Auto-select Default' correctly selects the groups and 'Auto-select Objects' correctly selects the objects within the groups when using a partial marquee selection. Left - Adjustment Nested to the Group | Middle - Adjustment Nested to the Object | Right - Adjustment Above the Object Inside the Group

 
Screen Recording

Marquee Selection v3.mp4

Hi @purplie,
Try changing the 'Auto-select' option to Objects...

Marquee Selection.mp4

1) I am using Tab. 👍
2) I opened up your file and as soon as the chapters synchronized the pages changed and I had the same problem trying to update the section page numbers (using Tab, of course)...
The solution offered by Hangman seems to work as he stated. I will either have to forsake this strategy or remember to update the section page numbers, until they get around to fixing this.
All, thanks for your help!

Thanks. On quitting and re-opening, it worked fine. I think maybe the issue was the file I was editing. I took a screen grab, and rather than wait for it to appear on the Desktop and open from there, I dragged the preview icon directly into Affinity Photo, so perhaps it was trying to export to the same location as the original file, but was unable to find it? That's my theory anyway. If I have the same issue I'll try your remedy. Thanks.

Thanks, I'll add the extra detail to the other thread

@NathanC,
I can certainly confirm there is an issue here...
A very quick test shows that every time new artboards are added to the Designer file and the Publisher file is re-opened, all the placed artboards in the Publisher file are reset to the first artboard and a random selection of placed .afdesign pages are then shown as missing in Resource Manager.
I've yet to test vector cropping any of the placed files...

Signs.mp4

For avoidance of doubt, .mov screen recording converted to .mp4... A known and logged bug as mentioned above...

Light UI.mp4

Hi All,
I have logged this to be investigated further by our developers
Thanks
C

@MikeTO - I'll start off by admitting I have not had a chance to read this cover to cover - so far I have merely dipped in and skimmed in a few places. However what I have seen seems very well presented, informative and accurate. I would like to thank you for making this available as a free resource and also take this opportunity to thank you for your contribution on the beta forums which has been both notable and significant.
Adam Whitehouse
Project Manager, Affinity Publisher

Hi @Nixerman and welcome to the forums,
If you've already created your slices, changing the artboard names won't automatically update the slice names, you'd need to delete any existing slices and recreate them for the artboard name change to be reflected...
Just toggle the layer visibility on or off in the Slices panel for the slices you want to export then only the visible slices will be exported...

Not that I can see...

Hi @Cealcrest,
With regards to your 'first page glitch', you have the same outer shadow FX applied to both your picture frame and the picture itself, pastedImage-7.png. If you remove the Outer Shadow FX from the picture your file should then export correctly.

I'm not actually seeing an issue with your 'second page glitch' file when exporting page 2 either with or without the Outer Shadow FX applied to both the picture frame and the picture but I suspect it's caused by a similar issue...
For your David Brock Smith flyer, the issue is that exporting to PDF (for print) or PDF (press-ready) doesn't support the unflattened transparency of the Outer Shadow FX for either the red band across the top of the page or for the US flag.
This can be seen by exporting using either PDF/X-1a, PDF/X3 or PDF (flatten) presets or by changing the Rasterise Unsupported Graphics in the Advanced Export section for the other PDF presets to Everything, (though the latter will rasterise all the text as well), all of which will flatten the transparency and overcome the issue.
So your options are to either export using either PDF/X-1a or PDF/X3 (Note: you'll see the same issue exporting using PDF/X4) or to rasterise the red band and flag layers unchecking Preserve Layer FX when asked.

Doing this for both the red band and the flag then allows you to export the file using either PDF (for print) or PDF (press-ready).

Thanks. Yes, I see it. A simpler solution to the adjustment.
Still, the glitch is an error, but I'll have your approach in mind next time I do this sort of thing.

[Updated Nov 30 2023 - new version for Publisher 2.3 with 120 more pages than the first version]
Learn how to format text and publish books and other long documents with Affinity Publisher 2.3. This free in-depth manual is filled with steps, tips, and recommendations for:
Character and paragraph formatting - added Nov 30 Text styles - added Nov 30 Documents, Pages, Master Pages, Sections, and Baseline Grid Text Frames, Text Flow, and Stories Books and Chapters Cross-References, Table of Contents, and Index Notes - including Footnotes, Sidenotes, and Endnotes Fields - including Page Numbering, Running Headers, and Custom Variables Anchors and Hyperlinks Printing and Exporting Settings This manual does not cover objects and photos so it covers approximately half of the topics.
Updated version:
Publisher Manual Nov 29 2023.pdf
 
Q&A
Is there a full manual I can purchase? No, this is all there is. Is this really free? Yes, I'm making it available free of charge. It's copyrighted to prevent others from publishing it as their own. Is there an iPad version? No, the steps and screenshots are for the macOS and Windows versions. Is there a version for Designer or Photo? No, but the text features are largely the same so you may find it useful. Why does it use a print layout if it's a PDF? It's a demonstration of how to use the features it describes to create a print book. Original version:
Publisher Manual Sep 26 2023.pdf
Publisher Manual Sep 18 2023.pdf

Hi All,
We have just made 2.2 live across all App Stores and our website. As always, the feedback we have received from you all during this beta has been an incredible help in both shaping the new features as well as squashing many bugs!
The build we have released is the same as RC3 (build 2005), meaning for the time being whether you use the latest beta version or switch to using the release version they are the same. If you anticipate taking part in the next beta you may wish to keep your current beta version installed, as this will be updated on auto update when a new beta is available. This will either be a 2.2 patch if we feel one is needed, or moving straight onto a 2.3 beta.
It would be impossible for us to do what we do without your support, and I just wanted to say a huge thanks for everything you have contributed to this release.
All the best,
Ash

Hi Hangman,
I've logged this to be improved in a future update.
Thanks
C

Hi @Hangman,
Thanks for providing detail along with sample files, I can't see this being as expected with it being a significant behaviour change between versions as is more likely a regression over V1. I've replicated the issue and logged it with the developers. 

Hi @NathanC,
I would agree... one thing I forgot to mention in the original post is that you can copy and paste individual lines of text (cells) from the on-page table created in Publisher to a table based on a Master page...
Many thanks for logging...

Hi @Hangman,
I'm leaning towards this being unexpected behaviour, as despite a table being a master page object you're fully able to edit it's contents (other than the actual formatting) so I would expect it to at minimum copy the content of the table in similar to what's happening with the 3rd party app copy/paste, so i've logged this with the developers.