Petar Petrenko

That is why book feature is needed in Pubisher. To keep styles and settings on sync.

That would really be great and would push Affinity Publisher ahead of other players.
Meantime, you can pin your picture to the Title (you can do it right now) and then you can use Paragraph Decorator to hide the Running Header with a think white line.

It isn't actually a page break, it is a next-frame break. It only acts like a page break if one has single threaded text frames on each page. But if there are two or more threaded text frames on a single page, the numpad Enter key moves the insertion point to the next threaded frame on the same page.

Please, add tooltips (or labels) over these 4 fields. It is not so easy to remember them if used occasionally.

Why complaining? You had a trial period to try the program. Why you bought it if you didn't like it at all? You had to search through the forums at first, to see the frequency of new versions and then make your decision.

Please, add tooltips (or labels) over these 4 fields. It is not so easy to remember them if used occasionally.

Please, add tooltips (or labels) over these 4 fields. It is not so easy to remember them if used occasionally.

I think the only problem here is that Affinity didn't included in their roadmaps they will work on iPad versions of their software and on Publisher before they are going to finish the 1.x cycle. Once they do that, new versions will come faster.

The functionality to switch between artistic and frame text would be a great addition to Designer... Illustrator's implementation of doing this (double click a specific node on a text object, or right click > convert to...) is a perfect example on how it should be handled.

Here's a thread with a whole bunch of other people wanting this as well.

Again, a topic conjures up fond memories of FreeHand.
FreeHand had just one kind of text object. It could be set to auto-expand horizontally (i.e., becoming functionally equivalent to a so-called "art text" object in other programs) by simply doubleClicking the right middle handle. It could be set to auto-fit its contained text vertically by doubleClicking its bottom middle handle. The text objects could be bound to and released from paths (instead of being treated as a separate "path text" object). They could be threaded, whether bound to a path or not. They could be set to auto-expand when bound to a path, thereby preventing the problem of accidentally truncated text in complex maps, as is so chronically common in maps built in Illustrator.
This is conceptually parallel to the fact that FreeHand also never had any need for two separate selection tools. Its single selection tool enabled you to edit paths at the whole object level and at the node editing level. That elegant interface design made path drawing far less tedious, more fluidly efficient, and more powerful than any drawing program that insists on following Adobe's hideous model of two primary selection tools.
Macromedia finally gave in to ill-advised "demand" from Illustrator users to add a second pointer tool. When added, it provided absolutely no additional functionality. It was literally nothing but an accommodation to Illustrator-habituated users who just refused to learn that it was absolutely unnecessary. FreeHand users simply ignored it. It was not until FreeHand's very last version that its white pointer did anything that the black pointer didn't, and even that was a minor detail that could have been implemented without adding another tool.
Despite Illustrator's two selection tools (three, really, when you include the ill-conceived "Convert AnchorPoint Tool")--actually because of it--Illustrator to this day does not "know the difference" between a path being selected at the object level versus merely having all its AnchorPoints selected. This causes all kinds of silly inconsistencies such as being unable to use the Break Anchor Point command when all of a path's Anchor Points are selected. (You have to unintuitively de-select at least one Anchor Point for it to work.)
Because object selection is so bedrock foundational to an object-based program, its tedious effects "cascade upward" throughout the program's interface. In a nutshell, it's what makes working in Illustrator feel as frustrating to beginners as trying to eat spaghetti with a single chopstick.
It's because Illustrator's white pointer behavior is conceptually "upside down" from intuition. It's the selection tool you have to use to edit a path.  But its first click always selects the most "internal" sub-part element of whatever construct you are trying to manipulate. Rather than intuitively selecting an object of interest and then "digging down" to its subparts with subsequent clicks, Illustrator's scheme first selects some "molecule" of the object of interest and requires use of a modifier key and subsequent clicks to "back out" of it to each next higher level.
It's metaphorically like getting up in the morning and needing a pair of socks. So you intuitively try to open your sock drawer. But your hand passed right through the closed drawer, and the only thing you can grab is a single thread of a single sock. So you have to then use both your hands to select a single sock, and grab again with both hands to grasp the folded up pair. All this "Bizzarro World" behavior instead of simply opening the drawer and grabbing the pair of socks.
The beginning of the end of FreeHand was not the Adobe acquisition. It was when it started to emulate Illustrator's hideous interface.
Unfortunately, because things like selection tools and text objects are foundational to the program built upon them, I'm sure it's too late to back-track the existing conventional-wisdom (i.e. "like Illustrator") in either case. But I say again: If you want to build a better drawing program, Adobe Illustrator is not the program to emulate.
JET

