MadCap Software Forums

@ MattyQ: My instance of Flare 11.1.0 doesn't think there's an update available yet, so I haven't been able to test for myself. @MadCap staff: I just checked with our chief architect about the xmlns: that points to your hosted schema. He said that he didn't think this would flag anything in a Salesf...

For those of us who implemented the manual workarounds when this issue first hit, what exactly do we need to "back out" when upgrading to the newest version of Flare? would presume that the following steps should be done, but it's worth double-checking here... Remove the @namespace declara...

If not, then you're going to create a problem for those of us who use rendered Flare projects as the Help content for Salesforce apps. Security review guidelines for Salesforce managed packages tend to flag anything you add to a Salesforce org that includes external callouts to the public Web like ...

Here is a slightly different issue for MadCap to consider in their fix for this problem: I hope that the permanent fix will NOT use a callout to an .xsd file on the madcapsoftware.com site like this permanent fix does. You are planning for the fix to use internal project files only, correct? If not,...

Hmmm, however, it turns out that applying @robhollinger's suggested fix to our main project stylesheet is screwing up the internal stylesheet used by the XML editor. Fonts are all wrong, as if each topic does not "see" the stylesheet reference to the project stylesheet in the HEAD element ...

For what it's worth, we also have hover behavior on our XREFs and also our drop-down headers. I just applied @robhollinger's suggested fix (pasting the following line as the very first line of our main project stylesheet): @namespace MadCap url(http://www.madcapsoftware.com/Schemas/MadCap.xsd); This...

Hey, all, This is not a perfect solution, but in the course of our documentation, we wanted to have a "Before You Begin" dropdown that opened automatically when the page was loaded. I created kind of a clunky script that was able to open a single instance of a specifically-named dropdown....

I've filed a detailed bug report about this, but for folks who run into the same thing, here are the symptoms and a (tedious) workaround: Affected SCMs : Perforce, and possibly others. Note that my company does NOT bind Flare directly to Perforce, because performance of bound projects is terribad. F...

I agree, thank you so much for posting your experience and recommendations. I just tried to import a project from Perforce and I get an error which prevents me from even finding it. I was actually hoping to find something on the error, but found your post instead. My project is embedded with the co...

There is currently only a "preview" link for the new Flare 11 project template. Without a download link, it is difficult to figure out how the new "Menu" and "Topic Toolbar" skins/proxies were implemented in your new Flare 11 Help, and the current Help doc itself does n...

Hi Thomas, I've not looked at Perforce in Flare 10 yet (too many other more important things to do first), but are you saying that Perforce integration in Flare doesn't support repositories that use streams (we use streams)? Or are you saying that if your Perforce implementation uses streams, then ...

(raises hand)

After quite a lot of experimentation, I threw in the towel. IMO, it's still better to work with Perforce in a non-integration manner.

http://forums.madcapsoftware.com/viewto ... 96#p103945 if you're interested in details.

I've spent roughly 20 hours over the past two weeks trying to make Flare 10's native integration with Perforce work acceptably well for production authoring and SCM among multiple writers. I have created (and obliterated) two stream depots in the testing process, and I've manually created and delete...

Because of a serious bug with table rendering in the HTML5 skins, I'd like to know how to force all topics to initially render as fully expanded in HTML5 outputs. The bug has been reported to MadCap, but until fixed, the default behavior of HTML5 skins is unacceptable. (To see the reported bug and h...

For those using a Surface Pro (2 or 3), I found the following workaround. It's not ideal, but it lets you be productive in Flare on this particular device. This approach should also work for other Win 8.x "ultrabook" devices with HD+ screens like the Surface Pro 2/3 have. Short version: Ch...

Win 7 Enterprise 64-bit. With IE9: exact bug described in OP.

I can confirm that upgrading from IE9 to IE11 fixes this particular issue.

@RamonS : The specs for a Surface Pro 3 are hardly "entry level desktop". @Madcap: I have the same issues as the OP, and what's worse is that the Skin Editor won't correctly display the live preview correctly at all. Yes, you _can_ set the system's default 2160 x 1440 resolution to "M...