Flare 3.1 to Flare 4.0

[Alicia143]

I upgraded to 4.0, but when I send files to the developers to upload to GUIs (webhelp), they say that the XML is different, and they need the old version of the help. So, I have to compile each time using Flare 3.1. This leads me to believe that everytime I update my version of Flare that it will no longer be compatible with the GUI. Therefore, this causes rework for developers. Is this true?

What can I do that will allow me to upgrade Flare, without causing extra work for my project teams?

Thanks,
Alicia

[KevinDAmery]

Haven't heard about that one before. What type of target are you building to?

Also, did the developers mention what specifically was different?

[carolhobz]

We sent a webhelp project created in Flare 4.2 to our localization vendor is using Flare 3.0. They get an error when they build the help (...quasar.css Line 577. char 6. Bad token in selector). At that point in the CSS, I see this:
MadCap|xref.ConceptPageNumber
{
mc-format: '{paratext}';
}

Could this be a related problem?

Carol

[LTinker68]

There were changes to how the stylesheet is created in v4 versus v3. You can't go backward because when you do, the new stylesheet code and everything inserted after it is deleted. The new code is things like MadCap|toggler instead of toggler. So v3 doesn't recognize the new styles in v4. The localization vendor needs to upgrade to v4 or you need to do your edits in v3 until they upgrade.