Report on Webform and Attribute Data

There's currently no way to see them on one screen, this would be a fuller implementation that we're doing right now.

I'd suggest jumping over there and asking. I got the impression he was just suggesting it was possible, not that he was doing it.

While it's possible to do that, I honestly don't see this module having a long enough life in D6 for that development to happen since Commerce module is the future.

Here's what we did:

The concept is to create hidden webform fields that will store attribute values. The data is saved in UC and in webfrom hidden fields at the same time. This means you have to create a hidden field in the webform for each attribute and name it after the attribute label.

We modified the UC event registration module - added a piece of code that reads attributes and on submit looks for form elements with names that match the attribute labels.

We also needed to use Quantity on some attributes and we had to modify the UC Quantity to make it work. The ajax price box from this module also didn't work for us, we commented them out so they don't interfere with our custom solution.

To store the Quantity in webform you create a hidden field for each option and name it [attribute label]|[option label].

Additional benefit was that with this approach we could intersperse attributes with webform fields - by making them all attributes without price and adding the matching hidden webform fields. Before the change webform fields would always be rendered first and then came the attributes. We needed some extra information that is not price related but the information is related to an attribute so we needed some kind of visual proximity between them.

Basically your solution is the same only we use PHP to do the matching and saving, it's not as hard-coded as your solution and it should always work (doesn't depend on js).

We're not happy with our solution, ideally UC event registration module would automatically create hidden fields, connecting attributes with correct webform fields is tricky when done manually. Maybe another tab should be added to the paid event CT that allows you to choose which attributes to make available inside the webform (defaults to all.)

This is just a quick reply because I don't have time now to elaborate. Does this answer your question? Do you have any suggestions or more questions?

@portulaca How did you manage to do this? I'm looking to do the same thing, but according to this (http://drupal.org/node/288199) you have to put the $form['#submit'][] = 'uc_event_registration_client_submit'; in between the two existing submit calls in webform.module: $form['#submit'] = array('webform_client_form_pages', 'webform_client_form_submit');

If you do that, you can populate hidden fields and they show up in the table -- but your forms don't get added to the cart, at least if they're multi-paged forms. Single page forms do get added but the visitor then has to go to their cart, the form doesn't redirect them.

Never mind, I figured it out -- just do a db_query. If anyone else is interested in this and needs more details, here's what I did. I'm not done, as I'm still having problems with radio button attributes and I haven't sorted out text inputs at all, but it's a start:

