Fatal error with Drupal 10.2.x

Thanks for reporting. Considering its alpha version, will have to postpone looking into this as a major version update in custom_field to support the new field changes outlined: https://www.drupal.org/node/3386675 → . Recommend sticking with 10.1.x version of core for now since 10.2.x is not yet recommended for production anyway.

I hit this with 10.2.0 today... I'll dig a bit and see what I can find.

I can confirm this. It appears that several pretty significant changes → were introduced field-wise in Drupal 10.2, which causes much trouble to field-related modules, among others to Custom field.

10.2 has a full release now and this is a blocker as it is giving fatal errors. Should this be un-postponed?

Moving to active status.

Setting version to new 3.0.x-dev branch to start working on this issue there. New release for 2.x limits core version to max ^10.1.

I was able to update to Drupal core 10.2.1 combined with custom_field 2.0.0-rc6. I believe the constraint in custom_field's composer file needs to be made more strict.

Currently: "drupal/core": "^9.4 || ^10.1" allows effectively any version of 10.

Suggested: "drupal/core": "^9.4 || ~10.1.0".

The ~ "specifies a minimum version, but allows the last digit specified to go up." More details on that: https://getcomposer.org/doc/articles/versions.md#tilde-version-range-

Additionally, are there any suggestions of where to start looking to fix the issue?

Ahh.. yes I missed that. Does .info.yml need also to follow the same pattern for core_version_requirement?

I think so. I haven't tested those constraints in a .info.yml file myself, but this page → says so.

The core_version_requirement key in *.info.yml files for modules, themes, and profiles now supports semantic versioning as implemented by the Composer project.

Nice to have a single standard for version constraints!

Alpha release on the way. Its not perfect yet but its functional enough to prevent the fatal error. The major problem to solve now is to somehow sync storage and field settings on changes via ajax since they are now combined in the same form. Appreciate any help if someone wants to contribute.