Closed (won't fix)
Project:
Commerce Core
Version:
7.x-1.x-dev
Component:
Product
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
17 Jan 2011 at 15:10 UTC
Updated:
25 May 2011 at 05:29 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
Bojhan commentedSomething like this.
Comment #2
rszrama commentedComment #3
rszrama commentedOne thought is we can use a GET parameter in the URL or something and use it to alter the field edit form so it has to be required and single value. On subsequent edits, users should be able to change these, but we can just have a general warning displayed that "field_x no longer qualifies as a product attribute field because you changed setting_y."
Comment #4
blup commentedHere's a github branch with a Product Attribute field. Let me know if it's ok.
https://github.com/blup/drupalcommerce/commit/accad6d6e005d08de49c408598...
Comment #5
pcambraComment #6
blup commentedThe previous branch was adding a product attribute field. As per discussion with rszrama, i'll try a new version using the existing list fields, with a 'product attribute' row in the 'manage fields' page (similar to Bohjan's mockup).
Comment #7
rszrama commentedThis still needs to be done, but I've added a separate issue for another aspect of this usability that needs to be improved: #1038320: Replace the "magic configuration" of attribute fields with explicit settings
Comment #8
rszrama commentedAs it turns out, the issue I linked in #7 above evolved from a simple bypass option to an explicit group of settings enabling a field as an attribute field and adjusting its representation on the Add to Cart form. As such, I don't think we need to pursue this particular issue any further. I've flagged #1038320: Replace the "magic configuration" of attribute fields with explicit settings for review at the upcoming UX sprint, but I believe it will be a better approach than the magic configuration w/ a separate "add field" row on the manage fields tab.