Jay Parlar schrieb:
> I think that Tom Tobin ([EMAIL PROTECTED]) was given the job of
> administering the Trac whitelist.
He whitelisted me (hey, thanks!) when I sent him personal mail.
He will need the IPs you use to access Trac. I guess dynamic IPs
would give him headaches ...
Michael
--
Joe wrote:
> It does bring up the general sort of question - is there a mechanism by
> which individuals can get "whitelisted" or otherwise allowed access to
> the wiki to post up code, patches, etc?
I put some thought into this but couldn't figure out a way to make this
feasible. This would almo
I think that Tom Tobin ([EMAIL PROTECTED]) was given the job of
administering the Trac whitelist.
Jay P.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email t
I forgot to mention that I attempted to put this in the Wiki again and
askimet failed me.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-develo
Thanks, Joe. I've actually updated it to this:
from django.conf import settings
from django.contrib.auth.views import login
from django.http import HttpResponseRedirect
class RequireLoginMiddleware(object):
"""
Require Login middleware. If enabled, each Django-powered page will
require
Jared's posted it on his site -
http://superjared.com/entry/requiring-login-entire-django-powered-site/
It does bring up the general sort of question - is there a mechanism by
which individuals can get "whitelisted" or otherwise allowed access to
the wiki to post up code, patches, etc?
I really
On 10/27/06, Jared Kuolt <[EMAIL PROTECTED]> wrote:
>
> I'd like to add a Middleware class that I wrote to the Wiki, but I keep
> getting rejected by askimet.
>
> The class requires an authenticated user for every view. This is
> beneficial for any closed project. Does anyone suppose something lik
