Hi Tim,
You are right, this view use a @cache_page decorator and after cleaned the
cache the problem was solved. I would never imagine that I must clean cache
on update to 1.8.
Sorry by post here, but I touth that was a seriosly bug on wsgi module.
By.
Em quinta-feira, 9 de abril de 2015 07
This query came up on IRC a few days ago. I believe it was solved by
clearing the site's cache. This is one of the recommended steps in "How to
Upgrade Django."
https://docs.djangoproject.com/en/dev/howto/upgrade-version/
On Thursday, April 9, 2015 at 1:14:35 AM UTC-4, Curtis Maloney wrote:
>
>
