Perhaps this has already been reported; I did not find a match.
Main settings permits the province display to be set to "Display full province name." When this is done, parts of Drupal's administrative UI do not work.
Specifically, on my Acquia-hosted site a "500 Internal Server Error" is returned when one attempts to browse these URLs:
The Acquia technical support team tracked the first of these down to a piece of PHP code. Here is their technician's comment:
"Okay, so I did some heavy code diving and found the root of the issue, it is in location module. Specifically around line # 1630 in location.module: $form['form']['fields'] = array( '#type' => 'location_settings', '#default_value' => isset($old['form']['fields']) ? $old['form']['fields'] : array(), ); The '#type' is referring to a location_settings field type. This is a custom form element and in the process function for this element loops through all the fields that could be used by user profiles and builds a sorting table. The Province field is causing issues when it is being built. From location_locationapi(): case 'province': drupal_add_js(drupal_get_path('module', 'location') .'/location_autocomplete.js'); $country = $a5['country'] ? $a5['country'] : variable_get('location_default_country', 'us'); return array( '#type' => 'textfield', '#title' => t('State/Province'), '#autocomplete_path' => 'location/autocomplete/'. $country, '#default_value' => variable_get('location_use_province_abbreviation', 1) ? $obj : location_province_name($country, $obj), '#size' => 64, '#maxlength' => 64, '#description' => NULL, // Used by province autocompletion js. '#attributes' => array('class' => 'location_auto_province'), '#required' => ($a4 == 2), ); The particular line is $country = $a5['country'] ? $a5['country'] : variable_get('location_default_country', 'us'); The $a5 param in this case is empty for some reason. I don't know the module well enough to tell you why or if it should be, but that is causing the segfault. The $country value ends up being the array: [10-Oct-2010 17:56:42] Array ( [default] => [collect] => 2 [weight] => -99 ) instead of a string which is expected. It's unclear why this should cause a segfault. My guess is that some code in the form API for building the autocomplete urls doesn't like it. At any rate, there's the issue. I've got to head out right now, I guess the best thing to do is to file an issue in the location module's queue which I can do tomorrow. In the meantime, one of my colleagues may be able to modify the code to not show this field, or perhaps there is a configuration setting to not use it?"
Indeed, when the above option is selected, the referenced parts of my administrative UI are unavailable. As soon as the option is reverted to "Display province/state code.", the administrative UI behaves normally.
IMO this is a serious flaw in the Location module, because it means that one cannot have content displaying the full province/state names. Thus Solr search, in particular, becomes less useful. Etc.