Hey Randall sorry it took me so long to get back.
So the quickstart you sent me works but I realized that my example was
not working because my template tries to use the urls in tg.paginate
like this:
<div>
<span><a
href="${tg.paginate.href_first}">First</a></span>
<span><a href="${tg.paginate.href_prev}">Prev</a></span>
<span py:for="page in tg.paginate.pages">
<a py:if="page != tg.paginate.current_page"
href="${tg.paginate.get_href(page)}">${page}</a>
<b py:if="page ==
tg.paginate.current_page">${page}</b>
</span>
<span><a href="${tg.paginate.href_next}">Next</a></span>
<span><a href="${tg.paginate.href_last}">Last</a></span>
</div>
Somehow the input_values got updated and put in self but the following
lines didn't get tended to: So this seems to be the problem(These
lines numbers are probably not correct in reference to the current
source):
160c117
< self.href_next = turbogears.url(cherrypy.request.path,
self.input_values)
---
> self.href_next = turbogears.url(cherrypy.request.path,
> input_values)
164c121
< self.href_last = turbogears.url(cherrypy.request.path,
self.input_values)
---
> self.href_last = turbogears.url(cherrypy.request.path,
> input_values)
173c130
< self.href_prev = turbogears.url(cherrypy.request.path,
self.input_values)
---
> self.href_prev = turbogears.url(cherrypy.request.path,
> input_values)
177c134
< self.href_first = turbogears.url(cherrypy.request.path,
self.input_values)
---
> self.href_first = turbogears.url(cherrypy.request.path,
> input_values)
-Ian
On 11/2/06, Ian Wilson <[EMAIL PROTECTED]> wrote:
> I'll try that when I get to work.
>
> On 11/2/06, Ian Wilson <[EMAIL PROTECTED]> wrote:
> > Yeah okay well sorry I can't be of more help right now I am getting
> > run over at work by more work. I think using it without the patch
> > actually seems to be working as long as I use keyword arguments
> > everywhere and as you mention in that post the order matters as
> > well(paginate versus validate). And if it means anything it has been
> > incredibly useful to me. That is wierd that the test util is so
> > broken.
> >
> > -Ian
> >
> >
> > On 11/2/06, Randall <[EMAIL PROTECTED]> wrote:
> > >
> > > Looks like patch 6 introduced new problems. I really need to write
> > > unit tests, but I've run into trouble there:
> > >
> > > http://groups.google.com/group/turbogears/browse_thread/thread/4380df8d5b5823ec/7f0e5025b4263014?lnk=raot#7f0e5025b4263014
> > >
> > > Patch 5 should work for you. Note that until I can write a full set of
> > > tests for it, I don't consider the paginate changes stable.
> > >
> > > Randall
> > >
> > >
> > > > > >
> > >
> >
>
--~--~---------~--~----~------------~-------~--~----~
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?hl=en
-~----------~----~----~----~------~----~------~--~---