Like, would like more if…

Global Styles is what we need to dynamically encompass all object attributes globally, ie: fill, stroke, FX etc…

No, those are not global colors in the sense that is being requested here.  If you edit a global color on a swatch palette, every object in the document which uses that global color is updated immediately to use the new color which was set.
Global colors are only supported in Document-level swatch palettes, and for good reasons, which have been discussed previously here on the forum.
What is being requested here is basically, if the document has global colors A, B and C, then allow me to save schemes X, Y and Z, each of which may have different colors for each of A, B and C, so that when I switch to scheme Y, every object in the document which uses one of those global colors is immediately updated to match the selected scheme.

Glad to see layer states come to Publisher in 2.4 as it is a very useful feature. However, it if very frustrating that they cannot be renamed or reordered. I always must delete them and make a new one to edit the name. Editing the order would also simply be good for organisation. This functionality exists in layers (duh), and swatches, so surely it can be added to layer states relatively easily. I can't think of any reason as to why it shouldn't be added.

Suggested improvements to States feature:
Ability to rearrange order of States. Ability to rename States. Ability to group States in names Groups. Ability to capture unique File/EXIF/IPTC data per State. Safeguard accidental deletion of States. Safeguard accidental update of States. Safeguard accidental deletion: the Add and Delete buttons for States are very small and very close together. The incidence of accidentally clicking Delete while trying to add a new State is very high. Delete has no confirmation and no undo. Options: relocate buttons or confirm delete or undo delete State using document History? Same problem with  hitting Update when aiming for Settings.
Metadata: layer States are effectively subdocuments/variants, which when exported often need specific amendments to metadata (eg: if a layer containing a cat is turned off, there should no longer be a metadata tag for 'cat' when exported). At the moment, the only solution is to mash metadata for all States together and then amend metadata manually when exporting them, as was the case before States were available. If States captured metadata it would be very useful.
[As an aside, I would add editing tag metadata is currently difficult because there is a text justification and scrolling bug for that field creating abnormally large gaps between tags that constantly shift while typing, making it hard to proof-read tags for punctuation and spacing errors. Tags have to be edited in Notepad and pasted in because it is too difficult to type them directly.]

Using this for the first time this may be user error or misunderstanding, however I created and then broke down an illustration with a number of Groups and layers named for finding under Queries. These worked great. I then used these switched options to create captured states. 
I then needed to add another switchable option, created new content as both a Layer and a Group. Both will switch through Queries panel, but the new artwork will only turn on in my new "final" state  (OUTPUTS) and unlike other captured states will not switch off when selected.
So I assumed – Select the state you already have but want to remove new content from, switch off new query, update state.
However if I click the final state, new layer switches on, but none of the updated states will switch it off.
If I manually switch the query off it will then not appear again until I select my final state. 
I notice that the number of layers has not increased in the original states to match the number in the final added artwork - is this the issue? Shouldn't an update to a state capture all the content of the document?
To get to the desired result again I had to recapture all 10 states – not great. But all states then contain same number of layers.
–––––––––––––––––––––

 
AND…
Is there a reason why you can't rename a query or captured state? 

For the beginners in the room, I'd love a little link to explain how Regular Expressions work. I love documentation though, just me.
 

This seems to be a "specific file" issue. I have created a couple of new files similarly to Hangman and it's all good. Checked with my work partner on identical equipment and he said his is behaving as it should. So seems I have a "problem" file. Will try and resolve that issue tomorrow. 
Not a bug… just a glitch I hope.
This is not a bug but as hoped above a glitch in the file, don't know where or why, but updates to both Affinity and OS have occurred since original file creation in February. 
Fixed by creating new file, importing colour palette from old doc - important as global colours - then cutting and pasting content into new file. Happily back on track. 

This seems to be a "specific file" issue. I have created a couple of new files similarly to Hangman and it's all good. Checked with my work partner on identical equipment and he said his is behaving as it should. So seems I have a "problem" file. Will try and resolve that issue tomorrow. 
Not a bug… just a glitch I hope.
This is not a bug but as hoped above a glitch in the file, don't know where or why, but updates to both Affinity and OS have occurred since original file creation in February. 
Fixed by creating new file, importing colour palette from old doc - important as global colours - then cutting and pasting content into new file. Happily back on track. 

