D10.2, Add Select field Error

Formatting changes to make this easier to read.

'type in anything' do you mean the normal format

value|Label

I confirm, same error, impossible to proceed. The problem is represented by the impossibility of adding fields to already existing and (previously) functioning projects.

Some updates:

I redid it from scratch again: installed drupal 10.2.0, and then tested adding a list of text without adding other modules, works! So the previous problem indicates the compatibility issue of some modules with this new core version, but I don't know which one. so far, I added webform, commerce and display suite, still works!

I need to create reference fields from a block in views, the current reference to views connects to the entire view rather than a block in that view, while reference to block seems has nothing to do with blocks in views. So previously I installed Block field module, but I am afraid it may give me trouble, because it is still the beta version. Any advice?

@sdsc, thanks for reporting back on your progress, that is really helpful. Based on that I am changing this to a support request.

For questions about the Block field module (which I am not familiar with), you can ask in issue queue → for that module.

Found it!!!

I went to update option value on an existing select list field, and I encountered the same error again! I then uninstalled "Field permission" module which I installed earlier today. Then I came back to edit the same select field, NO ERROR messages!!!

So, for now, I am positive that the module Field Permission has some compatibility issue with the core version. Hope this information can help you solve the problem.

That makes sense given 10.2 combines two forms, one of which field permissions would be form altering

I confirm, the problem is caused by the field permission module, which still remains an indispensable module for some platforms.

It looks like field permissions is triggering save of the field storage in an entity builder. Now that the field storage may be edited in the field config form, this could cause other undesired side-effects.

Opened MR because it looks like this module is already using GitlabCI 🤩

I'm also encountering this after updating to Drupal 10.20 from 10.17.

In my case I can't edit an existing field of type list select (text) or create a new field of this type.

I have the Field Permissions module enabled, so am assuming that this is the root cause as described above for me too.

Since this is critical, do we want to commit the current fix (all tests are passing) and deal with the fallout/ideal fix in a follow-up?

I'm not sure why I was not seeing the setting being saved in my previous testing. I tested this both with existing fields and new fields and it seems that the value gets saved correctly with the MR. FWIW, it was working in the UI in all of my previous tests so maybe I was not looking at the right value with xdebug.

So for what I'm concerned, the MR should be ready. We can work on moving the settings to the storage part of the form in a follow-up issue.

I've tested the patch and it looks fine. Thank you.

Thanks all! I'll cut a new release shortly.

Automatically closed - issue fixed for 2 weeks with no activity.

tarazingo → changed the visibility of the branch 3409364-d10.2-add-select to hidden.

Updating the Field permission module to 1.3 solves the issue.