MadCap Software Forums

Well, look at that. Just got a notification for a new Flare update. Going to hop right in and check out those snippets. And a TFS fix for Dave too!

Thank you both very much!
The Windows upgrade thing is a little concerning because I could not reverse an upgrade; those come from my company's IT department.
Same here. But my coworker had the issue, and it didn’t matter if he reverted to R2 or 2017 - they both had the same problem. So it’s not ...

Has anyone had issues with r3?
I had terrible issues with r2 and went back to 2017, so I am leery of upgrading again.
There was an issue with shorthand padding, but MadCap addressed it in a manual patch ( http://kb.madcapsoftware.com/Content/Flare/Patches/Flare_2017_r3/Padding_Shorthand_Gives ...

I've come across two main instances where links are inaccurately reported to be broken.

1 - Renaming a folder sometimes causes "broken links" in the files it contains. This is a known bug, and can be solved by deleting the project's Analyzer folder and letting it regenerate.
2 - The file name and ...

This question was asked over in the Flare Users Slack chat last week. The MadCap rep said it was not currently possible, but he logged a feature request to turn it off.

If more people complain, it's more likely to get fixed, so you might consider submitting your own feature request: https://www ...

Iocus_Rood wrote:That's what it was. Guess I look like the nooblord today. Thanks very much for all your help!

Glad you figured it out!

When you say from the output - are the images present at all in the initially generated output? You mentioned uploading your files to SharePoint before, so I had assumed that the images were present/visible in the initial output (i.e. in the default Flare Output folder), but not when the files are ...

SteveS wrote:If I had that to do I'd try doing a batch edit in Snagit. It will do something on each file you nominate, and save the file. Let the machine do the work, I say...

Good call. I always forget about batch edit!

Iocus_Rood wrote:Open individual and re-save within Madcap? I can give that a try.

I believe we did it in Snagit and Capture, actually. It didn't seem to matter where we did it, something had just gotten corrupted I guess. It was a very weird issue.

Hopefully someone here will have a better answer for you than I do. But I just wanted to say that you're not alone. We experienced the same when using Lingo's machine translation feature (we ran our files through the MT and then had the translator review and correct, rather than translating ...

We had an odd issue at one point where a bunch of our images weren't showing up in Internet Explorer (but they were fine in all other browsers). Opening them each individually and then just re-saving them solved it for us. Not sure if that will help you, but it's something to try.

Use the chapter break method to change the page numbers, exactly as you outlined. Then (while still in the topic Properties for the Introduction), select the Auto-numbers tab and use the Chapter Number options to Reset to 1.

What version of Flare are you using? That functionality was added to the menu proxy in 2017 R2: http://help.madcapsoftware.com/flare2017r2/Content/Proxies/Flare/Creating-Topic-Menu.htm

If you're on an older version and unable to upgrade, you can try Dave Lee's solution: https://forums ...

Yay! Happy to help.

Do you have Exclude content not linked directly or indirectly from target selected in the advanced tab of your target? If so, Flare will exclude your custom Search.htm page and create its own Search1.htm

The workaround is to add an xref to Search.htm within another page. We added it to our "contact ...

It looks like you might be looking in the Unclassified section - try the PrintSupport section instead. If that doesn't work, make sure that all properties are being displayed (not just "set" or "assorted relevant" properties).

The font generating either in the wrong font or with bizarre spacing seems to be an issue with Windows 10 and Flare.

It's a font setting on Windows 10 causing PDF output to have bizarre spacing. It can be fixed by adjusting the font magnification.
Ah yes, the odd spacing issue. That's actually ...

Check the medium at the top. Are you by chance in the Tablet or Mobile medium? If so, switch to the Web medium and make your changes there.

If you are still having issues, create a new skin using the MadCap defaults and migrate your settings over a few at a time (testing the menu as you go). This ...

LAI_Dave wrote:Ah Ha! In the Setup tab of the side menu skin i had "Fixed Menu" set to Web. I changed it to None and the problem went away! Thanks for your advice, it was a solid approach but i didn't need to go there.

Awesome! Glad you figured it out.

Open the Top Nav skin and expand the Menu section (not Menu Item). Look at the 1st Level > Background > Color - it's probably transparent. Changing the color should fix your issue. You may want to check out the 2nd/3rd/4th level backgrounds as well, if your TOC has additional levels.

I'm pretty sure that the MadCap default skin breaks lengthy titles by default (at least, it does in 2017 - I'm not on R2). Have you tried creating a new skin and seeing if that fixes it? If it does, then migrate your previous settings over a few at a time and see what breaks it. If it doesn't, the ...

I have seen this in my projects! But hadn't yet put 2+2 together to realize that it only happens for the first list item. No solution yet, unfortunately.

At least now I know the common denominator, and that it's not just happening at random. That makes it much easier to submit a bug report!

It seems like it should display a message at some point to tell you that you can't export from Lingo to Flare from project that is not the Lingo original project, but that shouldn't be a common workflow, either. If it's uncommon, I tend to run into it! :)
Yeah, I was confused as well the first ...

This is happening to me, also. Recently upgraded to 10.1. Will be contacting support.
I've seen this happen when accidentally exporting from a bundle instead of the source (i.e. you created a new project > exported files to a bundle for translation > translated bundle > attempted to export from ...

Mritunjay_g wrote:Thanks Cdschroeder,

I modify the js page(auto created while publishing) and could achieve the desired result.

Thanks,

Glad you figured it out and got everything working!