Automation MadCap Flare Technical communication

Automated QA: Checking for broken links in your Flare output – now also for HTTP links

Posted on Author msander Comments(5)

The CheckLinks tool now also finds broken http and https links in addition to finding broken local relative links.

The syntax for running the tool is, for example:

C:\> Checklinks2 "C:\OutputFolder" "C:\LogFolder"

For info about the existing tool, see http://techwritingengineer.com/automated-qa-checking-for-broken-links-in-your-flare-output/

msander

Related Articles
Automation MadCap Flare Technical communication

Free Tool to Create MadCap Build Logs with Time Stamps

Posted on Author msander

To troubleshoot a complex build process I needed time stamps on each line of the Flare build log. It’s not possible today, but MadCap has created a feature request for it… …and in the meanwhile, I’ve created a tool you can use to generate a log file with time stamps. You can use this tool for any […]
Javascript MadCap Flare

How to add wiki-words to your HTML5 output in MadCap Flare

Posted on Author msander

Would you like to link certain words or phrases to your internal wiki, or perhaps to Wikipedia? Would you like to build your output only once, but still be able differentiate between “internal” and “external” audiences? Keep reading. The idea 🙂 The idea is to add a span-class to your style sheet, and then highlight […]
Automation Excel MadCap Flare Technical communication

Generate 10,000 Flare topic files in 7 minutes

Posted on Author msander

Tired of setting up Flare topic files manually? Got enough work to last until Christmas next year? Keep reading and learn how you can use Excel to create 10,000 topic files in less than 7 minutes. Click here to download an example spreadsheet. Set up or import your data to Excel (e.g. a list of topics). Set […]

5 Replies to “Automated QA: Checking for broken links in your Flare output – now also for HTTP links”

  1. This sounds good. But when I run it nothing happens: no error message but no text file either.

    Any ideas what the problem might be?

    Reply

    1. Great, thanks. That works fine. It doesn’t like it if you leave trailing backslashes in the paths though. I get:

      Unhandled Exception: System.ArgumentException: Illegal characters in path.
      at System.IO.Path.CheckInvalidPathChars(String path, Boolean checkAdditional)
      at System.IO.Path.GetFileName(String path)
      at System.IO.StreamWriter.CreateFile(String path, Boolean append, Boolean checkHost)
      at System.IO.StreamWriter..ctor(String path, Boolean append, Encoding encoding, Int32 bufferSize, Boolean checkHost)
      at System.IO.File.InternalWriteAllText(String path, String contents, Encoding encoding, Boolean checkHost)
      at System.IO.File.WriteAllText(String path, String contents)
      at HREF_CHECKER.Module1.WriteLogFile(String logText, String logPath)
      at HREF_CHECKER.Module1.Main()

      Feature request: print some output on the command line – e.g.
      “x broken links found. See log file ”

      Thanks again. That’s a really useful little tool.

      Reply

      1. In my previous comment I used angle-bracketed text which disappeared on submit.
        After “See log file” add the path/name of the log file.

        Reply

Leave a Reply

Your email address will not be published. Required fields are marked *