Hey, I've been doing the Django thing for a few months and only
recently have felt less noobish. Of course, I was learning Python as
I went along too. Anyhow, I'm glad it worked.
Also check out http://www.djangosnippets.org/snippets/83/ if you get
into django-tagging.
Branton
--~--~-
Cool!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more
Well, there is, but you really ought to validate somehow.
Like shabda says, django is expecting a python datetime object. You
can create one with your string by first grabbing the individual bits
and then using the datetime function to create one.
from datetime import datetime
year, month, day
On Tue, Dec 20, 2011 at 11:09 PM, Divick Kishore
wrote:
> On Wed, Dec 21, 2011 at 6:04 AM, Branton Davis
> wrote:
> > It sounds like your custom user template context variable might be
> causing a
> > conflict with the default if you're also using django.contrib.aut
It sure seems like #2 that I mentioned before is the issue. Your context
processor is overriding the 'user' template context variable that the admin
uses. I just looked at some admin templates and they definitely use the
'user' variable. Name it something else or add logic to the context
process
AmaoZhao's answer is probably the best. You can also try:
class PostForm(forms.Form):
post = forms.CharField(label='', help_text=None, max_length=160,
widget=forms.Textarea(attrs={'rows':3, "cols":70,}))
The auto_id parameter only controls whether label tags and id attributes
6 matches
Mail list logo
