Skip to main content
A
Community Expert
AmebrCommunity Expert
Community Expert
November 9, 2015
Question

Multiscreen publishing - parent publishes all children?

  • November 9, 2015
  • 1 reply
  • 1243 views

Hi all,

Just setting up merging in Multiscreen HTML5 output. It appears that publishing the parent publishes all the children that might exist in the "mergedProjects" folder. This is pretty undesirable behaviour when different people are working on each of the children and with different publishing schedules.

How do people manage this so that outdated or draft/test builds aren't pubished?

And does anyone know if this is the same for Responsive HTML5? Would we need to publish the parent and children all at the same time every time (given the children have to be generated into the parent build - or is that only the first time)?

Regards,

Amber

This topic has been closed for replies.

1 reply

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
November 12, 2015

It often happens the first time you generate the merge and I have never understood why that should be. I think you will find that whenever you generate the parent again, it will not happen.

No guarantees. It is best to generate somewhere and then publish. If it should generate all, you simply don't publish as well.

See www.grainge.org for RoboHelp and Authoring tips

@petergrainge

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
A
Community Expert
AmebrCommunity ExpertAuthor
Community Expert
November 13, 2015

Thanks Peter.

I realised I have Republish All ticked in the parent which forces everything to be republished all the time. When this setting is unticked, then RH only publishes stuff it thinks is different, including stuff in the mergedProjects. How it determines that I'm not sure.

To be safe, I think I'll remove the publish destination from the parent, and manually copy the output across to the server when needed - theoretically the parent shouldn't have to change very often.

Thanks again,

Amber

Peter Grainge
Community Expert
Peter GraingeCommunity Expert
Community Expert
November 14, 2015

Hmmm, I thought the only issue was publishing. Perhaps I should carefully re-read the thread? I've never seen the process of generating actually generate the child projects as well. How would that happen? Does it launch another instance of RoboHelp and generate the children?

I'm confused.

Cheers... Rick


My dear Rick, will you please stop applying logic to this? No of course

generating one project should not generate all the children, any more than

should publishing.

It's the generating that goes beserk rather than the publishing. Generating

will always generate all the topics in a project because the generate

process clears the generate folder. Sometimes though it just carried away

and then goes on to generate every project in the merge. No it doesn't open

another instance, it just generates from the parent.

Republish All only applies the publishing part of the generate and publish

process because generating is always all topics.

I believe the problem may have a connection with the phase of the moon.

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.
Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices