In the past few months, users have been having intermittent problems viewing my Webhelp output files such as not being able to open the first topic, topics not displaying when selected in the Search pane, and screenshots not displaying even though the text does.
On investigation, most of the error messages users get when this occurs point to the MadCapAll.js file. A couple of examples are:
"Can't execute code from a freed script. MadCapAll.js. Line 8227. Code: 0. URL: http//[directory path]/MadCapAll.js"
and
"Unable to get value of the property 'split': object is null or undefined. MadCapAll.js. Line 8227. Code: 1. URL: http//[directory path]/MadCapAll.js".
Has anyone else seen these or similar problems and if so, do you know how to fix them?
Thanks.
Viewing errors and the MadCapAll.js file
Re: Viewing errors and the MadCapAll.js file
Hi devans,
Did you get a response or find out what caused this issue?
This post is a couple of years old, but I was wondering if there was any more information (perhaps from MadCap?) on what the potential casuses of this issue are.
In particular: "Unable to get property 'getElementsByTagName': of undefined or null reference. URL: http//[directory path]/MadCapAll.js".
I rarely see this type of error in house, but have just received a call from support where this error is occurring.
Thanks,
Did you get a response or find out what caused this issue?
This post is a couple of years old, but I was wondering if there was any more information (perhaps from MadCap?) on what the potential casuses of this issue are.
In particular: "Unable to get property 'getElementsByTagName': of undefined or null reference. URL: http//[directory path]/MadCapAll.js".
I rarely see this type of error in house, but have just received a call from support where this error is occurring.
Thanks,
Re: Viewing errors and the MadCapAll.js file
Sorry, I didn't get any information about this problem but it seems to have disappeared. It might have been a problem with a particular version of a browser. You could ask the users to try using a different browser. I also find that clearing the browser cache helps to sort out any viewing problems when they do arise. For example, if I rename an HTML file in Flare and users have looked at that page, they get an error 404 that the topic is missing. Clearing the cache gets rid of that problem.
Sorry I can't be of more help.
Sorry I can't be of more help.
Re: Viewing errors and the MadCapAll.js file
No problem, thanks for the response.
I thought this might have been an issue to do with IE 11 (as I later found out that is what the customer is using), but we have tested the webhelp in IE 11 and it works fine.
We are using Flare 9.1.2.
Hoping it is some kind of one off problem and have also forwarded your suggestion of clearting the cache to the consultant.
Thanks,
I thought this might have been an issue to do with IE 11 (as I later found out that is what the customer is using), but we have tested the webhelp in IE 11 and it works fine.
We are using Flare 9.1.2.
Hoping it is some kind of one off problem and have also forwarded your suggestion of clearting the cache to the consultant.
Thanks,