Error please select field definition definitions root - Исправление ошибок и поиск оптимальных решений проблем

Forum Overview >> Editor

Category	Editor
Created	02.12.2016 06:52

Tony Price (brownthumb)	02.12.2016 07:08
if you have an empty mod map that has only 1 field in it’s field folder and you make many fields, how does one duplicate and set everything up so that the game recognize’s each field for it’s size, shape, price, and still have it’s missions?

Michael Hudson (Unknown)	02.12.2016 10:43
Edit: Duplicate Field01 in fields Folder, and rename Field02 and so on, you will have to set fieldMapIndicators for each field, and the fieldBuyTrigger. Then you will need set extra field dimensions. Duplicate corner01_1 and rename Corner02_1 then Corner02_2 and finally Corner02_3. In GE highlight Fields Folder then go to Menu/Scripts/FS17/Map and Toggle Render Field Areas, This will show your field areas. Also Set Field Sizes will calculate fields for you There is a good explanation here: http://fs-uk.com/forum/index.php?topic=187663.15

Michael Hudson (Unknown)

02.12.2016 10:43

Edit:
Duplicate Field01 in fields Folder, and rename Field02 and so on, you will have to set fieldMapIndicators for each field, and the fieldBuyTrigger.

Then you will need set extra field dimensions.
Duplicate corner01_1 and rename Corner02_1 then Corner02_2 and finally Corner02_3.

In GE highlight Fields Folder then go to Menu/Scripts/FS17/Map and Toggle Render Field Areas, This will show your field areas.
Also Set Field Sizes will calculate fields for you

There is a good explanation here: http://fs-uk.com/forum/index.php?topic=187663.15

Tony Price (brownthumb)	02.12.2016 13:50
tried setting up a simple 4 corner field, but when i highlight fields folder and toggle Render Fields Area and Set Field Sizes i get Error: Please select fieldDefinitions root!. if that means selecting the fieldDefinitions thing inside the folder for the field itself i tried that too with same results. what am i doing wrong?

Michael Hudson (Unknown)	02.12.2016 15:56
Have you brought your fields into map yet? Then you select fields transform group, sorry not Fields folder, then Toggle Render Field Areas

Tony Price (brownthumb)	03.12.2016 06:32
doesn’t matter what or how i do, still get the same error:…Error: Please select fieldDefinitions root!, have yet to find anything anywhere that can point me to the field Definition root, or what it means.

Bruce Hay (Stussy)	04.12.2016 03:01
I was having the same problem, however Michael’s reply did work, make sure you select the first level of fields on the Scenegraph, then toggle Render Fields, then Set Field Sizes, works a treat!

James Norred (Cajunwolf)	18.12.2016 14:46
bump

Douwe Kerstma (Unknown)	22.02.2017 19:37
still don’t work here. , first off… my english is not that good but i think i understand what i was supposed to do. if i try to render or set the field at the orginal maps in GE it works like it supposed to be. but in my own made map it still don’t work. i did do what micheal hudson told us. is there someone who can help me pleace?? , i’ve lost hours to try it all out and i don’t know what to do anymore

Douwe Kerstma (Unknown)

22.02.2017 19:37

still don’t work here.
, first off… my english is not that good but i think i understand what i was supposed to do.

if i try to render or set the field at the orginal maps in GE it works like it supposed to be.

but in my own made map it still don’t work.

i did do what micheal hudson told us.

is there someone who can help me pleace?? , i’ve lost hours to try it all out and i don’t know what to do anymore

Jonathan Monks (Unknown)	05.11.2017 14:05
I notice this is an old thread but as a solution has not been publicly posted I thought I would contribute. So I had a blank map that had no fields! I managed to get this working from ground zero (not even having a root ‘fields’ folder to begin with). I too encountered the dreaded ‘error:Please select fieldDefinitions root’ message. This is how I solved it. First I created a transform group called ‘fields’ (the root folder thats required for all fields). Then I exported/imported ‘field01’ from GoldCrest map and used that to border my field in the new map.(making sure field01 was put within the root group of course) However, to fix the error (and I will assume those that still encounter this even if they have the root folder selected will be for the same reason)… Because I had to create the root folder myself, when I compared it to the goldcrest ‘fields’ transform group, in the User Attributes, it has a script entry that you will need to also have set up in your blank/custom map. To do so, make sure the ‘user attributes’ window is open when you click ‘fields’ in your scenegraph. If you’ve created it by hand, or somethings gone wrong and the entry is missing, first: .select ‘script callback’ in the dropdown menu in ‘user attributes’. .in the textbox type ‘onCreate’ (minus quotations) .Click Add A new entry called OnCreate with a blank textbox beside it should have now appeared. In that blank text box copy paste the following: ‘FieldDefinition.onCreate’ (minus the quotations). Save your map! Now, when you highlight ‘fields’ and run the two scripts ‘set field sizes’ and ‘toggle render field areas’ they should now both execute without that error! Hope that helps any future encounters!

