Missing option "type" for "color" field

Hi,

I’m adding a custom Product attribute to Product entity (table ‘oro_product’), and when I run the command ‘console oro:platform:update –force’ I get this error on “running full reindexation of website index” step:

Shell

> loading Oro\Bundle\MigrationBundle\Migration\UpdateDataFixturesFixture > running full reindexation of search index > running full reindexation of website index [Symfony\Component\Config\Definition\Exception\InvalidConfigurationException] Missing option "type" for "color" field oro:migration:data:load [--fixtures-type [FIXTURES-TYPE]] [--dry-run] [--bundles [BUNDLES]] [--exclude [EXCLUDE]] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-s|--shell] [--process-isolation] [-e|--env ENV] [--no-debug] [--disabled-listeners DISABLED-LISTENERS] [--current-user CURRENT-USER] [--current-organization CURRENT-ORGANIZATION] [--] <command>

1 2 3 4 5 6 7 8 9 10

> loading Oro\Bundle\MigrationBundle\Migration\UpdateDataFixturesFixture   > running full reindexation of search index   > running full reindexation of website index                                                                                      [Symfony\Component\Config\Definition\Exception\InvalidConfigurationException]     Missing option "type" for "color" field                                                                                                                            oro:migration:data:load [--fixtures-type [FIXTURES-TYPE]] [--dry-run] [--bundles [BUNDLES]] [--exclude [EXCLUDE]] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-s|--shell] [--process-isolation] [-e|--env ENV] [--no-debug] [--disabled-listeners DISABLED-LISTENERS] [--current-user CURRENT-USER] [--current-organization CURRENT-ORGANIZATION] [--] <command>

The way I’m adding my attribute is like:

PHP

// Add color $table->addColumn( 'color', Type::STRING, [ 'oro_options' => [ 'extend' => ['owner' => ExtendScope::OWNER_CUSTOM], 'datagrid' => ['is_visible' => DatagridScope::IS_VISIBLE_HIDDEN], 'view' => ['is_displayable' => true] ], 'notnull' => false, 'length' => 255, ] );

1 2 3 4 5 6 7 8 9 10 11 12 13 14

// Add color             $table->addColumn(                 'color',                 Type::STRING,                 [                     'oro_options' => [                         'extend' => ['owner' => ExtendScope::OWNER_CUSTOM],                         'datagrid' => ['is_visible' => DatagridScope::IS_VISIBLE_HIDDEN],                         'view' => ['is_displayable' => true]                     ],                     'notnull' => false,                     'length' => 255,                 ]             );

And

PHP

/** * @var array */ private const FIELDS = [ 'color' => [ 'searchable' => true, 'filterable' => true, 'filter_by' => 'fuzzy_search', 'enabled' => true, 'visible' => true ] ]; /** * {@inheritdoc} */ public function load(ObjectManager $manager) : void { $this->makeProductAttributes(self::FIELDS, ExtendScope::OWNER_CUSTOM); }

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20

/**      * @var array      */     private const FIELDS = [         'color' => [             'searchable' => true,             'filterable' => true,             'filter_by' => 'fuzzy_search',             'enabled' => true,             'visible' => true         ]     ];       /**      * {@inheritdoc}      */     public function load(ObjectManager $manager) : void     {         $this->makeProductAttributes(self::FIELDS, ExtendScope::OWNER_CUSTOM);     }

What option type is missing and how to set that option? Thanks.

Topic

[Ilya AntypenkoParticipant]

Hi nevoeiro,
Which version are you using?

It happens because you marked your field as “searchable”=>true.

New field should be added automatically to the search index since 2.5.

Could you please run

Shell

app/console cache:clear

1	app/console cache:clear

for your environment. And run migration load command again.

As a workaround try to add website search configuration for it.
Something like this:
https://github.com/oroinc/orocommerce/blob/632f0c19a2db01f7940c2e17621bf90534ff673a/src/Oro/Bundle/ProductBundle/Resources/config/oro/website_search.yml

E.g.

YAML

Oro\Bundle\ProductBundle\Entity\Product: fields: - name: color type: string

1 2 3 4 5

Oro\Bundle\ProductBundle\Entity\Product:     fields:         -             name: color             type: string

[nevoeiroParticipant]

Hi iantypenko,

I’m using platform 2.6 and commerce 1.6

What you mean with “New field should be added automatically to the search index”?
Don’t we need to add “searchable”=>true?
If I don’t add that, then the field isn’t searchable.

Regarding your suggestion if I clear cache and run the migration:load I don’t get the error. But I don’t want to run that, I mean I don’t want to have a error.

For the workaround I got this:

Shell

> Oro\Bundle\OrganizationProBundle\Migrations\Schema\UpdateConfigsWithOrganizationMigration > Oro\Bundle\EntityConfigBundle\Migration\WarmUpEntityConfigCacheMigration Loading permissions... [Symfony\Component\Config\Definition\Exception\InvalidConfigurationException] The value "string" is not allowed for path "mappings.Oro\Bundle\ProductBundle\Entity\Product.fields.color.type". Permissible values: "text", "decimal", "integer", "datetime" security:permission:configuration:load [--permissions [PERMISSIONS]] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-s|--shell] [--process-isolation] [-e|--env ENV] [--no-debug] [--disabled-listeners DISABLED-LISTENERS] [--current-user CURRENT-USER] [--current-organization CURRENT-ORGANIZATION] [--] <command>

1 2 3 4 5 6 7 8 9 10

> Oro\Bundle\OrganizationProBundle\Migrations\Schema\UpdateConfigsWithOrganizationMigration   > Oro\Bundle\EntityConfigBundle\Migration\WarmUpEntityConfigCacheMigration Loading permissions...                                                                                                                                                                                      [Symfony\Component\Config\Definition\Exception\InvalidConfigurationException]                                                                                                     The value "string" is not allowed for path "mappings.Oro\Bundle\ProductBundle\Entity\Product.fields.color.type". Permissible values: "text", "decimal", "integer", "datetime"                                                                                                                                                                                      security:permission:configuration:load [--permissions [PERMISSIONS]] [-h|--help] [-q|--quiet] [-v|vv|vvv|--verbose] [-V|--version] [--ansi] [--no-ansi] [-n|--no-interaction] [-s|--shell] [--process-isolation] [-e|--env ENV] [--no-debug] [--disabled-listeners DISABLED-LISTENERS] [--current-user CURRENT-USER] [--current-organization CURRENT-ORGANIZATION] [--] <command>

I changed ‘type:string’ by ‘type:text’ and it worked.

Is this the best approach to add a new searchable attribute? What is the best practice to add a searchable attribute programmatically without having that issue on migration load?
thanks

[vitaliyberdyloParticipant]

Hello, nevoeiro
I recheck you code on commerce 1.6.
Reindexing was successful without errors.
It looks like there really were some issues with your cache.
Adding field to website search configuration manually is not necessary.

But consider for reindexation working your attribute should be in attribute family.
https://github.com/oroinc/orocommerce/blob/1.6/src/Oro/Bundle/ProductBundle/EventListener/WebsiteSearchProductIndexerListener.php#L180-L182

[nevoeiroParticipant]

I couldn’t get it working on my side without your workaround. Attribute was added to default family on my migrations too.
If I back to this topic again I’ll post my finds.
Thanks.

[Author]

Replies