Multiscreen/Responsive HTML5 Generation failing in RoboHelp 2019.0.14 New UI

Sep 23, 2020

Copy link to clipboard

Copied

Updated a Webhelp project originally created in RBH 2014. I have version 2019.0.14, using the new UI (not classic). In addition to keeping the Webhelp version of this fairly simple Help project updated (TOC, Index, maybe 20 total topics, nothing fancy), I also now need to create output that will work on mobile phones and tablets (Android and IOS). I should preface this by saying I'm not a RBH expert or advanced user...I rarely need to use RBH. For the mobile device outputs, creating apps for the Apple and Google stores is NOT an option, not wanted by our Developers. So I'm assuming I need to use Multiscreen/Responsive HTML5. I'm working my way through Peter Grainge's RoboHelp Tour. But in the meantime...I saw something in there about taking a look at the error log if Generation fails. I looked and the generation stopped either during or before the Index was "processed." It appears to have processed all the topics, but stopped after/on the Index. Is that of any significance? Any other tips to help me get this pesky output created? Any help from the community would be greatly appreciated. Thanks, all!

Views

92

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Multiscreen/Responsive HTML5 Generation failing in RoboHelp 2019.0.14 New UI

Sep 23, 2020

Copy link to clipboard

Copied

Updated a Webhelp project originally created in RBH 2014. I have version 2019.0.14, using the new UI (not classic). In addition to keeping the Webhelp version of this fairly simple Help project updated (TOC, Index, maybe 20 total topics, nothing fancy), I also now need to create output that will work on mobile phones and tablets (Android and IOS). I should preface this by saying I'm not a RBH expert or advanced user...I rarely need to use RBH. For the mobile device outputs, creating apps for the Apple and Google stores is NOT an option, not wanted by our Developers. So I'm assuming I need to use Multiscreen/Responsive HTML5. I'm working my way through Peter Grainge's RoboHelp Tour. But in the meantime...I saw something in there about taking a look at the error log if Generation fails. I looked and the generation stopped either during or before the Index was "processed." It appears to have processed all the topics, but stopped after/on the Index. Is that of any significance? Any other tips to help me get this pesky output created? Any help from the community would be greatly appreciated. Thanks, all!

Views

93

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Sep 23, 2020 0
Sep 23, 2020

Copy link to clipboard

Copied

There's no multiscreen html in New UI, and your webhelp has been automatically converted to a Responsive HTML5 output. Note that if the output was called "Webhelp" in Classic, that will still be its name, but it has definitely been converted. If you look at the icon to the left of the output preset name, it'll show a shield with a 5 in it. That means it's a Responsive HTML5 output now.

 

There is a setting on the skin which determines whether it behaves like webhelp in RH Classic (does not change layout to fit different sized screens) or is actually responsive (changes layout to fit different screen sizes). I believe this is on by default so you shouldn't have to change anything to get an output that works on desktop, tablet and mobile.

 

On to the error message. 🙂

 

Did a popup message display stating generation failed? What was the exact wording or can you get a screenshot of it? Can you remember what the progress popup was showing just before generation failed? Also the last 6-10 lines of the log might provide some clues. (Actually, the messages probably won't help, but one lives in eternal hope.)

 

 

 

 

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 23, 2020 0
Sep 23, 2020

Copy link to clipboard

Copied

The setting to be non responsive is off by default when you create a new skin or upgrade a responsive skin in a Classic project. It is on by default when you upgrade webhelp that was in a Classic project.

 

As your project has changed from WebHelp to Responsive, the calls from your software will need to change. As your developers are going to have to make that change, it might be a better option to look at Frameless outputs. That is where future RoboHelp will go so changing now will save having to change again later.

 

If you don't progress the generation issue, it might be worth creating a new preset, not a duplicate and trying with that.

 

Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 23, 2020 0
Sep 24, 2020

Copy link to clipboard

Copied

Peter, my Update 12 has responsive turned on for an upgraded webhelp output. Do you know when it changed as I can't see anything in the issues fixed page.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 24, 2020 0
Sep 24, 2020

Copy link to clipboard

Copied

I don't think it has changed. What I said was "It is on by default when you upgrade webhelp that was in a Classic project".

 

Please use the blue Reply button at the top to help me help you. The black Reply link nests replies and they sort out of order.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 24, 2020 0
Sep 24, 2020

Copy link to clipboard

Copied

Nope I'm still lost.

 

Here's what I have.

 

Classic project with :

a. Responsive HTML5 using Azure Blue.

b. Webhelp using <traditional no skin>.

c. Webhelp using <Default>.

d. Webhelp using Aquamarine.

 

Upgrade to 2019 New UI:

a. Responsive using Azure Blue. Azure Blue has Responsive selected

b. Webhelp (all), no Layout selected, but generates fine and the skin appears to be Azure Blue in the output. All work as Responsive outputs.

 

I'm missing something somewhere, I'm just not sure what.

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
Reply
Loading...
Sep 24, 2020 0