I have a views search block(attached(using block admin page) to a node called search) with exposed fulltext search filter and this only works when ajax is enabled(but this doesnt work well too, cos there will be a page request after ajax request and page will be redirected to the page(what form action parameter sets) in couple of minutes.) So the form action parameter will be <form action="/"..
instead of the current page that is the "search". So action parameter should be action="search". If i have a page view beside the block view then somehow this page will be used and form action will be set to this view page. So if the view page path is view-search-page then action parameter will be action="view-search-page" and this is not set anywhere on setting page.
modules:
- Search API 7.x-1.11
- Database search 7.x-1.2+2-dev
Drunken, I can provide the site where it is used or more info, just let me know. Thx
Comments
Comment #1
mibfire CreditAttribution: mibfire commentedComment #2
drunken monkeyWhy don't you just use a "Page" display for the view? The thing with the block and a node at "/search" looks like a terrible hack, it's no wonder it won't work.
Also, in what way does this even relate to the Search API Autocomplete module?
Please provide a clearer description.
Comment #3
drunken monkeyComment #4
mibfire CreditAttribution: mibfire commentedImagine the following situation. The client would like to add some content for search page. How could you solve this? There is header and footer in views page but client wont edit content in views ui. They wanna use a unified gui to add content like node/x/edit. This is why i attached the block to node. But if i used a page view for this would it be a workaround? So if i attached a page view for node would it work with ajax and without ajax same way? If my view page path is view-search-page then would the form action be "search" as the node path is search? Cos if there is no js then form will be redirected to the path of form action property.
You are right, this issue should have been added to search api module. My bad.
Comment #5
mibfire CreditAttribution: mibfire commentedComment #6
mibfire CreditAttribution: mibfire commentedComment #7
mibfire CreditAttribution: mibfire commenteddrunken?
Comment #8
drunken monkeyAh. Hm, yes, I guess this would really be a tricky requirement. And I know that Views isn't as flexible as you'd hope when it comes to defining how a block should behave.
Anyways, I'm pretty sure this isn't really Search API-specific, so the question should better go into the Views issue queue. I wouldn't know how to best solve this myself, sorry! (Well, actually, a custom Views display plugin should be easily able to do this, but would of course be kind of a last ressort.)
Comment #9
drunken monkeyComment #10
drunken monkeyComment #11
mibfire CreditAttribution: mibfire commentedShall we move this issue to views issue queue?
Comment #12
drunken monkeyI already did. See above:
Comment #13
jyraya CreditAttribution: jyraya commentedHello,
I was searching an answer to another issue when I found this request.
I had to integrate a view with a full text search into the display of a content type too. I solve my problem by using Panelizer, Views pane (coming with CTools), Search API and of course Views"... and it worked for me.
How to do:
And it works...at least for me but I did on several projects without meeting problems.
Hope this helps
Comment #14
MustangGB CreditAttribution: MustangGB commentedClosing this as outdated to tidy up a bit around here. If you're still having problems with the latest release please create a new issue.