Jonathan Monks (Unknown)

05.11.2017 14:05

I notice this is an old thread but as a solution has not been publicly posted I thought I would contribute.

So I had a blank map that had no fields!
I managed to get this working from ground zero (not even having a root ‘fields’ folder to begin with).
I too encountered the dreaded ‘error:Please select fieldDefinitions root’ message.
This is how I solved it.

First I created a transform group called ‘fields’ (the root folder thats required for all fields).
Then I exported/imported ‘field01’ from GoldCrest map and used that to border my field in the new map.(making sure field01 was put within the root group of course)

However, to fix the error (and I will assume those that still encounter this even if they have the root folder selected will be for the same reason)…

Because I had to create the root folder myself, when I compared it to the goldcrest ‘fields’ transform group, in the User Attributes, it has a script entry that you will need to also have set up in your blank/custom map.

To do so, make sure the ‘user attributes’ window is open when you click ‘fields’ in your scenegraph.
If you’ve created it by hand, or somethings gone wrong and the entry is missing, first:

.select ‘script callback’ in the dropdown menu in ‘user attributes’.

.in the textbox type ‘onCreate’ (minus quotations)

.Click Add

A new entry called OnCreate with a blank textbox beside it should have now appeared.

In that blank text box copy paste the following: ‘FieldDefinition.onCreate’ (minus the quotations).
Save your map!

Now, when you highlight ‘fields’ and run the two scripts ‘set field sizes’ and ‘toggle render field areas’ they should now both execute without that error!

Hope that helps any future encounters!

Peter Du Pree (highdesert)	20.12.2017 03:31
@Jonathan Monks Thanks, Jonathan! Very good, concise explanation. Did the trick for me.

Peter Du Pree (highdesert)

20.12.2017 03:31

@Jonathan Monks

Thanks, Jonathan! Very good, concise explanation. Did the trick for me.

Note: Log in to post. Create a new account here.

Источник

By jjgw on 23 Jun 2019 at 17:13 UTC

I got this message in the status report after upgrading to drupal 8.7.3:

Content
The node.feeds_item field needs to be updated.
Taxonomy term
The taxonomy_term.field_illustratie field needs to be updated.

Note that prior to the upgrade
— node.feeds_item was not used or changed
— taxonomy_term.field_illustratie was created

None of these drush 8.1.1 commands could solve : drush cron / drush cr / drush updb / drush entity-updates

Comments

What else than drush entity

jjgw commented 24 June 2019 at 17:40

What else than drush entity-updates should I run?
The drush command returns just the same message as shown in the status report.

That seems unlikely? To

pobster commented 24 June 2019 at 18:00

That seems unlikely? To check … you’re running ONE of the following;

drush updatedb:status --entity-updates

drush entity:updates

You should receive output looking something along the lines of…

The following updates are pending:

node entity type :
The node.feeds_item field needs to be updated.

 Do you wish to run all pending updates? (yes/no) [yes]:
 > yes

 // Do you wish to run all pending updates?: yes.

 Finished performing updates

Are you maybe not saying «yes» to running the command? Is your drush being run as part of a CI job (and hence not passing -y?)

The outcome is the same!

jjgw commented 25 June 2019 at 06:14

The outcome is the same!
The drush commands you’re suggesting are for drush version 9.
So I ran the drush entity-version twice with the drush version 8.1.17 present on the server

[cur@www45 jan.site]$ drush updatedb:status —entity-updates
The drush command ‘updatedb:status’ could not be found. Run `drush cache-clear drush` to clear the commandfile cache if [error]
you have installed new extensions.
[cur@www45 jan.site]$ drush entity:updates
The drush command ‘entity:updates’ could not be found. Run `drush cache-clear drush` to clear the commandfile cache if [error]
you have installed new extensions.
[cur@www45 jan.site]$ drush version
Drush Version : 8.1.17

[cur@www45 jan.site]$ drush entity-updates
The following updates are pending:

node entity type :
The node.feeds_item field needs to be updated.
taxonomy_term entity type :
The taxonomy_term.field_illustratie field needs to be updated.
Do you wish to run all pending updates? (y/n): y
Cache rebuild complete. [ok]
Finished performing updates. [ok]
[cur@www45 jan.site]$ drush entity-updates
The following updates are pending:

node entity type :
The node.feeds_item field needs to be updated.
taxonomy_term entity type :
The taxonomy_term.field_illustratie field needs to be updated.
Do you wish to run all pending updates? (y/n): yes
Do you wish to run all pending updates? (y/n): y
Cache rebuild complete. [ok]
Finished performing updates. [ok]

Then, it’ll be throwing an

