Publisher relative Path to subfolder

[Lukas.S]

Hello there

I tried linking PDF Files into my .afpub file.
Am I right that i only have 2 options.
I can either choose a absolute Path which only works exactly in that directory which is not what i'm looking for.

The other way is to "include file on export" but then all the file would be in the same directory as the .afpub file which is also not perfect because of the file hierarchy and a overwhelming amount of files in the main directory.

Now as far as my research got me there is no way to link a pdf which stays in a subfolder and i can copy the whole folder wherever i want.
Is this correct?

Thank you

[MikeTO]

1 hour ago, Lukas.S said:

I tried linking PDF Files into my .afpub file.
Am I right that i only have 2 options.
I can either choose a absolute Path which only works exactly in that directory which is not what i'm looking for.

The other way is to "include file on export" but then all the file would be in the same directory as the .afpub file which is also not perfect because of the file hierarchy and a overwhelming amount of files in the main directory.

Now as far as my research got me there is no way to link a pdf which stays in a subfolder and i can copy the whole folder wherever i want.
Is this correct?

Linked resources are stored with absolute paths and there's no way to set it to use relative paths. However, if you put all of your linked resources in a single folder (with as many subfolders as you like, then you can move that folder anywhere. When you open the document Affinity will alert you to the missing files and ask if you want to re-link. It will open a dialog to let you find the first missing file - when you do that, it can find all of the others based on that single file, even if there are thousands of them.

So the best solution to saving your work is to create a project folder for the document and a resources folder inside of it. Then move the project folder, relink when prompted, and all will work fine.

Project 123 folder
  - Project123.afpub
     - Resources (or Images or whatever you want to call it)

The Include File on Export feature is for creating a package for distribution and has nothing to do with all of this. You can find more information on it in the free manual I've shared in the forum - the link is in my signature.

Cheers

[Lukas.S]

Thank you for your fast reply and the manual.

I will certainly look into it.

Have a good day.

 

[chapolote]

This is strange in my opinion.
Publisher should definitely have the option to use relative pathes. It doesn’t make sense, especially working with other people on same document, if the directories of files have to be adjusted to publisher instead of that publisher follows an existing folder structure. 
Relative pathes is the only way to ensure, that files can be located in a similar folder structure but on different drives. 

The workaround of relinking files costs unnecessary time and is cumbersome if files have to be edited several times by different users. 
 

is there any explanation, why this is not implemented?

[MikeTO]

5 minutes ago, chapolote said:

This is strange in my opinion.
Publisher should definitely have the option to use relative pathes. It doesn’t make sense, especially working with other people on same document, if the directories of files have to be adjusted to publisher instead of that publisher follows an existing folder structure. 
Relative pathes is the only way to ensure, that files can be located in a similar folder structure but on different drives. 

The workaround of relinking files costs unnecessary time and is cumbersome if files have to be edited several times by different users. 

is there any explanation, why this is not implemented?

I don't work for Serif so I don't know the answer. I wish it used relative paths, too.

[Alfred]

1 minute ago, MikeTO said:

I don't work for Serif so I don't know the answer. I wish it used relative paths, too.

You’re not paid by Serif.

FIFY.