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 a problem because a) that condition shouldn't be on those topics and isn't marked for those targets, and b) that condition doesn't even exist in our project any more.
I don't think this behaviour is actually doing anything, but we have been having odd compiler errors lately and we're trying to eliminate suspects.
Condition inserted at build time
-
- Propeller Head
- Posts: 10
- Joined: Tue Apr 25, 2006 2:22 pm
- Location: Ithaca, NY
- Contact:
Re: Condition inserted at build time
Are you using a masterpage and does the masterpage have a condition on it or in it?
Lisa
Eagles may soar, but weasels aren't sucked into jet engines.
Warning! Loose nut behind the keyboard.
-
- Propeller Head
- Posts: 10
- Joined: Tue Apr 25, 2006 2:22 pm
- Location: Ithaca, NY
- Contact:
Re: Condition inserted at build time
Ah, yes, that was the problem. Thank you!LTinker68 wrote:Are you using a masterpage and does the masterpage have a condition on it or in it?