Side Nav Panel does not display in HTML5 Help output

This forum is for all Flare issues related to the HTML5, WebHelp, WebHelp Plus, and Adobe Air Targets
Post Reply
DownintheHoller
Propeller Head
Posts: 11
Joined: Tue Mar 01, 2022 12:03 pm

Side Nav Panel does not display in HTML5 Help output

Post by DownintheHoller »

Hello,

We're a first-time implementer of MadCap Help. We've packaged HTML5 Help with a Side Navigation panel skin. The skin template is derived from one of the sample skins found on the MadCap Resources web page. We did some minor customizing to the CSS and HTML, but did not touch any of the scripts.

When the files are launched from the local host, everything displays fine in the browser.

When the files are served via the server-side host, the side navigation panel does not display or displays only fleetingly and then vanishes.

This is what the error messages say:

Uncaught TypeError: Cannot read properties of undefined (reading 'config')
at inpage.js:141:114697
at inpage.js:141:140272

Uncaught Error: Mismatched anonymous define () module: function(){return it}
http://requireis.org/docs/errors.html#mismatch
at C (require.min.js:13:239)
at L (require.minjs:41:80)
at Object.g [as require] (require.min.js:104:375)
at requirejs (require.min.js:126:445)
at MadCap.WebHelp.HelpSystem.LoadLanguage (MadCapAll.js:64:16884)
at MadCapAll.js:64:10074)
at MadCapAll.js:64:17094)
at Object.exeCb (require.min.js:119:100)
at $.check (require.min.js:62:165)
at $.<anonymous> (require.min.js:89:38)

See attached screenshot as well.

I found similar posts on this forum, but their workarounds do not seem to work in our case. Refer to:

viewtopic.php?f=12&t=33034&p=142038&hil ... us#p142038

viewtopic.php?f=6&t=30760&p=140597&hili ... ne#p140597

As always, your suggestions are most welcome. Thank you.
You do not have the required permissions to view the files attached to this post.
DownintheHoller
Propeller Head
Posts: 11
Joined: Tue Mar 01, 2022 12:03 pm

Re: Side Nav Panel does not display in HTML5 Help output

Post by DownintheHoller »

Well, we found this issue. It was on our side: Chrome plug-ins we had added. It works in anonymous or incognito mode.
Post Reply