Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hey guys,
when I have required attribute, uc option image doesn't work correct.
Can you look on it?
Thanks
yannick
Comment | File | Size | Author |
---|---|---|---|
#7 | ucoi-required-attributes-907966-7.patch | 1.9 KB | stewart.adam |
Comments
Comment #1
joelstein CreditAttribution: joelstein commentedI can confirm the same issue. Making the attribute not-required fixes the bug, and then the images show. Is this perhaps a problem with the way Ubercart deals with required attributes?
Comment #2
Rar9 CreditAttribution: Rar9 commented+1 didn´t it used to work?
Comment #3
storytellerjeff CreditAttribution: storytellerjeff commentedSubscribing - It did used to work. I've got the same problem. As soon as I make an Attribute required - the images don't show up.
Comment #4
AllyMediaGroup CreditAttribution: AllyMediaGroup commentedConfirm, I disabled required attribute and the first image shows up, but the image does not change when selecting different selection, in either radio buttons, or select field.
Comment #5
yannickooMy problem is that my option (color) jumps to the first (white) but the option image isn't shown up.
I cannot understand why the module selects the first element via js.
Please let us bring the module forward :c
Comment #6
OriginalSauce CreditAttribution: OriginalSauce commentedIs there a way around this to make this work with setting the required field?
Comment #7
stewart.adam CreditAttribution: stewart.adam commentedAttached patch fixes the issue with required attributes.
Comment #8
matthandThe patch is not applying for me on the dev release from July 12, 2011. What dev are you using with this patch? Thanks for the help!
Comment #9
stewart.adam CreditAttribution: stewart.adam commentedThe patch was against git, 6.x dev branch.
Comment #10
matthandThe current dev version on git is what I attempted to patch as well. Has something changed since your patch was made?
Comment #11
stewart.adam CreditAttribution: stewart.adam commentedIt doesn't look like they have made any commits lately but I was developing this patch after I had patched a few other issues so the line numbers may be off a bit. I just re-tested after a fresh checkout and it applies cleanly on git branch 6.x-1.x with fuzz enabled: