Search problems

Permalink
I have set up the search page of my website as explained in the useful tutorial 'How to make Concrete5's Search/Search Indexing Work'. However, I still have a couple of problems:

At the moment my search is only picking up keywords from the page addresses and not the content of the website.

Also as you can see on my webpagehttp://www.queeneleanor.org.uk/index.php?cID=52... there is no box showing where to put in the search term. In fact, I have this problem in all my edit dialogue boxes too when I am adding media - it doesn't have a box showing where to put file names and such like in.

Any help on these two problems gratefully received.

 
jonsel replied on at Permalink Reply
I would really like some help on this - has anyone any ideas?
LucasAnderson replied on at Permalink Reply
LucasAnderson
1. Make sure when you add the Search block, you select 'everywhere' in the "Search Within Path" section.

2. It looks like your site's theme has a global style set for input boxes to remove borders. The box is there, but there is no border on it.
jonsel replied on at Permalink Reply
thanks - this is checked but still doesn't search whole site - only page titles.
jonsel replied on at Permalink Reply
Still no luck - can't search site - only searches headings - any ideas?

Also how can I change the global style for the theme - I can't find any reasons for the missing boxes in the style.css file? In any case the boxes are missing on all input boxes including those on the standard concrete edit controls from the control panel.
LucasAnderson replied on at Permalink Reply
LucasAnderson
I think the answer to your problem can be found here:http://www.concrete5.org/help/building_with_concrete5/developers/se...

(special thanks to b-lew)

For your style issue, looking at your CSS file (http://www.queeneleanor.org.uk/concrete/themes/QE/style.css) it has this in line 1:

html, body, div, span, object, iframe, h1, h2, h3, h4, h5, h6, p, blockquote, pre, a, abbr, acronym, address, code, del, dfn, em, img, q, dl, dt, dd, ol, ul, li, fieldset, form, label, legend, table, caption, tbody, tfoot, thead, tr, th, td, textarea, input, select {margin: 0; padding: 0; border: 0; font-weight: inherit; font-style: inherit; font-size: 100%; font-family: inherit; vertical-align: baseline;}


Notice that this area has "input" as a selector and within the style for all of these you have "border: 0". This effectively removes any border from ANY of the elements listed above, including all your input fields. My recommendation is to either remove the "input" or the "border: 0;".
jonsel replied on at Permalink Reply
Many thanks for solving the latter problem which had vexed me for some time - I now have boxes at last - I had overlooked that part of the style sheet.

Re the search problem - I have done everything suggested in that very helpful guide and it still doesn't work. I wonder if it is because I misunderstood this section:

'If you've added any custom blocks and the content from those blocks are not showing up in your search results the problem is most likely that the block developer did not include the "getSearchableContent()" function in the block's controller. This function should returns trimmed down text content for a given block.'

I have this line in the core block controller. Do I need to reference it also in the page style sheets where each custom block is referenced?
LucasAnderson replied on at Permalink Reply
LucasAnderson
Can you paste/attach your theme files so I can review them? I think the problem may be with how you named your editable content areas. By default, the search only indexes content within Main and Main Content block areas. If you have a different area name that search index is not looking in it.
jonsel replied on at Permalink Reply
I do indeed have lots of different names for content blocks
e.g.
<div class="column-content">
<? $a = new Area('first panel'); $a->display($c); ?>

I did then reference this in the index_search file as $is->addSearchableArea('first panel'); as described in the guide.

I suspect I haven't done enough though!
LucasAnderson replied on at Permalink Reply
LucasAnderson
This might be a crazy question, but did you run the index maintenance job again after you added those calls to the index_search file?
jonsel replied on at Permalink Reply
yes!
LucasAnderson replied on at Permalink Reply
LucasAnderson
Are you using a custom block, or just the regular Content block?
jonsel replied on at Permalink Reply
I took the original templates from Arcsin. I then added the editable blocks as described in the tutorial. I just put new names in for the content blocks to make it easier for users to understand them on each page(although I fear I may have done the opposite!). The blocks are then editable exactly as in the standard themes.
LucasAnderson replied on at Permalink Reply
LucasAnderson
Let me clarify:

"Block" refers to the module that controls content/images/etc. This gets added to a template Area.

"Area" refers to the editable location in the template. This is the Area you can add Blocks to.

So, when you go to Add/Edit a block, which blocks are you using?
jonsel replied on at Permalink Reply
Oh right - standard content block
LucasAnderson replied on at Permalink Reply
LucasAnderson
Two things:

1. Are you using caching on your concrete5 install? Try clearing that if you haven't.

2. I'll take a look at your code. Please attach a copy of the following:

- Your main template file "default.php or whatever"

- Your index_search.php file

Thanks!
jonsel replied on at Permalink Reply
do I need to clear cache on host's install or just on browser?

I have tried attaching files but it says invalid file extension for php files (although they are text files).
Mnkras replied on at Permalink Reply
Mnkras
rename them to .txt
LucasAnderson replied on at Permalink Reply
LucasAnderson
There is a 'cache' setting within Concrete5. Check the Site Settings area.
jonsel replied on at Permalink Reply 2 Attachments
I have cleared the cache - didn't help. Here are the files
broga replied on at Permalink Reply
Why if I search for example "banana" it doesn't return:
"Banana","Bananas" or "bananas" .... it only returns "banana"...

How to fix it?
Leap replied on at Permalink Reply
I'm having the same problem as described here...

Does anyone have a solution yet?
jonsel replied on at Permalink Reply
A bit frustrated that we are not getting an answer on this but was looking for something else in the forum and came across this thread which may address our problems.

http://www.concrete5.org/community/forums/block_requests/bad_search...

I wish the support forum was set up in a similar way to vbulletin and then it would be much easier to find all the relevant threads and also to search them. I find the way they are set up here to be very difficult to navigate around. Apart from that I think Concrete 5 is tremendous!!
digitmaster replied on at Permalink Reply
digitmaster
Hi,
look at my own workaround here:

http://www.concrete5.org/index.php?cID=34395...

I solved in this way.
After one week of frustration >:-)
Let me know if it works, please.

bye.
jonsel replied on at Permalink Reply
Digitmaster
Fantastic - it works!! Here is a virtual drink! After all the head scratching and blind allys, this is the definitive solution to the indexing problem where you have created additional blocks using non-standard names. Many many thanks. Worth just adding that the indexed_search and database_indexed_search are located in the concrete/libraries folder.
zoinks replied on at Permalink Reply
Is there any way to search the entire root directory?

I have a client who is using a lot of PDFs and is currently using Yahoo Search to search his root. It grabs all the info on the PDFs, apparently.

Having a Search bar that redirects to a Yahoo page is kind of crappy, though.