iFinity

If you're talking abuot a common misspelling, yes, that's easy to do.

If you want to redirect a common misspelling to one of your pages, just go to your ''Admin"->"Page Urls" page, select the page you want the redirection to go to (in your case, the home page) and add in the misspelt page name.

If you're talking about a generic catch all for any unrecognised Url, you should probably do that through your site 404 handling.  You can define custom 404 handling in your asp.net web.config file.

I've got plans for a custom 404 page setting in a future release, but it's a fair way away at the moment.

It's my belief, that, all things being equal, it's better to return a 404 status when an invalid url is requested than a 301 or 302.  However, the best thing is to return a 404 status and give the user more options to find other pages (assuming they got the domain correct)

In the menu options for this forum module, there is a 'My Settings' link.  In there, you can subscribe to different forums by checking the 'subscribe' box.

In each forum, there is a notification checkbox.  In each thread, there is a notification checkbox.

You must only choose one of these options - if you check the checbox to subscribe to all forums in a group, you shouldn't use any of the other checkboxes.  You can only subscribe to a thread if you haven't checked the 'subscribe to forum' checkboxes.  If you have duplicated any of these, you'll get an exception when you create a new thread.

As for the page rebuild index, in your 'Host -> Friendly Url Settings' page, you should see an option in the 'Regex Filters' which has the heading of this 'Rebuild Page Index and Update Cache when Url matches this Regex'.  In it is a regex filter.  Any request that matches this filter will result in the page index being rebuilt.  So, if there is something in your Urls that looks like it will match this value, then you'd be getting too-frequent page index rebuilds.  But as yours is happening on a regular basis, rather than a random pattern, I'd say it has something to do with app pool recycling or web cache clearing.  It's very difficult to tell without an in-depth analysis of the site, including all the asp.net caching settings, IIS app pool and website settings and a few other things.

It's only something to worry about if you are experiencing poor performance, though.   I will put an option in to 'silence' the messages so you don't fill the log - this will be in the next release.