MadCap Software Forums

Yeah all my URLs have changed from underscores to %20 for spaces in filenames. I'm getting user reports for broken links every day.

If anyone is still struggling with this - I found none of the above solutions to work, but this suggestion in Stack Overflow did work: "The @font-face rule can have “font-family” defined as any name. However, I recommend using the default name seen in Flare. You can find out what name Flare is ...

Confirmed bug. Fix is in development. Go back to the previous version if you encounter it.

Anyone getting broken links (pointing to htm file on local machine) for cross refs in their PDF output in v2021?

Have since discovered that single-language PDFs are put in the output tmp directory.

Solved - my Flare project wasn't pointing at the original Lingo project, it was pointing at a Lingo project that I received from the translators - which contained all the same files, and presumably was basically identical, but Flare didn't like it anyway.

Has anyone seen this message before?

I'm trying to build a Flare project that links out to a Lingo project for translated content (the languages in the Target are pointed at the Lingo project) but the target won't build.

I don't have translated content in the Flare project - the translated content resides in the Lingo project. So I can go to an output (PDF) target, add a new language under the default language (English) and link to the Lingo project so it pulls in the translated content when I build the PDF. But the...

In the Language tab of the target editor for Flare, it appears to be impossible to remove the 'default' language, so when I build a target with translated content it builds the English one with the translated version appended to the bottom. I just want to output a PDF with the translated content onl...

Anyone have any updates on this?

Madcap don't appear to be very bothered about making output work on Linux servers...

Thanks Paul, I'll give that a shot...

I've just run into this problem with the side navigation skin, it was driving me nuts for days - I couldn't work out why my published output was broken but the local output was fine. Eventually I checked the Chrome console (which I should have done at the start) and found that the server was failing...

Solved: with lower case filenames on, the output is publishing css in the 'Skins' folder but the topics are looking for css in the 'skins' folder.

So basically, using lower case filenames with the side navigation skin breaks your output on Linux-based web servers.

Any MadCap staff around that would know the answer to this by any chance...?

Using the old HTML5 skin, in the published output on the server, navigating to [project]/webhelp/ opens the startup topic with navigation. Navigating to [project]/webhelp/home.htm does the same. [project]/webhelp/content/home.htm opens the topic without navigation. No biggie because I don't use that...

Yes, in the space where the logo & search box are. It's bizarre that there isn't an out-of-the-box function. I had a solution for the old HTML5 skin that lived in the <toolbar> section of the skin which copied header text from an html file in your resources folder. But the sidenav skin doesn't h...

Would I be right in thinking that there's no way to add a document title to the header for a side navigation skin...?

I've requested a feature to switch off the tocpath string multiple times with no success. If more people make the request, we might get it into the next build.

https://www.madcapsoftware.com/feedback ... quest.aspx

Why they proactively removed the only workaround is a mystery.

I've had to uninstall too - Flare was freezing up & causing issues for Windows (10). My start menu would stop working & when I tried to restart the PC it would just sit there with a black screen indefinitely.

Kathy_123 wrote:It's embarrassing to send someone the URL to a specific help page when the URL looks like utter trash.

You can just chop off the tocPath string after the filename - it's a PITA though when you have to deal with a lot of URLs.

I asked technical support about it, this was the reply: "It is not a recommended workflow to alter the Flare source files and is not covered under the umbrella of support. I will not be able to provide this workaround or updated versions of this workaround if/when it changes in future version. ...

In 2017 r2 they also apparently un-checked 'upload log file' for HTML5 destinations, which has been particularly annoying.

The code has changed. I suspect it's possibly this that now needs to be commented out: if(MadCap.Utilities.HasRuntimeFileType("TriPane")){L+=encodeURIComponent("?"+Q+"Path="+V)} If anyone with JS chops can verify that would be great. I'll have to leave it on for now &am...

AAAAAAGH

why is this still happening

*facepalm*

Same code change tested & working for Flare 2017 also.

File is C:\Program Files\MadCap Software\MadCap Flare 13\Flare.app\Resources\WebHelp2\Desktop\Scripts\MadCapAll.js

Why we still have to do this for every release is beyond me