Hi
i(my customer) just made the big mistake to create a Dropdown with:
Field Name and Field ID = event
after that, nothing happens after submit.
even the debugger didnt work/come, the only thing that stay, was a clear site (like than, when i would use a blank thank you message)
till i find out that this fieldname/id was the problem i spend 1-2h with search and by try and error.
maybe forbid reserved values is to strict, but a warning before safe with the hint:
Warning your form uses values that are reserved by the system would be great.
i dont know wich other values are reserved too, but it could be that it is more than just "event"
Best Regards
grafik
i(my customer) just made the big mistake to create a Dropdown with:
Field Name and Field ID = event
after that, nothing happens after submit.
even the debugger didnt work/come, the only thing that stay, was a clear site (like than, when i would use a blank thank you message)
till i find out that this fieldname/id was the problem i spend 1-2h with search and by try and error.
maybe forbid reserved values is to strict, but a warning before safe with the hint:
Warning your form uses values that are reserved by the system would be great.
i dont know wich other values are reserved too, but it could be that it is more than just "event"
Best Regards
grafik
Hi grafik,
You should avoid anything that typically occurs in Joomla! URLs like 'view', 'task', 'option', etc. and possibly anything that might be a PHP reserved word e.g. 'true', 'continue'
Bob
You should avoid anything that typically occurs in Joomla! URLs like 'view', 'task', 'option', etc. and possibly anything that might be a PHP reserved word e.g. 'true', 'continue'
Bob
i normally try :wink:
but i cant talk for the customer 🙄
thats why i would like chronoforms do this (prevent to use/ or at least give a hint when such a value is used)
this has very low priority to "fix" and maybe it can be done with other "critical" name checks, like not use: -äöü$ and all the other things that may create an error
but i cant talk for the customer 🙄
thats why i would like chronoforms do this (prevent to use/ or at least give a hint when such a value is used)
this has very low priority to "fix" and maybe it can be done with other "critical" name checks, like not use: -äöü$ and all the other things that may create an error
This topic is locked and no more replies can be posted.