pobster commented 25 June 2019 at 17:26

Then, it’ll be throwing an error somewhere? Take a look in your dblog, your php error.log, your syslog even? It’ll be that something is mismatched and unable to be changed. One thing which springs to mind as being a blocker before (and isn’t guaranteed to be your issue) was an issue around the NOT NULL value being unable to be altered.

I’ve found this issue queue which may help you with being able to view what the expected and actual values are for the differences at least? https://www.drupal.org/project/file_entity/issues/2914935

Unfortunately I believe i am

jjgw commented 28 June 2019 at 12:52

Unfortunately I believe i am stuck because the drupal log files were deleted and i have no access on provider’s logfiles.
I now also notice quite late that the drush entity-updates command has been deprecated.
I don’t know if it has made the problem worse, anywhere it didn’t work.

Devel Entity Updates Question

elebrun commented 28 June 2019 at 20:34

I’m seeing that installing this to run drush entup is the solution to upgrading to 8.7.3 with entity mismatches in regards to taxonomy, but this isn’t supposed to be run in production, correct? Are people running this in production to resolve this problem anyway?

I get this too

tjtj commented 3 February 2020 at 18:48

./drush entity:updates
The following updates are pending:

node entity type :
The node.feeds_item field needs to be uninstalled.

Do you wish to run all pending updates? (yes/no) [yes]:
> yes

In Connection.php line 695:

SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘mydb.node__feeds_item’ doesn’t exist: UPDATE {node__feeds_item} SET deleted=:db_update_placeholder_0; Array
(
[:db_update_placeholder_0] => 1
)

In Statement.php line 59:

SQLSTATE[42S02]: Base table or view not found: 1146 Table ‘mydb.node__feeds_item’ doesn’t exist

So how do I fix this?

Hello,

Pozi commented 2 March 2020 at 14:13

Hello,

i don’t know if this is a proper way fo solving this issue but i solved the same error with my custom module DB schema table install.

Probably due to some sort of error module schema was not installed. You need to find table schema definition in contrib module that you use (should be placed in a root if module in *.install file) and make copy&paste into your module hook update of table schema definition.

Your module part should be done as described here: https://www.drupal.org/docs/8/api/update-api/updating-database-schema-andor-data-in-drupal-8

Good luck!

I get an error message

tjtj commented 20 May 2020 at 16:59

./dr entity:updates
The following updates are pending:

block_content entity type :
The Custom block ID field needs to be updated.
The Revision ID field needs to be updated.
comment entity type :
The Comment ID field needs to be updated.
crop entity type :
The Crop ID field needs to be updated.
The Revision ID field needs to be updated.
feeds_feed entity type :
The Feed ID field needs to be updated.
feeds_subscription entity type :
The Feed ID field needs to be updated.
file entity type :
The File ID field needs to be updated.
media entity type :
The ID field needs to be updated.
The Revision ID field needs to be updated.
node entity type :
The ID field needs to be updated.
The Revision ID field needs to be updated.
paragraph entity type :
The ID field needs to be updated.
The Revision ID field needs to be updated.
path_alias entity type :
The ID field needs to be updated.
The Revision ID field needs to be updated.
payment entity type :
The Payment ID field needs to be updated.
shortcut entity type :
The ID field needs to be updated.
taxonomy_term entity type :
The Term ID field needs to be updated.
The Revision ID field needs to be updated.
webform_submission entity type :
The Submission ID field needs to be updated.
menu_link_content entity type :
The Entity ID field needs to be updated.
The Revision ID field needs to be updated.

Do you wish to run all pending updates? (yes/no) [yes]:
> yes

In SqlContentEntityStorageSchema.php line 1870:

The SQL storage cannot change the schema for an existing field (id in block_content entity) with data.

You can comment out several

geles commented 27 November 2021 at 13:04

You can comment out several line in SqlContentEntityStorageSchema.php as

// if ($this->hasColumnChanges($storage_definition, $original)) {
// throw new FieldStorageDefinitionUpdateForbiddenException(‘The SQL storage cannot change the schema for an existing field (‘ . $storage_definition->getName() . ‘ in ‘ . $storage_definition->getTargetEntityTypeId() . ‘ entity) with data.’);
// }

Worked for me

Thanks! This simple solution worked for me for some configurable fields (tax_rate, profile).

Worked for me too

gbirch commented 25 September 2020 at 14:05

Worked for me too. Date field changed from datetime to pure date.

Giles Birch
Tech-Tamer, LLC

Thanks a million! This

joegl commented 2 September 2021 at 22:26

Thanks a million! This resolved it for us.

Just a note — we had to save the «storage settings» for the field, which is on a different edit tab than the main edit tab.

surprisingly it worked

i tried running the command drush entity:updates and this promted the following error:

Drupal removed its automatic entity-updates API in 8.7. See https://www.drupal.org/node/3034742.

