It seems that the webform_rules`s functions triggered before the hidden fields are removed from the submission. As a result, the export values of selected conditionsl fields consists of ones that have been hidden, despite the fact that in the webform results table all ok.

That's sad. Or maybe I'm wrong?

Comments

tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
commented
Priority: Critical » Normal

alexmatveev,
I changed the priority of this request from critical to normal.

My current focus for this module is getting it stable enough for a RC release. Just because of time constraints(this is volunteer work), I am not focusing on integration with other modules.

If anybody wants to sponsor(i.e. pay) for development of this modules for specific features I would be interested.

I am not able to look into how webform_rules functions but changing the weight of the modules might work.
check out this: http://drupal.org/node/110238

sorry I couldn't be more help.

Ted

tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
commented
Status: Active » Postponed
tedbow’s picture

tedbow
he/him
Primary language English
Location Ithaca, NY, USA
commented
Category: support » feature
rkeppner’s picture

rkeppner commented

I was having a similar tangle using both webform_rules and webform_pay with webform_conditional. In my case, I solved it with a custom module that altered the weights of the modules in question. I just put the following in mymodule.install:

function mymodule_install() {
  // Change module weights to get them to play nicely together.
  db_query("UPDATE {system} SET weight = -1 WHERE type = 'module' AND name = 'webform_pay'"); // First
  db_query("UPDATE {system} SET weight = 0 WHERE type = 'module' AND name = 'webform_rules'"); // Second
  db_query("UPDATE {system} SET weight = 1 WHERE type = 'module' AND name = 'webform_conditional'");  // Third
}