Install the new version of Drupal, enable the field UI, install butils, and use the field UI to create a new field, but the above error is displayed, and the field UI fails to create a new field.
The above error occurred when creating a new field.
qiutuo → created an issue.
qiutuo → created an issue.
I'm also getting the same error today, and the research found that it was caused by the missing "category" in the custom field.
After testing, it was found that the problem was not fixed, and the setting default value was not enabled in the setting field, and the problem still existed, and the message An invalid form control with name='default_value_input[field_abc][0][value][format]' is not focusable, when setting the default value is enabled and Text is selected Format, you can perform a save, but the text format is not saved to the database.
The error is not reported on the page where the content is added, but when a field is added to the content type and saved, an error will be reported when the field is set again, or when an existing field is reused in another type.
For example, if you click Re-use an existing field, select datafield, enter the field setting interface, and click Save to get an error.
Only when you use text_format will the error be reported, and if you use textarea, no error will be reported.
An error occurred in the following path,
/admin/structure/types/manage/article/fields/node.article.field_abc
To reproduce the above error, freshly install Drupal 10.2.5, node add article type, add long text for datafield,
Field: text
Storage :big
Widget: text_format
The above error is reproduced, and there is no response after clicking Save.
Field: text
Storage :big
Widget: text_format
As long as the text_format is selected, the rows setting is not displayed, the default format setting is not displayed, and the field cannot be saved when it is modified.
This is the management path: /admin/config/development/easy-entity-field
Set the content entity type to be used here.
Prompt in status:
The following changes were detected in the entity type and field definitions.
Easy entity field
You only need to find a field created by the easy_entity_field module, click edit, and then perform a save once to solve the problem.
Hello, I have corrected the above issue.
Hello, the above problem has been fixed, and there is no other prompt to execute phpcs.
Can I add a new field type, similar to the entity_autocomplete of jsonapi_reference field, and select the remote data from the list displayed by entering the keyword in the input box.
Please update to 3.0.1.
If you add a map field type to a custom content entity or custom field, the Deprecated function: unserialize() message is displayed when the data is output.
qiutuo → created an issue.
Please update to version 2.0.2.
An error was reported because the added field already has data and has not been deleted. The next step is to address this issue.
Please update to version 2.0.1 to solve all the above problems.
I also reproduced the above error in another scenario,
When I use the ECK module to create the content entity type, the above error is thrown after the entity type is deleted,
After using: 3052404-21.patch the following error occurs,
Symfony\Component\Routing\Exception\RouteNotFoundException: Route "entity.field_config.weixin_field_edit_form" does not exist. in Drupal\config_translation\ConfigNamesMapper->getBaseRoute() (line 209 of core/modules/config_translation/src/ConfigNamesMapper.php).
In fact, the entity type no longer exists, and the "entity.field_config.weixin_field_edit_form" route does not exist, but the prompt says that there is no such route.
I also reproduced the above error in another scenario,
When I use the ECK module to create the content entity type, the above error is thrown after the entity type is deleted,
After using: 3052404-21.patch the following error occurs,
Symfony\Component\Routing\Exception\RouteNotFoundException: Route "entity.field_config.weixin_field_edit_form" does not exist. in Drupal\config_translation\ConfigNamesMapper->getBaseRoute() (line 209 of core/modules/config_translation/src/ConfigNamesMapper.php).
In fact, the entity type no longer exists, and the "entity.field_config.weixin_field_edit_form" route does not exist, but the prompt says that there is no such route.
My understanding is that classification design can be done according to the data type, for example, user entities: name, gender, age can be placed in the base table.
For example, working experience: company name, business scope, entry time, position, departure time and many other fields, and there will definitely be multiple pieces of data, which requires the establishment of a new entity type, using entity references, Dynamic Entity Reference fields to achieve association, or It is a custom field to achieve.
For small and medium-sized projects, the impact on performance is actually not too great. For applications with millions or tens of millions of data, more advanced performance optimization solutions are needed.
Now popular micro-services can create multiple micro-application services based on application data types, and use APIs for data exchange, that the single-table approach is more clean and friendly.
Hello, Drupal is excellent and has given us a variety of solutions. Programmers are required to design according to project requirements. The Easy entity base field module can work together with the Field module in the core without affecting each other. Programmers can choose which fields belong to The base table or use an independent field table. For projects with a small amount of data, the Easy entity base field may be a good solution.
The original intention of the design is that my project needs a lot of data types. ECK has not been updated for a long time, so I designed a module that can easily create entity types. After creation, use Easy entity base field to add base fields, which solves unnecessary repetitive work.
When you remove the hook in step 1, the newly added entity reference field in the user entity should be removed synchronously, but this is not possible now,
After testing, the fields in the core, only the entity reference fields cannot be deleted,