Closed (duplicate)
Project:
Drupal core
Version:
x.y.z
Component:
forms system
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
23 Dec 2005 at 16:45 UTC
Updated:
10 Jan 2006 at 10:23 UTC
Jump to comment: Most recent file
Comments
Comment #1
chx commentedLet me list what you do not read:
The error is reported for a gazillion of times. Matt Westgate and Chris Johnson helped me crafting the patch last night (and let's not forget Adrian, hunmonk, m3avrck for brainstorming it). I mailed the devel list this morning asking for testing.
Anyways, thanks for the report :)
Comment #2
morbus iffThis is probably my fault - I came in late to one of his discussions and didn't get the full details before I said "Make an Issue outta it."
Comment #3
Steve Dondley commentedWell, I don't think it should be a requirement to follow the development list to submit a bug.
I did get lazy and not do a search in the bug/patch queue. I usually do. But I find it kind of hard to pinpoint duplicate bugs/patches with it. Maybe I don't how to use it very efficiently? At any rate, it's easier for me to report a bug and let someone else to determine whether or not it's a dupe. You have confirmed this. :) Though I'm sorry if it created more work for you. :(
Comment #4
php_coder2114 commentedNone of the patches work.
Comment #5
Bèr Kessels commentedThis bug also appears in the following case:
1. Create nodes
2. Create new vocabulary w. terms (multilpe select, not required!)
3. Go edit the node. the select is empty!
4. Store the node.
See attached screendumpt for the PHP errors and the form errors.
I would expect form aPI to:
* select <none> as the default in case of a NULL value
* default to <none> w/o an error if nothing was selected.