Integration with Views module

cool stuff :)

+/**
+ * Implementation of hook_rules_action_info().
....
+function views_rules_oaction_info() {

This will not work. :)

Additional it would be cool to allow arguments. I don't know wether this is hard to implement

Views only provides support for Drupal core data. Modules are expected to provide their own Views support (and many, many modules have embraced this, so it works).

Let's ensure the code is ready, then we can see whereto it goes.

@patch: $display_id_description This is not really a description about the argument, but a help text. Use the action form callback to set this. Also the view should be selectable in a form. Isn't it possible to make the display selectable too? Then is it possible to render a view without html? Perhaps we should add an option to use http://api.drupal.org/api/function/drupal_html_to_text/6 on it.

Cool, I'm looking forward to your next version. For doing multistep action forms you can have a look at rules_action_taxonomy_load_term_form() or the cck action.

@views display: agreed!

I'm working on project that would require this. will help on testing. great work!

UPDATE: it does not work for me yet. So what exactly this action will produce? Rendered view? How do i insert this as variable in other actions (variable, syntax)? Also I still don't get View Arguments that is required value. How about view with no arguments or one with multiple? Should this be required? What is tipical value for this field?

How is this connected with this issue? http://drupal.org/node/329500

Overall this looks simple and promising, would like to learn more so i can contribute better.

subscribing

Subscribing....

Busdriving

Subscribe

+1
Subscribe

+1 subscribing

sub...

Totally subscribing, will test and provide feedback as soon as I can.

I'm not sure we need a AJAH form to select a view display, standard practise is to just use a optgroup select list to choose both at the same time.

I'll get a patch up and working asap.

Here's a patch that includes selecting a view using a select box, and passes in the arguments correctly, they are optional too.

I'm still not sure how you'd use the view in other, later conditions, as the view result is only around in a string variable, and needs to be available to token really. @fago is there an easy way to get the rendered view into the token system so it's rendered output can be used almost anywhere?

There is, of course, a bug in the above patch, so the view would never get rendered. The attached is tested and works!

Need others to test this patch, you may want to patch rules with #723980: Expose basic rule variables to token so that it's super easy to see the output of the rendered view.

The patch in #19 looks fine to me! I just committed the mentioned token related patch.

@code:
Well as it's code to to provide an action for views it should go into the views module - don't know though whether merlin is open for that. Anyway, maybe it would ease maintaining / improving it nevertheless, if it would go into a separate "views-rules" module? Rules itself currently doesn't ship with any rules integration for a contrib module and I'd like to keep it that way.

Given that this issue started in the views queue and moved into the rules one, we're probably not going to get it in either, which is a shame.

Moved to a new module for work to be able to continue.

yea, all contrib modules with views integration has a folder within named 'views' and a modulename.views.inc file.

I believe this is the same methodology of Rules modules, where other contrib modules wanting to integrate with Rules will have the rules.inc file within its module folder, and not in the Rules module.

I have not seen the contrib module views inc files included with the Views module (i think it will be difficult for the Views maintainers to maintain all the different contrib modules).

Is there a chance of this views integration living within the Rules module folder as a rules.view.inc file?
Or is the best path to take to have it as a separate module?

Well the point is this is not like any regular views integration - I'm not sure whether merlin has realized that in #2. Instead it's a rules action for views, thus code that integrates views with the rules module and not the other way round.
So if you prefer to have that shipping with views, I'd suggest you'd give it another try.

Subscribing

subscribing

#521640: sql query in/as condition references this issue in regard to using views results as conditions.

Sbcr

subscribing

sub

Subscribing.

Would be nice to have a rules condition based on views, that allows for comparison of a number with the count of the views result (>, >=, <, <=, =).

An example: if count of a certain node type with the same values in one or more specific fields (arguments of the view), then "set a form error" (with Rules forms module)

I am willing to contribute such features to this project, let me know if you are interested in including it.

You can achieve the result mentioned in #32 using programmatic calling of views in the php condition widget.

Edit: I think.... I've achieved a "show me all the nodes of type x" from views and used the count to evaluate a true/false, and return that...

I know that is possible. You can accomplish about everything with the PHP condition widget, but it's not very easy to reuse, feels rather like a hack and is not supposed to be used by non-programmers.

Watching this with much interest +1

This has been committed in http://drupal.org/cvs?commit=364506.

Will open another issue for the condition.