btw, I was correct, it was the development settings causing the problem
On Wed, Jul 13, 2011 at 1:43 PM, Joshua Russo wrote:
> Correct
>
> --
> You received this message because you are subscribed to the Google Groups
> "Django users" group.
> To view this discussion on the web visit
> https://gr
Correct
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/K5yKllF_gPcJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe fro
*light bulb* I forgot about my development vs production settings. I was
only changing the TEMPLATE_DIRS in the main settings.py that represents my
production settings. I'm not in a place where I can test this but I'm almost
certain that's what the problem is.
--
You received this message beca
To be clear, when you say registration/login, you mean
templates/registration/login, correct?
Your 'registration' directory should be in a 'templates' dir.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to dja
Cool, thanks for the confirmation.
I do have my template directories explicitly listed in TEMPLATE_DIRS. I even
made sure that my app's templates came before the admin templates, but for
some reason it's not picking up my /registration/logged_out.html and the
others that show up in the admin's
On 07/13/2011 12:46 PM, Joshua Russo wrote:
That's fine, but I was under the impression that the templates could
be overridden just by creating the proper path in my template
directories. Is that not true?
It's true. Check the order of your TEMPLATE_DIRS in settings.py. If you
don't have t
That's fine, but I was under the impression that the templates could be
overridden just by creating the proper path in my template directories. Is
that not true?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the we
gt; *An:* django-users@googlegroups.com
> *Betreff:* Trouble overriding registration templates
>
> ** **
>
> I want to use my own logout template but it doesn't want to pick it up. The
> login template worked just fine, but for anything that's already in the
> adm
Am I wrong about how templates work?
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-users/-/FVBKI9qS2PQJ.
To post to this group, send email to django-users@googleg
Sorry, auto correct strikes again. I was trying to reply quickly from my
phone. I meant auth, not author views.
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-us
I do have a views that are basically just proxies for the author views, but I
was under the impression that if I just wanted to replace the registration
templates then all I needed was a registration directory in my templates
directory with the right file names. From there it should just take th
@googlegroups.com
Betreff: Trouble overriding registration templates
I want to use my own logout template but it doesn't want to pick it up.
The login template worked just fine, but for anything that's already in
the admin's template/registration folder, it only wants to use those. I
t
I want to use my own logout template but it doesn't want to pick it up. The
login template worked just fine, but for anything that's already in the
admin's template/registration folder, it only wants to use those. I tried
putting my templates folder before the admin templates folder in the list
13 matches
Mail list logo
