Hello,
there seems to be a difference between Flare 11 and Flare 12 when using the Madcap css style 'mc-disable-glossary-terms: true;'. We use this setting to prevent terms in specific styles from beeing converted into glossary popup links. For example, there's a class 'p.glossary' with mc-disable-glossary-terms: true; that prevents glossary links in the glossary topic itself.
This has worked well for years and versions up to Flare 11. Now, a collegue in another european department uses Flare 12, and the mc-disable-glossary-terms refuses to work. He builds the same project that I created in Flare 11 in his Flare 12 version, and there is no disabeling. If he build the same project in Flare 11, everything's fine.
Has anyone heard about this? Is the flglo file or css file treated in some different way in Flare 12?
I found some posts about differences between Flare 11 and 12, but nothing about trouble with mc-disable-glossary-terms: true;. We are planning to migrate to Flare 2017 soon, and I'm a little unsecure about what we will expect...
Regards
Herbert Pösch
mc-disable-glossary-terms: true;
-
Herbert Poesch
- Propeller Head
- Posts: 20
- Joined: Tue Aug 12, 2014 5:17 am
-
GregStenhouse
- Sr. Propeller Head
- Posts: 330
- Joined: Tue May 13, 2008 3:27 pm
- Location: Christchurch, New Zealand
Re: mc-disable-glossary-terms: true;
No problems here with that setting and Flare 2017, maybe raise a support ticket if you're worried about specific behaviour between Flare 11 and Flare 12?