Posted by Joe.Cafiero on April 19, 2011 at 10:46pm
Text blocks on Panel pages and content in slideshows on Panel pages don't always update right away when edited or added -- the same way as, say, edits to instances of simple content types.
Flushing caches will usually force the updates through so anonymous viewers can see the same content as admin.
Is the delay purely dependent on the caching rules in place on an individual site or is there something standard about how soon updates -- to nodequeue content, for instance -- become published?
Can flushing caches this way be a bad thing, if your site is not high volume?
Comments
Yeah, I would think it is
Yeah, I would think it is just the block cache. Whenever there is a problem seeing new content I also clear the cache. It shouldn't be a problem on a reasonably low volume site. At least I've never faced a problem doing so. There would be a problem if you have lots of constantly changing data. You'd end up fighting against your own cache.
another slow content update question
thanks for the feedback, david
i've not seen these slow-update issues with node content; i assume there's no kind of caching issues there?
somewhat related question: have you ever had reports from content editors making edits to node content, saving, then the changes not showing up when they view the page; i've had this happen to me a few times, as has my assistant, who's more the heavy content editor; generally if we log out and back in the problem corrects itself, but not always ... we've had a few instances where we've had to trade off an edit -- i.e., i can edit a page she can't (doesn't seem to be related to our differing privileges because it will always be a page she has previously edited with no problems)
"making edits to node
"making edits to node content, saving, then the changes not showing up when they view the page" - If they are not logged in when viewing the page, it is likely the cache. If they are logged in, that's unusual. I have only seen that when Firefox refused to update. Firefox can really be annoying when it comes to caching pages.
If you are logged in, you will not see cached pages, so that should never be a problem. Cached content is only served to anonymous users.
I've had this problem with
I've had this problem with Firefox as well when logged in. Restarting the browser and clearing the cached fixed it for me.
Hope they fix the memory leak problems with future releases Firefox releases.
http://www.webbfx.net/
sounds like you've both hit it
that is the browser we've had the experience with
having worked pre-drupal with entirely cache-less web sites, i think we may have become over-focused on drupal caching and under-focused on browser caching
it's when logged in that we've noted this and it has been firefox; many thanks to you both
No problem, I encounter this
No problem, I encounter this every few months. Glad I'm not the only one! :)
http://www.webbfx.net/
My general work flow involves
My general work flow involves two browsers. I always have one open and logged in (most likely Firefox) and another open and not logged in. Much easier then constantly logging in and out, and much easier than trying to do the multiple Firefox profiles trick.
This is what I do also and it
This is what I do also and it works. We are going to be doing some more optimization and hope we can get the cache to be only five minutes instead of the hour it is now - for some users.
For the browser or drupal
For the browser or drupal content? If it is a node, and content changes, it should update right away.
same problem for me
rotor banner blocks on Panel pages and content in rotor banner is not update while edit or update.
This will effect after 5 Hrs. of updation for anonymous user and for admin user this will affect at a time.
After flushing cache in performance page this will not affect.