bad loading of defaults from the cck number type causes new nodes to (silently) not be saved.

Hello. I am seeing a bad interaction between usernode.module and number.module. It might actually be a bug in content.module itself. It's very complicated and i've been struggling with it for days .... but to summarize: When the usernode has a cck multiple integer field, one of its possble values is 1, and that value is selected as a default, then the default seems to be loaded as boolean TRUE instead of int 1. This later causes validation to fail, so the usernode does not get created.

More details: this is a field with multiple integer values allowed: 1, 2 or 3. (The widget is multiple-checkbox.) Setting 2 or 3 as a default does not seem to be a problem, but setting 1 causes this failure. (BTW we originally had our values as 0, 1, and 2, but the 0 was even more problematic: it kept being stored in the DB as NULL!) Editing the node with a normal node form doesn't seem to be a problem, but usernode.module uses drupal_execute(). usernode.module also supresses all drupal_set_message() output during that drupal_execute(); comment that out on lines 233 & 239 to see the actual error message from array_key_exists().

The failure actually happens at line 144 of number.module, where array_key_exists() is called with its first arg being that boolean TRUE. (I fixed it with a hack: i check for a bool there and cast it to an int. Works for me, but wtf is it a bool in the first place?)

I have spent a lot of time chasing through CCK with xdebug, but the comments are few & i don't really get what's going on there half the time. I'll gladly experiment more if anybody has suggestions.