Make 'exposed form in block' work in panels: Change the $form['#action'] of views_exposed_form to request_uri() in panels_pane

This is a Panels issue. I'd re-file it but I don't know what version of Panels you're using.

I thought that panels was not recommended for production sites? Is this a development site? Does panels produce the exposed form in block option for a filter in views?

The problem here is that the exposed filter as a block is just a simple, Drupal block. Drupal's blocks are dumb and have no sense of context, so it doesn't know whether or not it's in a panel. So it can't pull the URL from the panel it doesn't know about. The setting on the panel pane therefore cannot affect the exposed filters in a block.

At this point they would not be in a block. They would need to be their own ctools content type, perhaps, which is probably ultimately the way to go in Panels.

How can a ctools content type be created?

subscribe

Better do it so:

function my_module_form_alter(  &$form, $formState, $formId )
{
	if ( $formId == 'views_exposed_form' )
	{
		$form['#action'] = url($_GET['q']);
	}
}

This fix is working for me! Thanks :)

SOLID fix. Thanks you so much, erikseifert!

This worked great....

Wow that was a surprisingly easy fix. GJ erikseifert and thanks.

Subscribe

As I understand, the issue is that when you expose the filters as block and want to add them in a certain area on every page on your site, the input that you provide to the block is not directed to the actual panel where you add the view.

I have solved my case with Panels Everywhere and Views content panes. The steps for setting up a site-wide exposed filter for me were the following:

1) Created a view with content pane display. The content pane has an exposed widget which I want to see on every page. I do NOT set the widget to be exposed as block.

2) I create a new panel page, add the created content pane to it and override the path for the content pane to have the panel path

3) In the site template provided by Panels everywhere I add the same views content pane again, and again I override the path to redirect my query to the panel page

4) In order not to have the content pane two times on the panel page (one printed by the site template, another by the actual page), I set the pane visibility on the site template to hide the pane on the panel page.

That's basically it, the solution is fairly simple but requires Panels Everywhere module.

Dm.

In case of those just finding this issue (like me). Using much of the suggestion in #419556-11: Make 'exposed form in block' work in panels: Change the $form['#action'] of views_exposed_form to request_uri() in panels_pane and on referenced threads I was able to redirect my exposed filter block to the correct custom Panels page.

* View (MY_VIEW_NAME) of data with exposed filters
* Exposed filters in block setting is on
* Views Pane display of MY_VIEW_NAME is added to a custom Panels page with path 'my/panel/path'
* Exposed filters block is used in a custom Panels home page with path 'home'

If a Views page display is available, the exposed form will redirect there. If a Panels page is created and holds the Views pane display pane related to the exposed filters, it doesn't know where to go. By default, applying the filter form on the home page would reload the home page with the filter query attached (e.g., mysite.dev/home?keys=0&tid=1). The action on the form was set to '/' since I had no Views page display.

When I used code from #419556-11: Make 'exposed form in block' work in panels: Change the $form['#action'] of views_exposed_form to request_uri() in panels_pane above it affected all of my exposed filter forms and I needed to restrict it to the specific View in question. Using a suggestion from merlinofchaos elsewhere, I first check for the View name to make sure we only apply to exposed filters of this View.

The exposed filter form now has an action of 'my/panel/path' and redirects properly with the required query string attached. Any suggestions on cleaning up the following?

function MY_MODULE_form_alter(&$form,$form_state,$form_id){
  if ($form_state['view']->name == 'MY_VIEW_NAME' && $form_id == 'views_exposed_form') {
    $form['#action'] = 'my/panel/path';
  }
}

I think I came up with a more elegant solution that will work for an exposed filter block in any panels context.

See below:

function MODULENAME_form_views_exposed_form_alter(&$form, &$form_state) {
  // check to see if this is a panel pane display
  if(strpos($form_state['view']->display, 'panel_pane') !== FALSE) {
    // if so, change the form action to reflect the panel's path
    $form['#action'] = request_uri();
  }
}

merlin, do you think it would be possible to incorporate this into the logic of the exposed filter block itself somehow?

Moving to the currently active version.

When you add an exposed from block to a panel, it should contain an option: Inherit path. That does what this does, without the hack.

Ah, OK. I wasn't aware that existed. Is it new?

Greetings,

I'm having a problem with this. I have an exposed form in a panel pane, I've checked the option "Inherit path", but the exposed form is not inheriting the path. It is working correctly in non-panels pages. Is there another variable that may be the cause of this?

Thanks for any help you can provide.

Scott

**Update 9-4-11** I was able to correct this - the issue was caused by an oversight on my part.

@scott859

We are having the same issue -- what was your oversight please?

This worked for me perfectly. I've ran into a snag though.

I'm using Panels Tabs (http://drupal.org/project/panels_tabs) to put some Exposed Views inside. I'm using it to give different sorting options to users after they perform a search using the filters.

Unfortunately, using this code/module, the tabs are now given two URLs. The code for the tabs should look like this:

<a href="#tabs-0-search_results-2">Tab 2</a>

But instead, it looks like this when I apply a custom title:

<a href="#tabs-0-search_results-1"></a>
<a href="/find" class="active" >By Date</a>

--

I'm new to using hooks, so I'm lost on this right now. My module code looks roughly the same, like so:

function exposed_filters_redirect_form_alter(&$form,$form_state,$form_id){
  if ($form_state['view']->name == 'search' && $form_id == 'views_exposed_form') {
    $form['#action'] = '/find';
  }
}

I'm a little confused on why the links to the tabs are given another anchor tag that is defined in the module. Is there any modification to the custom module to prevent this from happening?

#11 works for me too :)
Thanks

.

if ( $formId == 'views_exposed_form' )
{
$form['#action'] = url($_GET['q']);
}

Works perfect! Thanks for Erik Seifert!

This solved my issue!