MadCap Software Forums

I wish it was. We were constrained to the tripane, so we were stuck trying to find a workaround with that skin.

Lisa's right, though. The most sensible thing, if you're not stuck using the tripane, would probably be to switch over to the topnav.

We ran into this months back when we implemented our HTML5 output via an iframe in our product.

We experimented in part with the Mini-TOC proxy. To memory, the proxy does correctly synchronize, but in the end we just opted to hide the TOC automatically when the skin loads in a frame.

I setup our ...

Unfortunately, I think the age-old "restart Flare" or "copy and paste into the boxes" workarounds still stand strong. It doesn't look like there's been any additional movement on this issue from MadCap.

In effect, selecting a bullet type sets the list-style-type property for the UL element in your style sheet.

By default:
UL{
}

Setting the bullet type:
UL{
list-style: square;
}


This isn't really accurate. When you select a bullet list from the options, as Jim is describing...

Screen ...

So, the question is, can I password protect certain topics or am I looking at "yes, but... you have to use a third-party javascript or application"?


To memory, you were looking for a way to do this via a website?

Best practice, security is really the job of the web server, not of Flare. You ...

Users would have no way of knowing how to restore the tri-pane view by replacing the word "Content" with "#", and hence will have no way to discover the rest of the articles/topics in your KB/help from this page.

In your Target settings, you can specify for Flare to automatically add a link to ...

damadeo wrote:Where are the TOC entries in the Lingo project?

There should be one or more *.fltoc files (one for each TOC you have in the project) that contains the segments you need to get translated. If you have a filter applied to the File List window in Lingo, you may not be seeing the *.fltoc files.

2. Why when I imported my test Lingo project back into a <new> Flare project, all the previous project files were missing (toc, target, etc).


Hi, Diane,

Just to clarify, did you actually try importing a Lingo project into a Flare project, or did you export your Lingo project to a Flare project ...

Hi, all,

Somewhere along in this thread, someone was looking for code that expanded all dropdowns in a topic. I was recently doing some code refactoring and wanted to pass this on. If you want to make all dropdowns in a topic start expanded, just use the following code:


function clickDrop ...

Remove the @namespace declaration at the top of the master project CSS (because Flare now inserts this same declaration at run time if you leave a default target option enabled). I'm presuming we don't want a "double instance" of this declaration?
Remove the "empty" CSS statement that we added ...

Various teams at my company are finding different issues with the "localhost" solution or alternative solutions.

The 'localhost' fix is not the correct one -- this will cause issues in the content served to the web.

The correct fix is the one Rob lists here:
https://forums.madcapsoftware.com ...

Choccie is right -- the most straightforward and secure method would, I think, be to deliver separate outputs. Security management, the idea of serving different content based on a user, is really the job of the server, I think.

That said, when you add condition tags to content, as long as that ...

Oh and to clarify, the fix wipes out styling when in place during a build. it needed to be put in the file post-build.

I'm not seeing any issues in the build process on our end -- is it maybe a syntax issue? The CSS parser in Flare is pretty fragile.


Just as a thought, for those running into an ...

To note, after updating to Chrome 47.0.2526.80 m (64-bit), the fix Rob stated (viewtopic.php?f=13&t=26711&start=25#p117901) does now work correctly for us.

For what it's worth, I did my testing in Chrome version 47.0.2526.80 m, which seems to be _very_ new (as of today or yesterday). Maybe Google fixed the issue in one of the early v47 builds that was causing @robhollinger's fix to not work for some of us?

Just retested in the version of Chrome you ...

Cool, no worries. To note, once MadCap releases the patch for Flare 11, it may be good to switch the CSS back to the MadCap|<...> version. I believe the Stylesheet Editor in Flare won't recognize the [class*=... version. Generally, we handle all our CSS modifications outside the application, but I ...

Hi, Davbo,

A few people have provided some temporary solutions in the following threads:

viewtopic.php?f=13&t=26711
viewtopic.php?f=9&t=26723

This is a bug related to a Chrome 47 feature.

It's those Pseudo classes that are not handled by the browser correctly.

Other examples would be:
MadCap|popup:hover
MadCap|xref:hover

If you were to set the xref hover class, that would take over as soon as you corrected the dropdownhotspot styles.

Gotcha! Thanks very much for the patience ...

The issue stems from the new feature in Chrome 47 to support CSS Namespace rules. Namespace rules were previously ignored, and now appear to match anything.


Hi, Rob, sorry to trouble you. -- This doesn't appear to be the case in our output. The MadCap namespace styles are being applied ...

Has anyone here found a solution that can fix it on the web?

Is there some code a developer can enter where these files are already deployed that will fix this temporarily?

The fix I detail above does work on the web, and I've already deployed it to all the project output on our server. It's ...

If it's helpful, I created a workaround for this issue for our organization, since we've also encountered it. In our case, the issue was that the MadCap|dropDownHotSpot:hover style was getting applied to all elements in the topic. I worked around this by converting MadCap|dropDownHotSpot:hover to ...

We also encountered this issue with Chrome 47. In our case, it appears to be an issue with the way Chrome 47 is parsing the MadCap styles:

chromeWindow.png

In our case, the issue was that the MadCap|dropDownHotSpot:hover style was getting applied to all elements in the topic. I worked around ...

We don't run into any issues with changes being lost, but that may be related to workflow. We don't include the translated files, once they're created, in the original project. Instead, we maintain a directory of translated projects. Our workflow looks a little different. This workflow assumes you ...

I just mentioned it because if someone's new to source control, then they want to be using Flare first - and use things like Team Explorer or Visual Studio for troubleshooting or branching/merging.

Yeah, good call, and thanks! I mostly wanted to suggest it because we were under the impression ...

...why do you use Team Explorer, when Flare already has built-in integration for TFS?

Hey, Dave,

Yeah, good question. Initially we were using Flare mostly, but we started running into a few different scenarios/issues that inclined us to all utilize Team Explorer in addition to the in-application ...