I am using Robohelp Version 2020.7.46 to generate a Frameless output and use it to implement context-sensitive help.
Clicking the index.htm file in the Output folder loads the page correctly. However, on uploading the Output folder to SharePoint/S3 Browser, the index.htm page does not load. Additionally , when I click on one of the topics in the Outputs folder, only the content is displayed, but full TOC on left, In this topics section on right, Search button, and other elements (Header, Favorites) on the page are missing.
Any suggestions would be greatly appreciated.
not sure about the other items not loading but for the index, is there a difference in the casing for the index file (Index.htm vs index.htm). My server is case sensitive and selecting the convert all files name to lower case setting in the output gave me a small heart attack when i tried to build my site at first. So the links in my output topics started with uppercase but the files themselves were lowercase, which resulted it 404s. It all loaded fine in my local build but pushing it to the server is where i hit the issue.
Thank you for sharing this information, but this is not what I am looking for.
The index.htm page is generated/accessible in the output folder, but I can not access it when put on server. The topics pages display just the content and do not load the template style.
Sharepoint is not my area but I suspect it is behind the problem. Index.htm launches various processess that open the toc, the toolbar and the default topic. I suspect the problem is related to how RoboHelp does that.
If a further search on Sharepoint posts does not find the answer, then I think you will need to go to Adobe Support. See https://helpx.adobe.com/contact/enterprise-support.other.html#robohelp for your Adobe Support options. The email link email@example.com is recommended as it reaches a team dedicated to Technical Communication Suite products including RoboHelp.
My site www.grainge.org includes many free Authoring and RoboHelp resources that may be of help.
I think you need to generate sharepoint output, which creates aspx files instead. Your sharepoint administrator may also need to change a few settings to allow it to work. I think one of the settings is allow custom scripts, but I can't remember the other setting.
This is assuming that the "SharePoint/S3 Browser," is uploading to a sharepoint library.