Attempted to create an instance of field with name field_d_ask_for_product on entity type node when the field storage does not exist

Created on 1 November 2022, over 2 years ago
Updated 26 June 2024, 10 months ago

I am getting the following error when freshly installing droopler 3.1.0 on a Linode live server for a new website. I used composer to get the code by running the following command:

composer create-project droptica/droopler-project <path> "^8.3.1"

The PHP version is 8.1.
The composer version is 2.4.4

mod_fcgid: stderr: Uncaught PHP Exception Drupal\\Core\\Field\\FieldException: "Attempted to create an instance of field with name field_d_ask_for_product on entity type node when the field storage does not exist." at /home/user/public_html/web/core/modules/field/src/Entity/FieldConfig.php line 315

Thereafter it used all the available real and virtual memory. I had to reboot the server.

Interestingly the same code installed successfully on my local development environment built upon Lando Lando

What could be wrong?

🐛 Bug report
Status

Active

Version

3.2

Component

Code

Created by

🇬🇧United Kingdom aanjaneyam

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇬🇧United Kingdom rajeevk London

    I tried installing this today with DDEV, and just after the installation, I got this error just after the install. I was trying to install the latest "3.2.0-rc1" version to test it locally. It was resolved after running the 'drush cr' once, as mentioned in the previous comment. Thanks

  • I had this error message when i created a new FiledType.
    I chose names for columns in the schema (example: this_is_an_example_schema_column_name) that were too long.
    When i wanted to create the field in the backend with name mycustom_options (example: field_mycustom_options) than i got that error.
    But when i created the field in the backend with name foo (field_foo) it worked.

    The reason for that was, that the field name and the column names i chose in my schema were combined in the database as column name.
    Example:
    - field_mycustom_options_this_is_an_example_schema_column_name
    - field_foo_this_is_an_example_schema_column_name

    so - the problem was, that the resulting column name was too long for drupals column name restrictions and drupal obviously refused to create the schema with that nice message.

    Solution for me was to shorten the column names in my Custom FieldType.

Production build 0.71.5 2024