Build Primary not possible after copying project

[PracGren]

I made a copy of my MadCap project and placed it on a folder on a server as a back-up.
When I start the project from the folder on the server, the project opens but it is impossible to Build Primary.
Same problem after my project has been translated with Lingo. Lingo produces a 'New project' with the translated files, but now I cannot create any HTML pages anymore!
The creation of web based HTML-pages is of course the reason why we use MadCap.
Since my upgrade to MadCap 12 i have this problem. In MadCap 10 this was possible.

[chrisj]

Are you getting an error when you try to build a target, or what specifically is happening? Is the target you want to build still marked as primary? Without more information it's hard to determine what might be happening.

[PracGren]

In my project on the C:\ disk, the button 'Build Primary' has a dropdown option to build the HTML primary.
In my copied project (or an export with Lingo) on the server, the button 'Build Primary' has no dropdown option to build the HTML primary.
Pushing the button 'Build Primary' (so not on the dropdown option) starts a so called build, buit finishes 1 second later with the message 'Terminated' and in the end nothing is build.

In attachment the two screenshots with and without te dropdown option.

[wclass]

Is it possible that no primary target is set? I have sometimes noticed this when I have restored a project from a zip file, and I need to reset the primary.

[Nita Beck]

This may be a long shot, but have you checked to make sure that the HTML5 target in the copied project actually IS set as the primary target? I have seen cases where there is a project for which no target has been set as the primary target.

In the Project Organizer\Targets, is there a primary target designated?

[PracGren]

1. I have MadCap project on local C:/ disk. Regulary I make a copy to the server.
2. This copy is the source for the Lingo translation project, for another person. The Lingo project is synchronized from this copy on the server, as the Lingo project has no access to my C:/ disk.
3. The Lingo project is exported when translated.
4. I open this translated Lingo export in MadCap to build the HTML, and here it goes wrong.

I tried to find a solution and found one work-around:

1. I copied the Lingo project from the server to my C:/ disk
2. I opened the Lingo project from the C:/ disk
3. I exported the translated Lingo project on my C:/ disk
4. I opened the exported Lingo project in MadCap
5. Now it was possible to build the primary form the exported Lingo project

I come to the conclusion:
A. That it has to do something with the path that is not found, but I have no idea where to correct the path.
B. I have a major problem whenever my C:/ disk crashes as I cannot start any HTML build from the copy on the server.
C. I upgraded recently from MadCap 10 to MadCap 12. This is the first HTML build I try with MadCap 12. Making a HTML build with MadCap 10 from the copy on the server was no problem.

I would like to figure out what changed in MadCap 12 (or MadCap 11) in relation to the HTML-build.
If I copy an entire MadCap project to the server, why should I have to define the primary target again to build the HTML when I open the project on a server? On the server the primary target is not found anymore, and I think a reference to the path referring to the C:/ disk on the server which exists on MY C:/ disk but not on the server C:/ disk is the cause.


Could this be examined if this is the cause?

[Nita Beck]

I'll ask again: Does it appear that there is no primary target designated at all?

If that is the case, and if you then set the HTML5 target as primary, can you then build? I can't explain why Flare might not keep track of the primary target in the copy, but if you can set the target as primary and then build, I think that's your solution.

[PracGren]

There is a Primary target assigned in the copy of the project on the server. De button 'Build Primary' however has no drop down button "Build HTML5" as show on the screenshots earlier.
Pushing the button 'Build Primary' (not the dropdown button "Build HTML" as it not available) starts an HTML-build 'starts' but after one second it is finished, off course without result.
The Frame 'Builds' at the bottom shows 'TERMINATED' message after one second.

You can easely reproduce this error:

1. Try to copy an entire MadCap project from which you have already once build a primary HTML on your local C:/ Disk to a server (or a perhaps also to a different Disk).
2. Start up your project from your copy, and you wil see the Primary Target an your Build Primary will not work (the same way) as they do on your C:/ disk.

I found a work-around, bud as you mention it is hard to explain why the copy does not function the same way the original project does.
There must be somewhere a reference to the location of the origanal project on the local drive.

Putting everything back on the C: / disk resolves the problem, but this cannot be the purpose...

[Nita Beck]

Sorry we can't help you sort this out further. If you think this is a bug, please report it to MadCap so it gets their attention: https://www.madcapsoftware.com/feedback/bugs.aspx

[chrisj]

After you copy the project to the server, can you still open the desired target and build it that way, or does the target not exist anymore? How exactly are you copying the project to the server?

[NorthEast]

If it's working locally, but not on the server, then maybe check your server.
Check the Windows permissions you have for the folder on the server - can you read, write, modify?

The primary target is set for each user in this file in your project:
...\(Your project)\Project\Users\(Your name)\UserData.fluser

It'll include a line like this:
PrimaryTarget="/Project/Targets/Your Target.fltar"

[PracGren]

After you copy the project to the server, can you still open the desired target and build it that way, or does the target not exist anymore? How exactly are you copying the project to the server?

I made a copy to the new location in Windows using 'copy' - 'paste'. I suppose as 'dynamic' link is not defined as dynamic but static. Instead of changing the path to te new location it still refers to the location it was copied from. As that link is not accessible from the new location, the primary build process stalls.

[PracGren]

If it's working locally, but not on the server, then maybe check your server.
Check the Windows permissions you have for the folder on the server - can you read, write, modify?

The primary target is set for each user in this file in your project:
...\(Your project)\Project\Users\(Your name)\UserData.fluser

It'll include a line like this:
PrimaryTarget="/Project/Targets/Your Target.fltar"

Both files in the copied project are available, and there are no restrictions on accessing the folders.

UserData.fltar has following content:
<?xml version="1.0" encoding="utf-8"?>
<CatapultUser
PrimaryTarget="/Project/Targets/HTML5.fltar" />

In both original and copied project the content both files is exactly the same.
The primary build has the intention to start, but finishes after one second and the build frame reports: Build TERMINATED but thers are no HTML pages build.

[Nita Beck]

Rather then copy-and-=paste, what happens if you open the project on the server and zip it up (Project > Zip Project), and then copy the zip file to your computer and unpack it with Flare there?

[PracGren]

Rather then copy-and-=paste, what happens if you open the project on the server and zip it up (Project > Zip Project), and then copy the zip file to your computer and unpack it with Flare there?

Has exactly the same effect as 'copy' 'paste' the project. Primary Target HTML5 is defined, drop down on button Build Primary is not available and pushing the button 'Build Primary' starts up a build but is terminated after 1 second.
I think I wil report this as a bug