big smile

A small one but very useful!
 
Please consider adding a revert option to the file menu command in all Affinity apps. 
The user can click on revert to re-open the file and discard all changes since the last save. Yes, there are other ways of doing this, but a file menu option is super handy!

You can create your own preset from the burger menu in the advanced section which would include your bleed setting. However that preset doesn't save the area being chosen to export (largely down to area can be your current selection, which doesn't make so much sense for a preset). That said I agree that your last setting in Area should be maintained, we'll take a look.

I waste so much time because even in V2 the export dialog cannot remember the pdf export settings I have chosen. 
We've been complaining about the default to 'spreads' forever, and it is still here. 
Remembering dialog box settings wasn't rocket science 25 years ago. I'd love to record this as a bug, but I guess it is still just a mere feature request. 
 

Thanks for the additional info, I haven't forgotten about this, it's on my "to do" list. I will endeavour to take a look in more detail tomorrow.
Lee

Here is nomi02118's original post incase the admins are looking for it: 
 

@Pauls @Dan C This is still an issue in Affinity Publisher V2. I have created a new thread for it here:
https://forum.affinity.serif.com/index.php?/topic/172281-linked-publisher-documents-get-displayed-as-blank-pages/

I have added the files.
For those files, the workaround doesn't work either. 

Hi Lee - can you confirm that if you purchase from Serif website, you cannot get Mac Store updates?
As big smile points out, the auto update of the App Store is great and preferable to manual download via a website.
Cheers

Hi big smile
I also purchased from the Serif site and would prefer App Store updates rather than manual downloads. 
I've just tried installing from the App Store. It seems to overwrite the existing V2 apps (downloaded from website) but if you are logged into your Serif account, it seems to recognise your licence.
So, fingers crossed it will auto update via App Store.

I bought V1 directly from Serif, rather than the Mac App Store. I partly regretted it, as the Mac App Store makes it so much easier to update apps and also do family sharing between systems. 
With V2, it looks like you can download the apps from the Mac App Store, and then you enter your licensing details. If you buy the License from Serif, then will the apps still update via the Mac App Store? Or will you to update from inside the App (like with V1 when you bought from Serif)
Also, are there any dis/advantages to buying a universal license direct from serif rather than the Mac App Store?
If you buy a universal license from the Mac App store can you still activate on Windows?
Thanks!

Hi big smile, 
Apps purchased from the app store will update via the store you purchased from. Though if you purchase a universal license from the App store you are free to download and install/update whichever version you wish from either our store as a DMG, or the Mac App store.
The app is also a free to download app that is unlocked by signing in with an account with a license, so no real downsides to either method.
Lee

You should find that all the apps are free on the Mac App Store, and initially run as 30-day Trials. You then can purchase Licenses within the app when you run it, and that's where you'll find the Universal vs Single-App licenses available.

Yup, I agree, the find and replace is too fiddly to use for multiple tasks (especially as you can't save searches). That's why I think Nested and GREP styles are an essential addition. 
Plus, with find and replace, it's all too easy to forget to do it. With Nested and GREP  it happens automatically, so it makes things less error-prone. 

+1 for GREP styles and Nested Styles
 
The Find and Replace is a powerful workaround, but being able to use GREP and Nested Styles would make things less error-prone (especially as Find and Replace doesn't allow you to save searches and it can be fiddly to enter in all the details on a repeated basis). 

Hi big smile, 
You can go to Document > Add pages from file
The rest is dependant on how the original document was constructed, but i think you'll find this does everything you need it to do.
Lee

Hi @big smile
I think it can be done. I have attached 3 files. "4 page document.afpub" was used to create the "4 page document.pdf" file. A new document was created "NEW DOCUMENT.....afpub. This has a Master Page A and also a Master Page B which is inside Master Page A. The PDF file "4 page document.pdf" is placed on Master Page B. All pages are tagged with Master Page A. Go to Page 2 and use the Layers panel to right Click on Master B, change to Edit Detach, then click on "4 page document.pdf" to change the page number to page 2. Repeat for the other pages. The original PDF on Master B can then be moved and scaled and this will change the 4 pages in the document. It's a bit fiddly but not too bad.
 
NEW DOCUMENT WITH PDF ON MASTER B.afpub 4 page document.pdf 4 page document.afpub

Issue:
In my Affinity Publisher documents, I tend to use the same text styles. When copying and pasting text between the documents, the styles get duplicated with a number added at the end. This happens even if the styles are identical. Example:

^ These are all the same style which have been duplicated when copy & pasting between documents. 
Solution:
When copying and pasting between a document, Affinity should ask the user how handle duplicate styles rather than just numbering them.
 
Here is an example of how it could work:

This dialogue box would pop up whenever copying and pasting text in situations where Affinity would currently just duplicate the style.
This dialogue box would be optional, activated first via an option in preferences, so users who like the current handling of style can chose not to activate the option. 
Merge Styles - Keep incoming definition This option will cause the two styles to be merged. All values will follow the source document. 
Merge Styles - Keep local definition This option will cause the two styles to be merged. All values will follow the local document. 
Create new style - This will create a new style (which is how Affinity currently handles it by duplicating the style and adding a number to the name).
Additional options:
Clear Overrides - Any differences between the local and incoming style will be discarded. 
Keep Overrides - Any differences between the local and incoming style will be kept as overrides. 
Save Overrides as character style - The differences can be saved as a character style. 
Example:
I have  "Document A" which has  text that has a style called "English translation". This is just Helvetica, bold text 12pt. 
I copy and paste this text into "Document B" that already has a style  called "English translation". If I select "Merge Styles/incoming" then the style from Document A will be used. If I click clear overrides, then any differences between the text in document A&B will be lost. 
 
Who would this be useful for:
This would be useful for users who regularly copy and paste text between Publisher documents. 
 

I found a work around to this:
1. Place the instance of the symbol in a group.
2. Now you can turn on/off the group visibility without breaking the syncing of the symbol. 

This does what the user wants but at the cost of unlinking the visibility attribute from the instance meaning it will never sync again with the other instances if the user needs to revert the process at some point (that is, make the visibility honour other's instances visibility state again).

You could turn off Sync, toggle the visibility of the symbol instance, then turn on Sync again.

To clarify slightly, note that users cannot create system wide *.clr pallets (the ones stored in System/Library/Colors/) only per user custom ones. IOW, each user account on the Mac can have its own set of custom *.clr pallets, which for that user will be available in any app that supports *.clr pallets.
So if either of your Macs have more than one user account, you may not get the custom pallets you expect when copying from one Mac to the other.

The three macOS system palettes are stored in System/Library/Colors/…
A custom system palette created in Affinity gets stored in your macOS user library folder, ~/Library/Colors/…

Thanks for the updates, unfortunately there's been no further development update to the bug report currently - but I'll be sure to inform you here when that changes

As a layout artist you see your project as a whole. Not as a collection of single pages. For the latter one better uses a illustration app like AD.
I consider it's a big mistake adopting the level concept of AD and AP for AP.  Most layouters use layers primarily for alternative designs, which can then be faded in and out with a single mouse click. Exactly this is not possible with AP and its current layers concept.
I know, it is difficult to change, because AP should be compatible with AD. But maybe you could bypass the problem by offering the option to mark selected layers as cross-project. This could be a publisher-only function.