It appears that:
`$fieldDefinition = $fieldManager->getFieldDefinitions($entity_type, $bundle_name)[$field_name]` returns `null`.
On the other hand, `$fieldDefinition = $fieldManager->getFieldDefinitions($entity_type, $bundle_name)` returns the current entity without the field that is yet to be created. So it returns null because the new field is not in the fieldDefinition.
Not sure this is a breaking change in core as the fieldmanger is identical to 10.1
Hi thanks for the patch, it seems to fix it at line 281, but now raises a new error:
TypeError: Drupal\gdpr_fields\Entity\GdprField::propertyCanBeRemoved(): Argument #1 ($field_definition) must be of type Drupal\Core\Field\FieldDefinitionInterface, null given, called in /var/www/public_html/modules/contrib/gdpr/modules/gdpr_fields/src/Form/GdprFieldSettingsForm.php on line 378 in Drupal\gdpr_fields\Entity\GdprField->propertyCanBeRemoved() (line 369 of modules/contrib/gdpr/modules/gdpr_fields/src/Entity/GdprField.php).
rbosscher → created an issue.
rbosscher → created an issue.
Not sure if it helps with the discussion, but my situation is almost identical to @manarak and I totally agree with him on all points.
I was able to upgrading my last D8 sites only 2 months ago, because of upgrade issues in contrib modules. Now we're already seeing the 10 alpha the `also available list` and it made me worry a little to be honest.