I've been trying to use drupal for several months now, so I don't know if that makes me a newbie or just a numptie, but, with all due respect, the core search module drives me crazy every time I try to find some info in drupal.org.
pleeeeeeeeeeeeeeeeeeeease could we have nedjo's SQL search / trip_search module (http://drupal.org/project/trip_search) installed/activated/enabled on this website? It won't take 5 minutes (assuming version compatibility...).
Apparently it runs happily along side the core search module (so no need to lose that functionality) but we would also gain:
1. boolean & phrase searching in basic search.
(imagine how much easier it would be to troubleshoot error messages with phrase searching!)
2. filter by category and/or nodetype in advanced search.
(which apart from anything else is going to help people get an over view of the site structure ...)
PLEEEEEEASE PLEASE PLEASE!!!!
thank you - in advance - for your compassionate contribution to my sanity.
:?
JohnG
Comments
me too ...
I think there should be a poll on drupal.org main page:
Should we enable trip_search on drupal.org
A) Yes
B) Of course
congratulations! you've won a prize for finding this page!
you win:
the grim satisfaction of knowing you're not alone in a meaningless unfathomable drupliverse.
You also win a prize: You
You also win a prize: You may test Steven's search patch free of charge. http://drupal.org/node/28159
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
Now killes, you forgot to
Now killes, you forgot to show them the test link:
http://drupal.org/node/28245
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
http://drupal.org/patch/review
--
Read my developer blog on Drupal4hu.
--
Drupal development: making the world better, one patch at a time. | A bedroom without a teddy is like a face without a smile.
so when will it be enabled for drupal.org?
I am in awe of Steven's work. The advanced search.module looks truly ... well ... awsome.
might I ask when it's going to be available 'in the shops' as it were?
and more to the point (of this thread), when will we be able to search drupal.org without risking our sanity?
;-)
It depends on the number and
It depends on the number and quality of favourable reviews the patch gets. Just saying "I like the features" won't help, though. If the patch gets committed it will be available on drupal.org after the next site upgrade.
--
Drupal services
My Drupal services
--
Drupal services
My Drupal services
self evident?
Thanks for the links BTW - interesting reading. I was looking at the criteria by which patches are evaluated, to see how my opinion would carry any weight. I came across this:
" There is demonstrated demand and support for the change. Demand is indicated by, e.g., comments on the drupal.org issues system or comments in forums or the drupal-dev email list. "
I wonder how the 'judges' can count the number of comments etc relating to problems with the current search.module? How can you count them if you can't find them?
so in my review, would this count?:
+1 because currently the search.module is holding back the whole communication system of the drupal.org community ? could we not stretch that to a +2 maybe?
+1 because the best 'alternative' available is to google site:drupal.org *
+1 because new drupal users get so frustrated trying to find answers to FAQs that they have to ask the question again ...
+1 because this clogs up the issues/forums unnecessarily ...
+1 because this annoys people who know the solution is already documented, and resent having to point it out again.
and if jozef agrees that would be +10 votes right ?
Forgive my sarcasm, but I'd pretty much given up on drupal as a useable CMS site chassis until nedjo revived the trip_search module. I can't believe there's only me, jozef and steven who think something needs done!
Does bribery count? If the patch goes through, and is enabled on drupal.org, I'll shut up for a whole week ... Deal?
or blackmail: a sponsored silence ... for every day I'm quiet, each sponsor pledges to vote +1 for steven's module. You can sign up here:
;-)
I can't believe that no one
I can't believe that no one has helped out nedjo, and Steven with actual code contribution instead of merely demanding without actually contributing help. A bad solution in the long run doesn't help anyone and can make future upgrades much more difficult.
As to your quote, please go back and read the lines that preceed it. That is one out of several criterea.
Sarcasm really isn't all that interesting or constructive if no one actually helps out with testing and feedback to actually get work done. Silence isn't useful if no one is helping do work.
Have you tested the patch yet? Have you looked at the proposed UI images that have been supplied? Commenting here without actual help testing and reporting back the results is not constructive.
Links for how to contribute constructively have been supplied.
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
fair enough, but ...
I entirely agree that code contributions are far more useful than comments. Unfortunately - and I'm always apologising for this - I'm no programmer. So my ability to contribute as you ask is severely limited. ( I don't have the facilities to run a CVS version nor patches, so I can only comment on what others have commented about the patch). If I sent a patch, I think you would wish you'd never asked!
"demanding" ? no - "begging", yes. My latest theory is that PMing requests is a bit more friendly and personal than adding to the 'feature requests' list which I imagine could feel like a ' list of demands' or 'specifications' from ' the community' to the coder.
I have had communication with Steven and flatter myself that some of my UI suggestions (aka requests) have been taken on board. As to the coding nuts and bolts, though fascinating, I can barely understand the concepts, let alone the code!
Apart from that, I can only offer encouragement to coders, and I hope that a bit of cheeky banter on this thread might provide a little humorous relief for anyone who shares my sense of frustration with the site-search function on drupal.org.
After all, this thread is about using drupal.org website, not for reviewing Steven's patch. I sincerely hope that Steven's patch will resolve the issue raised here and will work better than trip_search, but if not, the original request (which does not require code submissions, just admin permissions) for trip_search to be enabled still stands.
The last thing I want is to discourage the people (and it seems like quite small group compared to the number of drupal users) who actually create the code that we love to fiddle with, so
+1 to sepeck for trying so earnestly to wring code out of a stone,
+1 to everyone who contributes code, no matter how shakey,
+0.01 to everyone who can only sit on the sidelines and cheer,
-1 to hecklers ;-)
UI enhancements are as good
UI enhancements are as good as code. All the code in the world won't help without a useable interface.
As to performance details, see here for more information by people/persons more familier with it.
Note: I don't do php either.
-sp
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
server load required by trip_search
sepeck, you kindly wrote in a PM (ages ago) :
"From what I understand (I may be wrong) the added load would be more then slight. Some of the new infrastructure is undergoing testing, perhaps we may see the core site team revisit the issue then, but not until."
I wonder if you know of any news on that one?