| Post |
|
Member | mores posts 21 9:17 pm June 22, 2009
| |
|
|
I have a lenghty form, and it's all working fine, except for the radio buttons – they won't transmit their value in the email. Tracking works fine.
Here's what I have in the field name box:
[id:akzeptierenodernicht]#Ja|Ja, ich akzeptiere die Datenvereinbarung|set:true#Nein|Nein, ich akzeptiere die Datenvereinbarung NICHT
And when I use {akzeptierenodernicht}, this is exactly what shows up in the email – not the value but the curly brackets etc.
Any ideas?
|
|
|
Admin
| Oliver Munich, Germany posts 6237 9:42 pm June 22, 2009
| |
|
|
start with a simple example, e.g.:
my button[id:my_button]#ja#nein
|
|
|
|
|
Member | mores posts 21 9:09 am June 23, 2009
| |
|
|
could it be that it is not possible to use fields without field names?
I now added a field name and removed the commas (those too cause problems quite frequently)
[id:akzeptierenodernicht]Akzeptieren#Ja|Ja, ich akzeptiere die Datenvereinbarung|set:true#Nein|Nein, ich akzeptiere die Datenvereinbarung NICHT
and then the next checkbox group that had no field name didn#t work anymore (it worked previously), so I added a field name and now it's all good.
BUT: my form looks like crap :(
can you confirm that this is indeed the issue?
|
|
|
Admin
| Oliver Munich, Germany posts 6237 7:39 am June 24, 2009
| |
|
|
mores said:
could it be that it is not possible to use fields without field names?
possibly.
I now added a field name and removed the commas (those too cause problems quite frequently)
a comma in the label shouldn't be an issue.
[id:akzeptierenodernicht]Akzeptieren#Ja|Ja, ich akzeptiere die Datenvereinbarung|set:true#Nein|Nein, ich akzeptiere die Datenvereinbarung NICHT
and then the next checkbox group that had no field name didn#t work anymore (it worked previously), so I added a field name and now it's all good.
great. that's the way it is supposed to be.
BUT: my form looks like crap :(
why don't you change the CSS then to make it look better?? and/or use text-only fields were needed…crappy input = crappy output.
can you confirm that this is indeed the issue?
|
|
|
|
|
Member | mores posts 21 9:14 am June 24, 2009
| |
|
|
why don't you change the CSS then to make it look better?? and/or use text-only fields were needed…crappy input = crappy output.
Yes, using CSS to hide some elements came to me while I took a shower this morning. Regarding the crappy input: that's the way my client's employer wants it. First make people check that they read the disclaimer, then let them not agree with it. So now I have a definition of how they want it and I need to pull my hair out trying to get it done :)
|
|
|
Admin
| Oliver Munich, Germany posts 6237 9:03 pm June 25, 2009
| |
|
|
i hear you.
but there are always alternative approaches to solve an issue…ie. hiding short form labels of certain fields (so they stay short in the admin email) but providng more descriptive text only fields as "proxy field labels" so to speak.
|
|
|
|