116 Posts
10 years ago
1
Topic
Hi,
I have a form with many fields grouped in sub-forms (groupX) and published in tabs. I kept adding fields and testing and after a while I my new fields, though they appeared to be working in the form would not be saved in the database.
I spent the afternoon trying to understand what made them different from other published earlier and nothing would jump at me.
I eventually tried to change the method from "GET" to "POST" and O miracle now they are saved in the database.
I thought I would share that here as I'm pretty sure I'm neither the first nor the last one to stumble upon that problem.
"POST" requests are not limited in length unlike "GET" requests and I guess that's the reason for this behavior.
Regards.
Xav.
I have a form with many fields grouped in sub-forms (groupX) and published in tabs. I kept adding fields and testing and after a while I my new fields, though they appeared to be working in the form would not be saved in the database.
I spent the afternoon trying to understand what made them different from other published earlier and nothing would jump at me.
I eventually tried to change the method from "GET" to "POST" and O miracle now they are saved in the database.
I thought I would share that here as I'm pretty sure I'm neither the first nor the last one to stumble upon that problem.
"POST" requests are not limited in length unlike "GET" requests and I guess that's the reason for this behavior.
Regards.
Xav.
693 Posts
10 years ago
0
Level 1
Hi Xav,
Thanks for the post. The main difference is probably cache and browser history. But maybe in some cases it doesn't matter.? Perhaps this should be added to the tracker as feature request for optional Http Request Methods.
thanks,
Randy
.
Thanks for the post. The main difference is probably cache and browser history. But maybe in some cases it doesn't matter.? Perhaps this should be added to the tracker as feature request for optional Http Request Methods.
thanks,
Randy
.
