Verity K2 Error codes for ColdFusion

I recently had a need to dig into the internals of the Verity K2 search engine for ColdFusion and I needed to interpret some of the more esoteric error codes that Verity can produce. I searched the web for hours looking for a document that I knew existed (I'd read it before) but I just couldn't find on my system. Needless to say, now Verity is a defunct search engine technology, searching the Internet proved to be a fruitless process. In the end, I ended up running a network wide search across all our internal servers for PDF files that contained references to Verity K2.

It seems that a long time ago, I had the foresight to save a copy of the document I needed to what is now a 10 year old server that is about to be retired :-) Thankfully it hasn't been retired yet!

Anyway, as the rest of the Internet doesn't seem to think this document is any use when in fact it is an excellent resource for all the error codes that Verity K2 can produce, here it is!!!

Download Verity K2 Client Programming Guide

Useful SEO techniques when re-building a web site

Over the past few years, we have taken over the development and maintenance of several well established high profile websites and more often than not, we've been changing the technology that the sites are powered by to our preferred solutions. One of the major challenges along the way especially with high traffic sites with thousands of back links is to try to preserve those links whilst deploying a new site that may or may not have the equivalent pages and or structure.

So what tools and techniques are available to us?

Converting a site from PHP to ColdFusion 8 using the New Media CMS

We recently took on the re-development of a reasonably busy website with a large amount of mixed content that was originally written in a mix of straight HTML and dynamic php pages with around 130 pdf documents as well.

The overall health of the site prior to re-development was not great. There were a hundred or so faulty links, pointing to .htm files instead of .php files and vice versa which resulted in a couple of hundred 404 page not found errors. The HTML that the site used wasn't standards compliant which caused rendering issues in some of the less popular browsers and the sites search engine rankings were poor due to a lack of decent search engine optimisation on the site. From an accessibility point of view, the site would only work correctly if JavaScript and full image capabilities were enabled and it looked just awful on mobile devices.