MadCap Software Forums

I am generating a WebHelp output for a web application using Flare 8.

My team runs a security scan on everything using an app called Cloudscan and it came up with what it deems a "critical" security flaw in the WebHelp output I gave them. Here is the text of the scanner message:

Issue: Cross-Site ...

To be honest, I'm not convinced it was Flare that caused it. It could easily be that the error she had was a symptom rather than the cause (in other words, a drive died or Windows screwed up so the files that Flare was working with were no longer there - so naturally it popped an error).

That ...

Assuming the data recovery won't be a problem in and of itself, does anyone have any ideas about why Flare did this?

I apologize - I should have been more clear. The files and folders are physically gone from the PC. They are not in the Recycle Bin, as I would expect for files that might have been erroneously deleted. Unfortunately this user was working from a local drive on a Windows XP machine and no recent ...

Good morning,

Someone on my team was renaming folders in the Content Explorer view of Flare 4.2. Flare was prompting to update links, which she was doing. However, after a number of folders renamed, she got the nebulous "Flare has encountered an error and must close." When she re-opened the project ...

It does happen in both. I would say Firefox is a wee bit faster, but there is still a delay. I did a tag check and everything is properly closed and nested.

Our project has two topics that contain 4 togglers, each with 5-10 instances of drop-down text. The drop-down text body of most of them also contains at least one snippet.

We have found that the performance of these two topics is severely degraded. In the Preview and in the compiled WebHelp ...

LTinker68 wrote:Are you using a masterpage and does the masterpage have a condition on it or in it?

Ah, yes, that was the problem. Thank you!

Does anyone know why Flare would insert a condition into every topic at build time? We have discovered when viewing the source of compiled topics (both in WebHelp and CHM) that Flare has taken it upon itself to place "MadCap:conditions='Primary.Web_Server'" into the HTML tag of every topic. This is ...

Wondering if anyone has seen this issue.

I compile a CHM with a modified Default skin. It displays fine on my PC when I launch it. However, when the developer puts it in a build and launches it, it display the TOC and some raw XML in the content pane. If he clicks away to another topic it displays ...