Active
Project:
Addnode
Version:
5.x-1.2
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
2 Jan 2008 at 10:55 UTC
Updated:
21 Jul 2008 at 17:31 UTC
Seems to work better if you make the field not required.... If it's required, it seems the validate mechanism gets in the way somehow.... sees that the field isn't filled (even though it will be, using a newly submitted node) and explodes...
The "fix" is just not to require the field.... a better fix would be nice :-)
Comments
Comment #1
igray commentedWith this patch, I have been able to mark a nodereference field as required when using addnode. I did not test with a nodereference field that can have more than one type.
Comment #2
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.
Comment #3
mxgfx commentedThis issue should still be open, as the above patch didn't fix the problem. It's a good start though. I'll attempt to make some adjustments if I can.
Comment #4
mxgfx commentedMy apologies for not opening the issue with the last comment.