Views Hacks Drupal 7 branch

Subscribing... would love to see it for D7 too!

really needed ..

Anyone interested in helping out with coding to port to D7?

I would like to help out. I already started on my own (local). Waiting for further instructions from mantainer.
A couple of things i would like to note:

The reset button (module views_filter_reset) was already incorporated in Views 3.

I don't understand how the class views_filters_selective_exposed_form_plugin can extend the class views_plugin_exposed_form_basic if the later does NOT exist in the Drupal 6 - Views 2 installation and (what is really funny) php doesn't issue an error. According to php.net

If a class extends another, then the parent class must be declared before the child class structure. This rule applies to class that inherit other classes and interfaces.

I would like to help out as well. Starting with D7 port of autosubmit module. Further information is welcome.

cheers Alex

Um. Yeah. Me too. (ie. subscribe)

Thanks everyone. Some comments:

* Since the Reset functionality is in Views 3, no need to port it.
* The class views_filters_selective_exposed_form_plugin is only activated in Views 6.x-3.x - check the function views_filters_selective_views_api to be convinced.

Re #5: What information to you need?

#7 Nothing special yet. Just thought you can provide some additional info especially about autosubmit..

hey, I'm finishing autosubmit. just a little question to hide the apply button: when i enable a views reset button, it automatically hides together with apply. it's because of their ident type name: submit.

So I managed it by hiding the apply's class ".views-submit-button". I'm not sure if this is a good way since classnames are likley to change..

please find the D7 autosubmit in the attachment. Comments are welcome.

Alex

+1

Here is a port if Views Block .. I think the only thing missing is a new default view.

+1

Thanks everyone! I will start a D7 branch where I place those patches. I won't be able to maintain them actively for the time being, so if anyone is interested in co-maintaining he D7 branch please contact me privately.

Subscribing

I am new to Drupal and am using Views3. I am trying to figure out how the "reset button" has been incorporated. I currently am exposing a few filters for my viewers and it would be great if there was a button right next to the apply.

I appreciate if anyone can explain how I can see and implement this new feature in Views3

Thanks

@#15
no need to implement. it a feature already.
see what #7 wrote:
* Since the Reset functionality is in Views 3, no need to port it.

goto: views->edit->exposed form settings->Include reset button

cheers

@ Wallace123455
Please use the forum (& others)for this kind of questions.
In views 3 you don't need to "implement" this funtionality, the reset button in the Exposed Form section (Exposed form style settings) of the Views admin interface.
Wellcome to Drupal!

Thanks for everyones responses. With your help, I figured out how to enable the reset button.

Thanks again.

Posting a dev version of views_filters_selective compatible with D7-Views 3.
Some changes are:
Pure Plugin approach instead of hook form_form_FORM_ID_alter.
views_filters_selective_views_plugins()
views_filters_selective_exposed_form_plugin class.
Upgrade following api-upgrading.html
Use D7 Database Abstraction Layer.
Like any other dev it's use is not recomended in prod. enviroments. Just a starting point to move foward.
Some tests on views 3 dev (not the beta)

I would relly like to see the ajax auto refresh functionality ported to D7. Thank you guys for all your hard work. I would like to help, but I am more of a themer.

I would relly like to see the ajax auto refresh functionality ported to D7

It also has been incorporated in VIEWS 3 (see the latest dev release & attached picture)!! ;-)

subscribing

@neoglez no UI for views_filters_selective yet I suppose, right?

Changing the title of the issue for dashboard clarity.... sanity reasons.

subscribing
I come from http://drupal.org/node/463678 and I'm looking for a way to make a views exposed filter with a select list displaying only relevant, available terms.

using #19 returns the following errors :

Notice: Undefined variable: result in views_filters_selective_handler_filter() (line 215 of (...)/sites/all/modules/views_filters_selective/views_filters_selective.module).
Warning: Invalid argument supplied for foreach() in views_filters_selective_handler_filter() (line 215 of (...)/sites/all/modules/views_filters_selective/views_filters_selective.module).

just a basic Code review with coder module some tabs removed,
views_filters_selective_exposed_form_plugin.inc needs a @file block description

Thanks all for your efforts. Just to set expectations realistically, I'm currently not working on D7 for any of my projects, so I'm not ready to open a D7 branch for Views Hacks. If anyone here wants to test the ports here and maintain the D7 branch, please contact me privately and we can discuss it.

@Jerome F Thanks for the formating.
The major problem here is the approach to execute a clone view for every single filter and the way the results are scanned to reduce the filter(s) options.
At the moment i'm trying to change that into:

1. Execute the (one) clone of the view.
2. Scan the (view clone) results to collect info about wich options of wich filters are there.
3. Reduce the real view (not the clone) filter options to ones collected in the step before.

