At 3/13/2005 11:53 AM, Jan Steinman wrote:
On 13 Mar 2005, at 03:27, Mike wrote:
The extension does not get called because the browser has cached it locally. The content is no longer dynamic. Is there anything I can do on the server side to cause the browser to not use its cached version? The extension looks like a nice feature accept it can't deliver dynamic content.
The solutions I've seen proposed is 1) make your dynamic content a Special page, or 2) have pages conditionally set a "no cache flag" when saved, then add spaghetti code throughout the known universe to do different things based on this bit.
Or use the following piece of code/hack in your extension, it works just fine for me to adress this "problem" (yes, it is a problem). Again, a hack, but does the trick until a clean solution is found.
$ts = mktime(); $now = gmdate("YmdHis", $ts + 120); $ns = $wgTitle->getNamespace(); $ti = wfStrencode($wgTitle->getDBkey()); $sql = "UPDATE cur SET cur_touched='$now' WHERE cur_namespace=$ns AND cur_title='$ti'"; wfQuery($sql, DB_WRITE, "kwBreadCrumbsNoCache");
-- Sebastien Barre