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

[Post-Multi-Variation-Support] Handle Attribute/Option Sync by Using IDs Instead of Names #254

Open
faisal-alvi opened this issue Dec 6, 2024 · 0 comments
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc.

Comments

@faisal-alvi
Copy link
Member

faisal-alvi commented Dec 6, 2024

  1. If a merchant changes the slug or name of an attribute in WooCommerce or renames a dynamic option in Square, a new option/attribute is created instead of updating the existing one in the next sync.
  2. If a merchant creates custom attributes with names identical to existing taxonomy attributes, it results in issues during import/sync. Products using the same-named custom attribute are updated (replaced) incorrectly with the taxonomy attributes.

Explore a way to track options/attributes by their ID instead of their name. A team discussion would be required to evaluate the importance and feasibility of this enhancement. Implement this improvement only if the need is established and prioritized during a healthy discussion.

It’s not mandatory to use IDs instead of names. Names are functional and easier to manage. Even WordPress core uses names for retrieving taxonomy details, so handling syncs using names is still a valid approach. However, I felt it was worth creating the ticket for potential future enhancements.

@faisal-alvi faisal-alvi added the priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc. label Dec 6, 2024
@faisal-alvi faisal-alvi added this to the Future Release milestone Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: low The issue/PR is low priority—not many people are affected or there’s a workaround, etc.
Projects
None yet
Development

No branches or pull requests

1 participant