Well I switched to per view caching and it went off quite easily.
Thanks for the encouragement.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to
That's excellent - strange I came across the problem right at the same
time you were fixing it ;)
-P
On 20/07/06, Jacob Kaplan-Moss <[EMAIL PROTECTED]> wrote:
>
> On Jul 20, 2006, at 4:45 AM, Phil Powell wrote:
> > It seems odd that this doesn't seem to have popped up as a common
> > issue, if
On Jul 20, 2006, at 4:45 AM, Phil Powell wrote:
> It seems odd that this doesn't seem to have popped up as a common
> issue, if it is indeed something related to site-wide caching - it's
> definitely a bit of a show-stopper when it comes to having a client
> using an admin interface which doesn't
On 7/19/06, Phil Powell <[EMAIL PROTECTED]> wrote:
> Is there a simple way to disable caching for admin? Or should it
> happen automatically?
Probably the best way to handle this is to cache only pages that
*aren't* being served to a logged-in user; this has several
advantages:
* The admin
Hi,
> 1) Am I right in thinking that decorators were only introduced in Python 2.4?
yes, decorators were introduced in Python 2.4. But you don't have to use
them.
A non decorator syntax would be:
myview = cache_page(myview, 900)
> 2) This would mean overriding the admin views for every
Thanks for the feedback guys - good to know that I'm not alone in
seeing this behaviour.
It seems odd that this doesn't seem to have popped up as a common
issue, if it is indeed something related to site-wide caching - it's
definitely a bit of a show-stopper when it comes to having a client
is there a similar decorator to cache the output of a tag?regardsIanOn 20/07/2006, at 6:28 PM, Axel Steiner wrote:Hi, It looks like the right way to deal with this is to implement per pagecaching, but that doesn't look too simple to me. I hope that someonewill prove me wrong by posting some simple
Hi,
> It looks like the right way to deal with this is to implement per page
> caching, but that doesn't look too simple to me. I hope that someone
> will prove me wrong by posting some simple instructions for implemeting
> per page caching. Alternatively please post a mechanism for disabling
>
I can confirm that the odd behavior that you are seeing comes from
setting up the global caching for a site. I see the same thing on a
site under 0.91 that uses global caching, but not at all on other
non-caching sites. (BTW, the work around is to periodically blow away
the files *admin* in the
Hi,
Perhaps I'm missing something simple, but ever since I enabled caching
middleware in my apps, I've noticed that it's causing lots of strange
behaviour in my admin: updates taking a while to show up, new objects
not showing up, messages taking a while to filter through.
I'm assuming it's
10 matches
Mail list logo