@Hangman exactly that, yes. 

Thanks for letting me know, I've updated the development log regarding this issue and 'bumped' it with our team, to bring it to their attention once again.
I hope this helps

Thank you. Same for me – I don't see the reason (and logic, considering any other kind of »compound object«) behind its current behaviour. 🤷‍♂️

Strange transparency rendering behaviour when adding transparency to individual lines created with arrowheads.
This has probably been a forever thing, but have just bumped into it again when fading parts of a flow build.
If you create a single line with an arrowhead (curve layer) and change the layer transparency, designer renders the line and arrowhead as individual objects, which given that they are overlayed to prevent gapping creates a more dense area where the line meets the arrowhead.
Work around is to group the object… which seems like an odd thing to need to do for a curve line that should behave as a single object.
I can't think of an application where I would want/expect the current standard behaviour.
 

Thanks for fixing, beta seems to function perfectly. Look forward to next release.

I can't use offset tool. 

การบันทึกหน้าจอ 2566-10-01 เวลา 12.57.11.mov  
การบันทึกหน้าจอ 2566-10-01 เวลา 12.55.09.mov  

This will work if you update. This is a very old feed on a v1 Publisher forum. 
 
Working with Publisher 2.1.1 and Dropbox v182.4.6427 this works exactly as it should. 
 
Don’t expect a v1 fix. 

I can't provide an exact guarantee for when this issue will be fixed, but it will be marked as a higher priority with our developers due to the number of reports - so hopefully this will be resolved in an upcoming beta 

I want to support with all I can do, that Affinity Publisher *needs urgently* a dialogue, which has rightly the name "Font Manager".

The menue item "Font Manager" is in fact NOT a *manager*, because no one can manage here fonts! It only shows what I am missing...
In the last 4 weeks, I initialised a total move off Adobe towards Affinity Suite and Apple silicon. I am graphics designer since 25 years, and I have hundreds and hundreds of design files, which I saved in those weeks one by one as .idml in order to move to AFPub. (I know, there is an "extension" by markzware...)
Furthermore 90% of my fonts from old days are Postscript Type 1 fonts – which are all lost because T1 is abandoned and has be replaced/substituted by .otf or .ttf!

In reading that thread about Font replacement, I got a real horror that I did wrong in deleting the Adobe Suite...
I think, the developers of AFPub should see not so much the "theory" about missing fonts, but the *praxis* of typesetters and graphic designers:
It is very urgent, that we have a dialogue to replace globally any font in a document by an other one (Helvetica Italic –> Helvetica Neue Italic; MT Garamond Regular –> Palatino Regular). And that can't be done with search&replace! If you have 340 pages of a book with ("fluffy" typeset) parental advices, you will get crazy.
 That would be *really* important!
Best wishes from Germany
Johannes

First off great artwork Stuart! Now to be honest what you are trying to do there is actually a reason as to why we have been a little unsure about including this feature. The use case we are trying to cover is not about warping artwork in that way with 1000s of objects. It is actually to more cover the cases of needing to warp embedded documents or images. And I can say that the only reason you are seeing pretty decent performance there is because you are on the Windows version and that in fact currently has the destructive version of the filters which is incorrect.

I've just recorded a quick vid of why we have included it. This is using Designer to create some mock up options of an iPad app, where the UI of the app itself is also a Designer document. You can place the multi-artboard UI file as an embedded document in your mock up. Apply a live perspective from pixel persona to place in the iPads. As it's non destructive after you've done that you can still choose which artboard you want to show in your mock up. You can even edit the embedded document, float the window and update the source file while the mock up updates in real time.

Obviously this is perspective, with live warp you could use it to warp an embedded document on something like an open brochure (where the page is curled a bit) or a bottle label or whatever. But yeah, for these cases it felt wrong we are forcing people to use Affinity Photo to achieve this, especially when the type of mock up or whatever you are doing is better suited to use Designer to create the other elements around it (or to have options on artboards and things like that).

While this I think offers a fantastic (and unique) workflow for this kind of thing, the possible issue is the assumption that could be made that this is some alternative to use like vector warp when that isn't the intention. We'll have to try to be very clear about this with our help / learning materials around it as best we can.
LivePerspective_2.mov  
 

