MadCap Software Forums

I have a parent project that I use to merge several child projects into a single help system. I use the TOC to link to the .mcwebhelp file of each child project. When I generate the final help build, Flare creates a folder called Subsystems where all of the child projects reside. My company would li...

It turns out that some customizations I made using a skins.css file were the reason the Search Bar disappeared. I inspected the search bar element in the browser and was able to see that the search bar now has a search container and I needed to apply my overrides to that instead of the search bar it...

I have an HTML5 Tripane project with a search field/bar in the middle of the header. When I open my Flare 2018 project in Flare 2020 and build, the search bar does not display even though it is configured in the Skin and displays in the Skin preview.

Thanks for any help!

I have a project that I output to CleanXHTML. The output is then picked up by a build script, converted to Markdown, and merged into another system. I am testing Flare 2020 and the CleanXHTML now has this div just inside the body tag <div role="main" id="mc-main-content"> This is...

I have to check the "Use lowercase file names" option or many external links to help will break.

I tried putting the code in a snippet and that didn't work. My build hangs at Resolving links in output files....

Does anyone else have any other tips?

Thanks!

After much research, I found an answer that worked for me in the MadCap forums. There is an ampersand & character in the Google Tags script that the XML parser in Flare does not like. You have to escape it out. Refer to this entry on the forum. https://forums.madcapsoftware.com/viewtopic.php?f=1...

Adding this to a skins.css seemed to fix radius for me. html.left-layout #contentBody { -webkit-border-radius: 0px 0 0 0; -moz-border-radius: 0px 0 0 0; border-radius: 0px 0 0 0; } To resolve the issue I had to override the default Flare skin settings by importing my own css. Here is how I did it: 1...

I was having the same problem. I finally figured out that the top nav project I was building had an H1 style in the div above the body proxy on the master page. When the project built and then updated the cross references it was picking up the title of the H1 style from the first div in the master p...

I don't know if this is related, but I now have no scroll bar in my search results. I implemented the style selector you suggested for the double scroll bar, but I am not sure if this is the culprit.

ul.menu._Skins_mySkinName.mc-component
{
overflow: unset;
}

Any thoughts?

Thanks, Ana

Dave,

A thousand times Thank You!!!

The KB was exactly the missing piece of the puzzle. You have saved me a huge amount of time and agony. If you are ever in NH, I owe you a beverage of your choice.

Ana

HI David, Did you ever figure out how to do this in Flare 2017 r3? I am not much of an expert at CSS or js and I am struggling to fix my side menu. Your code worked beautifully in the prior version of Flare and now I just get the three parent nodes, they don't expand, and I can't see the children at...

Hi Leslie,

I did try the update scenario and Salesforce does figure out that it is the same article and updates it properly. So modifying articles you have already published seems to work well.

Regards, Ana

Hi,

Does anyone know if the Menu Proxy issue was addressed in the 5/31/2017 update to 2017 r2? I read through the release notes and it doesn't seem like the issue has been fixed.

Any information you can provide would be helpful.

Thanks,
Ana

Hi,

Did the 5/31/2017 update to 2017 R2 address this issue? I am having the same issue, so I had to go back to 2017.

Thanks for any additional info you can provide.

Did you get a separate license for it? I read in the docs that it needs its own license. It would be good to experiment with it before deciding that you want to use it. There is a thirty day trial for the Salesforce app. It worked really well. I did have a little bit of a hard time setting it up be...

I figured it out. I had a required field set on my article type in Salesforce that the topic in Flare didn't have. I made the field optional and then everything started working.

I am trying out the new Salesforce Connect publishing destination. My Flare log file tells me I am successful, but I don't see my article in my Salesforce organization.

How can I troubleshoot this?

Thanks!
Ana Bahr

Rita,

Did you ever figure this out? We are looking at the same option.

Thanks, Ana