Q: What is the difference between a short description and a long one?

A: First off: short descriptions are short (400 characters – text only), long ones are long (and can include html formatting). There’s also more to it:

Linkchecker bugfixes

There was a number of bugfixes applied to linkchecker since its initial release:

  • Since a lot of servers do not correctly process “HEAD” requests, the linkchecker switched to doing full “GET” requests for higher accuracy in results.
  • The linkchecker now supports HTTPS URLs.
  • Support for redirects has been greatly enhanced — this was causing most false-positives when reporting broken links.

The second report sent on Monday is with the latest version of the Linkchecker, and should be more accurate than the previous Full report sent earlier that morning.

Please continue to report the bugs when you find them. We’re squashing them as quickly as possible.

Avoiding errors when updating images and attachments

There is a known issue with updating images and attachments in an existing Channels item.  If you wish to make a change to an existing image or document, you must delete the existing attachment, and re-upload it.  However, you must first delete the attachment and then save (submit) the item before uploading the attachment again.  Otherwise you will encounter an error.  We are looking into the issue and will get back to you when we figure out the cause.

Beta podcast – episode 1

Janina and I just got back from the Web 2.0 Expo in San Francisco last week, and Anthony was at the CNIE conference in Banff. We all had an amazing time and learned a lot, but weren’t sure how to share this with our colleagues on our return. So we did a podcast:


Link checking is available for beta-testing

We are finally implementing a long-requested feature: link-checking the pages to report when good links go bad. This feature is not yet available to everyone — you have to be part of the special “beta-tester” group in order to be able to turn it on for your site. Moreover, this feature will only be available to site managers, who can then designate who receives the reports using the site-management tool:

Turning on the linkchecker

The reports run on weekdays and come in two varieties — “Full” reports and “Brief” reports. “Brief” reports run Tuesday through Friday and only check links within our site, for example a link from “/collaboration/” to “/hr/broken/”. “Full” reports are prepared for you on Monday morning and include links to external hosts, not just internal links.

The reports look like this:

Linkchecker sample report

The reports show the page with the broken link, then the status of the check (e.g. “Not Found”), then the link location (the “href” part of the <a> element), and then the text of the link to help you locate it on the page.

Participating in the beta program

If you are a site manager and would like to test-drive this feature, please fill out a feedback report requesting access to the beta-tester program: feedback form.

Blog authors are solely responsible for the content of the blogs listed in the directory. Neither the content of these blogs, nor the links to other web sites, are screened, approved, reviewed or endorsed by McGill University. The text and other material on these blogs are the opinion of the specific author and are not statements of advice, opinion, or information of McGill.