Installing custom installation profile with few features causes installation to crush.

>  // You are about to DROP all tables in your 'drupal8_mdb_dev' database. Do you want to continue?: yes.                                                     
> 
>  [notice] Starting Drupal installation. This takes a while.
> 
> In SerializedColumnNormalizerTrait.php line 36:
>                                                                                
>   The generic FieldItemNormalizer cannot denormalize string values for "value" properties of the "behavior_settings" field (field item class: Drupal\Core\Field\Plugin\Field\FieldType\StringLongItem).

Comments

VladimirAus created an issue. See original summary.

berdir’s picture

berdir
Primary language German
Location Switzerland
commented
Category: Bug report » Support request
Priority: Major » Normal
Status: Active » Fixed

This change was required for the security fix. You need to re-export your default content. (Install old version, update, export).

berdir’s picture

berdir
Primary language German
Location Switzerland
commented

If you are not using behaviors, e.g. the value is "a:0:{}", you can also remove the whole field from the default content.

vladimiraus’s picture

vladimiraus
Primary language English
Location Brisbane 🇦🇺
commented

Thanks @berdir. Just found it myself. The solution was to remove the following lines from default_content

    "behavior_settings": [
        {
            "value": "a:0:{}"
        }
    ],
damienmckenna’s picture

damienmckenna
Location TN, USA
commented

Might it be worth noting this in the release notes?

jurriaanroelofs’s picture

jurriaanroelofs commented

Can you point out the changes that fixed the problem for paragraphs please? or documentation about how to update your module for the changes. I'm asking because my demo content is crashing installation profiles that are using the same field settings storage design, in the Formatter Field module ( https://www.drupal.org/project/formatter_field )

Simply updating core and re-exporting the default content does not solve the problem, so I'm guessing we need to patch the Formatter Field module somewhere.

jurriaanroelofs’s picture

jurriaanroelofs commented

Ok I found documentation for the Drupal core patch that explains what new property to add to your entity. In case anyone else needs it: https://www.drupal.org/files/issues/2019-02-20/3034584-2.patch

"serialized_field_property_names"

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.