Hello,

I am using a 3rd party module isn't searchable, at least not in the way I would like.

The module simply displays content on a page formatted via a template and editable via a form.
So far so good.

The problem is with making the data on the page searchable.
Firstly, could anyone tell me why the information on the page for this module isn't indexed?
I thought the indexer would just run through the pages one by one and grab their content and index it.
But that isn't happening, on a given page the html module for example has it's data indexed but the 3rd party modules data isn't.

Is it possible to do anything to force the content displayed by the 3rd party module to be indexed?

The data for the module is held in a database table (which i defined), the primary key of which identifies the page for which the data is to be displayed. i.e. for a primary key value of 1, the page name would be something like 'mypage1.aspx'. I don't know if this helps.

I would be really grateful to hear from anyone who can shed light on this.

Steve

Hello,

modules have to implement the ISearchable interface to let DotNetNuke know that they have indexable content (http://www.dotnetnuke.com/Resources/W...) , otherwise DotNetNuke would not know what data should be indexed or what user(s) can see - by using ISearchable a developer can ensure they dont expose private data (such as settings) and DotNetNuke can filter based on the user/security role.