<?php
// Handle attributes
  if (isset($form_state['values']['uc_event_registration_attributes'])) {
    $attrs = $form_state['values']['uc_event_registration_attributes'];
	
	//cycle the attributes looking for matching hidden webform fields to populate
	foreach($attrs as $aid => $value){
	  $field_name = $form['uc_event_registration_attributes'][$aid]['#title'];
	  foreach($form_state['webform']['component_tree']['children'] as $comp){
		if($field_name == $comp['name']){
		  //get cid
		  $cid = $comp['cid'];
		  //identify field type
		  switch($form['uc_event_registration_attributes'][$aid]['#type']){
		    //select options
			case 'select':
			case 'radios':
			  //get the option value
		      foreach($form['uc_event_registration_attributes'][$aid]['#options'] as $opt_key =>$opt_value){
				//if the key matches, save the value
				if($value == $opt_key){
				  $attr_value = $opt_value;
				  break;
				}
			  }
		  }
		}
	  }
	  //update the record in the database
	  $sid = $form_state['values']['details']['sid'];
	  db_query("UPDATE {webform_submitted_data} SET data = '%s' WHERE cid = %d AND sid = %d", $attr_value, $cid, $sid);
	}?>

Hi @Saoirse1916,

Can you show all the steps you did to get this working, I just cant seem to get it. Do you create the hidden fields within the webform tab in the drupal ui or in the webform module.

I just cant seem to wrap my head around it.

Thanks in advance

Yes, I just created hidden fields using the Webform UI -- the trick is that they have to match the attribute names exactly. Then the code I posted above runs through the list of webform fields looking for matches and updates the values with what was submitted in attributes. Then you can query all the fields either through the basic Webform reports or through a View using MySQL Views and a few other modules.

It's not exactly an ideal situation as was posted before. You're doubling your efforts if you have attributes that you want to report on -- but it does work.

I found a bug in my method, which is that if the user saves a draft of their webform or hits the Previous Page button on a multi-page form, it doesn't update the attributes properly (or throws an error). The reason is because on an update there is no $form_state['webform']['component_tree']['children']; rather, the correct array is $form_state['storage']['component_tree']['children'].

So to handle this you will need to do an if(isset($form_state['webform']['component_tree']['children'])){ and a corresponding }elseif(isset($form_state['storage']['component_tree']['children'])){ check to see what you're dealing with.

Hope this helps someone!

One more update, in case anyone's using this method. It was all working fine for me for a few weeks at which point we updated several modules, Webform among them. After the round of updates, it turned out that something would delete and then re-save every webform component but it would not update the hidden fields that I used to save attributes, presumably because they are hidden. Something now calls the function webform_submission_update -- I don't think Webform itself is to blame since I looked back through old versions of the module and nothing changed in that function -- but when it's called everything gets wiped out.

So, the solution is to move the attribute/hidden fields updating routine to the conditional actions file and have it called once the order is paid. I expanded the uc_event_registration.ca.inc file to add in a few other conditional actions that send a confirmation, add in the order number, final price, etc. Here's what I did:

<?php
// Update the webform with the order number, price, coupon, and rate adjustment
function uc_event_registration_update_order(&$order, $settings) {
  
  if(isset($order->data['coupon'])){
	$coupon = $order->data['coupon'];
  }else{
    $coupon = 'None';
  }
  if(isset($order->data['rateadjustment'])){
	$rateadjustment = $order->data['rateadjustment'];
  }else{
    $rateadjustment = 'None';
  }
  if($coupon != 'None' || $rateadjustment != 'None'){
    if(isset($order->order_total)){
	  $ordertotal = $order->order_total;
    }else{
	  $ordertotal = '';
    }
  }else{
	$ordertotal = '';
  }
  foreach ($order->products as $theproduct) {
	$orderid = $theproduct->order_id;
	if($ordertotal == ''){
	  $ordertotal = $theproduct->price;
	}
    $sid = $theproduct->data['uc_event_registration']['sid'];
	
	// Get the order comments and associated cid
	$result = db_query("SELECT cid FROM {webform_component} WHERE nid = %d AND form_key = '%s'", $theproduct->nid, 'uc_event_registration_order_comments');
	if (count($result) > 0) {
	  $getcid = db_fetch_array($result);
	}
	$result = db_query("SELECT message FROM {uc_order_comments} WHERE order_id = %d", $order->order_id);
	if (count($result) > 0) {
	  $getcomments = db_fetch_array($result);
	}
	if ($getcomments){
	  $comment_cid = $getcid['cid'];
	  $comments = $getcomments['message'];
	}else{
	  $comments = false;
	}
	
	// Update all attributes -- use a db_query to find a matching field name and get the cid
	if (isset($theproduct->data['attributes'])) {
	  $attribs = array_keys($theproduct->data['attributes']);
	  foreach($attribs as $attrib){
		$component = db_query("SELECT cid FROM {webform_component} WHERE nid = %d AND name = '%s'", $theproduct->nid, $attrib);
		if (count($component) > 0) {
		  $getcomponent = db_fetch_array($component);
		}
		// Matched field, update the table
		if ($getcomponent){
		  db_query("UPDATE {webform_submitted_data} SET data = '%s' WHERE cid = %d AND sid = %d", $theproduct->data['attributes'][$attrib]['0'], $getcomponent['cid'], $sid);
		}
	  }
	}
	
	db_query("UPDATE {webform_submitted_data} SET data = '%s' WHERE cid = %d AND sid = %d", $orderid, 2, $sid);
	db_query("UPDATE {webform_submitted_data} SET data = '%s' WHERE cid = %d AND sid = %d", $ordertotal, 3, $sid);
	db_query("UPDATE {webform_submitted_data} SET data = '%s' WHERE cid = %d AND sid = %d", $coupon, 4, $sid);
	db_query("UPDATE {webform_submitted_data} SET data = '%s' WHERE cid = %d AND sid = %d", $rateadjustment, 5, $sid);
	if ($comments){
	  db_query("UPDATE {webform_submitted_data} SET data = '%s' WHERE cid = %d AND sid = %d", $comments, $comment_cid, $sid);
	}
  }
}
?>

The first bit deals with the results from another module, uc_discount_coupons, but the rest should make sense.

@Saoirse1916

I'm still a bit confused by your two code snippets. I'm trying to implement them but I'm not exactly sure where they should go. I can see in the latter snippet you mention uc_event_registration.ca.inc, should it go in a particular place in that file? For the first snippet does that get placed in the main webform.module?

Thanks!

No, forget the first one -- it worked for a while but some update broke it. The second one goes in uc_event_registration.ca.inc, which is included in the UC Event Registration module. This function is called when an order gets marked as completed. It cycles through the list of webform fields and updates them with the value of any matching attributes.

Thanks for the update. I actually ended up going in a different direction with this but I really appreciate your response.