Hi,
I had a form which needed to capture the details for media events.
So I added a textbox and gave it the fieldname "event"
This caused a blank page on submit.
Took a bit of mucking about to work out which field was breaking chronoforms :wink:
I then changed the fieldname to "eventName" and all was good.
Probably just need to add this to the info/instruction under the field name when adding a new field to warn users that a field with the name "event" will make it bomb.
Otherwise - awesome extension!
Cheers folks.
I had a form which needed to capture the details for media events.
So I added a textbox and gave it the fieldname "event"
This caused a blank page on submit.
Took a bit of mucking about to work out which field was breaking chronoforms :wink:
I then changed the fieldname to "eventName" and all was good.
Probably just need to add this to the info/instruction under the field name when adding a new field to warn users that a field with the name "event" will make it bomb.
Otherwise - awesome extension!
Cheers folks.
Hi blueraspberry,
There is a FAQ here but it's not the easiest to find as 'event' appears in most of the other FAQs too :-(
Bob
There is a FAQ here but it's not the easiest to find as 'event' appears in most of the other FAQs too :-(
Bob
Thanks Bob. Yes indeed the word event is in almost every post!
My take on it would be to alter the following info line to include the "reserved words":
Anyhat - for me it's all good now. Thanks for the link to the FAQ on reserved words, I'll keep that to hand.
My take on it would be to alter the following info line to include the "reserved words":
No spaces or any special characters, but underscores _ and square brackets [] are allowed.
Anyhat - for me it's all good now. Thanks for the link to the FAQ on reserved words, I'll keep that to hand.
This topic is locked and no more replies can be posted.
