On Apr 27, 5:09 pm, Ian Bicking wrote:
> On Mon, Apr 27, 2009 at 6:52 PM, Mike Lewis wrote:
> > Sorry for the confustion. It essentially contains 3 things.
> > - An oauth client (uses SA as a store) which could be used outside of
> > pylons, repoze, or even wsgi
> > - A repoze.who plugin that us
On Mon, Apr 27, 2009 at 6:52 PM, Mike Lewis wrote:
> Sorry for the confustion. It essentially contains 3 things.
> - An oauth client (uses SA as a store) which could be used outside of
> pylons, repoze, or even wsgi
> - A repoze.who plugin that uses the OAuth client. I used the OpenID
> repoze.wh
On Apr 26, 12:33 pm, Ian Bicking wrote:
> On Sun, Apr 26, 2009 at 11:25 AM, Mike Lewis wrote:
> > I wrote some OAuth repoze plugins and whatnot. There's a demo here.
>
> >http://github.com/mikelikespie/oauth-repoze
>
> > I probably should refactor the OAuth and repoze modules out
> > eventually.
Moin,
Am Montag, 27. April 2009 18:47:38 schrieb Clemens Hermann:
> I modified the patch slightly to get rid of the AttributeError here:
> http://paste.pocoo.org/show/114528/.
Great, thanks. The patch is working perfectly.
> However, as you do no longer have a default controller/action you'll
>
Mike,
> I think I ran into this problem and worked around it by making my
> template at a higher level that avoids pagelink.
paginate.Page and paginate.Page.pager accept arbitrary additional
keyword arguments.
These get passed to url_for. Hence you can use them to provide the
controller/action f
Moin Christoph,
> > if routes.Mapper is configured with explicit=True (as recommended)
> > then webhelpers.paginate.Page._pagerlink fails.
>
> Thanks, I didn't even notice that. I can reproduce the problem.
>
> > This patch fixes the issue:http://paste.pocoo.org/show/112812/
>
> Not for me yet.
>
