csross Posted May 5, 2005 Posted May 5, 2005 I have Movable Type 3.16 installed on a RedHat server. When I was running 3.121, a very experienced user noticed that sometimes after he posted an entry, it didn't immediately show up on the index.html page. There were instances when it didn't show up for some time (although it did appear in the daily entries). Has anyone experienced this? Quote
TCH-Bruce Posted May 5, 2005 Posted May 5, 2005 Welcome to the family csross I removed the duplicate post. Sorry I don't have an answer for you. We have some experienced MT users here maybe they can shed some light on this for you. Quote
TCH-Rick Posted May 5, 2005 Posted May 5, 2005 The most likely problem is the page is either cached in the browser or the ISP is serving a cached page. You can set the browser default to check for a new page every time it is loaded. In IE this is under the Internet Options/General/Temporary Internet Files Settings. Quote
csross Posted May 6, 2005 Author Posted May 6, 2005 The most likely problem is the page is either cached in the browser or the ISP is serving a cached page. You can set the browser default to check for a new page every time it is loaded. In IE this is under the Internet Options/General/Temporary Internet Files Settings. <{POST_SNAPBACK}> Thanks. I'll tell him to give it a try. Quote
jwbowden Posted May 6, 2005 Posted May 6, 2005 I have Movable Type 3.16 installed on a RedHat server. When I was running 3.121, a very experienced user noticed that sometimes after he posted an entry, it didn't immediately show up on the index.html page. There were instances when it didn't show up for some time (although it did appear in the daily entries). Has anyone experienced this? <{POST_SNAPBACK}> The simplest explanation is the browser caching, if the problem persists and it isn't caching (browser or server) then you might consider looking into the "dynamic publishing" feature of MT 3.15 and above. Welcome to the Forum! Quote
TCH-BillH Posted May 6, 2005 Posted May 6, 2005 Welcome to the forums! My vote is on Rick ... I bet your ISP is caching your page. It's happened to me a number of times. What a pain! Quote
TweezerMan Posted May 6, 2005 Posted May 6, 2005 I tend to favor the caching theory as well, but there is another possibility. MT rebuilds indexes and archive pages as a background task, and if something goes wrong during that process, it can sometimes die off without any error messages at all. This can leave the entry archive page updated (rebuild) because it is rebuilt first and in the foreground, but the main index page won't be updated until something else happens to trigger the main index page to be rebuilt again without an error. I believe there was an MT bug on this kind of behavior, but I don't remember off-hand which MT3 versions are affected by it. It is fixed in the latest version of MT though. Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.