Zac Beldan Posted September 8, 2023 Share Posted September 8, 2023 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 Quote Link to comment Share on other sites More sharing options...
thomaso Posted September 8, 2023 Share Posted September 8, 2023 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). Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
walt.farrell Posted September 8, 2023 Share Posted September 8, 2023 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. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
walt.farrell Posted September 8, 2023 Share Posted September 8, 2023 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. thomaso 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
R C-R Posted September 8, 2023 Share Posted September 8, 2023 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. Quote All 3 1.10.8, & all 3 V2.5.6 Mac apps; 2020 iMac 27"; 3.8GHz i7, Radeon Pro 5700, 32GB RAM; macOS 10.15.7 All 3 V2 apps for iPad; 6th Generation iPad 32 GB; Apple Pencil; iPadOS 15.7 Link to comment Share on other sites More sharing options...
thomaso Posted September 8, 2023 Share Posted September 8, 2023 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) Quote macOS 10.14.6 | MacBookPro Retina 15" | Eizo 27" | Affinity V1 Link to comment Share on other sites More sharing options...
walt.farrell Posted September 8, 2023 Share Posted September 8, 2023 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. thomaso 1 Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1 Link to comment Share on other sites More sharing options...
Zac Beldan Posted September 13, 2023 Author Share Posted September 13, 2023 Thanks everyone walt.farrell 1 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.