Conditional tags not working for content in one folder

[Liv_W]

Hi everyone,
I am having an issue with conditional tags, applied to sections of text, not working for content in one folder,inside the Content folder. I tested it with a topic that was just in the Content folder and the tagging worked. I had previously tagged this folder with a condition tag, but since removed it. Could that have an effect? I have been playing with this for hours and I am really baffled.
Thanks,
Liv

[dorcutt]

I don't know exactly what's going on, but this should help shed some light on the subject. First off, try closing and reopening Flare. Sometimes that helps.

1. Make sure that Windows is set to display system and hidden files. (edit: oops! forgot half the sentence).
2. Using Windows explorer, navigate to the folder inside the Content folder that is misbehaving
3. Check to see if the folder has a ".folder.props" file in it. This is what controls conditions for folders.
4. Open the PROPS file in a text editor and see if something odd is in it.
5. If necessary, make a copy of the PROPS file as a backup, then delete it.

If this doesn't work. try deleting your Output and Analyzer folders. Backup any output that you want to save first.

[Liv_W]

You were right. There is a props files that I think may be causing some problems, and I attempted to remove it,via deleting it in my folder, but it keeps coming back in our source control, Team Foundation Server. Can it be removed through Flare or does it have to be deleted on the TFS?
Thanks,
Liv

[dorcutt]

In this case, I think that you would need to delete it separately in both Windows and in TFS, and you might have to do some jiggering to make sure that Windows and TFS agree that the file should be deleted so it stays deleted. If you have issues with this, you might want to ask whatever local support you have or in the Source Control folder.

I'm in "trial and error" mode when it comes to TFS myself still, I'm afraid.

[Liv_W]

Thanks for your help. I'm taking the easy way out and moving the content and deleting the folder. I am not that familiar with TFS either and am afraid of causing some unforeseen damage.
Thanks again,
Liv

[dorcutt]

No problem! Good solution.

For what it's worth, I suspect that your difficulties deleting the PROPS file were directly related to the cause of the original problem. I think TFS was retaining a previous version of that PROPS file and was sneaking it back in secretly somehow, messing things up.