MadCap Software Forums

I'm using Flare 6.1 (having been a Flare user since 3.x).

I suddenly discovered that the Project Organizer is not displaying my TOCs folder. My files are all there when I navigate through Windows Explorer to look for them but Flare doesn't seem to see them.

Here's a screen capture...

The only time I've seen something like that was when I had a project on a networked drive and there was a delay between the time I created/renamed a folder and seeing the change in the Flare GUI, but if I didn't do a refresh in the pane it still updated within a minute or two.

There's also a Users folder that's not showing up (based on the screenshot on the right), but that one normally doesn't show up, so you might want to double-check the properties of the Tocs folder via Windows Explorer to see if you somehow inadvertently changed it to an archive-only folder or changed something else that resulted in it not being treated like the other folders.

One last thing... In my project the folder is called TOCs not Tocs. Maybe you renamed it and that resulted in it not being recognized???

LTinker68 wrote:One last thing... In my project the folder is called TOCs not Tocs. Maybe you renamed it and that resulted in it not being recognized???

Nope, the issue wasn't a networked drive as the project files are all local and it wasn't the folder properties either. The issue was that I was working with restored files that had been backed up before a system upgrade to my desktop. Somehow all the TOCs folders got renamed to Tocs for my projects which is why Flare wasn't seeing them. Gonna have to run around and change the folder names back.

Still... is that a Flare bug? That the UI is sensitive to folder name case?

Thanks for the response, Lisa.

Is it a bug?

Considering Flare creates and maintains the directory and it was third party software that restored using a different name (TOC does not equal Toc in the purest sense) don't know that it is a bug. Is it annoying? Yes.

Anything that affects usability should be reported, leaving it up to Madcap to look at. They may fix it, or not, depending on resources and how important the issue is seen to be (that's why the more who report an issue, the better; lots of reports make it more important). So, I'd lodge a bug report: https://www.madcapsoftware.com/bugs/submit.aspx to see if they can stop it catching someone else out. And, given the stress surrounding an event when you have to restore from a backup that might not be a bad thing...