DNA0101

I am going to post this issue for the developers as a usability problem. This predicament has wasted me and others endless hours sorting this design setting that needs to be more clearly mentioned. I found one line not even highlighted that makes all the difference on the Baseline help page.
"The baseline grid's Grid Spacing option overrides the leading value of frame text."
No mention on the Leading page that this will constrain your layout tweaking severely...and get you thinking it's a bug or you are an idiot. 🤨

What a confusion: Special layer, Layer layer, container, Artboard...
I hope Affinity will raise Artboards on higher level in v. 2.0 and give them a separate panel with the same rang as "Pages" in Publisher.
After all, pages, artboards... are all substrates or canvases which designers use to place the elements of their artworks on specific layers.

This only works with a special layer created in Affinity Designer. This allows you to work with many objects in a particular layer, ignoring everything except this layer. This way you can work with a very complex design without being afraid of accidentally moving objects on the bottom layers.

Why would you use Affinity Publisher if you can use text editors that are more suited to the type of text required for export to ePub or that export directly to ePub, Mobi, Azw etc.
Google Docs can output as ePub OpenOffice or LibreOffice are both capable with a plugin called writer2pub Sigil is another app ...and I think Scribus will also output to ePub. LibreOffice Writer will export to EPUB and Directly as EPUB

If they're going to spend time developing a function, I'd rather it be a function that wasn't Mac-specific. Many of us are Windows users.

If you install the free e-calibre it will change a PDF into Epub, MOBI or about anything else faster than it took me to type this
And it has a rudimentary editor to make small corrections if need be

Yes, now that I’ve checked, I can confirm that something went wrong with the styles in the table of contents. I set up a single style and then clicked on the individual anchors, deleting them one at a time “by hand” with the Del key. In fact, I noticed that it wouldn’t let me delete them before, because I wasn’t on the page where the anchor was.
I won't hide the fact that I haven’t yet grasped the subtleties of the problem (for example, I can’t say how I made such a mess of things), but the important thing is that it’s now fixed.

Also check your Baseline Grid settings for your document. These are in View - Baseline Grid Manager - .
 

and also for the individual text frame in View - Studio - Text Frame:

If the original text frame was not set to lock to Ignore Baseline Grid, and your document or text frame has a baseline grid (showing or not) then changing the leading may not necessarily change the line spacing. This is 9pt leading with a 48pt Baseline Grid:
 

Cheers,
H
 

Hi Tibreizh,
Welcome to Affinity Forums
Affinity Photo/Designer don't have a timeline nor support animated GIF's/animation.

Must be a different app running in the background hijacking it. I just tried setting up Alt + P on a clean VM and it's all fine. Glad you got it sorted. What if you press ALT + P now that it's not longer a shortcut in or app? Does it still break other shortcuts? 

Status: Beta
Purpose: Updates and Fixes
Requirements: Purchased Affinity Publisher
Windows Store: Not submitted
Download: Download
Auto-update: Available
---
Hi,
We are pleased to announce that Affinity Publisher Customer Beta 1.8.3.627 is now available as a download from the link above.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
This beta is an incremental update to the 1.8.2 version recently released to all customers (though it installs parallel to the release). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below.
---
General
Fix for AutoSave
Fixed issues with live filters making layers disappear
Fix for embedded documents not rendering at specific zoom levels
Fix for crash pulling out groups under an image frame
Boolean Operation fixes
Fixed possible crash saving documents containing embedded documents if there was a colourspace mismatch
Via Layer Panel, linked documents were being opened as embedded and edits were not being committed to the linked file
Shift-Invert selection behaviour with the Move Tool was broken
Resource Manager 'Collect' could collect multiple copies of the same placed image
(Mac) In the New Document dialog, 'Show in Finder' wasn't working for top level folder
(Win) Font Manager could be launched with Resource Manager
(Win) Fixed crash cycling through justification options in a table
(Win) Floating (undocked) panels were collapsing too small and clipping content
Page Management
Fixes for page operations that required spreads to be split
Page objects could be incorrectly rescaled when master page was resized
Text
Filler text is now copied to clipboard as the expanded text rather than as '<FillerText>'
Unpinning a node can scale it incorrectly
Fixed crash copying mixture of filler text and regular TextTool
Text > Upper Case could crash if the selected text was already Upper Case
Copy-paste Arabic text from docx comes as Chinese in Publisher
(Win) Some lines weren't correctly indented when using right align and right indent
Import
Empty (0K) files could crash the import process
Export
PDF Export was not honouring  gradient map's colour space
PDF Export images downsampling to the wrong DPI under certain circumstances
PDF Export was failing with placed documents in LAB colourspace
PDF Export of placed images makes more effort to preserve their colour space
PDF Export fix for export of objects  with empty clipping paths
---
To be notified about all future Windows beta updates, please follow this notification thread 
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

