CiviCRM Community Forums (archive)

Another for my short book "Edge Cases of the Southern Seas" ...

On two client sites now, an admin has disabled the "Default" location type.

This causes all manner of weird and wonderful ripples throughout the system, such as: when registering a new user via the parent UF, the associated contact record will be created but no email address will be assigned to it.

The per-site fix is to check the default box. Easy enough, until someone else comes along six months or a year later (and maybe at a different client install) and unchecks it, and various things stop working again. So I think a code fix is indicated

One fix would be to require via the UI that one location type was set to "default".

Another (simpler, IMO) fix would be to change the format of the query in CRM_Core_BAO_LocationType::getDefault() so that it's of the form,
SELECT * FROM civicrm_locationtype ORDER BY is_default DESC, name LIMIT 1 rather than SELECT * FROM civicrm_locationtype WHERE is_default = 1 LIMIT 1. Should produce the same end result and allow CiviCRM to fall back to any other location type that is configured when none is set to default.

Personally, I rather like ORDER BY is_default DESC, RAND() ... it seems fairer. Just an idea.

Observed on 2.2.x, not sure if it came through to 3.x.