On 1/27/07, Panos Laganakos <[EMAIL PROTECTED]> wrote: > > I've added the allow_future option, and indeed it worked. Thanks alot! > > Though, not sure what "in the future" means. a matter of the date not > being the same in the db and the server or something? Care to explain?
the thing is that in the database you have a record that have pub_date set to some date in the future. Since the generic views are meant for archive/newspapers/blogs etc., they display only objects, that have already been published (publication date is in the past). You can override this behavior using allow_future=True > > On Jan 26, 1:08 am, "James Bennett" <[EMAIL PROTECTED]> wrote: > > On 1/20/07, Panos Laganakos <[EMAIL PROTECTED]> wrote: > > > > > Indeed, that did it. Though, I'm curious, as there's already content in > > > the posts table, shouldn't these show up as I've defined them in the > > > template?Do the Posts already in the table have their pub_date in the > > > future, > > by any chance? > > > > -- > > "Bureaucrat Conrad, you are technically correct -- the best kind of > > correct." > > > > > -- Honza Kr�l E-Mail: [EMAIL PROTECTED] ICQ#: 107471613 Phone: +420 606 678585 --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
