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

EAV Attribute for Customer does not update - website scope issue #39591

Open
2 of 5 tasks
mc-christian opened this issue Jan 30, 2025 · 1 comment
Open
2 of 5 tasks

EAV Attribute for Customer does not update - website scope issue #39591

mc-christian opened this issue Jan 30, 2025 · 1 comment
Labels
Reported on 2.4.7-p3 Indicates original Magento version for the Issue report.

Comments

@mc-christian
Copy link

mc-christian commented Jan 30, 2025

Preconditions and environment

  • Magento version: 2.4.7-p3
  • Another website (e.g. Second Website) besides the Main Website.

Steps to reproduce

  1. Create a custom EAV attribute for the customer entity. There are many ways to do this, but here's Adobe's Add a custom text field attribute.
  2. Make sure the attribute appears: Admin Panel -> Customers -> All Customers -> Click "Edit" on any customer -> Select Account Information; the new attribute should be there.
  3. Populate the new attribute with anything and click Save and Continue Edit (this should work).
  4. On the Associate to Website dropdown select the "Second Website" and click Save and Continue Edit.
  5. Edit the new attribute once again, and click Save and Continue Edit.

Expected result

The new attribute updates its value.

Actual result

The new attribute maintains its previous value set with Main Website scope.

Additional information

Allowing for custom attributes is a basic but powerful feature, and this issue prevents custom attributes from working for customers belonging to any website other than the Main Website.

If it helps, on this Abobe article, it says that "The scope of the Customer custom attribute is Global only, while other entities support the Global, Website, and StoreView scopes." However, I found a reference to the new attribute on the table "customer_eav_attribute_website". I also tried removing the entry from that table but it doesn't fix the issue.

Release note

No response

Triage and priority

  • Severity: S0 - Affects critical data or functionality and leaves users without workaround.
  • Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
  • Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
  • Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
  • Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.
Copy link

m2-assistant bot commented Jan 30, 2025

Hi @mc-christian. 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.


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.

@github-project-automation github-project-automation bot moved this to Ready for Confirmation in Issue Confirmation and Triage Board Jan 31, 2025
@engcom-Bravo engcom-Bravo added the Reported on 2.4.7-p3 Indicates original Magento version for the Issue report. label Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Reported on 2.4.7-p3 Indicates original Magento version for the Issue report.
Projects
Status: Ready for Confirmation
Development

No branches or pull requests

2 participants