New changes to set label logic cause integrity constraint violation

Thanks for the report. Good finding! +1 Let's investigate further.

Wrong reference (edited)

Thanks for the report! @grevil and me will also take a look at it asap!

The Form States API bugs should be fixable quite easy, if we can be sure they exist, as first step.

Same issue for me.

Are there any updates on it?

Maybe the issue 🐛 Automatic entity label does not take into account the field constraints Needs review could help

I have custom code that creates a node and prior to the change I was able to not set a title value using the create method on the entity storage handler. It looks like if I provide the value of "%AutoEntityLabel%", then programmatically created node is successful without the integrity constraint violation exception.

This comes from auto_entitylabel_entity_presave(), which checks if the label is equal to the placeholder value, but if the label is NULL, then it won't do anything.

I think the previous behavior could be maintained if the check included NULL and the placeholder value.

@mradcliffe sound good, could you prepare a MR draft?

This comes from auto_entitylabel_entity_presave(), which checks if the label is equal to the placeholder value, but if the label is NULL, then it won't do anything.

I think the previous behavior could be maintained if the check included NULL and the placeholder value.

I don't think I was correct about this, but there are tests now.