Rename ConditionTagSet: why is it that difficult?

[Skooter]

I have needed to rename ConditionTagSets several times. Anyway, I admit to using the old Robohelp Find & Replace tool to replace all instances of the old tag set name with the new one. I've done this often in the past with no dramas.
In version 4, it seems to work fine for .folders.props files and snippet files, but images? No, sadly not.
While the condition has been properly replaced in the .props file, Flare doesn't recognise it.

So, if I then delete the props file and create a new .props file by setting the condition in Flare, I get:

<?xml version="1.0" encoding="utf-8"?>
<fileProperties conditions="Support.mmdisplay,Help.mmdisplay,KB.mmdisplay" />

Where "Support.mmdisplay" is the old ConditionTagSet I renamed,
and where "KB.mmdisplay" is the new (renamed) condition tag set.

Bizarre!! So where is Flare picking up the reference to the old ConditionTagSet name? Gives me a big headache trying to sort it out.

(Don't know why those clever MadCap developers can't help us rename ConditionTagSets and then apply the change throughout
Must have been a popular feature request and surely not that hard???).

[Paul Griffiths]

So you're saying that selecting the Conditional Text set in the Project Organizer, pressing F2 and renaming the set doesn't work? I didn't know that.

[Skooter]

Flare version 4 has not changed in so far as a warning mesage is still displayed in the ContextTagSet Editor:
"Note: If you rename a condition tag, it is a good idea to do so before applying that tag to your content. If you rename a condition tag after you have applied it to content, your name change will not be captured in the content where you applied the tag. "

So I have two issues:
1) I shouldn't need to use Find&Replace in the first place - Flare should be able to handle renaming of conditiontagsets.
2) Find & Replace no longer works as expected (it used to work fine in 3.1)

(p.s. I wouldn't normally change my conditiontagset names willy-nilly, but I'm revising the way my projects are organised to make the best use of global projects)

[Paul Griffiths]

We seem to be talking about two different things:

(1) Renaming an entire condition tag set
(2) Renaming individual tags within that set

As far as I am aware, (1) works just as you expect it to and (2) doesn't. I really can't understand why MadCap did the right thing with (1) but not (2).

[RamonS]

Make your voice heard...or better to write your comments read here:
https://www.madcapsoftware.com/bugs/submit.aspx

[Skooter]

No, I'm talking about having to find and replace the tags in the content, i.e. the MadCap:conditions="SOMETAGSETNAME.SOMETAG" entries in topics or snippets or image .props files. The point is I shouldn't have to.

[wijnand]

I think the problem he is trying to list is that when you change the name of your conditional build tag it loses its connection with the conditions you made with the original name.

I have a solution for you ! Change the names of your conditions then start up MadCap Analyser 2.0. When its dont with its advanced scan it will give you a list of all the conditions that have incorrect names and where they are. You can then select all the ones that belong together and rename then in one go without it causing problems. I have just tried this and it worked perfectly on one of my dummy projects. just keep analuyser running in the background, change one name fix the undefined conditions and then continue until you are done. should be a lot faster then using Search and replace