Hi Henry -
 
Mission accomplished !
Although I had no success with putting the setQueryType into the onclick method of the button, it seems that I have made the request a POST by putting, somewhat simply:
 
<dataset name="blah" querytype="POST" etc..
 
My http debugging proxy showed a POST, and when I nervously opened IE (as a developer, Im sure Im not along in that, lol), it submitted my form ! Hooray :).
 
Thanks to yourself and Luis Eduardo for your informative and very prompt responses. Laszlo rules my roost once more.
 
Very bests,
 
Mike.
----- Original Message -----
Sent: Wednesday, September 06, 2006 5:50 PM
Subject: Re: [Laszlo-user] setQueryType and POSTing of large form

Can you send me the source code you're using to declare your dataset?


On 9/6/06, Mike at TOL23Design <[EMAIL PROTECTED] > wrote:
Hi Henry -
Thanks for your response :)
 
I am adding the setQueryType to the button action for my form like so:
 
<button fontsize="16" height="40" width="120" isdefault="true" >Submit Form</button>
 
yet when I examine the request that gets sent, I see:
 
GET /beta/update_offers2.php?%5F%5Flzbc%5F%5F=1157580598797&offer%5Fstatus=new&offe[etc].. HTTP/1.1
Host: www.foo.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.6) Gecko/20060728 Firefox/1.5.0.6
 
I am just going to try setting it using an 'onit' method, as I believe I saw in a similarly themed forum thread between yourself and someone with a similar problem at:
 
Look forward to hearing any thoughts or experience on why it's ignoring my request :).
I need to be able to use POST, as IE is naturally rejecting the GET version as it weighs at about 2900 characters.
 
Many thanks again,
 
Mike
 
 
----- Original Message -----
Sent: Wednesday, September 06, 2006 2:42 PM
Subject: Re: [Laszlo-user] setQueryType and POSTing of large form

It should be possible to get it to use the POST method. In SOLO, there is a currently a bug that you cannot use the magic "lzpostbody" parameter to force it to post a raw string as the content, but you should be able to get it to use POST method for a normal dataset.

Can you send me a very small example of your dataset and how you are setting it's query type?

I will try to reproduce it in the current trunk release.


                                                                                                       































                                    




























m,.llppooppppppppooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooo                                                                                                                                                                                                                               kk k kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk                                                                                                                                                                                      

On 9/6/06, Mike at TOL23Design <[EMAIL PROTECTED] > wrote:
Hallo people !
 
I am in somewhat of a bind..
I have developed a fairly large form with a couple of hundred fields and I submit it fine when I use the app in Firefox.
IE however, will not tolerate character strings over 2038, so does not even send a request, as revealed my headers proxy debugger thingy.
This also shows me that despite trying to set the 'setQueryType' to POST, the request when it goes from FF is still a GET.
This is a solo-deployed app. and I think I read that this is a known bug, that the setQueryType does not activate under SOLO...
Any thoughts on the best approach to fixing this ? (and saving the relationship with my client, lol :)..
Naturally, I am lax to break up the form into several seperate ones, although I could do that transparently, and have the submit button submit them all at once.
This would be rather cumbersome on the php, which would need to be rewritten somewhat.
Any thoughts/hacks on how I might achieve my goal most efficiently ?
 
Thanks for everything !
 
Mike,


_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user





--
Henry Minsky
Software Architect
[EMAIL PROTECTED]




--
Henry Minsky
Software Architect
[EMAIL PROTECTED]

_______________________________________________
Laszlo-user mailing list
[email protected]
http://www.openlaszlo.org/mailman/listinfo/laszlo-user

Reply via email to