Responsive HTML5 Output is getting stuck on Compressing files

Forum|Forum|3 years ago
January 5, 2023
2 replies
257 views

When generating two different HTML5 outputs from my project, RoboHelp appears to be getting stuck on Compressing files. The status bar continues to run under Output Presets. If I view the log file, it shows that Output generation was successful and the files seem OK, but I would prefer that RoboHelp indicate to me that the generation was successful. Has anyone else seen this? I am using RoboHelp 2020.8.34.

This topic has been closed for replies.

Correct answer JC @ Salient

I was able to identify the problem. A post generation script was missing. Once I put the script back in place and re-selected it in the output, it generated successfully and didn't get hung up.

Peter Grainge

Community Expert

In addition to @Jeff_Coatsworth suggestions, are generating two simultaneously or consecutively. If done one at a time, how long have you left the status bar running?

________________________________________________________

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

Use the menu (bottom right) to mark the Best Answer or Highlight particularly useful replies. Found the answer elsewhere? Share it here.

J

JC @ SalientAuthorCorrect answer

Inspiring

I was able to identify the problem. A post generation script was missing. Once I put the script back in place and re-selected it in the output, it generated successfully and didn't get hung up.

A

Amebr

Community Expert

It might be worth reporting this as a bug. I think it would be good if there was a message that the post generation script could not be run/found/something. 🙂

You can request features and report issues here: https://tracker.adobe.com/

Post the item number in the discussion so people can easily vote if they want the same functionality.

Jeff_Coatsworth

Community Expert

Few troubleshooting questions - was this happening before or is it the first time? Does it occur when you try it with the sample project? If so, then it's probably something to do with the software or your environment; if not, then it's something in your project that's tripping up the process. If that's the case, then it comes down to identifying the topic(s) that are getting the process stuck.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded