Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How to prevent Text/HTML module being indexed for searchingHow to prevent Text/HTML module being indexed for searching
Previous
 
Next
New Post
10/29/2008 8:53 AM
 

Hi,

I have built the static content for a clients site using a large number of Text/HTML modules in a standard 3 column layout. The client has asked that only content from the main ContentPane should be returned when using the SearchInput control. The question is, how do I prevent the content of a specific module i.e. all modules that are displayed in the left and right panes, from being indexed and added to the search tables? I have tried simply deleting the associated database entries for these modules, but the site re-indexes the search content and they are re-added.

Is this possible?

Regards,

Chris

 
New Post
10/29/2008 9:49 AM
 

You can simplely modify the TEXT/HTML module to make a new TEXT/HTML module which does not support being index.

Delete the ISearchable inteface and associated implement functions, rename the assembly name and store procedure prefix.

 
New Post
10/29/2008 11:08 AM
 

Seeing as the site is due to go live in about two weeks, and all content has now been loaded using the standard Text/HTML module, I was hoping there would be a solution that could work with the existing module. What you have suggested would obviously work, but time is now against me and having to update modules on over 50 pages of the site is not really an option.

Is there an alternative?

 
New Post
10/29/2008 11:15 AM
 

You could go into the database (desktopmodules table) and remove support for ISearchable from the Text/HTML module. I would then clear out the search tables and have it completely reindex the site.

To disable iportable you'll probably need to remove the businesscontroller information from the table, as well as change the SUPPORTED FEATURES record. This will also disable the Import/Export functionality of the module.


Chris Hammond
Former DNN Corp Employee, MVP, Core Team Member, Trustee
Christoc.com Software Solutions DotNetNuke Module Development, Upgrades and consulting.
dnnCHAT.com a chat room for DotNetNuke discussions
 
New Post
10/30/2008 5:48 AM
 

Thanx Chris, that sounds like a more feasible solution.

 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...How to prevent Text/HTML module being indexed for searchingHow to prevent Text/HTML module being indexed for searching


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out