Addressfield integration

Hi!

unfortunately this is still an issue...

YES, I have a working solution now.

I think all problems here are due to what amarcus explains here: http://drupal.org/node/1678596#comment-6226254

So, to resolve, I've used the addressfield_tokens module and developed a workaround similar to what I've already used here: http://drupal.org/node/1542404#comment-6046606

Addressfield_token provides a function _addressfield_tokens_country() very similar to location_country_name() provided by location module.

Here what I did:

In the view that retrieves all countries list I opted to use addressfield_token formatters/tokens, an turn on aggregation settings to group by country. In this way I obtain a select that shows wrong html, but correct data (resolving issue I've described in point 3 in my first post in this thread):

<select name="view_global_filter_addressfield" id="edit-view-global-filter-addressfield--2" class="global_filter_2-view_global_filter_addressfield form-select">
  <option selected="selected" value="">Worldwide</option>
  <option value="46">AL</option>
  <option value="47">IT</option>
  <option value="50">US</option>
</select>

So now I can do a form_alter to manipulate and rebuild the select in this way:

function helper_form_alter(&$form, $form_state, $form_id) {

  switch ($form_id) {
    case 'global_filter_2':
      $modified_options = array();
      foreach ($form['view_global_filter_addressfield']['#options'] as $option) {
        if ($option == 'Worldwide') {
          // manage exception for first value 'All' (worldwide in my case)
          $modified_options[''] = $option;
        }
        else {
          $modified_options[$option] = _addressfield_tokens_country($option);
        }
      }
      // Assign the new modified options:
      $form['view_global_filter_addressfield']['#options'] = $modified_options;
      break;

  }
}

And all works fine now!

Yes, this is still a workaround, so I hope this module can better manage addressfield data someday...

Thank you very much!!!

Thank you for your suggestion ceaucari but we already know about location_taxonomize (see my comment here: http://drupal.org/node/1542404#comment-6039412).

What we are trying to do here has another purpose.