There are other collateral things to take care of.
@infojunkie A 7 branch would really help to work collaborative!

@neoglez I tried to use this with the attached view if that's of any help. the taxonomy_csv module let you import the attached taxonomies if needed.
I use an article with term reference fields and a location field with at least cities and countries.

With this I think you can reproduce #25 if these errors are not visible on your side yet.

OK, 7.x-1.x branch created.

Wao! That was fast! Thanks all, specially infojunkie for attending my request.
...tanking care of _filter_selective to attempt to publish (at least) a working version.
I really think the plugin approach (to reduce filter's options, not to integrate into views) should take ctools advantages (views is already dependant of it and vfs from views, so...), in this matter we have to keep in mind that there could be diferent kind of filters (also user-defined) and vfs should be able to get info(instructions) from those on how to filter their own options.

Subscribe...

I'm about to start a project for a client and will DEFINITELY need the selective filters module...
it was one of my favourites in D6 and it's permanently in my "pocketknife" modules list! :)

@neoglez @Jerome F Please let me know if there's something we can do to speed things up...

Check out tomorow ;-)

curious to see what's going on :-)

+1

@neoglez: I've planned to have a look at the code with a developper tomorrow morning, could you update the git version to your last version in order not to duplicate efforts, if you please?

I can't, have no commit access ;-(

I'm testing following the approach described in 28.
I'm leaving this issue and opening a newone only for vfs (Views Hacks Views Filter Selective Drupal 7 branch) to be able to work in a more modular way.

+1 :-)

@neoglez is now the maintainer of D7 branch :-)

subscribe

Would an extra pair of hands be useful for work on the D7 branch?

I'm going to to be using Views Selective Exposed Filters and Views Composite Exposed Form Plugin for a project so I'd be happy to take on co-maintainership and work on those.

Also, it would be really great if someone could make a D7 dev release: #1358028: Please make D7 releases.

Joachim, thanks for offering your help. I'll gladly take it, because I think the current state of Views Hacks on D7 is less than ideal. Since I don't have time to work on it, I'll let you lead the initiative. I'd appreciate that you consult with me on significant architectural changes if any are needed.

Thanks! I'll do what I can.

I'll file issues for any changes (apart from anything that's just comments or code style). Doubt I'll make any big changes but I'll wait for your input.

I've made the 7.x-1.x-dev release visible so we can perhaps get more eyeballs on the D7 work done so far.

What's blocking an alpha release? I can see these issues open:

- #1022974: Drupal 7 port of views_filters_autosubmit
- #1183628: Views Block Drupal 7 branch
- Views Filters Reset is now in Views core.

Given that technically an alpha release doesn't have to be feature-complete, we could make one now anyway. What are people's opinions on this? How functional are the various modules?

Opinion on views_filters_selective + better exposed filters :

1 - works for me after slight modification :
On views_filters_selective_exposed_form_plugin.inc, deleted those lines (around lines 127-135) :

if (!$this->exposed_filter_applied()) {
          $any_label = variable_get('views_exposed_filter_any_label', 'new_any') == 'old_any' ? t('<Any>') : t('- Any -');
      $filter_element['#options'] = array('All' => $any_label) + $filter_element['#options'];
       $filter_element['#default_value'] = 'All';
       }

2- Still have an error with views with empty results :
Warning: preg_split() expects parameter 2 to be string, array given in _filter_url() (line 1432 of ..\modules\filter\filter.module).
and cannot have working "empty result behavior" in views, i had to write it in the template.

Do please file new bug reports for any specific problems :)

Just a note to say I've committed an update to Views Flipped Table to make it work on D7.

Any thoughts on whether it's time to make an alpha release?

Thanks @joachim! We can make an alpha release when all sub-modules are functional.

I was thinking we could make an alpha release fairly soon, so we get more eyeballs on the sub-modules that are ready now. 'alpha' means 'not feature-complete', so it's ok if some sub-modules are not functional at all yet -- as long as we clearly say which ones.

Sure, works for me. I'm currently working on a better version of views_filters_selective, will notify you when it's ready.

The new views_filters_selective module is now ready, feel free to make an alpha when you want.

View auto refresh patch for 7.x-1.0-alpha1

I've filled an issue with a patch fixing several issues with the argument handler in views auto-refresh. See #1837410: Minor fixes to Views Auto-Refresh to make it actually work

@Oliver, views auto-refresh is working well for me (version 7.x-1.x-dev). I don't understand the motivation for the changes in your patch. Also the patch is not well formed and don't apply.

btw I think this issue can be closed. Better to post new issues for specific problems.

> btw I think this issue can be closed. Better to post new issues for specific problems.

Good idea.

@Jonhattan,
Ok, I didn't check 7.x-1.x-dev. Please ignore my patch :)