Geeklog Forums

First What determines Today's Featured Article, when and why does it change. I have data that I don't want to change on the front page. Should I just do this with a static page? Second I know this has been discussed before but I'd like to see a "Sticky" feature. like that what's in a popular PHP forum. In the forum you can stick a thread on top. If you stick another thread it sticks to the one above and so on. Third Seems to be a bug with Windows and IE, when something changed on a page, you have to clear your cache (temporary Internet Files) and delete them in order to see the change. I first thought maybe it was caused by cookies, However that isn't so. I even put in the meta tags for progma etc. Microsofts Knowledge Base says the IE is looking for the end of 64k of data before it replaces the page and if it doesn't see that it will not replace the page. They recommend another meta tag at the end of the document. That didn't work either. I have notice however that Geeklog.net doesn't seem to have that problem. Any ideas?

In the Admin's version of the story editor, there's a drop-down above the story edit field where you can change a story to "featured". This will automatically make any other featured story a normal story.

You can use the "static page on frontpage" hack to have a static page above the stories. This will be much more flexible (and comfortable) in Geeklog 1.3.8, btw.

"Sticky" stories: I thought we had a feature request for this but can't find it at the moment. Anyway, this is probably not coming anytime soon, I'm afraid ...

bye, Dirk

Try this link http://www.geeklog.net/article.php?story=20030310061103740

For the sticky idea, why don't you add it to the feature request list so it doesn't get lost.

I use windows and IE6. My browser serves up old cache pages for geeklog.net . I experienced this on my site as well. While fixing another problem, the caching of old pages was also fixed.

I was having problems with geeklog not recognizing a person was logged in if they entered the site via a side page (ie other than index.php) or through a subdomain. So, I fixed all my cookies to include all parameters. As a side benefit, this allowed me to remove the autorefresh feature in index.php. I also added some cache control metatags to header.thtml. On my site, the autorefresh was the main culprit for causing browsers to load cache pages ignoring the metatags. YMMV.

You mention changing some things on your site to help this problem - cookies, refresh, etc. Do you mind sharing exactly what you did so we can do it too? Thanks a lot, Mark

Got it, Thanks!

I have copied that info, Thanks!

Here is the fix for webpage cache in IE. Place this in it's entirety at the top of the header.thtml and it will fix that ol problem. <?php header("Expires: Mon, 26 Jul 1997 05:00:00 GMT"; // Date in the past header("Last-Modified: " . gmdate("D, d M Y H:i:s" . " GMT"; // always modified header("Cache-Control: no-store, no-cache, must-revalidate"; // HTTP/1.1 header("Cache-Control: post-check=0, pre-check=0", false); header("Pragma: no-cache"; // HTTP/1.0 ?>

I tried this out on my test site which still has the refresh code in it. Putting the no cache info as headers in header.thtml seems to work on my system too. If it's placed in metatags instead, the refresh causes those to be ignored.

If you only have a caching problem, then try ronack's suggestion. Unless you have the same problem with cookies as I did, it's far easier just to put headers in the header.thtml file rather than modifying a couple lines in like six files.

That code worked for me. I was having the problem in Opera. I'd log out and go back to the home page and be logged back in. Now it works. Thanks! Mark