MadCap Software Forums

Update to my code snippets above: The actual jQuery 3.0+ recommended syntax for .ready() doesn't even include the text ".ready()" - so to call an anonymous function, it is now: $(function() { <your code> }); . Ref: https://api.jquery.com/ready/#ready-handler:~:text=As%20of%20jQuery%203.0%...

I am grateful to kathryngz & NorthEast for their code above, however, I did have problems getting it to work when I enclosed it in the jQuery recommended $(document).ready() call to wait for the page to fully load: $(document).ready( function() { <your code> //***DIDN'T WORK*** }); Almost in fru...

My IT Dept solved this problem for me yesterday - it's just as @Psider said, clearing the cache will solve it.

In my case the problem either showed 0 results or the Search runs forever (>1 hour). It only happened in Edge - in both Chrome & Firefox it worked perfectly.

Unfortunately with the latest release of Flare 2023, this bug still hasn't been fixed. My code shown in the previous post fixes the Vimeo URLs in the Flare 2023 output.

I've previously published this information in the Web-based Outputs forum, but I thought I'd repost here as my solution can be adapted to be more versatile and do many more fixes/work-arounds and general admin with the Flare output. Firstly, a recap of the purpose of my original post: if you link to...

I think you can achieve what you want using an almost unbelievable feature of CSS (and one of my favourites) - reading & outputting the value of an HTML attribute. I'm afraid I don't have direct experience with the MCPopupContainer since this component is not supported in Flare's HTML5 Side Navi...

Unfortunately with the latest release of Flare 2022, this bug still hasn't been fixed. So you might be interested in using my solution to automatically fix the rendered Flare output. This takes the form of some post-build processing automatically started from your Target that spawns a Powershell scr...