I will investigate this. I suspect the issue is that it gets a result both for the html content instance and a separate hit for the matching meta description or keywords on the page.

Right, so it gets a match on the Html content and on the page description since both have "Chicken Fingers".

I don't have an immediate solution, it was only recently that someone requested we make it also find results based on the meta data of the page, maybe I need to add a config setting to make it possible to disable this. The meta should reflect the content of the page anyway so it seems sufficient just to match the content. I will try to get a setting in place for this for the next release.

Best,

Joe

fyi, there is a newer build available on our Novell Forge download page, mojoportal-build-2009-11-07-mssql.zip that has this fixed. If you upgrade to that build and then rebuild your search index, it will get rid of the duplicate results and you can leave the descriptions as they are.

btw, I like your site, looks like some really good recipes, I'm going to have to try some of those.

Best,

Joe

Upgrading is pretty much the same as initial installation. There is documentation here:

http://www.mojoportal.com/upgrading.aspx

As long as your database connection string and custom settings are in user.config, you basically deploy the new files on top of the existing ones and then visit /Setup/Default.aspx to complete the upgrade.

You should ideally backup your database first and the current files, but at minimum, backup your Web.config file in case there are any custom sttigns there that you need to add into the new Web.config file.

Hope it helps,

Joe