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.
This commit is contained in:
Drake 2006-11-22 15:52:32 +00:00
parent 0903b1011e
commit c10b5b4fec
2 changed files with 8 additions and 1 deletions

View file

@ -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