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!
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.
At the beginning I was thinking that probably the problem was on my side so what I did is I installed another template from Joomla24.com.
This time I was using Jooroos Template and what I found was that the error was gone but for some reason the Extension was breaking my CSS Files.
By this time I was checking the Website Help Support from this Qlue Extension because I was lost. I did not found any helpful information in there for Joomla 1.6 and when I contacted the owners they answer me that they not provide help to this Extension unless you buy the pro Version and pay for that.
After that what I did, I totally installed Joomla 1.6.3 from scratch with the normal Sample Data to test the Extension in a normal Joomla 1.6 Website without using any other extension or personal Data. This time I found that the Extension was working only with one template.
If an extension does not even work with the Sample Data and the standard Joomla Templates plus there is no help for this extension in Joomla 1.6, this is a not to go extension.
This extension only worked with Beez5 - Default-Fruit Shop.
Regarding Beez2–Default and Beez2-Parks Site, it just kept breaking the CSS Files.
This is my Rating
Extension for Joomla 1.5 = 5 Starts
Extension for Joomla 1.6 = 1 Start
Support = There is no support for the FREE Version unless you buy the Pro Version.
Overall Rating 5+1 = 6
Which makes 6/2 = 3
I hope with this review the owners see after this problem because so far they offer me no help while contacting them and it seems like a promising extension.
Then I tried this extension. I got things set up quickly and the only thing I couldn't figure out was how to get it to work for top level domain errors. Then I saw the handy (in bold face)instructions on the module page telling me exactly how to edit my .htaccess to get it to work and everything is now working perfectly.
My 404 error page is BEAUTIFUL and just looks like another nice template article. I am am so happy with this extension. :) :)
There has been an update to my component which will allow you to assign templates or modules just to custom error pages.
Click on the documentation link to see how to achieve this.