Excellent Walt, really appreciate your rapid response and accurate assumptions! All looking good now. (messing with the resources was a misguide from elsewhere… when you're desperate you'll try anything, ill advised or not!)

Please find below direct links to the Hunspell dictionaries. You can right click the relevant link and select the option to Save Link As... to download the file.
af_ZA af_ZA.aff af_ZA.dic hyph_af_ZA.dic an_ES an_ES.aff an_ES.dic ar ar.aff ar.dic be_BY be-official.aff be-official.dic hyph_be_BY.dic bg_BG bg_BG.aff bg_BG.dic hyph_bg_BG.dic bn_BD bn_BD.aff bn_BD.dic bo bo.aff bo.dic br_FR br_FR.aff br_FR.dic bs_BA bs_BA.aff bs_BA.dic ca ca-valencia.aff ca-valencia.dic ca.aff ca.dic hyph_ca.dic cs_CZ cs_CZ.aff cs_CZ.dic hyph_cs_CZ.dic da_DK da_DK.aff da_DK.dic hyph_da_DK.dic de de_AT_frami.aff de_AT_frami.dic hyph_de_AT.dic de_CH_frami.aff de_CH_frami.dic hyph_de_CH.dic de_DE_frami.aff de_DE_frami.dic hyph_de_DE.dic el_GR el_GR.aff el_GR.dic hyph_el_GR.dic en en_AU.aff en_AU.dic en_CA.aff en_CA.dic en_GB.aff en_GB.dic hyph_en_GB.dic en_US.aff en_US.dic hyph_en_US.dic en_ZA.aff en_ZA.dic eo eo.aff eo.dic hyph_eo.dic es es_AR.aff es_AR.dic es_BO.aff es_BO.dic es_CL.aff es_CL.dic es_CO.aff es_CO.dic es_CR.aff es_CR.dic es_CU.aff es_CU.dic es_DO.aff es_DO.dic es_EC.aff es_EC.dic es_ES.aff es_ES.dic hyph_es.dic es_GQ.aff es_GQ.dic es_GT.aff es_GT.dic es_HN.aff es_HN.dic es_MX.aff es_MX.dic es_NI.aff es_NI.dic es_PA.aff es_PA.dic es_PE.aff es_PE.dic es_PH.aff es_PH.dic es_PR.aff es_PR.dic es_PY.aff es_PY.dic es_SV.aff es_SV.dic es_US.aff es_US.dic es_UY.aff es_UY.dic es_VE.aff es_VE.dic et_EE et_EE.aff et_EE.dic hyph_et_EE.dic fr_FR fr.aff fr.dic hyph_fr.dic gd_GB gd_GB.aff gd_GB.dic gl gl_ES.aff gl_ES.dic hyph_gl.dic gu_IN gu_IN.aff gu_IN.dic gug gug.aff gug.dic he_IL he_IL.aff he_IL.dic hi_IN hi_IN.aff hi_IN.dic hr_HR hr_HR.aff hr_HR.dic hyph_hr_HR.dic hu_HU hu_HU.aff hu_HU.dic hyph_hu_HU.dic id id_ID.aff id_ID.dic hyph_id_ID.dic is is.aff is.dic hyph_is.dic it_IT it_IT.aff it_IT.dic hyph_it_IT.dic kmr_Latn kmr_Latn.aff kmr_Latn.dic ko_KR ko_KR.aff ko_KR.dic lo_LA lo_LA.aff lo_LA.dic lt_LT lt.aff lt.dic hyph_lt.dic lv_LV lv_LV.aff lv_LV.dic hyph_lv_LV.dic mn_MN mn_MN.aff mn_MN.dic hyph_mn_MN.dic ne_NP ne_NP.aff ne_NP.dic nl_NL nl_NL.aff nl_NL.dic hyph_nl_NL.dic no nn_NO.aff nn_NO.dic hyph_nn_NO.dic nb_NO.aff nb_NO.dic hyph_nb_NO.dic oc_FR oc_FR.aff oc_FR.dic pl_PL pl_PL.aff pl_PL.dic hyph_pl_PL.dic pt_BR pt_BR.aff pt_BR.dic hyph_pt_BR.dic pt_PT pt_PT.aff pt_PT.dic hyph_pt_PT.dic ro ro_RO.aff ro_RO.dic hyph_ro_RO.dic ru_RU ru_RU.aff ru_RU.dic hyph_ru_RU.dic si_LK si_LK.aff si_LK.dic sk_SK sk_SK.aff sk_SK.dic hyph_sk_SK.dic sl_SL sl_SI.aff sl_SI.dic hyph_sl_SI.dic sq_AL sq_AL.aff sq_AL.dic hyph_sq_AL.dic sr sr-Latn.aff sr-Latn.dic hyph_sr-Latn.dic sr.aff sr.dic hyph_sr.dic sv_FI sv_FI.aff sv_FI.dic hyph_sv.dic sv_SE sv_SE.aff sv_SE.dic hyph_sv.dic sw_TZ sw_TZ.aff sw_TZ.dic te_IN te_IN.aff te_IN.dic hyph_te_IN.dic th_TH th_TH.aff th_TH.dic tr_TR tr_TR.aff tr_TR.dic uk_UA uk_UA.aff uk_UA.dic hyph_uk_UA.dic zu_ZA hyph_zu_ZA.dic

