Search Indexer options

Permalink
There seems to be a new config key called SEARCH_INDEX_AREA_LIST

But when I have a look at the code I see this:
http://svn.concrete5.org/svn/concrete5/trunk/web/concrete/helpers/c...

Only header and heaver nav are indexed?? I can't find any options in the dashboard to extend this.

What did I miss?

Remo
 
Mnkras replied on at Permalink Reply
Mnkras
no thats what it blacklists, by default its on blacklist
Remo replied on at Permalink Reply
Remo
hmm yes you're right but why doesn't it index any of my content.. Will dig around to code again
Mnkras replied on at Permalink Reply
Mnkras
yea i see that as well, fresh install with sample content, ran the indexer, search for concrete, no results, concrete5, no results

search is bugged
JimboJetset replied on at Permalink Reply
JimboJetset
Myself and Alex101 have been looking into this issue the last couple of days... below is the last email I sent him...

"If you look at the database table PageSearchIndex and browse the entries you will see that the 'content' column is empty for ALL rows... I added some content to your homepage and re-ran the indexer and the column remained empty... I added the exact same content to my own site and re-ran the indexer and the content field in my own db was populated so this is why your search is returning nothing because in the 'content' field of your PageSearchIndex table there is nothing to search for.... why this is happening I don't know but it seems for some reason the indexer is not populating the content field of the PageSearchIndex table. It may be worth asking the C5 team why this might be since we now know what is NOT happening."
Remo replied on at Permalink Reply
Remo
Okay thanks, this is at least a start.

I just had a quick look into the database. There's another thing which I don't recommend. The IndexedSearch class uses a truncate command to get rid of all content before scanning the page. Truncate isn't transaction safe and due to this you might end up having no incomplete content in PageSearchIndex during the time the indexer runs.

It's just a minor thing but I mostly work with enterprise applications and therfore think about transactions all day long. It's probably not as important to handle transactions proplerly when building a cms though..

I'll keep digging around the code but unfortunately the indexer seems to work fine on my sandbox now ):