Content with advanced search possible?
Permalink
Is it possible to build a content, that you can do an advanced search on?
For Example:
Content with Name, Age and Location
Name: Smith
Age: 12
Location: Germany
Name: Dave
Age: 40
Location: England
Name: Hugo
Age: 32
Location: France
Search for age between 10 and 30 and list the content
Is this possible with C5?
Sorry for my bad english^^
For Example:
Content with Name, Age and Location
Name: Smith
Age: 12
Location: Germany
Name: Dave
Age: 40
Location: England
Name: Hugo
Age: 32
Location: France
Search for age between 10 and 30 and list the content
Is this possible with C5?
Sorry for my bad english^^
I followed the Instructions.
But i cannot add a new block, where i can search for the custom attributes.
it still says, that there is noly the standard search block...
But i cannot add a new block, where i can search for the custom attributes.
it still says, that there is noly the standard search block...
The search system is something that I've been looking at recently. Not for any particular reason. More of just finding out how things work. I kind of assumed it would use generally accepted search techniques and was quite surprised when I found a 3rd party bolt-on and no sign of SQL anywhere.
I've been asking myself "why is it iterating over blocks and cached pages when we have full text search database capabilities at the core (MySQL)?"
The logic seems a bit backwards.
From what I have seen from a cursory inspection is that each block, page etc is iterated over and then searched for text using a zend search thingy (I may be wrong). This is quite limiting (as well as a burden that can be offloaded to a DB) as only pages and blocks (in the cache?) can be searched. I was expecting the MYSQL database (which contains everything) to be searched for the text and linked back to the page, block, attribute....whatever. After all it's only a few well crafted SQL joins and it's the sort of thing the MYSQL database is designed for.
I might have to get my crowbar out again and see what happens when I insert it. There's probably a really good reason the zend search is used. It's just not that obvious to me.
I've been asking myself "why is it iterating over blocks and cached pages when we have full text search database capabilities at the core (MySQL)?"
The logic seems a bit backwards.
From what I have seen from a cursory inspection is that each block, page etc is iterated over and then searched for text using a zend search thingy (I may be wrong). This is quite limiting (as well as a burden that can be offloaded to a DB) as only pages and blocks (in the cache?) can be searched. I was expecting the MYSQL database (which contains everything) to be searched for the text and linked back to the page, block, attribute....whatever. After all it's only a few well crafted SQL joins and it's the sort of thing the MYSQL database is designed for.
I might have to get my crowbar out again and see what happens when I insert it. There's probably a really good reason the zend search is used. It's just not that obvious to me.
I'm not an expert on this but I vaguely remember Andrew mentioning somewhere that in a prior version of C5 they did use MySQL's full text search, but it turned out to cause *worse* search results than before because without proper tuning it doesn't work well.
@jordanlev
Well. Even if that is so (I'm not sure it really needs fine tuning for the type of searches in CC5). With a little bit of SQL you can pretty much do full text searches with string comparison functions.
Well. Even if that is so (I'm not sure it really needs fine tuning for the type of searches in CC5). With a little bit of SQL you can pretty much do full text searches with string comparison functions.
http://www.concrete5.org/community/forums/block_requests/custom-att...
If you're not comfortable with PHP, etc.. let me know and I can help you out.
- Josh