Could you add the support for token values to the pay field. I am currently using alpha1 and notice that this is also not present in alpha2. I am using a session variable to populate the value and could do with it being implemented so upgrades will work.

Comments

quicksketch’s picture

quicksketch
he/him
commented

Which fields are you trying to prepopulate? For the most part, I'd probably avoid prepopulating any credit card information, since that means you'd have to store it somewhere in your database, which probably isn't a good idea.

quicksketch’s picture

quicksketch
he/him
commented
Status: Active » Closed (won't fix)
chrisivens’s picture

chrisivens commented
Status: Closed (won't fix) » Active

The only field I'm interested in having the value pre-populate is the price field. It's a donation form where the value of the donation is set by a link on a previous page. I certainly don't want the credit card fields to be auto-filled.

quicksketch’s picture

quicksketch
he/him
commented
Category: feature » support
Status: Active » Fixed

The only field I'm interested in having the value pre-populate is the price field.

See this handbook page: Working with Default Values.

chrisivens’s picture

chrisivens commented

Since there is no call to _webform_filter_values() the token replace does not work. That's what I added to the alpha1 version for my client to create the functionality they need. Ideally I want them to be able to upgrade without having to re-patch every time.

quicksketch’s picture

quicksketch
he/him
commented

I'm not sure what you mean by "Since there is no call to _webform_filter_values() the token replace does not work". Webform Pay let's you re-use any other textfield or select list in the form to serve as the total. Since these are just normal Webform fields, any token replacement should work fine on them. What patch are you applying to re-gain similar functionality?

chrisivens’s picture

chrisivens commented

Aaah, that must be something new to post alpha1 version. I did scan through the code and not it was totalling up other field values. The alpha1 version just had the fields created for you so that's what I had to alter. If you can now use any other item I guess that's my solution. Sorry for badgering you like this. I haven't got a copy of the latest code running on the client's dev server.

I'll accept this as fixed and rebuild the form when I get time.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.