When I import a master page, it comes over with the conditions on it from its native help system. If those conditional tags don't exist in the new help, then when I go to assign NEW tags to that master page, its square will show half white and half whatever color the new tag is. The white part usually means that I need to go into the XML and remove the tag from the old system, then it works fine. But sometimes, as now, the XML has NO conditional tag. It's usually right before the <head> tag. There's nothing there and doing a search of the XML shows that the old tag is nowhere in the code. The tag I just added isn't showing either, even though the square in the Content Explorer colors itself correctly (half of itself, anyway).
Has anyone experienced this? Where is this .flmsp file keeping the information about its conditionality if not in a tag? And why is this happening with some files and not others?
Thanks,
mdf
Conditional tags disappear from imported .flmsp files
Conditional tags disappear from imported .flmsp files
Matt F
You learn something new every day if you're not careful.
You learn something new every day if you're not careful.
-
KevinDAmery
- Propellus Maximus
- Posts: 1985
- Joined: Tue Jan 23, 2007 8:18 am
- Location: Darn, I knew I was around here somewhere...
Re: Conditional tags disappear from imported .flmsp files
Are you looking at it in the XML editor or a text editor? Sometimes going into a text editor can help if you haven't already.
Until next time....

Kevin Amery
Certified MAD for Flare
Kevin Amery
Certified MAD for Flare
Re: Conditional tags disappear from imported .flmsp files
Thanks Kevin,
I was looking at it first in Flare's xml editor and then in XMLSpy, an external editor. Yes, I've noticed that some things show up in an external editor that aren't visible in the internal one, but in this case, the conditional tags don't appear in the code in either editor. I'm thinking they might be in the body proxy, but that doesn't explain why sometimes I open a file and the conditional tag is right at the top. And anyhoo, where is the body proxy? I mean, it should be an xml file housed somewhere in the project, right?
I was looking at it first in Flare's xml editor and then in XMLSpy, an external editor. Yes, I've noticed that some things show up in an external editor that aren't visible in the internal one, but in this case, the conditional tags don't appear in the code in either editor. I'm thinking they might be in the body proxy, but that doesn't explain why sometimes I open a file and the conditional tag is right at the top. And anyhoo, where is the body proxy? I mean, it should be an xml file housed somewhere in the project, right?
Matt F
You learn something new every day if you're not careful.
You learn something new every day if you're not careful.
Re: Conditional tags disappear from imported .flmsp files
Oh, I see. It's in the *.flmsp.props file.
Duh.
Still curious why it appears above the <head> sometimes, but at least I can work with this.
Duh.
Still curious why it appears above the <head> sometimes, but at least I can work with this.
Matt F
You learn something new every day if you're not careful.
You learn something new every day if you're not careful.
Re: Conditional tags disappear from imported .flmsp files
I don't have Flare open at the moment, but as I recall, if you apply a conditional tag to the entire topic, then the MadCap:conditions (?) property is added to the <html> tag. I don't think I've ever seen it as a separate tag between the <html> and <head> tags, but maybe it did that since it's an imported project.
Lisa
Eagles may soar, but weasels aren't sucked into jet engines.
Warning! Loose nut behind the keyboard.
-
SteveS
- Senior Propellus Maximus
- Posts: 2090
- Joined: Tue Mar 07, 2006 5:06 pm
- Location: Adelaide, far side of the world ( 34°56'0.78\"S 138°46'44.28\"E).
- Contact:
Re: Conditional tags disappear from imported .flmsp files
I have noticed if you apply a condition and remove it the condition doesnt get removed, just the property. So you end up with madcap.conditions="". Then if you reapply or add condtitions a new declaration is added. This leads to the effect Matt has reported, rather than a plain red square (if red is the indicator for the condition), you see a red and white square.
Steve
Life's too short for bad coffee, bad chocolate, and bad red wine.