In Named Locations, setting a Parent Location of a location to itself is bad #1255
Description
On the Named Locations screen, if you set the Parent Location of a location to itself, bad things happen. The location will disappear from the tree view (so it can't be fixed via the web interface) and any check-in related screens (like check-in configuration or actual check-in) that use that location won't load and will time out.
This can be fixed by correcting the ParentLocation column in the database, but it would be good if there were a check so this couldn't happen.