What are the Slack Archives?

It’s a history of our time together in the Slack Community! There’s a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.

Because this space is not active, you won’t be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..

what about this one? ```Symfony \ Component \ OptionsResolver \ Exception \ UndefinedOptionsExceptio

UK7TM6CQJ
UK7TM6CQJ Posts: 123 πŸ§‘πŸ»β€πŸš€ - Cadet

what about this one? ```
Symfony \ Component \ OptionsResolver \ Exception \ UndefinedOptionsException
The option "choices_as_values" does not exist. Defined options are: "action", "allow_extra_fields", "allow_file_upload", "attr", "auto_initialize", "block_name", "by_reference", "choice_attr", "choice_label", "choice_loader", "choice_name", "choice_translation_domain", "choice_value", "choices", "compound", "constraints", "csrf_field_name", "csrf_message", "csrf_protection", "csrf_token_id", "csrf_token_manager", "data", "data_class", "disabled", "empty_data", "error_bubbling", "error_mapping", "expanded", "extra_fields_message", "group_by", "help", "help_attr", "inherit_data", "invalid_message", "invalid_message_parameters", "label", "label_attr", "label_format", "mapped", "method", "multiple", "placeholder", "post_max_size_message", "preferred_choices", "property_path", "required", "tags", "translation_domain", "trim", "upload_max_size_message", "validation_groups".

```

Comments

  • UKHR9UN00
    UKHR9UN00 Posts: 70 πŸ§‘πŸ»β€πŸš€ - Cadet

    You probably have to update the spryker module that causes this Exception. choices_as_values was deprecated.

  • UK7TM6CQJ
    UK7TM6CQJ Posts: 123 πŸ§‘πŸ»β€πŸš€ - Cadet

    spryker/product-management?

  • UKHR9UN00
    UKHR9UN00 Posts: 70 πŸ§‘πŸ»β€πŸš€ - Cadet

    You have to check your stacktrace to find the broken module. There are several modules using symfony forms.

  • UK7TM6CQJ
    UK7TM6CQJ Posts: 123 πŸ§‘πŸ»β€πŸš€ - Cadet

    that seems like, updates and issue is still there

  • UKHR9UN00
    UKHR9UN00 Posts: 70 πŸ§‘πŸ»β€πŸš€ - Cadet
  • UK7TM6CQJ
    UK7TM6CQJ Posts: 123 πŸ§‘πŸ»β€πŸš€ - Cadet
    vagrant@vm-mytheresa ➜  current git:(master) βœ—  composer show -i | grep spryker/product-management
    You are using the deprecated option "installed". Only installed packages are shown by default now. The --all option can be used to show all packages.
    spryker/product-management                                    0.18.8             ProductManagement module
    spryker/product-management-extension                          1.3.0              ProductManagementExtension module
    
  • UKHR9UN00
    UKHR9UN00 Posts: 70 πŸ§‘πŸ»β€πŸš€ - Cadet

    In that case I'd suggest to open a bug report at https://support.spryker.com/hc/en-us

  • UK7TM6CQJ
    UK7TM6CQJ Posts: 123 πŸ§‘πŸ»β€πŸš€ - Cadet

    remove usages of bug/NONE-fix-zed-interface

  • UK7TM6CQJ
    UK7TM6CQJ Posts: 123 πŸ§‘πŸ»β€πŸš€ - Cadet

    fixed usages and updated the package

  • UK5DS29L2
    UK5DS29L2 Posts: 546 πŸ§‘πŸ»β€πŸš€ - Cadet

    I know we had to:

    • update composer packages
    • fix files in src/Pyz
  • UK5DS29L2
    UK5DS29L2 Posts: 546 πŸ§‘πŸ»β€πŸš€ - Cadet

    and then we got rid of the probiem

  • UK5DS29L2
    UK5DS29L2 Posts: 546 πŸ§‘πŸ»β€πŸš€ - Cadet

    I have used spryker-shop/suite as a source for comparison

  • UK5DS29L2
    UK5DS29L2 Posts: 546 πŸ§‘πŸ»β€πŸš€ - Cadet

    then compared our repo with shop suite

  • UK7TM6CQJ
    UK7TM6CQJ Posts: 123 πŸ§‘πŸ»β€πŸš€ - Cadet

    did that too