What I have been doing is taking action at the controller method, and toss the Validator.
Since the kw dictionary holds JSON parsable strings, I use simplejson.loads() to get the data out.
Yeah I know it's sloppy...
I have not looked into paginate.py or the submit mechanisms of Turbogears in order to
find the root cause.
I'm working on a different part of the application now. Perhaps Mansi will be able to
have a look. It is still on our list of problems to solve.
Nicky
On 8/2/06, Randall <[EMAIL PROTECTED]> wrote:
Nicky, have you made any progress?
Randall
Nicky Ayoub wrote:
> On 7/27/06, Jorge Godoy < [EMAIL PROTECTED]> wrote:
> >
> >
> > "Randall" <[EMAIL PROTECTED]> writes:
> >
> > > The problem seems to be with compound widgets. Specifically, I'm using
> > > an AutoCompleteField widget. If I remove it from the form, paging
> > > works fine.
> >
> > I have AutoCompleteFields and I show them with paged datagrids. I can
> > change
> > the page and keep the other part of the page intact. Maybe if you post
> > some
> > code to the list or open a ticket with a quickstarted project that
> > reproduces
> > your problem we could see it better...
> >
> > --
> > Jorge Godoy <[EMAIL PROTECTED]>
> >
> > >
> >
> We are also having this problem. To me it seems like the paginate urls are
> being constructed in such a way that the form variables are included as
> simple strings. Once the postback is called our validator complains because
> the values are now json-like strings. My guess is that since they where not
> marshalled through the submit process of the form, the to_python() magic
> never happend.
>
> Jorge, would it be possible for you to show how you were able to solve the
> problem?
>
> Thanks,
>
> --
> --
> Nicky Ayoub
> G-Mail Account
>
> ------=_Part_273320_8853449.1154115583443
> Content-Type: text/html; charset=ISO-8859-1
> X-Google-AttachSize: 1620
>
> <br><br><div><span class="gmail_quote">On 7/27/06, <b class="gmail_sendername">Jorge Godoy</b> <<a href="" href="mailto:[EMAIL PROTECTED]"> [EMAIL PROTECTED]">[EMAIL PROTECTED]</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> <br>"Randall" <<a href="" href="mailto:[EMAIL PROTECTED]">[EMAIL PROTECTED]">[EMAIL PROTECTED] </a>> writes:<br><br>> The problem seems to be with compound widgets. Specifically, I'm using<br>> an AutoCompleteField widget. If I remove it from the form, paging
> <br>> works fine.<br><br>I have AutoCompleteFields and I show them with paged datagrids. I can change<br>the page and keep the other part of the page intact. Maybe if you post some<br>code to the list or open a ticket with a quickstarted project that reproduces
> <br>your problem we could see it better...<br><br>--<br>Jorge Godoy <<a href="" href="mailto:[EMAIL PROTECTED]"> [EMAIL PROTECTED]">[EMAIL PROTECTED]</a>><br><br><br><br></blockquote></div><br>We are also having this problem. To me it seems like the paginate urls are being constructed in such a way that the form variables are included as simple strings. Once the postback is called our validator complains because the values are now json-like strings. My guess is that since they where not marshalled through the submit process of the form, the to_python() magic never happend.
> <br><br>Jorge, would it be possible for you to show how you were able to solve the problem? <br><br>Thanks,<br clear="all"><br>-- <br>--<br>Nicky Ayoub<br>G-Mail Account
>
> ------=_Part_273320_8853449.1154115583443--
--
--
Nicky Ayoub
G-Mail Account
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "TurboGears" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/turbogears
-~----------~----~----~----~------~----~------~--~---
