exportValues breaks from 4.2.13 to 4.3.1 - help!

[JohnFF]

Hi gang,

First up, our install has a lot of custom modules.

Our Drupal-based system has a "dashboard" that some users can log into to add questions to a Drupal webform. Standard tpls & forms.

However, we can no longer add questions, because the $this->controller->exportValues() is resulting postProcessArray ( [qfKey] => bfb1ebe7d1b886253fcedbaf688f02de_1929 ), as opposed to the exploded values that it's meant to be. This works fine in 4.2.13, but not in 4.3.1 (which I'm passing through on my way to 4.4.4).

Help!!! What could be causing this?

Thanks in advance!

[Donald Lobo]

i think exportValues requires the name of the form as a parameter.  might want to search the code base for an example

lobo

[JohnFF]

Hi Lobo, I'd seen other instances of code where it was used without a parameter, but I will look for one to use in this instance! Thank you

[JohnFF]

The codebase has examples that use it without a param.

So I'm managing to access the values through $this->controller->_pages['Questions']->_submitValues

Doesn't seem right somehow? Is there a better way?

[JohnFF]

$params = $this->controller->exportValues($this->_name);^M
die(print_r($params));

Outputs

Array ( [qfKey] => 5d1a3018c7c46959fd5bb3b9ae381ba4_4482 ) 1