Ah, I understand, I thought the actual error was the template could not be found. But the problem was that the base.html was raising an exception. Fixed the error and everything is fine.
Thanks Karen. On 16 mrt, 13:14, Karen Tracey <[email protected]> wrote: > On Tue, Mar 16, 2010 at 6:58 AM, Sander <[email protected]> wrote: > > I'm using version 1.2 beta. Is there some kind of workaround? or do I > > have to downgrade to 1.1.1? > > You could try the latest patch on the ticket, but I think you'd need to get > an SVN checkout for that, since I know there has been at least one other fix > in that same area of code so I doubt the patch will apply cleanly to the 1.2 > beta level. > > You could manually double-check all the templates referenced from your base > template -- one of them is apparently mis-identified or missing. The problem > only affects the name reported in an error situation, it does not cause > valid templates to fail to load. > > Or you could back off to 1.1.1, for at least long enough to let it tell you > which template it is really having trouble reading. > > Karen -- 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.
