Main Stories
Slash Boxes

Slash Open Source Project

Slashcode Log In

Log In

[ Create a new account ]

Article Poll

Poll I found this article to be
Very Helpful
Not Helpful
Not Very Helpful
[ Results | Polls ]
Comments:0 | Votes:0

How Do You Clear Users Cache or Force Refresh?

posted by Krow on 07:14 AM February 7th, 2001   Printer-friendly   Email story
ubiq writes "As admin, I made changes to the Organization block and saved them. This is the block where by default the "Andover" links show up. I put in a whole new set of links. When I view the home page as a new user, my changes show up. But for a previously logged-in user, the old Andover block still shows. I tried waiting overnight to see if it would automatically refresh, but no luck - still shows Andover for that user. Is there any way, after making changes to the blocks, to force all users to refresh, or clear the cache, so that they see the changes? Thanks."
This discussion has been archived. No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login
Loading... please wait.
  • Does anybody know if this is needed in Bender? I will be having a number of authors on my Slash site that have neither the privileges nor the knowledge to restart Apache every time they change something.
    Steve Linberg, Chief Goblin
    Silicon Goblin Technologies []
  • Restart Apache Server. Is very effective always. It works the next time you reload the page.
  • Well, you can set story_expire and block_expire (which also handles templates) to small numbers, so the cache will expire quickly, and then you won't need to restart to do updates. Currently, in bender, blocks expire in an hour, and stories in 10 minutes. Note that resetting these values from the Variables editor _does_ require an httpd restart. But that should not need to be done other than during setup.

    During development, set cache_enabled to 0, and _nothing_ will be cached. This is _not advisable at all_ for production sites, as caching is required to get reasonable performance, especially for templates.
  • Try restarting your web server. mod_perl has a tendency to hold things in memory. Also, set MaxRequestsPerChild to something small, depending on your hit rate. This will cause the child httpds to exit after they service that many requests, and flush the "caching" of mod_perl automatically.
    Sci-Fi Storm:
  • Yes, I did stop and restart slashd. That did rebuild pages but not for the logged in user, only for the new user. When I stopped and restarted Apache, though, everything got refreshed for everyone.
  • by Anonymous Coward
    Stopping and starting slashd also helps because it forces the pages to be rebuilt.