MadCap Software Forums

If you want the headings from inside a topic to be included in a menu proxy.
1) Open the TOC and edit edit the TOC item(s).
2) Go to Auto-generate tab, and select Compute sub-entries from linked file.
3) Choose to Insert or Replace with Computed Entries , and select the heading level Depth .

Flare ...

It's possible if you use a menu proxy - but not using a mini-toc proxy.

You'll need two TOC files.
* In the first TOC file, set the TOC item labels to the partn number of the hardware item. Set this TOC file to be the primary TOC in the target properties.
* In the second TOC file, set the TOC item ...

I can't answer why, but I can confirm that Flare includes conditions as properties in HTML5 outputs. So what you see is normal.
But I'm not aware of any way to stop it doing this.

I thought it would look best to do this by having a hyperlink back to the knowledge base as an option in the top navigation menu.

Open your TOC file, add a New Item , open the item Properties , then enter the URL to your Knowledgebase in the Link .
If you want it to open in a new tab, go to the ...

That might be happening because CSS file doesn't exist or the path to the file is wrong.

I think the console is saying it's getting a file with a MIME type of text/html instead of text/css . So if it's getting a HTML file instead of your CSS file, that suggests something like a 404 page is being ...

When you paste in the code from Google Analytics, look for async and change it to async=""

You need to do this because Google's code is HTML, but Flare's editor uses XHTML which is a stricter form of HTML. One of the differences is that you can't minimise attributes by missing out the ="".

At a rough guess, the script may not work if you have multiple conditions applied to the same HTML element.

So if you have HTML like this:
<p MadCap:conditions="Conditions.Web,Version.A">

Then try structuring the HTML so that the version condition is not on the same tag as your other conditions ...

I would check what CSS is used for div.home-footer.

Also, the MadCap:pageFooter style is intended to be used for footers in Word outputs, not for HTML5 outputs.

I haven't seen this problem with the same xmlns reference, but I have seen it for xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd".

Topics should include this xlmns reference in the html tag:
<html xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd">

But for some ...

Also, start using some AI tools. That's probably the most useful thing you can learn at the moment.

This is what I've found useful:
* Experiment with the parts of Flare you've never used.
* Understand the basics of HTML and CSS.
* Take a look at how Flare's HTML5 output is put together.
* Learn how to inspect the HTML/CSS of your output using your browser developer tools (F12), so you can fix ...

I'd suggest contacting MadCap support.

I had this issue around 10 years ago in Flare v11. When I published targets from projects bound to source control (TFS), the published files (usually images) were being set as read only. So if any of these files had to be replaced the next time I published ...

You haven't said what you've tried, so perhaps give an example of how you are trying to set up the font.

In your CSS you will need to add one or more @font-face statements that point to the local font files.

I use something similar to the 'slightly deeper browser (s)upport' approach on CSS tricks ...

The side navigation menu label will display whatever you have set in the TOC as the Label (in the TOC item's properties).

So you could do this two ways:

(1) If the TOC item's Label is set to [%=System.LinkedTitle%] then it'll display the title of the topic. As you haven't set a topic title, this ...

Yes, you can insert a search bar proxy on your landing page.

See Flare's help: Creating a Search Bar

If you want to hide the search bar in the header on the landing page, that topic also mentions "How to Hide the Search Bar From a Single Topic".

You need to provide more detail on how you use these condition tags and variables in your content.

Remember you can set variable definitions and conditional text settings at the target level, so you may only need one set of variables and conditions.
For example:
- You could have the variable ...

When we tried on a colleagues machine the general source control for the project all works fine, but the publishing destinations do not show the "remote repository" in them at all and we had to create them, when we did publishing would not work and basically it was telling us to do a pull from that ...

I don't use git, but there's a knowledgebase article 'Connecting Git.exe to Flare', and it seems to have extra steps that aren't included in that help page.
See: https://kb.madcapsoftware.com/knowledge ... _Flare.htm

Zauberlehrling wrote: Wed Jan 08, 2025 9:04 am I took the Snippet Condition off, see the result (Spoiler: it's a failure).

Ok, but did you set conditions for each target on the target's Conditional Text tab?
You would need to set conditions as follows:

PDF target:
- ScreenOnly : Exclude

HTML target:
- PrintOnly : Exclude

(1) This isn't how you use snippet conditions.
As you have conditioned text that you want to exclude/include in separate target outputs, then you only need to set the conditions in the target Conditional Text tab. This will apply the conditions to everything in your target output (including content ...

It was flagged as an issue in our accessibility audit because of how it impacts the page navigation sequence.

If you navigate the page using the keyboard, you expect to follow a consistent navigation sequence.
(https://www.w3.org/WAI/WCAG21/Understanding/focus-order.html)

The problem with setting ...

In the last 7 years I've also learned that doing this is a really bad idea for accessibility, so I'd recommend not to do this.

The "Output" folder is only used when you build a target - not when you publish a target.

Flare creates an "Output" folder when you build a target, and you cannot stop it creating this folder.
By default, the "Output" folder is put in the same location as your Flare project, but you can change ...

Set up your styles in the @print medium, as that will be used when you print from a web browser.

The Tripane skin uses frames, meaning the skin and your topic are like separate pages. So stylesheets linked from your topic are not applied to the skin (header, navigation, etc.).

But there's a way to add your custom CSS to the Tripane skin.

Open your Tripane skin, go to the Toolbar tab, then ...

MadCap Software Forums

Search found 6250 matches

Re: TOC Entry Labels for Side Nav vs Mini TOC

Re: TOC Entry Labels for Side Nav vs Mini TOC

Re: Conditions appearing in built help

Re: Can I put a hyperlink to a website in the header for a Top navigation skin?

Re: Enabling Fonts in Navigation Pane (Style.css)

Re: Flare & Google Analytics - Flare not accepting GA tag code

Re: Custom version dropdown script breaks one of our conditions

Re: Body running under the footer

Re: xmlns= xmlns= xmlns= xmlns=....

Re: Seeking to Up my Game

Re: Seeking to Up my Game

Re: Publish failed - Access to path [file name] is denied

Re: Locally Host Google Material Icons

Re: Hidden inline text in header not always hidden

Re: Different location for search bar on landing page and internal pages

Re: Use of multiple sets of Variables and Conditional text

Re: Publishing Destinations with Source Control

Re: Cannot integrate Git.exe with Flare

Re: Snippet Condition in PDF and HTML

Re: Snippet Condition in PDF and HTML

Re: Set focus on search bar on load

Re: Set focus on search bar on load

Re: Avoiding output folder

Re: Styling for printed topics from web outputs

Re: Enabling Fonts in Navigation Pane (Style.css)