In my post at
https://forum.affinity.serif.com/index.php?/topic/108445-affinity-photo-file-sizes-much-smaller-with-ver-18/
I expressed my disappointment that Save As in APhoto Ver 1.8 would not reduce the huge file sizes of afphoto files originally saved with APhoto Ver 1.7.
Here is a simple procedure that will achieve this goal of resaving those huge, older Ver 1.7 documents  to the much smaller Ver 1.8 file format.
1. Open an afphoto file saved originally with APhoto Ver 1.7 (that afphoto file will be huge compared to the original jpg camera image)
2. Rename the background layer to Background-OLD (to avoid later confusion)
3. Open as a new APhoto document the original jpg file that was used in the Ver 1.7 file
4. Rename the background layer to Background-NU (to avoid later confusion)
5. Select and copy all layers including the Background-OLD layer from the original Ver 1.7 document
6. Paste all these layers from the Ver 1.7 document into the new document that contains only Background-NU, that is the original camera photo
7. Delete the Background-OLD layer
8. Click Save As to produce a new Ver 1.8 afphoto file. It will be identical in appearance to your original Ver 1.7 file, but it will be far smaller in size.
In one of my test cases, I had a jpg photo from my camera that was 8,204 KB in size. Using APhoto Ver 1.7, I had cropped the image and added a pixel layer plus 6 adjustment layers. Some adjustment layers affected only selected portions of the image. The pixel layer was used for some Inpainting fixes to the original image. Using Save As in Ver 1.7 the resulting afphoto file was 52,175 KB, about 6.4 times larger than the original jpg file.
After following the 8 steps above (copying all of the Ver 1.7 layers to the Ver 1.8 document and then deleting the old background layer copied from the Ver 1.7 document) the resulting afphoto file was only 19,091 KB. This is only about 2.3 times larger than the original jpg from the camera. Because I had also cropped the image in Ver 1.7, I first had to Unclip Canvas in the Ver 1.7 document and then crop the image in the Ver 1.8 document so that all adjustments and the pixel layer would be aligned.
 
 

Status: Beta
Purpose: Stability and General Testing
Requirements: Purchased Affinity Publisher
Windows Store: Not submitted
Download: Download
Auto-update: Not Available
---
Hi,
We are pleased to announce that Affinity Publisher Customer Beta 1.8.2.603 is now available as a download from the link above.
If this is your first time using a customer beta of an Affinity app, it’s worth noting that the beta will install as a separate app - alongside your store version. They will not interfere with each other at all and you can continue to use the store version for critical work without worry.
This beta is an incremental update to the 1.8.0 version recently released to all customers (though it installs parallel to the release). We recommend that you use this beta in preference to the store version if you are affected by any of the issues listed below.
---
StudioLink: We have updated StudioLink to ignore the 'patch' version when checking compatibility. StudioLink should be enabled if any corresponding version 1.8 product is available.
---
General
Fix for bleed not available in Photo Persona New document panel - terminology and UI tweaks New document panel - saves settings between uses. (Mac) Fixes for blurry icons on non-retina screens Document Management
Stability and performance improvements adding and deleting pages Fixed issue with sections being incorrectly deleted when pages deleted (Win) Fix for inability to scroll through whole document in certain circumstances Geometry 
Stability and performance improvements for geometry operations Text
Fixes for Catalan Hyphenation (Mac) Fixed crash typing into Font name selection UI Hyperlinks
Fixed issue exporting caused by hyperlinks Import / Export
XLSX - File import improvements (Win) PDF Export - PDF X4 convert image colour space was not available IDML Import - crash fixes for specific documents IDML - import of hyphenation ---
To be notified about all future Windows beta updates, please follow this notification thread 
To be notified when this Publisher update comes out of beta and is fully released to all Publisher customers, please follow this thread

I did a simple test: copying and pasting some text containing 2 URL in Libre Office, and exporting this à .docx
Next, I place this file in an existing APub document: the 2 links are visible in the links panel (I use the French version, not sure of the exact name of this panel).
Why can't you do the same in a blank document, to apply the needed text styles to those paragraphs and URL ? It's easy, since there's a small button at the bottom left of the Links panel that you can use to show and select the text of the link. And there's already a character style applied that you can personalize.

I don't have any idea how it might work with Wordpress. However, all the hyperlinks (of any form) that I just used in a .docx file produced by LibreOffice were properly recognized when I Placed the .docx file. So if you can get them into LibreOffice and they are recognized there, they should be recognized by Publisher based on that experiment I just performed.

Hi Ulysses,
There's already plans to implement a non destructive Develop Layer in Affinity Photo. Check the roadmap for more info on other things coming in v1.x. Other improvements may come in future versions. We are only in v1.6...

Hi MEB,
Thanks for clarifying. I get that, and I always used Bridge + Camera RAW + Photoshop before I had LR. The difference is that when I have gone through that process with Camera RAW I still have the same RAW file (which I can open in any other program) + a puny xmp file of a few kb that allows me to go back and tweak the developing at any time, continuing right where I left off. I just assumed that Affinity worked along the same principle and was very surprised to find that in order to save my edits in a form that allows me to go back and continue to work on the photo where I left off, I have to save in a format that is an order of magnitude larger than the original RAW. Seems like a very odd solution to me, and I'm afraid it will disqualify an otherwise very nice program as my first choice.

Hi svinto,
Welcome to Affinity Forums
Affinity Photo wasn't designed to manage libraries the same way as Lightroom or another DAM software does. It doesn't use databases neither XMP sidecar files to store edits, not is able to apply the same settings to a bunch of images from the same photoshoot. It's mostly a RAW converter/developer and photo editing app that offer a similar workflow to Adobe Camera RAW + Photoshop where you typically open a couple RAW's to develop (recover shadows, general tone adjustments etc) then move to Photoshop for further localised editing. In Affinity that would mean open the RAW (which is displayed in Develop Persona) for global adjustments/development (as in Adobe Camera RAW) then pressing Develop to move it to Photo Persona for localised edits (which would be the equivalent to moving to Photoshop for further editing).

Hi @DNA0101,
Apologies for the late reply, the first issue you have reported should be solved in the latest beta.
I've exported your files in 337 and the hyperlinks seem to function as expected.
Can you let me know if you have any issues with this file in the current beta?
Thanks!

It does work but can be a little confusing at first
Basically, there are 3 parts:

A>Set up you Styles
Create Styles in Paragraph Styles for your headers {what you want to define as TOC content }
B. Create TOC Text Frame in Document
1. Add Text Frame
2. Insert TOC either from Text/Table of Contents/Insert Table of Contents or Top Left Icon on TOC Panel [Without anything selected you should see 'No Table of Content Entries Selected']
3. Open View / Studio/Table of Contents Panel
4. Make sure you have a text frame selected
5. Select style [applied to title/header/chapter name etc..] from the visible defined styles list in TOC Panel [checkbox]+page number checkbox if required
This should add a basic list of headers and page numbers for the location of the defined style on pages in the document
C.Define styles for use in TOC
You can apply styles to the TOC using TOC dropdown on the Table of Contents Panel [Click menu to create new]
When you create a new Style name here 2 new Style (1Para+1Chr) Entries get added to the Text Styles panel. They exhibit the prefix of the TOC Style name [myStyleName:xxxx].
Edit these Styles to define the appearance of the actual TOC on the page (one for the TOC List;one for the TOC Page Number)
 
There is also a tutorial video available to help you:
https://affinity.serif.com/en-gb/tutorials/publisher/desktop/video/286545105
 

Hello @DNA0101,
if your goal is to have headings in the TOC that do not display a page number you can achieve this.
Just look for the character style that is assigned to the page number and edit it. Under 'Style > Character > Colour & Decorations' you click on 'Text fill' and there you can assign 'no fill' this particular style. That way the numbers will not be displayed. See attached screenshot.

I also append my test document for you to investigate.
d.
TOC.afpub

Hi Adam,
Why do you hide your update notes under "Bugs" and not  put them where one would normally expect to find them, i.e. in "Announcements"? I don't start my day by reading the Bugs column  of AP.
I opened up AP and it forced me to upgrade. No problem.  But with the upgrade should come a ReadMe or something that lists the new/upgraded features.  Your explanation of the "pinning" feature isn't that good either.  The product is not ready for prime time but keep going.

I have seen nothing that indicates that such a ToC can be constructed automatically.
However, you can place the section name for each section in a text frame on the first page of each section, using a unique text style, and include that text style in the ToC. When you do that you can tell Publisher not to show the page number for that text style, and you'll have something like you want.
Note that you can even somewhat automate the process by using a Master Page for the first page of the section, with a text frame into which you've inserted a field to contain the section name. (View > Studio > Fields, then with the text cursor in a text frame double click on the field name Name in the Document Sections part of the Fields panel).
I've done something similar (without the Master Page for the sections) in the attached .afpub file.
 
Toc-with-sections.afpub

In the Section Manager panel, it would be handy to be able to double click on the section on the left and go to the page.

Thanks for the clue as I was starting wonder if it was a bug. My font spacing on both font sets were too spread out. Now I can move on...