- Issue created by @rmorelli
- 🇮🇹Italy rmorelli
Actual error is internal server error, ie a white page..
Here is the messagge in dblog
TypeError: Drupal\Core\Entity\Sql\DefaultTableMapping::requiresDedicatedTableStorage(): Argument #1 ($storage_definition) must be of type Drupal\Core\Field\FieldStorageDefinitionInterface, null given, called in /home/www/drupal10.3.1/web/core/lib/Drupal/Core/Entity/Sql/DefaultTableMapping.php on line 335 in Drupal\Core\Entity\Sql\DefaultTableMapping->requiresDedicatedTableStorage() (linea 525 di /home/www/drupal10.3.1/web/core/lib/Drupal/Core/Entity/Sql/DefaultTableMapping.php).
Would you please take these steps to ensure this issue gets attention?
- Update the issue summary above to include the exception message. That will more clearly explain the bug, as readers will not have to read comments to find essential information.
- Update the issue summary above with more detailed steps to reproduce from a clean Drupal install. In particular, explain exactly how to implement the custom entity type that is involved. Be sure to verify the steps yourself on a clean Drupal install.
- Remove the "Needs issue summary update" tag and change the issue status to "Active".
- 🇳🇿New Zealand quietone
Changes are made on on 11.x (our main development branch) first, and are then back ported as needed according to the Core change policies → .
- 🇨🇭Switzerland berdir Switzerland
Errors like this typically happens when doing an entity query on a non-existing field.
This is mixing terminology, is it now a content type or an entity type?
comment_entity_predelete(), which triggers the error, just does an entity query on entity id and entity type, that should absolutely not fail. It might be possible that your entity storage for comments is somehow messed up.
- 🇮🇹Italy rmorelli
@berdir you're right I've ended up commenting predelete
Entity storage for comments it's surely broken because I've deleted comment field...
Hopefully this week I'll have time to reproduce it on a fresh drupal installation