Cannot Type Text in Topics; CSS Error in Messages?

This forum is for all Flare issues not related to any of the other categories.
Post Reply
mdomask
Jr. Propeller Head
Posts: 2
Joined: Fri Jul 26, 2013 2:00 pm

Cannot Type Text in Topics; CSS Error in Messages?

Post by mdomask »

Hi, all,

I am trying to evaluate Flare for possible use by my company. So far, I've been able to import our current RoboHelp project into flare, complete with ToC, Index, CSS, etc.

However, I cannot seem to actually edit any topics. I've tried both creating a new topic and editing existing ones. I open the topic, put my cursor where I want to type, type a few characters (normally just 1), and then get the following in the Messages panel:
CSS: C:\Users\<username)\Documents\My Flare Projects\Test Conversion\Content\Test Topic.htm: CSS: Invalid font-style: none

I cannot seem to actually type any text at all in Flare. This is not a very good first experience in the evaluation.

I've tried the import both with and without creating styles from inline formatting.

Any help would be appreciated.

Thank you!
LTinker68
Master Propellus Maximus
Posts: 7247
Joined: Thu Feb 16, 2006 9:38 pm

Re: Cannot Type Text in Topics; CSS Error in Messages?

Post by LTinker68 »

mdomask wrote:So far, I've been able to import our current RoboHelp project into flare, complete with ToC, Index, CSS, etc...

CSS: Invalid font-style: none
The problem isn't with Flare. Somewhere in that content you imported from RoboHelp, there is a CSS declaration where the font-style was set to "none". None isn't a valid value for that attribute. The valid choices are normal, italic, oblique, or inherit. I can't tell from that error message if the declaration is also missing the semi-colon to terminate the declaration, which could also be causing problems. RoboHelp might have just ignored that bad declaration, but Flare doesn't.

That bad style declaration could be in the imported stylesheet or in the topic. Since you're having problems when you create a new topic, I'd say it's more likely to be in the stylesheet file. I would open the stylesheet file in the Internal Text Editor and do a find on font-style: none.

To test it, you could make a copy of that stylesheet outside of Flare as backup, then in the project, open the stylesheet file in the Internal Text Editor and delete all the code and save the file. I've never actually tried that, but with no code, Flare should resort to the default styles, so try creating a new topic and see if you run into the same problem. If you don't, then you've narrowed the problem down to the original stylesheet.
Image

Lisa
Eagles may soar, but weasels aren't sucked into jet engines.
Warning! Loose nut behind the keyboard.
Msquared
Propellus Maximus
Posts: 848
Joined: Mon Aug 06, 2012 10:19 am
Location: Southampton, UK

Re: Cannot Type Text in Topics; CSS Error in Messages?

Post by Msquared »

It is also worth noting that MadCap support are really, really helpful, and if this looks like blocking you, you could try contacting one of their sales team with your query initially. When I was evaluating Flare I found a few things I couldn't get working, and they were very helpful.

And the excellent support doesn't stop once they have sold you Flare either.They usually have some sort of bundle offer on their support packages, and they are worth every penny.

Welcome to the Flare community!
Marjorie

My goal in life is to be as good a person as my dogs already think I am.
rob hollinger
Propellus Maximus
Posts: 661
Joined: Mon Mar 17, 2008 8:40 am

Re: Cannot Type Text in Topics; CSS Error in Messages?

Post by rob hollinger »

During your Trial experience, you have free access to Phone support.
Give us a call and let us help you locate and remove that bad style and answer any current questions you might have.

7:00 AM to 4:00 PM (Pacific), Monday-Friday 858-320-0387 option 4
Rob Hollinger
MadCap Software
mdomask
Jr. Propeller Head
Posts: 2
Joined: Fri Jul 26, 2013 2:00 pm

Re: Cannot Type Text in Topics; CSS Error in Messages?

Post by mdomask »

Thanks, all. The CSS change seems to have fixed it.
Post Reply