This means you can improve on the ugly standard error page and generate an error page that's user friendly, navigational and even include a search box to help direct the user to the page they are looking for.
Return the correct HTTP error (many other extensions do not do this and it's important for SEO!)
Detect errors (eg 404 Page not found) and display a custom page in your own template
Custom error page can include modules!
Tried the non-commercial version and it work "out the box." Realizing the value of this extension, we have upgraded to their commercial version for 19 bux. FAST fix for all the broken links (including 500's) - less than 10 minutes - the site is fully functional. That was done without reading their documentation. The only thing we are still struggling is assigning modules to custom pages - perhaps it is time to read the manual... :)
That means these errors will be displayed within the content area of your template, so the user never leaves the template and will retain access to menu items or other important navigation functions (like searching).
It also notifies you after X attempts to visit a broken URL, so you can locate what needs to be rewritten and address those issues.
I have the commercial version, it's totally worth it. I'm very happy with the functionality and support - I got a reply within minutes of sending a question.
Initially the extension didn't work but I contacted Aaron and he had a fix out to me in less than an hour which I understand will now form part of an upgrade.
Well worth $19
All I get is the text I specified in the Qlue custom page but the template is not assigned. The extension owner in previous reviews claims that the documentation tells you how to do it but I haven't seen that notes anywhere. My website has SEF enabled and the template style is assigned to All.
It seems that I have to get the commercial version in order to get the non-commercial version to work!
You create an error page from within the component, then you create a menu item and link the menu to the error page from within the component (rather than say an article as you normally would). Don't publish the menu on any of your pages and set the menu in the rhs prefs for bots not to scan etc (you son't want Google crawling it). This seems to then publish whatever you have put in error page you created within the component into the main body field on your page.
I'm assuming this is how it works with the non commercial version as well, I upgraded to the commercial version in the hope that I would get some customer support (Qlue do not offer any support for the free version).
With a comprehensive how-to doc, this would be an outstanding product.
Found this little gem, a little money and a little time and working Custom Error pages. Should have used this right from the start.
The tracking of bad URL's is a great feature as well.
Bonus result of this app is you can see the broken links and spot malicious attack attempts on your site.
The only problem I can see is that I had to buy it on faith, it wouldn't display properly on my template, and I couldn't figure out why, reporting a bug to them didn't help, and they insist on not giving help out if you're not registered. So on a leap of faith I registered thinking that they must be able to solve this.
After registration I opened a ticket, which they responded to immediatey, and they solved my problem within two updates to it.
Just too bad that this leap of faith had to be taken, if they had helped me without registration, this would have been an 'excellent' rating.