Use Skin Home Page off not working

Community Beginner ,
Dec 12, 2020 Dec 12, 2020

Copy link to clipboard

Copied

I'm using RH2020.3 and a Frameless Preset on a project that has a structure not suitable for the tiled home page, so I want it to open with the menus on the left at a specific start topic (i.e. no home page). When I uncheck the "Use skin home page", I get exactly what I need when generating the preset and viewing it from the local path. However, when I publish to IIS, it only works if I enter the full path to the file index.htm (e.g. https://domain/site/index.htm). If I point the browser to the site without including the index file (e.g. https://domain/site/) I get

404 - File to directory not found
.


In IIS, I have index.htm set as the default page, so I'm certain there's nothing wrong with the web server.

 

I think there might be a problem with the RH redirect script "./template/scripts/redirect.js" that called from index.htm. It's getting to index.htm the browser is then being redirected to the wrong URL by that script. In the browser, instead of seeing https://domain/site/default-topic.htm, I'm seeing the redirected URL https://domain/default-topic.htm. It's missing the site name in the redirected URL.

 

Is this a bug?

Does anyone know of a workaround?

Views

89

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
community guidelines
Community Beginner ,
Dec 12, 2020 Dec 12, 2020

Copy link to clipboard

Copied

This looks like a bug in RH 2020.3 redirect.js.

If I create a new project in RH2019, add the Orange Frameless skin, generate with a Frameless Preset with all the default settings but the "Use Skin Home" off and publish to IIS, the site starts without error using http://server/site/.

If I repeat this identical test using RH2020.3, the site only starts using http://server/site/index.htm; it shows the 404 error using http://server/site/.

If I copy the file template\scripts\redirect.js from the test website created with RH2019 to the test website created using RH2020, the site works without a problem.

I think this proves there is a problem with template\scripts\redirect.js in RH2020 compared with RH2019.

As I'm about to publish a live site, my workaround is to manually replace the file template\scripts\redirect.js with one from RH2019 each time a publish, but hopefully this can be fixed in a later release?

Graham Keen

 

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
community guidelines
Adobe Community Professional ,
Dec 13, 2020 Dec 13, 2020

Copy link to clipboard

Copied

For your case is the test you ran as that seems to prove the point. Against it is that no one else has reported this.

 

I have referred this to an Adobe contact and will let you know what comes back.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

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
community guidelines
Adobe Community Professional ,
Dec 13, 2020 Dec 13, 2020

Copy link to clipboard

Copied

I have had confirmation that this will be looked into. 

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

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
community guidelines
Adobe Community Professional ,
Dec 14, 2020 Dec 14, 2020

Copy link to clipboard

Copied

LATEST

Adobe have been able to replicate this and it will be fixed in the next update. Meantime you will need to use the workaround that you found.

________________________________________________________
See www.grainge.org for free Authoring and RoboHelp Information

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
community guidelines
Resources
RoboHelp Documentation