Attempt to create a field storage with an name longer than 32 characters

Created on 6 February 2023, almost 2 years ago

Updated 8 February 2023, almost 2 years ago

Problem/Motivation

Creating new media type using the custom providers bucket as a source could result into the error:
Attempt to create a field storage with an name longer than 32 characters

Steps to reproduce

1. Install oEmbed Providers module.
2. Create provider bucket with not really long machine name, i.e. video_providers
3. Try to create new Media Type using the newly created bucket.
4. See the error: Drupal\Core\Field\FieldException: Attempt to create a field storage with an name longer than 32 characters: field_media_oembed_video_providers in Drupal\field\Entity\FieldStorageConfig->preSaveNew() (line 326 of /var/www/html/docroot/core/modules/field/src/Entity/FieldStorageConfig.php).

Proposed resolution

Restrict possible length for the name of the provider bucket or cut the machine name of the related field to 32 chars (field_media_oembed_video_providers in example above)

🐛 Bug report

Status

Closed: duplicate

Version

2.1

Component

Code

Created by

🇵🇱Poland nsavitsky

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @nsavitsky
Status changed to Closed: duplicate almost 2 years ago12:41am 8 February 2023
Comment almost 2 years ago →
🇺🇸United States Chris Burge
@nsavitsky - Thanks for filing this bug report. It's a core bug: 🐛 MediaSourceBase::getSourceFieldName() doesn't check character max Needs work . On a prior bug report for the oEmbed Providers module ( #3267697: Provider buckets with names 14 characters or longer can't be used as media sources → ), we added documentation in the README about character length.

I'm going to go ahead and close this as a duplicate, but I'd encourage you to look at the most recent patch on 🐛 MediaSourceBase::getSourceFieldName() doesn't check character max Needs work .

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024