Changing name of a surface with invalid boundary condition type causes ruby error

[Neal Kruis]

No description provided.

[Peter Ellis]

I think this might be fixed. Or at least I can't reproduce in version 0.9.2. The "Foundation" boundary condition has now been added which addresses the problem in a different. But it still shouldn't be causing a Ruby error in any case.