in reply to Re: date on search results (super)
in thread date on search results

Well, it's gonna take a god to do that, or I'd have taken a whack at the patch myself.

Look at Everything/HTML.pm, in sub nodeName, and replace code from line 934 through the end of sub. You'll want to load up some CGI params expected by Super Search into the $q object, i.e. 

   $q->param( HIT => $node );  # HIT = title; $node is the search stri
+ng

   displayPage( getNodeById( 3989 ) ); # transfer to SS

[download]

One question is whether you'd want the SuperSearch to execute and display some results immediately, or just load up the search form and wait for the user to submit. I'd vote for the former, personally.

Between the mind which plans and the hands which build, there must be a mediator... and this mediator must be the heart.

Replies are listed 'Best First'.
Re^3: date on search results (super)
by tye (Sage) on Dec 05, 2008 at 22:22 UTC

    It always takes one of the gods to apply a patch. The fact that in this case the patch isn't as convenient for gods to apply doesn't actually prevent pmdev from producing a patch (which will not be a patch). (If I had recently seen a patch that had been tested on the pmdev test server, then I might further consider that difference, but I haven't.)

    Yes, I think the search should immediately run in this case. Most title searches will finish with a single submit of Super Search and the resulting server load will still be less than that generated by the current search behavior.

    Thanks for the pointers already provided. Thanks in advance if you produce something more concrete as well. I'm quite low on spare time but that usually changes at some point this month, so I might get around to updating Everything/HTML.pm with or without a more concrete patch then.

    - tye        

[reply]
[reply]

In Section Perl Monks Discussion