loukash

I'm logging this with our developers, as far as I'm aware we don't directly support this feature so it's certainly interesting to see the IDML parser is able to create these - I'm not 100% certain if you should be able to create linked path texts in Publisher and this is a bug, or if our developers chose not to implement this as a feature and instead allows .IDML imports to retain these as otherwise it could import a document that looks far from the original InDesign file.
I'll be sure to follow up here with any feedback I receive from the devs regarding this

I'm not convinced.
If it ever gets implemented, please make it a preference option so that I can turn it off. thanks

The actual "hack" was hidden in the video because the document was – deliberately – in Preview Mode.
The magic happens outside the pages:

The text frames on spread 1 are "linked layers", but linking is only enabled for the text content. The text frames on the other spreads don't need to be "linked layers" because the text from frame 1 will flow through them anyway.
The cat is a partially linked/synced symbol, but that's a remainder from an early stage of this experiment and likely unnecessary for the final result because the red cat now lives outside the page anyway.
You may need to switch back and forth between all three personae to enable and adjust the link and symbol features; but that's not even a hack: that's literally an Affinity feature by design.
The only "hack" here is how to enable the Links (or the Text Frame and Pinning) panel in all three personae. That's not "by design", rather a kinda "bug", or – more positively, paraphrasing the good ole Bob Ross – a happy accident. Search my post history on how to enable them (may work on Mac only).
In case you didn't know yet: the Cat shape tool is a built-in easter egg!

Sometimes Affinity will stop showing results when searching for a topic within Affinity's help on macOS. This issue is caused by Apple's Help Viewer cache not being correctly indexed. To clear the Help Viewer's cache, run the following command in Terminal:
killall helpd; rm -rf ~/Library/Caches/com.apple.help*; rm -rf ~/Library/Preferences/com.apple.help* Once you have ran the above command, please reboot your machine. When you next open the help within Affinity please allow some time for the Help Indexer to reindex our help.

This is most likely a MacOS help cache issue.
A quick fix could be to navigate to ~/Library/Caches and delete the "com.apple.helpd" folder. (That's how it's named on El Capitan; it might be named differently on newer MacOS.) Then restart the computer.
There are also helpful and free 3rd party utilities like Onyx that will let you delete various system and user caches in case of similar problems. Just make sure to carefully read their respective instructions and user manuals to better understand what they do.

Thank you again for your indefatigably effort! The easter-egg, resp. the easter-cat  was new to me, cool 🙂
In my current project i simply place the info box shapes in the respective pages. When new pages are added, than i move my shapes. "Only" less than 20 pages are affected by it.
In the end, I always try to keep it simple.

Ha!
Hold on, here's the clue:
It's ye olde DEFAULT ENGLISH (UK) LANGUAGE BUG!
The (temporary) fix:
Change the app language from English (or Default) to English US (or any other language you can read).
English US is what I'm using anyway – and thus suffering from all those related bugs elsewhere – hence I've never encountered this issue until now.
P.S. Although seeing that others are using e.g. German and having this bug anyway, it's likely not the only "source". Worth to try though.

I wouldn't say it's "broken", but the logic of how it works is, er, special.
Especially if you're comming from InDesign. Been there for the past 18 years, too…
So, after intensively toying with it for the past few weeks, I think I've finally figured it out.
The key to [No Style] (and many other app-wide settings) is Edit menu > Defaults > Save.
These defaults are contextual, depending on which tool is active. I.e. you can have different defaults for Frame Text Tool and Artistic Text Tool. And there are also defaults for strokes, text frames, image frames, you name it.
In other words, if you despise Arial as much as I do (don't let me even start on that!), you can override it by setting up your favorite default style using the Character and Paragraph panels, then save as default for each text tool.
I've been opting for Menlo 10 pt as the default font – also in Adobe CS – ever since Apple added it to the system fonts.
To reset your currently active style back to your previously saved default style, simply click the Revert Defaults button in the toolbar. This will always bring me back to my Menlo 10 pt now.

Yes. The feature is there in Affinity, but no UI to access it.
Not sure if this is a bug or just a "lazy omission".
For what it's worth, the current "ugly workaround" would be to create a "template" of linked text paths in InDesign, save as IDML, import to Publisher and save as an asset "template" for future use. Make sure to create enough linked paths in advance because you can always remove them later but you can't add/link more in Affinity.
So… here's a quick'n'dirty IDML A4 template with straight lines to get us going. You can always alter or hide any of the curves in Affinity as you see fit using the Text Frame panel, as well as style any text to your liking.
linked_text_on_path.idml

Yes. The feature is there in Affinity, but no UI to access it.
Not sure if this is a bug or just a "lazy omission".
For what it's worth, the current "ugly workaround" would be to create a "template" of linked text paths in InDesign, save as IDML, import to Publisher and save as an asset "template" for future use. Make sure to create enough linked paths in advance because you can always remove them later but you can't add/link more in Affinity.
So… here's a quick'n'dirty IDML A4 template with straight lines to get us going. You can always alter or hide any of the curves in Affinity as you see fit using the Text Frame panel, as well as style any text to your liking.
linked_text_on_path.idml

Neither would I, until this:
At least, @MattP was totally swift in fixing it.

about select object by name.
The software can select the objects by id name.  if users can intput the id name such as "name*"  , that mean select the id name start by "name......" .  It will be userfull to get the objects
 

When there's a will, there is always another option.

Sometimes, one has to think backwards.

Insert line breaks.

This just exports the spot colors as opaque while set to overprint. It doesn't recalculate the opacity values to tint values, which is what the Adobe PDF library does.
As noted in my other thread, I can work around by exporting to PDF/X-4 and converting to PDF/X-3 via Adobe PDF. In the meantime I've set up a few conversion filters directly in Acrobat X, so I don't even need to take the route via InDesign or Illustrator import as described in that thread.
Of course, that works for me only as long as I'll continue to work in El Capitan (or not going higher than Mojave). Which is OK for likely a few more years to come.

You mean text flowing from one text path to another?
Not as if you would be linking text frames, but "visually" it's possible:
create multiple curves as you see fit Layer > Geometry > Merge Curves – to make them one object Artistic Text Tool > convert the merge curves object to text path You will need to experiment how to manage the text flow then…

Neither would I, until this:
At least, @MattP was totally swift in fixing it.

FWIW, my favorite reference for all things related to the Apple Color Picker is The Macintosh OS X Color Picker. It's old so a few of the icons are different but it covers just about everything in its 'accordion' topics. So for example, clicking on the "Using Drag & Drop to Color Things in Mac OS X" explains how that works. 

Ha!
Hold on, here's the clue:
It's ye olde DEFAULT ENGLISH (UK) LANGUAGE BUG!
The (temporary) fix:
Change the app language from English (or Default) to English US (or any other language you can read).
English US is what I'm using anyway – and thus suffering from all those related bugs elsewhere – hence I've never encountered this issue until now.
P.S. Although seeing that others are using e.g. German and having this bug anyway, it's likely not the only "source". Worth to try though.

When the padlock is enabled in Colours panel, you cannot be sure of the colour model of a colour's definition - it will show a conversion from its real definition to the padlocked colour model. You need to disengage the padlock to see the actual definition of an object or swatch's colour.
Create Palette From Document is creating LAB swatches, and so the colours in the created swatches do not precisely match the original colours in your document.
Even if your original colours are defined as LAB in a LAB document, the created LAB swatches are not guaranteed to match the original LAB colours. There appears to be a conversion from original colour definition to a mysterious colour space and then to LAB.
 

+1
Also elsewhere:

And here:

That's on El Capitan.

FREE FREEEEEHAAAAAAAND!!!

Ha!
Hold on, here's the clue:
It's ye olde DEFAULT ENGLISH (UK) LANGUAGE BUG!
The (temporary) fix:
Change the app language from English (or Default) to English US (or any other language you can read).
English US is what I'm using anyway – and thus suffering from all those related bugs elsewhere – hence I've never encountered this issue until now.
P.S. Although seeing that others are using e.g. German and having this bug anyway, it's likely not the only "source". Worth to try though.

FREE FREEEEEHAAAAAAAND!!!

Ha!
Hold on, here's the clue:
It's ye olde DEFAULT ENGLISH (UK) LANGUAGE BUG!
The (temporary) fix:
Change the app language from English (or Default) to English US (or any other language you can read).
English US is what I'm using anyway – and thus suffering from all those related bugs elsewhere – hence I've never encountered this issue until now.
P.S. Although seeing that others are using e.g. German and having this bug anyway, it's likely not the only "source". Worth to try though.