MadCap Software Forums

Many thanks Dave - now working.
And thanks for all your input - it has been invaluable over the years

Can someone answer what is probably an obvious question? Following an old post I came across from Dave Lee about adding hints on improving search at the top of the results page:

https://forums.madcapsoftware.com/viewtopic.php?f=9&t=26808&p=118336

I'm falling down on how to link the topic I've ...

Hi all - I want to add some words to the built-in English skin. I may be missing the point but when I create a local copy for editing as per Madcap instructions all I get is an empty text file awaiting entries.

I surely don't have to add all the default words back in before adding any of my own ...

Hi - I have been having the same issue but have solved it by adding a class to the DropDownHead with a left-margin of 0em instead of the default 2.5em.

Hopes this works if you haven't solved the issue - I basically ended up having to add classes on virtually everything drop-downy as I also wanted ...

Bingo - that has done it :D . I now have no header and no breadcrumbs printing and will get round the h1 printing on every page (i.e. over the text on every page but the first) by advising users to set their browser to display the title in the browser's page setup so the topic name is shown on the ...

That's what I don't understand. I have hidden the H1 class for print by using display: none and also used that on the Breadcrumbs Proxy but the breadcrumbs are still printing. As Flare defaults to not outputting breadcrumbs in print I'm even more puzzled...I am using HTML output and have added the ...

Thanks Lisa - that's helpful. Thought page layouts were nothing to do with webpage printing but got desperate.
Had got rid of the H1 for printing by using the print medium for now. Wrestling with cutting out the breadcrumbs now but not having much luck.

Hi Daniel
Thanks for this but I'm still puzzling. I have always used the print medium to set up my normal print outputs (usually pdf) and they are fine, but I still don't get what is governing the print output when printing direct from a WebHelp page.

Is it using a Page Layout for that? Printing ...

How can I control the print output from Flare itself - i.e. that which uses the Print button?

Any print output using my Page Layouts are fine but printing direct from Flare when a topic covers more than one page results in the topic text printing on top of the heading and breadcrumbs on any page ...

No, well...thanks both anyway.

Dave - thanks. That is exactly what we are trying to do.

However, the addition includes a script manager to call a webserver and this has to be in the body of the Output file, so it looks like I will just have to replace the Output file each time I publish (or we automate the action to cut out user ...

Ramon
The file I am referring to is the output file (the one which creates the tri-pane screen) which I have named Online Help and selected the option to "use custom file extension ..." to output aspx files. That's what has some scripts added and which is getting overwritten by the Madcap one. Sorry ...

Tried adding it in to the Content folder - loaded at build and publish but still gets overwritten by the default file - and that is the one which is picked up by IIS. Renaming also does not help. Will carry on pasting in to the Output folder to overwrite the Madcap generated one for now and look to ...

Thanks for that - yes, I am talking about Javascript. We have some which are added to the master page and which work fine. However, this is specifically an issue with our Online Help output file (an aspx file) which as I understand it creates the tri-pane structure and holds the topics, TOC etc ...

Apologies if the answer to this is somewhere in the Madcap help but haven't come across it yet. What process does Madcap go through when publishing to the Output folder?

The output file (which I have called Online Help) appears to be rebuilt each time I publish. The problem is that we have Scripts ...

Good to know - thanks

Ann

With by the looks of it:
By View source:
<!-- frameBorder="0" is for IE 8 and below --><iframe id="topic" name="topic" frameBorder="0"></iframe>

Just looked at the Flare 8 help in IE6.
Wish I hadn't because at least 15% - 20% of our users are still on that version - the Search box extends right across the page, and the content does not even load. All I got was a wide sidebar containing the TOC and a big blank for the rest of the screen

When one of our customers enters something in the search field, then clicks on the Search button the following Javascript message appears:

Message: Object doesn't support this property or method
Line: 8681
Char: 1
Code: 0
URI: http://help.xssl.co.uk/content/SkinSupport/MadCapAll.js

before Help ...

Sorry - found a reply from Dave which answers this question, I think - i.e. put the Jscript in the master page.
Duh! should have thought of the obvious

But if anybody has any other suggestions for using Jscript with Flare would be interested to hear them for future use...

We have put Jscript functions in the <head> area, but, when published, these functions are removed.
Anybody any suggestions where we are going wrong?
Is this the right place or should it be in a separate file?

Just to report that I have also spotted the problem today when checking a build. Anywhere the copyright symbol is used I now have Â. Using Windows 7, IE8 and Firefox 5 - same in both browsers.
Also reported to support.

Some of my phrase searches in the WebHelp output are not being found. Having read this thread http://forums.madcapsoftware.com/viewtopic.php?f=13&t=10840&p=61622&hilit=search+phrase#p61622 - which led to the install of Dave Lee's plug-in (thamk you very much, Dave) so was not wasted :) - I am having ...

Right - at least I now know that the markers should appear at the beginning. I will investigate the non-scrolling region and see if I can work out what is happening. Thanks for your input...

Hi Dave - the markers appear in the editor all over the place. I'm sure they will work - I haven't publish an update yet using the filters but am checking because I found that, if there was an index keyword against my H1 non-scrolling header then that header rendered incorrectly when published. I ...