This happens when configuring a new content type that has no default value
this was fixed in 6.x but this problem is also in 7.x
fixed https://github.com/lelizondo/context_node/commit/ca232e44cd46fef787245e6...
Automatically closed -- issue fixed for 2 weeks with no activity.
Comments
Comment #1
lelizondo commentedthis was fixed in 6.x but this problem is also in 7.x
Comment #2
lelizondo commentedfixed https://github.com/lelizondo/context_node/commit/ca232e44cd46fef787245e6...