Optionally allow the quantity of product to be ordered to use a drop down select

Oops forgot to attach screenshot of select for quantity.

Yes definitively a choice for admin between textfield and select. If select - then we can either do a standard 0,1,2,3 or perhaps a min value, a max value and an interval? So then admin could make:

min value = 0
interval = 1
max value = 3

(would give you a select 0,1,2,3 #options)
Perhaps eg for pizza slices)

but equally possible to then configure:
min value = 0
interval = 10
max value = 100

(would give you a select 0,10,20,30...100)
Perhaps eg for raffle tickets

Or if admin wants more flexibility use the open ended textfield.

What do you think?

-- Karin

You mean there is a +1 added to your option values? Would you please attach a screen shot?

For your specific purpose do you think a config with a min, a max and an interval would work well?

The product is required - I believe that's why the user has to purchase at least 1. So 'unrequire' it - and check to see if you can select 0.

The product is required - I believe that's why the user has to purchase at least 1. So 'unrequire' it - and check to see if you can select 0.

Ah - I think John would appreciate it if you would file a new issue - re: js for 7.x-2.x branch. I'm going to stay focused on getting the select options to work for the 7.x-1.x

Ok, I've got things working.

The $form elements are:

  $form['extra']['choose_quantity_min'] = array(
    '#type' => 'textfield',
    '#size' => '6',
    '#title' => t('Minimum quantity:'),
    '#states' => array(
      'invisible' => array(
        ':input[name="extra[choose_quantity]"]' => array('checked' => FALSE))),
    '#default_value' => empty($component['extra']['choose_quantity_min']) ? 0 : $component['extra']['choose_quantity_min'],
    '#description' => t('Minimum quantity the user can select.'),
    '#weight' => 1,
  );
  $form['extra']['choose_quantity_max'] = array(
    '#type' => 'textfield',
    '#size' => '6',
    '#title' => t('Maximum quantity:'),
    '#states' => array(
      'invisible' => array(
        ':input[name="extra[choose_quantity]"]' => array('checked' => FALSE))),
    '#default_value' => empty($component['extra']['choose_quantity_max']) ? 0 : $component['extra']['choose_quantity_max'],
    '#description' => t('Maximum quantity the user can select. Leave at 0 if you would like to render a textfield instead of a select option.'),
    '#weight' => 2,
  );

and the foreach to render the webform elements changes to:

    foreach ($options as $product_id => $product_name) {

        if ($component['extra']['choose_quantity_max'] == '0'){
          $element[$product_id] = array(
            '#type' => 'textfield',
            '#title' => $product_name,
            '#title_display' => 'after',
            '#size' => 6,
            '#default_value' => isset($default_quantities[$product_id]) ? $default_quantities[$product_id] : 0,
            '#element_validate' => array('_webform_productfield_quantity_validate'),
            '#weight' => $component['weight'] + ('0.' . $i),
          );
        }
        elseif ($component['extra']['choose_quantity_max'] != '0'){
          $element[$product_id] = array(
            '#type' => 'select',
            '#options' => range($component['extra']['choose_quantity_min'], $component['extra']['choose_quantity_max']),
            '#title' => $product_name,
            '#title_display' => 'after',
            '#default_value' => isset($default_quantities[$product_id]) ? $default_quantities[$product_id] : 0,
            '#element_validate' => array('_webform_productfield_quantity_validate'),
            '#weight' => $component['weight'] + ('0.' . $i),
          );
        }
        $i++;
      }

In WEBFORM -> Form components:
So if you checkbox: Allow the user to set the quantity - the admin chooses a Min/Max (attached):

WEBFORM -> View:
And the user who orders will see either an open ended box or a limited number of select options (attached):

Questions: not sure about the "leave max at 0 to get a textfield rendering option" - but can't think of another way - at the moment. What do you think?

Here's a patch agains 7.x-1.0-beta6

My patch above needs to be amended - to ensure that options that don't start at minimum quantity = 0 will work properly.

        elseif ($component['extra']['choose_quantity_max'] != '0'){

         $myoptions = array();
          foreach (range($component['extra']['choose_quantity_min'], $component['extra']['choose_quantity_max']) as $mynumber) {
            $myoptions[$mynumber] = $mynumber;
          }

          $element[$product_id] = array(
            '#type' => 'select',
            '#options' => $myoptions,
            '#title' => $product_name,
            '#title_display' => 'after',
            '#default_value' => isset($default_quantities[$product_id]) ? $default_quantities[$product_id] : 0,
            '#element_validate' => array('_webform_productfield_quantity_validate'),
            '#weight' => $component['weight'] + ('0.' . $i),
          );
        }

If you like I can submit a new patch?

Sure - here it is. New patch against 7.x-1.x-dev - if you could review it that would be great.

Here's the patch.

Trying to trigger test bot visit.

Perhaps automated testing is not enabled for this project?

Thank you! I'll test this as well - likely over the weekend [together w/ the rewrite that will stop webform csv from producing notices to the dblog].

Hi - I've taken the patch from #21 and have applied it manually to version = "7.x-2.0-alpha3+11-dev"; Things have changed a bit (both line numbers and code wise) - but I got it working: producing a configurable min max option in the Webform element config and creating the select elements - for the end user. Will create/upload a new patch.

If you can give that patch a try and let me know if that works for you - that would be great. You may also need some CSS to help make things look nice.

Let me double check my patch.

Try this one - this is a diff -u with commerce_webform-7.x-2.x-dev/productfield.inc

What's your exact version - my diff is against:
version = "7.x-2.0-alpha3+11-dev"

Ah - try take the conditional out of play [for testing] - so that we can take this apart.

Ah good. But this is multiple is it not? In your case people can purchase multiple tickets (1 -> 10).

Yes I think the notices are related to the fact that you're using conditionals - as I don't see them when I order 2 slices of pizza.

I've done what you want to do - but without conditionals for the commerce product skus - in a nutshell:
- make a select element -> 1,2,3 etc (just integers)
- add the commerce product sku(s) of the products you want to sell to your webform
- add some javascript to your webform: it needs to do two things:
hide the commerce sku(s) from displaying (they will pop up in the cart)
for each commerce sku - set the quantity for your commerce sku to the value the user selected in the select element
- you can use conditionals for the address - etc (pop up as many address fieldsets as you need based on your select element value

Conditionals have not played well yet with commerce product skus - so I'm still doing it this way. For things like # adults, # students, make it a dinner theater yes/no; populate tickets -> for adult sku, student sku, dinner skus with the js -> and they all show up in the cart. With js you can react to when the user makes changes to the #

Example:

// Set the quantity of tickets SKUs - based on SHOW and NUMBER of Tickets Required
// 1. Hide the Fieldsets that contain the SKUs.
$('#webform-component-tickets--addamsfamily-saturday-march-14-7pm').hide();
...

$('#edit-submitted-tickets-number-of-tickets-adults').change(function() {
       $num_tickets_adults = $("#edit-submitted-tickets-number-of-tickets-adults").val();
       if($("#edit-submitted-tickets-dinner-theatre-confirm-1").is(':checked')) {
           $num_tickets_students = $("#edit-submitted-tickets-number-of-tickets-students").val();
           $total_tickets = parseInt($num_tickets_adults) + parseInt($num_tickets_students);
           // increase quantity of SKU:
           $("#edit-submitted-tickets-addamsfamily-saturday-march-14-7pm-addamsfamily-saturday-march-14-7pm-dinner-189").val($total_tickets);
           ...

Thanks for pushing this in John!