Design your business card and save it "Business Card 1" Create a new document, and place Business Card 1 as a linked, embedded object. Use Power Duplicate to create array of (say 3x3) cards.
Note: You only ever need to do this once for each size of card that you make. Save this file as "3x3 Business Cards". From now on laying out new business cards takes seconds…
Create your new business card and save as "Business Card 2" Open 3x3 Business Cards. Use the Resource Manger to replace the existing card with Business Card 2. Done.

 

Yes, I did. It is similar in methodology to the transform command in AI, but it is not a step and repeat command. Using the business card example, I have my 2x3.5 business card file placed on the artboard, I select the file, and select Transform Each (in Illustrator) and I can set the amount the file will be copied, say horizontally by 3.5 inches, and then select both instances of the file, Transform each again and copy the files vertically by 2 inches, and the use the transform again command to fill in the page.  This can be made into an action, so you really only need to select the first file and run the action to do what you need to do. In indesign, you can use the step and repeat tool and create as a grid and do it in one click.
The way affinity publisher and designer handle this is (in my opinion) kludgy and isn't fast. You can ctrl+alt drag the file to copy it and place it where you like, then select the 2 files and do it again, then you can use the duplicate command until you fill the page, then you have to go back and make sure the files are placed correctly using the transform tool which takes time. OR, you can select the first file, then hit ctrl +j, select the new duplicate, set it's position using the transform tool, select the 2 placed files, use ctrl +j to duplicate, then set the position using the transform tool because the duplicate command doesn't duplicate item positions if you set their positions using the transform tool, and repeat that ad nauseam until the page is full. This is not macroable as far as I can tell. I could probably setup the file with guides and use the snap function to ease the correct placing of the files, but I prefer to set the precise location of duplicated items using the transform tool. Why eyeball it when I can place it precisely where I want it?
I have been using design software professionally for a long while, and honestly this is not acceptable TO ME in a professional design suite. Time is money, and having to manually position duplicate files takes time. The minimum acceptable solution is the ability to macro the common layouts I use, but a strong and robust multiple duplicate tool is what I want and need in a design program. Sorry about the essay, but I really do like the software and would like to see it have a suite of good and useful tools (while avoiding bloat), and I feel I really need to explain what I would like in the final version and what I don't like in the current beta.
TLDR: Printing tiled isn't a good option, thomaso's suggestions work BUT aren't great and the current duplicate tool needs a whole lot of work to meet my needs as a user

Hi,
is it possible to add a dialog for missing font similar to the one when opening PDF file?



 

