static cache=enabled - when is it updated?

Author Message

Steven E. Bailey

Tuesday 10 October 2006 7:50:45 am

I've set up a static cache test site running 3.7.6, actually a new siteaccess for static pages of an existing site. The thought is to serve the static cached pages until someone logs in, at which time the site access is changed to the non-static.

It works as expected with viewing... meaning that after I tweaked the rewrite rules and ran the makestaticcache.php -s <new siteaccess> (and ran a shell script to add "static" to the title of each page) I ended up on the static site for the files that have a generated static file (and back at the dynamic site if I delete an index.html).

However, when I add new content, change stuff, delete stuff (and presumably move stuff), the static cache isn't automatically updated - or, more precisely, files are not changed/added in my static directory. Looking quickly at the code (ezcontentobjecttreenode.php, ezstaticcache.php, ezcontentcachemanager.php, cache.php, module.php, cachetoolbar.php) and the changelogs, it does appear that it should, and poking around this site I got the impression that it should automatically regenerate the static cache (although several forum entries also mentioned running makestaticcache.php as a cron job).

Running makestaticcache.php does fix everything.

So, am I wrong in my assumption and static cache pages are NOT updated on publish and therefore I should set up a makestaticcache cron?

Or, did I misconfigure something along the way and I should keep looking for that...

Certified eZPublish developer
http://ez.no/certification/verify/396111

Available for ezpublish troubleshooting, hosting and custom extension development: http://www.leidentech.com

Kristof Coomans

Tuesday 10 October 2006 10:35:04 am

Hello Steven

Maybe it's because of the bug I found last week: http://ez.no/bugs/view/9126

independent eZ Publish developer and service provider | http://blog.coomanskristof.be | http://ezpedia.org

Steven E. Bailey

Wednesday 11 October 2006 3:16:04 am

Thanks. That saved me a lot of debugging. I switched to 3.8.4 and with this change it works as expect. I still have a problem with the 3.7.6 but there were bug fixes in between.

Certified eZPublish developer
http://ez.no/certification/verify/396111

Available for ezpublish troubleshooting, hosting and custom extension development: http://www.leidentech.com

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 31 2025 06:13:36
Script start
Timing: Jan 31 2025 06:13:36
Module start 'layout'
Timing: Jan 31 2025 06:13:36
Module start 'content'
Timing: Jan 31 2025 06:13:36
Module end 'content'
Timing: Jan 31 2025 06:13:36
Script end

Main resources:

Total runtime0.0128 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0043 588.2734151.2266
Module start 'layout' 0.00430.0024 739.500036.6797
Module start 'content' 0.00670.0047 776.179794.1250
Module end 'content' 0.01150.0013 870.304733.9922
Script end 0.0128  904.2969 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002015.9479140.0001
Check MTime0.00097.0567140.0001
Mysql Total
Database connection0.00064.424210.0006
Mysqli_queries0.002015.341430.0007
Looping result0.00000.187910.0000
Template Total0.00107.610.0010
Template load0.00075.814010.0007
Template processing0.00021.771210.0002
Override
Cache load0.00053.676310.0005
General
dbfile0.00086.593580.0001
String conversion0.00000.052140.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs