Jump to content

Importing Master Pages from another document, in v2.1


Recommended Posts

I'm really tired of searching for an answer to this question -- all topics I've searched seem to prefer to sidestep the direct import of Master pages from another document.

When I try to use the Layers Panel, I copy all the layers below the group layer -- otherwise it doesn't work -- then I have the new Structure of my Master Page into the new Document.  Well, not entirely!  The content of the Fields are NOT transferred.  Then, when I switch over to the old document, the Fields reflect THAT document.  Why can't the Fields CONTENT also be copied?

OK, then we proceed to Affinity's Help System.  They want me to create some external .CSV file; then use some Import mechanism to read that!  Why?  The information is right there!

THE reason I upgraded to v2.1 is because (somewhere) I read or viewed that: "In v2.0 or v2.1, you can import Master Pages".  Yet every single article, help system topic, or YT video seems to go out of their way to side-step the topic of Importing Master Pages!  Why?  (Now, I cannot find the Import Master Pages in v2.1 or 2.0 "New Features"; but hey, I got improved dashed lines.)

I want to import, not only the Master Page Structure, but also the (selectable!) filled-in Fields from the older document!

Someone else said:  Use the Import feature from a Document saved as a Template.  OK, I tried that -- the "Template" file drags in the entire document:  Pages, photos, text, -- everything.  Why?  There are no options, that I can find, to do what I want; and I see absolutely NO VALUE in what Affinity calls a "Template" -- it's the same as the file itself!  OK, I create a directory with my 'Templates" in it, then I can use this upon New Document Creation.  Big deal -- still no selectable Fields content.

I truly seems as though Affinity is going out of its way to prevent me from re-using Master Pages!

Have I missed something?  Please assist.  I realize my tone here may be be a bit harsh; but it reflects the amount of time I've spent trying to Import Master Pages -- and this should not be rocket science.

Link to comment
Share on other sites

Document > Add Pages from File

Will import the Master Pages if the old document uses them but I have no idea exactly what you mean by...

1 hour ago, tkarl__nn said:

The content of the Fields are NOT transferred

 

To save time I am currently using an automated AI to reply to some posts on this forum. If any of "my" posts are wrong or appear to be total b*ll*cks they are the ones generated by the AI. If correct they were probably mine. I apologise for any mistakes made by my AI - I'm sure it will improve with time.

Link to comment
Share on other sites

It isn't as easy as importing the old file and using the (custom)fields created in there.
You can create a text only template with your fields and base a new document on that template.
Or place a saved afpub file with those fields present, either embedded or linked.
If you have it in the main project file you can edit that document in a new tab where you can edit the fields and close the new tab when done.
With embedded files it will only use that instance of the file and it will bring over the fields in the main project without altering the fields externally.
If it is a linked file it will ask you to save the linked file and it will update in both the main project file and the external file when saved.




 

Link to comment
Share on other sites

19 hours ago, carl123 said:

Document > Add Pages from File

Will import the Master Pages if the old document uses them but I have no idea exactly what you mean by...

 

Fields:
If you follow the menus:  Text,  Insert, Fields, then ... More -- you get a whole range of things to potentially add to your that are in a Table, in a window.  These 'things' are areas where you can type text into, and are then inserted into your Document when you Dbl Click the NAME of the Field -- then, those items appear in brown-Highlight -- meaning you cannot change them in your Document.  Transferring these items into another Document is proving difficult to impossible.

 

In the Attachment below, the Red bars are masking the actual content I placed there -- for my own privacy purposes.

Reply to guy in Publisher Forum.jpg

Link to comment
Share on other sites

18 hours ago, Return said:

It isn't as easy as importing the old file and using the (custom)fields created in there.
You can create a text only template with your fields and base a new document on that template.
Or place a saved afpub file with those fields present, either embedded or linked.
If you have it in the main project file you can edit that document in a new tab where you can edit the fields and close the new tab when done.
With embedded files it will only use that instance of the file and it will bring over the fields in the main project without altering the fields externally.
If it is a linked file it will ask you to save the linked file and it will update in both the main project file and the external file when saved.

That Reply, (Thank You!) was very difficult to follow.  
Can you translate that reply into simpler terms?

Link to comment
Share on other sites

5 hours ago, tkarl__nn said:

Can you translate that reply into simpler terms?

Perhaps:

  1. Save your document as a Template file. Possibly after deleting all the Document pages (but keeping the Master Pages).
  2. Create your next document based on that Template.

-- 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.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

Yes and only use the fields and maybe textstyles in this template.
Whenever you add pages and need those fields you can reach them as they are document based.
For layout stuff use other afpub documents that you bring in through placing as either embedded or as linked.

Ex.
New doc based on Fields Template.
New doc is called Main.
All text will be on Main also and fields are to be reached as these were stored in the template file.
Now you can add your layout stuff by either creating them or copy/pasting from other documents.
But you can also embed or link afpub/designer/photo files that are fully editable within publisher and use this to bring in layout stuff.



 




 

Link to comment
Share on other sites

9 hours ago, Return said:

Yes and only use the fields and maybe textstyles in this template.
Whenever you add pages and need those fields you can reach them as they are document based.
For layout stuff use other afpub documents that you bring in through placing as either embedded or as linked.

Ex.
New doc based on Fields Template.
New doc is called Main.
All text will be on Main also and fields are to be reached as these were stored in the template file.
Now you can add your layout stuff by either creating them or copy/pasting from other documents.
But you can also embed or link afpub/designer/photo files that are fully editable within publisher and use this to bring in layout stuff.



 

You can add any TEXT used in an old Master Page; but you cannot add "Fields" from the old Document, although the Page # comes through.

It seems as though I was mislead into thinking v2.0/2.1 had an enhanced way of importing Master Pages.  "Hundreds of improvements in 2.0/2.1"?  I don't see or use/need them.  I'll look over those 'enhancements' one more time; and will await anything useful in 2.2+  that may come along.

I may go back to using v1.10 as it is faster & more responsive when editing Text and overall faster on my old PC.  (I don't really need the enhanced dashed lines.)  I also saw the Warning that said you cannot edit any v1.10 Publisher document touched by v2.0/2.1.

Link to comment
Share on other sites

1 minute ago, tkarl__nn said:

I also saw the Warning that said you cannot edit any v1.10 Publisher document touched by v2.0/2.1.

Not touched. Saved.

-- 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.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

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.