Then I followed your suggestion but I needed to edit both EDUT and FIELD SETTINGS tab under the field to get this solved.

This was the simplest

newswatch commented 28 March 2022 at 11:14

This was the simplest solution offered. And it worked like a charm.

[Database error notifications always have me worred :/]

D9: This only removed statues

alaama commented 31 July 2022 at 23:34

D9: This only removed statues error in /reports/status but:

— I’v had some fields somehow translated to ‘es’ (ex: Title->Título) and other UI strings (URL Alias -> ALIAS DE URL) which did not updated back to ‘en’.

— Did not solve Mismatched field translation such as this one

Does not work if the field

arnoldbird commented 7 December 2022 at 21:42

Does not work if the field contains data:

In SqlContentEntityStorageSchema.php line 1756:

The SQL storage cannot change the schema for an existing field (field_profile_phone in node entity) with data.

Lifesaver — thank you

nattyweb commented 18 May 2021 at 11:40

Superb support — thank you — worked for me with «user.field_mailchimp_subscribe field needs to be updated». Drupal 8.9.15.

This Post

chrisjames commented 5 December 2021 at 12:50

After a core upgrade, we started getting «Mismatched entity and/or field definitions» errors, as well as database out of date errors in our Drupal instance.

It’s unclear which core upgrade it was.

We had 5 fields marked as mismatched in the Status Report error section.

Despite multiple attempts at the drush entup command and confirmation that the command was successful, the status report still showed the errors.

These errors all had something to do with paragraphs and viewfields (paragraph.pg hp vf blogs being one of them).

We tried the following process with Drupal Core 8.8.8 and Drush 8.3.2, and it finally fixed the errors outside of the drush command.

We simply clicked «Save Field Settings» from the administrative menu, Structure -> Paragraph Types -> Home Page Blog List -> Manage Fields, under machine name ‘field pg hp vf blogs’ and Field Type ‘ViewField’.

In four of the five cases, there was no data in the field, and in one case, there was no data at all.

I can confirm the above

Belba commented 13 July 2022 at 07:26

I can confirm the above. Had the error with a paragraphg field. Only re-saving the field settings, despite the warning that data already exists for the field, was the solution to make the error message disappear.

Drupal 9.4

Solved my problem, D9

radziaziz commented 12 August 2022 at 07:27

Thanks for the solution man!
In my case i use the same field (field type = entity referece) in 2 content type. Initally i set the field to accept unlimited value, then change it back to only allow 1 value. However i only change the settings at 1 of the content type, thinking that the settings will be copied at the 2nd. So the solution to just update (by click the Save field settings button) made sense, and most importantly it works!

Same issue

jbaum_13 commented 27 September 2022 at 12:39

We ran into the same issue and resaving the fields for the taxonomy term removed the entity mismatch errors.

Источник

Updating modules in Drupal 8 is similar to updating modules in Drupal 7 — the drush pm-update (drush up) command still works, but there’s a new «gotcha» that you need to look out for when updating modules that work with entities.

Sometimes, after updating modules that interact with entities, you’ll see a «Entity/field definitions: Mismatched entity and/or field definitions» error on your site’s status report (admin/reports/status).

In the screenshot above, this error was generated by updating the Inline Entity Form module from its alpha4 version to the most recent -dev version (the site also uses the Scheduled Updates module). As long as a mismatch is present, the fields listed in the error will lead to unpredictable results.

Neither rebuilding caches nor running cron will fix this issue («drush up» doesn’t automatically run this command either) — for these types of errors, the drush entity-updates command is what you’re looking for.

Once this command is run, your status report will look something like this:

This is just one more reason why checking your site’s status report page after updating modules is always a good idea.

Comments

Any non-drush method?

I’ve indeed run into this problem with pathauto in Drupal 8. However, I’m developing in a Windows environment. Is there a way to resolve these mismatch situations without the use of drush?

Non drush method

If you don’t have Drush for drupal 8, please add the following script written on this page before $response->send(); in index.php file.

Why no UI

Hi Mike, this is great, and I have no problem using drush, but it seems to me as a matter of principle that there should be a file like update.php to run to fix these issues. I have been Googling around all morning and can’t seem to find any info where this is being contemplated.

Источник

Comments

What else than drush entity

That seems unlikely? To

The outcome is the same!

Then, it’ll be throwing an

Unfortunately I believe i am

Devel Entity Updates Question

I get this too

Hello,

I get an error message

You can comment out several

Other possible solution

Worked for me

Worked for me too

Thanks a million! This

surprisingly it worked

This was the simplest

D9: This only removed statues

Does not work if the field

Lifesaver — thank you

This Post

I can confirm the above

Solved my problem, D9

Same issue

Comments

Any non-drush method?

Non drush method

Why no UI