Issue with Frameless Output in Robo Help - Partial Content Publishing

[chinju_mohan_1326]

I am currently experiencing an issue with Adobe Robo Help where the project published with the frameless layout is only showing partial content. Despite my efforts to resolve this, the problem persists.

Here are some details regarding the issue:

• Software Version: Version 2022.3.93
• Project Name: Help Support Document (Test)
• Output Format: Frameless
• Description of Issue: The output appears incomplete, with only a portion of the content being published. I have verified the project settings and publish options with the IT support, but the problem remains unresolved.

Could you please assist me in identifying the cause of this problem and provide guidance on how to resolve it? Any help or suggestions you can offer would be greatly appreciated.

[Peter Grainge]

Was it working and has now failed or are you new to the New UI version of RoboHelp?

I suspect it is the latter and you are not aware of the change in how content gets into the output. In Classic topics were published unless you excluded them. Now topics have to be in the TOC but they can be hidden from the TOC the user sees.

It's explained here. 

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

[Jeff_Coatsworth]

You talk about publishing being incomplete - have you tried generating the output locally & checking it before it's moved to its final location? The actions of "publishing" and "generating" in RH have two different meanings (publishing involves generating and FTPing the output someplace you specify; generating only creates output in a named local location).

[Peter Grainge]

Publishing doesn't automatically generate first, it will prompt you to generate if the last generation is out of date. 

________________________________________________________
My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

[Jeff_Coatsworth]

Wouldn't that scenario only apply if you had made no changes to any of your content or settings in a project? (in which case, why are you in there publishing again anyways?)

[Peter Grainge]

@Jeff_Coatsworth In a quick read I interpreted "have you tried generating the output locally & checking it before it's moved to its final location" as suggesting they had only published, which of course you cannot do.

When you publish, RoboHelp checks for any changes and if there are any it prompts you to generate first. If there aren't any, then it should not prompt and just proceed to publish. However, I have seen instances where on opening a project and going straight to publishing, it prompts when I don't believe there were any changes.

On occasion I have published and ignored the warning when what I am wanting to see is not affected by any changes.

I was just trying to clarify rather than contradict.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.

[Jeff_Coatsworth]

Having never published anything, my understanding of the publish process was theoretical - that it always generated first (I think to some temp location) and then transferred that output to the specified web server. As a troubleshooting aid, taking out the "transferring" part of that compound process allows you to check that the output generated to your named local location is "good" or not. If so, then you can look at the "transfer to the final destination" part for issues. As the OP hadn't specified that the output was looking good locally or not & that people think "generate" and "publish" are synonyms, I thought it was a good idea to see what exactly they think was incomplete. 

[Peter Grainge]

@Jeff_Coatsworth No that's not the way it is designed to work.

• You must generate but that is to a chosen location that is best on the same drive as the project. It is not a temporary process and for many authors it will be the final stage. Their developers will take the generated output and deal with copying it to the final location.
• Publishing is optional. It allows the author to copy the generated output to its final location or some other location than their machine from where the developers will lift it.

Suggesting they check the local output though was correct. @chinju_mohan_1326 had not stated whether the issue was with the generated output or the published copy. You were correctly wanting them to check the stage at which things were going wrong. Whilst the published output was stated, too often people use the term when they could mean either.

________________________________________________________

My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.