Publisher v2 templates in v1

[Zac Beldan]

I am building a template for a publisher using Publisher v2. Is there a way to export it to use with Publisher v1? Or will I need to recreate it from scratch?

 

TIA

[thomaso]

There is no option to export V2 as V1 .afpub. As workaround you could copy/paste the layers between both apps and documents (while I don't know what happens with objects created with V2 only features) – or export as PDF and open this in V1 (which may require adjustments to achieve the wanted setup as template).

[walt.farrell]

You need to create it from scratch, or you need to create it in V1, which will let it work for both V1 and V2.

[walt.farrell]

2 minutes ago, thomaso said:

As workaround you could copy/paste the layers between both apps and documents (while I don't know what happens with objects created with V2 only features)

That won't work for Frame Text objects, or (if I remember correctly) Tables, at all.

[R C-R]

4 hours ago, walt.farrell said:

You need to create it from scratch, or you need to create it in V1, which will let it work for both V1 and V2.

To be clear, this should work for *.aftemplate files created in V1 because when you open one, you get a new untitled document. But be careful not to export the file as a new  *.aftemplate file from V2 because if you do that it won't work with V1.

[thomaso]

4 hours ago, walt.farrell said:

That won't work for Frame Text objects, or (if I remember correctly) Tables, at all.

Is there anywhere a list of V2 features that create objects with incompatibility if copied to V1?

And aren't there ways in V2 for these functions to be made compatible with V1 without losing editability, but only limiting flexibility? (means, a kind of step between a native V2 document and an exported PDF)

[walt.farrell]

11 minutes ago, thomaso said:

Is there anywhere a list of V2 features that create objects with incompatibility if copied to V1?

Anything listed in the Affinity Store Technical Specifications, for each application, that says it's a new feature for 2.0 or 2.1 or (soon) 2.2 will cause problems.

But that won't be complete, probably, as you don't need to intentionally used any new functions to cause the issue with Frame Text, for example.

15 minutes ago, thomaso said:

And aren't there ways in V2 for these functions to be made compatible with V1 without losing editability, but only limiting flexibility? (means, a kind of step between a native V2 document and an exported PDF)

No.

[Zac Beldan]

Thanks everyone