Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Cloud] Problem with multiselect customer attributes #37189

Closed
github-jira-sync-bot opened this issue Mar 10, 2023 · 4 comments
Closed

[Cloud] Problem with multiselect customer attributes #37189

github-jira-sync-bot opened this issue Mar 10, 2023 · 4 comments
Labels
Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S1 Affects critical data or functionality and forces users to employ a workaround.

Comments

@github-jira-sync-bot
Copy link

github-jira-sync-bot commented Mar 10, 2023

ISSUE
Problem with multi-select attribute.

STEPS TO REPRODUCE

  1. Create a new multi-select customer attribute by setting few options(enable values required to Yes and show on storefront to Yes, set < Customer registration ] form )
  2. Load the customer registration form from the frontend

EXPECTED RESULT
Customer registration form load without any issue.

ACTUAL RESULT
Customer registration doesn't load. The following error triggered in exception log.

[2023-03-05T05:57:40.032602+00:00> report.CRITICAL: Exception: Deprecated Functionality: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /magento2ee/app/code/Magento/CustomAttributeManagement/Block/Form/Renderer/Multiselect.php on line 53 in /lib/internal/Magento/Framework/App/ErrorHandler.php:62
@github-jira-sync-bot github-jira-sync-bot added Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: PR in progress Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S1 Affects critical data or functionality and forces users to employ a workaround. labels Mar 10, 2023
@github-jira-sync-bot
Copy link
Author

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1717

@m2-assistant
Copy link

m2-assistant bot commented Mar 10, 2023

Hi @github-jira-sync-bot. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:


Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

@m2-community-project m2-community-project bot added this to Ready for Development in Low Priority Backlog Mar 10, 2023
@m2-community-project m2-community-project bot moved this from Ready for Development to Pull Request In Progress in Low Priority Backlog Mar 10, 2023
@chittima
Copy link
Contributor

Internal team is working on this issue

@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Ready for Development in Low Priority Backlog Mar 14, 2023
@m2-community-project m2-community-project bot moved this from Ready for Development to Pull Request In Progress in Low Priority Backlog Mar 17, 2023
@m2-community-project m2-community-project bot moved this from Ready for Development to Pull Request In Progress in Low Priority Backlog Mar 17, 2023
@m2-community-project m2-community-project bot moved this from Pull Request In Progress to Done in Low Priority Backlog Apr 14, 2023
@chittima
Copy link
Contributor

chittima commented Sep 8, 2023

Closed since it not community edition functionality

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Evaluated Issue: Confirmed Gate 3 Passed. Manual verification of the issue completed. Issue is confirmed Priority: P3 May be fixed according to the position in the backlog. Progress: done Reproduced on 2.4.x The issue has been reproduced on latest 2.4-develop branch Severity: S1 Affects critical data or functionality and forces users to employ a workaround.
Projects
Development

No branches or pull requests

2 participants