I'm using the Sexy exposed filters module (http://drupal.org/project/sexy_exposed) which replaces the exposed filter dropdown form element with a sexier one.

The module is very simple, it just sets its settings in an additional filter form submit callback with views_ui_cache_set($view). And it works fine , the settings get in the views_display table.

However, when I export the view, the settings do not appear in the exported code (neither by features nor by the views export link).

Since there are several exposed filter issues I think this is views related. It is easy to reproduce:

1. Create a view with a node reference exposed filter
2. Make the filter sexy on the filter form
3. Export the view using views' export link.

Result:
No 'sexy' settings in the exported code.

Comments

dawehner’s picture

dawehner
Primary language German
commented
Status: Active » Fixed

Well only things which are defined in option_definition can be exported. So you would have to write exposed form plugin like better exposed filters.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

czigor’s picture

czigor commented

Thanks, dawehner. I made a patch for BEF. #1494204: Incorporate the sexy exposed module

boobaa’s picture

boobaa
he/him
commented
Title: Sexy exposed filters export » Sexy exposed settings aren't exported
Project: Views (for Drupal 7) » Sexy Exposed
Version: 7.x-3.1 » 7.x-1.0-alpha4
Component: exposed filters » Code
Status: Closed (fixed) » Active

Let's give this another try in a more proper queue.

zserno’s picture

zserno commented

Thanks for pushing this. I just pushed a rewrite of SE as Views exposed form plugin. Please see 2.x branch in git. http://drupalcode.org/project/sexy_exposed.git/commit/6f82625

boobaa’s picture

boobaa
he/him
commented

2.x branch looks great, though I have some comments.

  • It would be even better if it had libraries.module support/dependency, to avoid hardcoding DDCL's path.
  • AFAIK only those files need to be listed in .info's files[] array that have classes. In this project, the only class is located in the sexy_exposed_exposed_form_plugin.inc file, so the other two entries simply don't make sense.
  • It would be even better if this branch had its own tarball generated and available from the project page itself (maybe with linking to this issue).
zserno’s picture

zserno commented

@boobaa: Thank you for your excellent remarks, sir. Libraries support is on the roadmap, will be included in the next release.
I think 2.x branch will be the main branch for 7.x.