Closed (fixed)
Project:
Apache Solr Panels
Version:
6.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
1 Feb 2011 at 16:22 UTC
Updated:
20 Feb 2011 at 02:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
erik seifert commentedSame to me.
Panels 3.9
C-Tools 1.8
ApacheSolr Panels 6.x-1.0-alpha-1
Comment #2
erik seifert commentedQuick fix for Search Form ( but not for filters ).
Set Path in Search Form
Comment #3
ximo commentedYou're likely using the "search-apachesolr_panels" page. That's a page automatically created by the Search API which gives all sorts of bugs, it's not the one you should be using. Sorry for this confusion, I blame myself for the lack of documentation.
What you want to do is create a new Page Manager page with a path like "find/!keywords". Under Arguments, assign the "%keywords" argument as a String (name it "Keywords"). Then under Content, add the three panes found in the "Apache Solr Search" category, plus any of the Apache Solr blocks found in the "Miscellaneous" category. The "Apache Solr search results" pane is where you configure the search, you should have the "Keywords" context selected here.
Attached is an example page of what I described that you can import into Page Manager. That should clear things up!
I apologize for the confusion, will work on documentation. And I'll see if I can work around the Search API to make the "search-apachesolr_panels" page go away.
Comment #4
killes@www.drop.org commentedYep, you are correct, I used the false panel! Thanks!
Comment #5
ximo commentedGlad that solved it :)
Renaming the issue, will work on this later…
Comment #6
dabeast commentedThanks this was very helpful. How would one go about making this the primary landing page from the search box? Sorry if this is a stupid question.
Comment #7
ximo commentedNot at all. See #1047630: Provide block for custom search pages. Depending on you using Panels Everywhere or not, that is either ridiculously easy or hard :)
Comment #8
ximo commentedMade it work without having to be part of the Search API (which was the problem).
FYI, the search block issue is fixed too. There's also improved documentation in the README plus an improved example to import into Page manager.
A beta coming up, stable release should be out before long, as I don't plan to add many more features and it seems very stable.