| Attribute | Average |
|---|---|
| Features | 3.33 / 5 |
| Reliability | 5 / 5 |
| Ease Of Use | 5 / 5 |
| Documentation | 4.67 / 5 |
| Vote Count | 3 |
Instead of showing a standard "404 Page not found", this module performs a search on the keywords in the URL, e.g. if a user goes to http://example.com/does/not/exist, this module will do a search for "does not exist". It also includes search engine keywords detections as well as regular expression based... [More...]
| Maintainer: | zyxware |
| Links: | |
| Categories: | Content, Path management, Search |
| Version | Date | Files | Release notes |
|---|---|---|---|
| 7.x-1.1 | 2011-Sep-08 | Download | Recommended |
| 6.x-1.11 | 2011-Aug-29 | Download | Recommended |
| 5.x-1.5 | 2009-Jun-29 | Download | Recommended |
| 7.x-1.x-dev | 2011-Sep-09 | Download | Development |
| 6.x-1.x-dev | 2011-Aug-21 | Download | Development |
| 5.x-1.x-dev | 2011-Feb-25 | Download | Development |
Options: Add a review
It's hard to call this a review of this module - what I will say is, I have written about a better option - using "customerror" module.
You can find that and a further comparison of various ways of tackling the error page issue HERE.
Chief among reasons not to use search404 is that it uses a DB query every time a 404 is generated - even for non-human users - which causes a large performance hit.
perfect! installed it; tested it with common "not found"m errors i get- and it works just fine. i'd recommend checking the module settings and ticking the box:
[ X ] Jump directly to the search result when there is only one result.
Really great at getting lost users back on track.
