Rules + Proximity Part 2

Thanks Antonio, that makes sense.

The first time I tried it I got this error upon saving the node: "Unable to send e-mail. Please contact the site administrator if the problem persists."

I think I saved it as a user who should have received notice, but not sure it is related. Cron failed, I reinstalled a backup, got the same error, but then Cron did not fail again and is not failing. The error seems to come up only once.

Then when I try to create more nodes there is no error message or notification.

I think you are right. What confused me is when the error did not happen repeatedly, but apparently I deletd the Rule at some point.

I did not have any email configured. This must be the problem. It wanted to send a mail but had no directions.

There are two options.

One is to add a second action, so that there are two actions in the same Rule, "Notify nodes based on geographic proximity" and "Send a mail to..."

Second is to set up a subsequent Rule, with the event as "Node is notified based on geographic proximity.

I am going to try option one because the system must have tried to send an email, and I will try to configure who should receive that.

Thank you.

Edit Please ignore this entire rambling comment. Think I figured it out!

Thank you!

I started receving alerts, but two problems: they go to just one user (I have 3 fake profiles set up to test) and they go regardless of the distance.

So I probably just set it up to send an email whenever a node is created, but who knows.

View: Filter - Node type A & Proximity Great Circle < 20 miles

Rule 1 - Event: Saving New Content
Condition: If content type B created
Action: Notify Nodes Based on geographic Proximity

Rule 2 - Event: Node is notified based on geographic proximity
Condition: none
Action: Send Email to [nodeB:author-mail]

One question: When I set up the view filter proximity "get location by node" it prompts for "Node where to start to search from." I set it to start at a user profile, and that is the user profile which is also always notified.

It is the only user profile available in the Node: selection box, though there are other profiles set up. I don't understand why it asks for a place to start search but it seems it may be related to why that user is the only one notified.

Attached is the screen shot of the filter.

I think I am getting closer to accurate but don't know. Thank you.

I have not yet figured this out.

The geography modules are confusing, and I was not experienced with Rules at the time. I have not tried it again recently.

I hope someone is able to figure it out and document it.

Hello -

Scalp, I am wondering if you are still working on Rules + Proximity.

I have been compiling lists of users to contact by running a Proximity filter in Views, and eventually it will be much easier to automate that, to send email automatically when a new node is created within X distance of a user.

It is not clear to me exactly what this patch does. Are you still using it?

On another note, I recently noted this new module to Geocode a node when a Rule is processed. Have not gotten it to work yet.

http://drupal.org/project/rules_geocoder

Hi scalp, Thank you. Following is what I tried. And, Rule 1 is always triggered, Rule 2 is never triggered. Any idea? Thank you and congrats for figuring it out.

View- Filter: my user id (no other filters or fields)

Rule 1-
Trigger - When Content is Changed.
Condition - Content = Node Type.
Action - Notify Nodes Based on Geographic Proximity, with the View Selected (it states 32.18688 miles from)
(also added an email be sent to me so I can see if this action is triggered)

Rule 2-
Trigger - When Node is notified based on geographic proximity.
Action - Rule Set
(also added an email be sent to me so I can see if this action is triggered)

Rule Set - Notify User

Thank you, I had missed the Views configuration in Step 14.

I think I followed the steps as closely as possible, but for me the first triggered rule triggers the action every time the node is updated, whether the distance is less than or greater than 30 miles.

However, the second triggered rule is never triggered, and most oddly the second triggered rule does not have the option for the Rule Set in the action setting. When I choose Rule Set, that Rule Set is simply missing from the list of Rule Sets. I have checked other triggered rules and the Rule Set is available as a possible action.

Hello -

Here is a copy of the exported View. I have been testing this setup and oddly at some times I get 10 emails indicating the second Triggered Rule has been triggered, which is equal to the Items to Display in the View, but this is before the new node is even geocoded.

And, I have only geocoded one user profile, my own.

Why in the second Triggered Rule do you schedule a Rule Set, instead of using an Action to send the e-mail from the Triggered Rule?

$view = new view;
$view->name = 'Rules_and_Proximity';
$view->description = 'Rules_and_Proximity';
$view->tag = '';
$view->view_php = '';
$view->base_table = 'node';
$view->is_cacheable = FALSE;
$view->api_version = 2;
$view->disabled = FALSE; /* Edit this to true to make a default view disabled initially */
$handler = $view->new_display('default', 'Defaults', 'default');
$handler->override_option('fields', array(
  'distance' => array(
    'label' => 'Distance',
    'alter' => array(
      'alter_text' => 0,
      'text' => '',
      'make_link' => 0,
      'path' => '',
      'link_class' => '',
      'alt' => '',
      'prefix' => '',
      'suffix' => '',
      'target' => '',
      'help' => '',
      'trim' => 0,
      'max_length' => '',
      'word_boundary' => 1,
      'ellipsis' => 1,
      'html' => 0,
      'strip_tags' => 0,
    ),
    'empty' => '',
    'hide_empty' => 1,
    'empty_zero' => 0,
    'set_precision' => 1,
    'precision' => '2',
    'decimal' => '.',
    'separator' => ',',
    'prefix' => '',
    'suffix' => '',
    'location_provider' => 'circle',
    'exclude' => 0,
    'id' => 'distance',
    'table' => 'openlayers_proximity',
    'field' => 'distance',
    'relationship' => 'none',
  ),
));
$handler->override_option('filters', array(
  'type' => array(
    'operator' => 'in',
    'value' => array(
      'user' => 'user',
    ),
    'group' => '0',
    'exposed' => FALSE,
    'expose' => array(
      'operator' => FALSE,
      'label' => '',
    ),
    'id' => 'type',
    'table' => 'node',
    'field' => 'type',
    'relationship' => 'none',
  ),
  'circle' => array(
    'operator' => '<',
    'value' => array(
      'value' => '30',
      'min' => '',
      'max' => '',
      'location' => '',
      'node' => '194249',
      'unit' => 'miles',
    ),
    'group' => '0',
    'exposed' => TRUE,
    'expose' => array(
      'use_unit' => 0,
      'unit' => 'unit',
      'use_location' => 0,
      'location' => 'location',
      'use_node' => 1,
      'node' => 'node',
      'use_operator' => 0,
      'operator' => 'circle_op',
      'identifier' => 'circle',
      'label' => 'Proximity: Great-circle',
      'optional' => 1,
      'single' => 0,
      'remember' => 0,
    ),
    'location_as' => 'node',
    'id' => 'circle',
    'table' => 'openlayers_proximity',
    'field' => 'circle',
    'relationship' => 'none',
  ),
));
$handler->override_option('access', array(
  'type' => 'none',
));
$handler->override_option('cache', array(
  'type' => 'none',
));
$handler->override_option('row_plugin', 'node');
$handler->override_option('row_options', array(
  'relationship' => 'none',
  'build_mode' => 'full',
  'links' => 1,
  'comments' => 0,
));