I do agree. The multiplying of styles that happens here is more cumbersome than it needs to be.
Along those lines, it would also be welcome if Publisher suggested assigning a different style when you delete one style. For example, if you were to delete a copy style, if the style was in use, a little message would pop up offering the option to replace all instances of the style to be deleted with another style of user's choice.

Many thanks for the further file and your continued patience here!
I believe I have been able to pinpoint the cause of this, as it seems to only occur with M1/M2 devices that have been updated to macOS Ventura, hence I was not seeing this issue on an M1 mac running Big Sur or Monterey, or on my Intel mac running Ventura.
I will be getting this logged with our development team for you now, thanks for your report  

Thanks for letting me know and I'm sorry to hear this! I have tried exporting once again, using PDF (digital - high quality) preset, the left hand PDF is from Publisher and the right from Designer - 

 
Note, the shutterstock image appears slightly blurry in my export as it is a 'Missing resource', but the transparency is correctly applied.
Just to ensure I'm not missing something with the export options from Publisher, can you please provide a screenshot showing the options that are selected for you when choosing this preset?

Happy new Year to everyone here at first 🍀
My question is already answered with this post but very unsatisfactory. So I more write to express my dissatisfaction about the masking problem here.
I started working with AP intensely and with youtube-tutorials for 3 month now. It's really a great software but it has some lacks that make it hard to work professional with it.
Most important for me is a good function of the masking. I'm a professional photographer and I worked with lots of different post producers worldwide. And all of them work with overlay masks in most of the layers. I'm used to that in PS too, but wanted to make a cut with Adobe because of the subscrition system, to give another company a chance and to recommend AP to other photographers, Photo assistants and students that just don't really need an Adobe subscription.
I suppose most people underestimate what it means to work for demanding clients. Just to give you an impression of how many layers can be in one picture I added an example. I have photo composings with more than 70 Layers and sure you have to make corrrections afterwards regularly if some masking has to be adjusted. Workarounds with even more layers at the end are very contra productive then. Colored overlay layer masks above the background are a basic requirement for me and any professional. Until now I just thought I couldn't find the function, but now I found out it's just not implemented, so please Affinity put in on your list with high priority.
Just as an addition it's pretty impossible to make a good pressure sensitive brush with AP. Most professionals work with tablets and there are so many parameters you can change in AP for a single brush but opacity with pressure is unfortunately not part of it. This for me is the second thing which really would be great to add to AP2.
Hope to see this 2 functions no too far in the future...

 
 

It's now been a few months since I upgraded to V2, and I can confirm that the export issues still plague my Affinity Designer and Photo when I'm in Export Persona.

I have a Macbook M1 (Monterey 12.6).

I never had this issue with Affinity pre-M1, but once I upgraded to Affinity V1 optimized for M1 the crashes started to happen. I was hoping for V2 to solve the issues, but they still came back.
So far, the only workaround that have reduced the number of occurrences is selecting the folder I want to export to by first pretend-saving the file to that same folder—that way the correct folder is brought up when I want to export. That only works sometimes, however.