Make handling of invalid values for "possible values" for list-based profile

fields slightly more robust.  It's still not ideal---the error goes to the
WebGUI error log, but the user should be given some indication that the
profile field is broken.

docs/changelog/7.x.x.txt

@@ -14,6 +14,7 @@
  - fix: op=viewPurchaseHistory prices are now formatted correctly
  - fix: A minor bug in the default viewPurchaseHistory template
  - fix: Thread determination of "current" Post, and shortcuts to non-Thread Posts
+ - fix: make handling of profile field possible values slightly more robust
 
 7.2.1
  - Made a change to version tag commits to deal with unusually long commit

lib/WebGUI/ProfileField.pm

@@ -131,7 +131,13 @@ sub _formProperties {
 	$properties->{label} = $self->getLabel unless $properties->{label};
 	$properties->{fieldType} = $self->get("fieldType");
 	$properties->{name} = $self->getId;
-	my $values = WebGUI::Operation::Shared::secureEval($self->session,$self->get("possibleValues")) || {};
+	my $values = WebGUI::Operation::Shared::secureEval($self->session,$self->get("possibleValues"));
+	unless (ref $values eq 'HASH') {
+		if ($self->get('possibleValues') =~ /\S/) {
+			$self->session->errorHandler->warn("Could not get a hash out of possible values for profile field ".$self->getId);
+		}
+		$values = {};
+	}
 	my $orderedValues = {};
 	tie %{$orderedValues}, 'Tie::IxHash';
 	foreach my $ov (sort keys %{$values}) {