Hello,

I definitely agree that this is a much needed feature. I too have a page footer on every page that shows up in my search results.

This is just a guess, but I suspect part of the difficulty in addressing this is that the core search method just asks the modules what content should be added to the index and the individual modules (by implementing iSearchable) report the answer. Then, the "searchable" feature is set in the module definition by the host. With this setup, to make the option for whether a module should be added to the search, the module settings couldn't actually be the same for every module because the "Don't Search this Module" setting would only apply to modules that are "searchable" in the host settings.

I mention that because, I think, the answer here is that it's really up to the individual module to choose whether or how to return information to the search index. So, the issue may be less with the core and more with the specific modules.

So, all this leads to a different sort of question - can we get a setting in the HTML module to control submission to the search? I think that would take care of most of this trouble...

Thanks,

Mike

Hi Joseph,

Thanks for the tip... Unless I'm missing something, though, doesn't this only work for external search engines? Much of the trouble is DNN's own search provider. Modules will get indexed multiple times if they are on multiple pages and sometimes you just don't want module content to show in the search results - even if it's public.

I submitted an enhancement request on this to Gemini this morning specifically for the HTML module: http://support.dotnetnuke.com/issue/V...
 

Hope all's well,

Mike