Due to an issue discovered with the management of placed documents e.g here, here and the fact that document corruption can occur, we have chosen to remove the download links to Build 330. We will post another update to rectify this issue as soon as possible.
If you have already downloaded 330 you may wish to consider reverting to Build 312, but be aware that due to new functionality in the later build, documents saved in 330 may not load in 312.
Thank you for helping us find this issue.
---
Please note Build 330 fixes the following issues in Build 326. Build 326 has been withdrawn and we encourage you to update if you are using it.
- Converting an Embedded resource to Linked could delete the original resource
- Replacing Image on a placed PDF could leave Resource Manager in an inconsistent state
- Crash copying and pasting embedded document resources
Thank you for reporting these.
Status: Public Beta
Purpose: Stability and General Testing
Requirements: 64 Bit Win 7 SP1 / Win 8.1 / Win 10  (>=1607)
We are pleased to announce Affinity Publisher build 330 is now available as a manual download from the link above. To be notified when there is a new beta please press follow on this announcement thread
As this is a beta it is considered to be not suitable for production use. This means that you should not attempt to use it for commercial purposes or for any other activity where you may be adversely affected by the application failing, including the total loss of any documents. 
We hope you enjoy the product, and as always, if you've got any problems installing or running up, please don't hesitate to post in this thread.
Any problems actually using this version please make a new topic in this forum and we'll get back to you as soon as we can. Please feel free to leave general suggestions and comments in the Discussion Forum. 
Many thanks for your continued feedback.
---
Fixes and Improvements 
A Note about Linked Images
Backing data and hi-res previews are now discarded for linked images when the containing document is saved, resulting in a drop in Publication file size. Please note that unfortunately this will not apply for linked images in existing documents, they will have to be replaced in order to see an effect. When a document with linked images is opened you may now momentarily see a low-res preview before the full image is loaded and 'pops in'. This is expected behaviour.
Other Fixes
Menus / Studio
(Win) Docking Pinning Panel to the left/right causes crash on next run up
Deleting global colours could cause crash
(Mac) OS accented colour set to Graphite now works correctly for font controls etc
Fixes for Expression Parser
Tools
Fixed selection of Picture Frames from Masters
Vector cropped object in Picture Frame now scales correctly
Text / Tables
Fixed noticeable text lag under some circumstances with Character Panel visible
Fixed auto-correct crash e.g. typing (a)
(MacOS) Ctrl+Alt+Tab in a table inserts a tab and switches document
Prevented deletion of entire cell range with non contiguous selection
On converting a shape to a text frame the context toolbar now shows the correct text tools
Fix for Find / Replace All when found ranges were adjacent
Resources
Improved locating missing resources on file load
Fix for Resource Manager incorrectly reporting resources as modified under some circumstances
DocX improvements - fixes for lists, colours and paragraph run properties
---
Earlier Release Notes Beta 312

Yeah Sean. it's really good and even faster and better than InDesign.
Thank you very much for you time and effort helping me to solve such a big transition problem (Quark, InDesign -> Publisher) for me.
Now waiting for footnotes only. I hope they will come (very) soon.

Then use Find and Replace to find the characters you want to apply the style to, and apply the style using that. See attached video.
ReplaceStyles.mp4

Is there anyone who doesn't have them?  

Sorry was not paying enough attention (or rather was distracted by a toddler!)
@dutchshader has the answer.
It is a real shame that corner tool radius can't be specified (and retained) as a percentage.

select the F and with the corner tool click "bake corners"

Hi,
I would like to suggest you to allow negative values for the bleed as an option. I am used to add bleed to the page size and negative bleed will just do the job for me.
Yes, I know that I can add guidelines or adjust the margins, but this is much simplier to do. Bleeds and margins can be visible at the same time on the page and easier to work.

+1 for footnotes and endnotes.
I think "sidenotes" are solved now by adding the new feature -> pinned objects.

Since Publisher is still in beta you probably should be posting this to the appropriate Publisher beta forum.

Thanks for reporting this and the confirmation, I've reproduced it here and logged it.

Confirmed. Any use of "Apply Body to Paragraphs and Preserve Local Formatting" gives me an instant Publisher crash on Windows.
Serif: If these .dmp files were uploaded by Publisher they're my two crashes trying this:

hi,
recently a group of us, AP users, in "Affinity Photo - Tutorials" facebook group are discussing making a so-called FB 3D photos for which you need a photo and it's depth-map simultaneously uploaded where FB combines them in a 3D effect photo.
so anyone trying this will have a really great help from depth-maps generated in a focus merge process only if we can save/export them in some photo format (Helicon and Zerene uses TIFF)
I think it will be a very small effort from Serif developers as depth map is already there, just save it somewhere.