---
title: "Madcap Flare Spotlight – “Six Persistent Flare Problems” Post by Paul Pehrson"
date: 2007-06-14
description: "$( document ).ready(function() { // Handler for .ready() called. $('#toc').toc({ minimumHeaders: 3, listType: 'ul', showSpeed: 0, headers: '#content h2, #content h3, #content h4, #content h5, #content h6' }); /*..."
canonical_url: https://idratherbewriting.com/2007/06/14/madcap-flare-review-six-persistent-problems/index.html
---

> For AI agents: a documentation index is available at https://idratherbewriting.com/llms.txt. Markdown versions of all pages are available by appending .md to any page URL.

# Madcap Flare Spotlight – “Six Persistent Flare Problems” Post by Paul Pehrson

**Update Feb 2008:** If you read Paul's post at the link below, almost everything is now crossed out, because Madcap has either fixed all the problems Paul raised or they explained workarounds. It's a really interesting read. Also, be sure to check out this [podcast with Paul](https://idratherbewriting.com/2008/01/19/madcap-flare-paul-pehrson/) as well as my post on [45 Things I Love About Flare, 31 Things I Hate About It](https://idratherbewriting.com/2008/01/31/45-things-i-love-about-flare-31-things-i-hate-about-it/).

Paul Pehrson has an excellent post detailing [six persistent problems](http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/) he's encountered with [Flare](http://madcapsoftware.com/products/flare/home.aspx). Paul introduces his post saying,

> I'm a Flare user, and I really, really, really like Flare as a help authoring tool (HAT). It's a solid program that does a lot of great things. On my recommendation, my company is going to renew our maintenance contract with Flare this fall, and I expect to be using Flare for a while to come.
>
> That said, I think that there are a few persistent problems in Flare that new users should be aware of when they start using the product. None of these are deal-breakers for me, even in the aggregate. Still, I think that these are things that if I had known were problems, I wouldn't have spent hours banging my head against the wall trying to solve them.

[![Technically Speaking — Paul Pehrson's blog](https://s3.us-west-1.wasabisys.com/idbwmedia.com/images/technicallyspeaking1.gif)](http://blog.paulpehrson.com/2007/06/13/six-persistent-flare-problems/)

I enjoyed Paul's post. Every tool has its shortcomings, quirks, and flaws that you don't experience until you start using the tool extensively. At least now if you go in the direction of Flare, you will be less likely to encounter surprises.