Closed (fixed)
Project:
Custom Search
Version:
6.x-1.1
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
19 Mar 2010 at 14:46 UTC
Updated:
1 Jun 2010 at 18:12 UTC
Jump to comment: Most recent file
Comments
Comment #1
jdanthinne commentedAdded in the DEV version.
Comment #2
mxtI've just tried this feature and I've noticed a smull issue with javascript validation.
See image in attachment please.
My REAL opinion: if there is at least an input filter setted up, I don't see any reason to keep mandatory default "search" input (like core does and consequently Custom search module does.
A user is forced to insert a keyword: why?!?!?? It would be possible that a user can do a search only selecting an Input filters (e. g. like a taxonomy term, or an advanced search input filed). Not necessarily he have to know BEFORE what he's searching for, may be he only want to show all contents with a taxonomy term associated to.
So I'd change rules for validation: "if at least an input filter is setted up, the research can be done using that filter"
MXT
Comment #3
jdanthinne commentedOkay, I hadn't tested the javascript... damm!
Corrected it to DEV so only the default search field is highlighted.
For the other thing, unfortunately (and please correct me if I'm wrong!), Drupal can't search content without at least a keyword. That's how the default search works, and I can't rewrite the entire search system :-). You can try via the /search page, select a content type and/or a taxonomy term (in the advanced search) and hit Search and you'll see that Drupal will give you a message "You must include at least one positive keyword with 3 characters or more."
Comment #4
mxtYes, I know that we have to keep default search input mandatory due to drupal core search system (so that's why I've attached the first image).
My second opinion was to be intended as "general" and I think it would be a Drupal CORE task to resolve elsewhere.
Particularly, It's correct that the default input search form is mandatory when a user starts searching from this block area, but I think it wouldn't be mandatory when a user is already on the result page, and starts a search THERE, in the advanced search drupal core form, where other filters are present.
Do you think I have to signal this "issue" in the core issues?
Comment #5
jdanthinne commentedYes, I think this belongs to core, not as an "issue", but perhaps a "feature request"?
Comment #6
D-Man commentedI'm a relatively non-tech web producer but have recently come across this issue on one of our clients' advanced search pages.
I wondered whether the need to add keywords when you have other filters could be 'hoodwinked' by adding hidden or default words to your free text, keywords field and then introducing an IF statement so those words would be used to index all of the content!?
So if the keyword box is always populated with - can this string be used as the default keyword for the command SEARCH EVERYTHING!!
(Obviously with a bit of trickery so that if you click on/off the field or reset to do a new search, it always populates with .
I think this should work, I just don't have the coding know-how to put it into action.
Feel free to shoot me down, dev world!! ;-)
Comment #7
jdanthinne commentedWell... in fact, I don't really understand what you mean!
There's so many terms : 'keywords', 'free text', 'keywords field', 'keyword box', 'default keyword', 'the field'....
Can you be more precise (perhaps with a mock-up, a screenshot with annotations, or a wireframe)?
Comment #9
cuka2 commentedHi there, I agree with your article and I will be back to check it more in the future so please keep up your good quality work. I love your content & the way that you write. It looks like you've been doing this for a while now. You're great, this is a niche information.
Banking Info | Smart Review | Online Game Wallpaper | Budget News