That:
{{ wpis.entry.lastChangeDate|date:"D d M Y" }}
gives me (why?):
2009-07-24 21:45:38.986156
and i don't know how to skip fraction part...
In my model i have:
addedDate = models.DateTimeField(default=datetime.now)
That:
{{ wpis.entry.lastChangeDate|date:"D d M Y" }}
gives me (why?):
2009-07-24 21:45:38.986156
and i don't know how to skip fraction part...
In my model i have:
addedDate = models.DateTimeField(default=datetime.now)
I suspect wpis.entry.lastChangeDate
has been somehow transformed into a string in the view, before arriving to the template.
In order to verify this hypothesis, you may just check in the view if it has some property/method that only strings have - like for instance wpis.entry.lastChangeDate.upper
, and then see if the template crashes.
You could also create your own custom filter, and use it for debugging purposes, letting it inspect the object, and writing the results of the inspection on the page, or simply on the console. It would be able to inspect the object, and check if it is really a DateTimeField.
On an unrelated notice, why don't you use models.DateTimeField(
auto_now_add
=True)
to set the datetime on creation?
Thanks for all hints... finally i did:
addedDate = str(datetime.now())[:-7]
before save object. In Model parts delete:
auto_now_add=True