Attribute Quantities

Use case

You want a product where a user can order the graphic design of a brochure. The base cost is $200, plus $20 per page.

Old way:

Create selectboxes/options with hardcoded options e.g:

5 pages +$100
6 pages +$120
7 pages +$140
etc

I *believe* that was the old way, I don't know attributes, and I hope there isn't something I've missed with this like the old 'ohhh *thats* where that feature is'.

New way:
Create a "Quantity Grid" attribute type.
Set price = $20 (which means $20 * however much quantity is specified)

Patch Summary

This issue and solution is similar to what I needed for a project I'm doing.

See attached screenshots for functioning and attached patch for 2.4.

This is the first time I've used attributes at all, let alone getting deep into the attributes API. So I may have this way wrong.

1. Added to "Quantity Grid" type to attribute creation form
2. Created new element type quantity grid to mimic the checkboxes element type. Instead of expanding out to checkboxes, it expands out to textfields for entry of quantities for a particular attribute
3. Changed a few functions to add special conditions to account for the attribute type.
4. Adds theming function for the textfields used in the quantity grid (probably not actually necessary - but it's for my project, so it's in there)

The result of these changes is that a user can configure a product with options and quantities.

Hello mintsauce, I'm also interested on this feature, are you going to publish that module? thanks

After patching, cyrillic symbols in attribute options looks like a rhombus with question mark (in admin/store/orders/XX)
cyrillic names of attributes looks correctly

#1: 782154-attributes-quantities_1.patch queued for re-testing.

Testbot doesn't function properly yet on fixed-point releases like 6.x-2.4, so you can ignore the test failure. I suggest running the tests locally to make sure they still work after the patch.

I re-rolled the patch from #1 against 6.x-2.7 using git.

Status has to be set to "needs review" to get the bot to test the patch ...

Let's try on -dev.

#9: attributes_quantities-782154-9.patch queued for re-testing.

OK, those error seem to be genuine PHP Notices caused by your patch. The patch needs to be cleaned up so that the tests run green. You can run the tests locally on your site if you want - that makes it easier to debug. You do this by enabling the (Drupal core) SimpleTest module then going to admin/config/development/testing to start the tests.

@TR - thanks for the SimpleTest tips. Hadn't done that before. Don't really want to do that again on Drupal 6.x...what a mess. Since I applied the 6.x patch from the SimpleTest module, I get a large amount of "Notice: Undefined property: stdClass..." messages.

I made one change that fixed most of the PHP notices. Re-testing locally still says there are a few left. However, I can't find them. Turning on the verbose option for SimpleTest just increases the number of errors. I've been using xdebug during development, but I can't get it to work as expected with SimpleTest. Even after trying all the tips here http://drupal.org/node/30011

I attached my latest patch. I'm just spinning my wheels at this point unless somebody can point me in a constructive direction. Ugh...time to go back out of this SimpleTest mess.

Easy solution. You need to add the following line to your patch (in uc_attribute.module):

@@ -1142,6 +1236,7 @@ function _uc_cart_product_get_options($item) {
         else {
           // Handle textfield attributes.
           $options[$index] = array(
+            'display' => $attribute->display,
             'attribute' => $name,
             'aid' => $aid,
             'oid' => 0,

Can you roll a new patch with this included?

Updated patch attached.

@TR Thanks. How did you find that? Familiarity with the codebase or some special technique using SimpleTest?

@FranCarstens Yes, I saw and tried that module. However, it only supports one quantity value per attribute. The patch in this thread supports one quantity value per attribute *option*. Two very different things.

This looks awesome; are there plans to include it in ubercart core, or maybe 3.x core? Or should I patch the file manually?

-Josh

The patch in #20 wouldn't apply anymore, so I applied it to the 2.7 tag and then merged it into 6.x-2.x (the commit id at the time was a3b910b6). A quick test shows that it still seems to work.

Hi. Anyone converted this patch to Ubercart 7.x? I would very much like to use this in 7.x.

Hi All

We need converted this patch to Ubercart 7.x? can any one help us.

Please have look the patch and suggest those lines to be change to port in to d7 ubercart 3.

i am waiting for postive response from anyone(drupal master/experts).
Thanks

I would also be very interested in a D7 / UC3 patch - Subscribing

Patch applied against 6.x-2.x but attribute details do not show properly on order page. Attribute name is trimmed to its first character. Cart and Cart checkout seems to be working pretty well. It does not however on Checkout review and order details at the backend.

UPDATE: Anyone having the same problem: By using hook_product_description_alter(), you can alter product attributes anyway you want to.

Hi ivanatrix, I updated this patch code for drupal 7 with uc3 and it works fine.

subscribed

Arvind, Can you please provide the patch you created for Drupal 7

Sure I will provide you patch for drupal 7.

You can share Patch for Drupal 7 please

@arvind.kinja Please share your patch for D7

@arvind.kinja Please share your patch for D7. Thank you!

@arvind.kinja still no patch for 7.x-3.11?
figured it out with stock... thanks!

#30 : I tried this patch, the problem with striped option names can be fixed this way:

--+ : added code to delete
++ : replacement code

in uc_attribute_admin.inc, from patch #26

function theme_uc_product_attributes($element) {
+ $product = $element['#product']['#value'];
$option_rows = array();
-
foreach (element_children($element) as $key) {
$optionstr = '';

- foreach ((array)$element[$key]['#options'] as $option) {
+ foreach ((array)$element[$key]['#options'] as $option_key => $option) {
--+ $append = $option['name'];
++ $append = $option;
+
+ // Show quantity for grid
+ if ($element[$key]['#display'] == 4) {
+ $context['type'] = 'amount';
+ $context['subject']['node'] = $product;
+ $price_info = array(
+ 'price' => $element[$key]['#options'][$option_key]['price_each'],
+ 'qty' => 1,
+ );
+
--+ $append = t('@qty×', array('@qty' => $element[$key]['#options'][$option_key]['quantity'])) . ' ' . $option['name'] . ' (' . uc_price($price_info, $context) . ' ' . t('each') . ')';
++ $append = t('@qty×', array('@qty' => $element[$key]['#options'][$option_key]['quantity'])) . ' ' . $option . ' (' . uc_price($price_info, $context) . ' ' . t('each') . ')';
+ }
+
// We only need to allow translation from the second option onward
if (empty($optionstr)) {
- $optionstr .= $option;
+ $optionstr .= $append;
}
else {
- $optionstr .= t(', !option', array('!option' => $option));
+ $optionstr .= t(', !option', array('!option' => $append));
}
}
- $option_rows[$key] = t('@attribute: @option', array('@attribute' => $element[$key]['#attribute_name'], '@option' => $optionstr));
+ $option_rows[$key] = t('@attribute: !option', array('@attribute' => $element[$key]['#attribute_name'], '!option' => $optionstr));
}