MasterPage absolute path links and version control

This forum is for all Flare issues related to styles, stylesheets and XML.
Post Reply
JimAtPanduit
Jr. Propeller Head
Posts: 3
Joined: Wed Nov 01, 2017 10:43 am

MasterPage absolute path links and version control

Post by JimAtPanduit »

When we checkout our madcap repo into a new machine or a different location on disk, the build log file (.mclog) has many broken link errors.

Link points outside project file:///C:/MadCap Repositories/IVUE3/madcap/IntraVUEHelp/Content/Resources/Images/madcap.BulletWhite.png
Missing table style C:\MadCap Repositories\IVUE3\madcap\IntraVUEHelp\Content\Resources\TableStyles\Simple.css

It does not look like there is a way to make these links relative except perhaps by editing the masterpage itself.

What is the best practice to avoid these errors when the output is built on a build machine?

Thanks,
Jim
NorthEast
Master Propellus Maximus
Posts: 6359
Joined: Mon Mar 05, 2007 8:33 am

Re: MasterPage absolute path links and version control

Post by NorthEast »

The files need to be inside the current project - you can't have absolute or relative links to files that are not part of the project.

Sometimes this can happen by accident - e.g. if you copy/paste images or tables between two open projects, the pasted content can have links back to the original project.

So my guess is that those links are to another project, and they will only appear to work on the PC where they were created. The links won't work for anyone else with a different local folder structure.

Flare should tell you that the target has external links in the build log.
JimAtPanduit
Jr. Propeller Head
Posts: 3
Joined: Wed Nov 01, 2017 10:43 am

Re: MasterPage absolute path links and version control

Post by JimAtPanduit »

Thank you, This tells us what we have to do.
Post Reply