Last post May 04, 2006 06:56 PM by J7Mitch
Mar 21, 2006 12:46 PM|jkhammond|LINK
I just completed updating to 4.02 from 3.1 for an intranet site with several hundred pages. After seeing 4.03 was out I updated to 4.03 the next day.
Specific web.config changes for my config, just FYI:
Broadcastpolling provider as default
cacheRolesInCookie = false
On both 4.02 and 4.03, I am seeing this issue:
Some REALLY strange cache type issues. For example, I add an html/textbox to a page. The module doesn't show up. I hit refresh. The module shows up. I hit refresh again. The module goes away.
In some more complex cases I have seen the page configuration change four times in a row! That is, I hit F5 four times, and it shows me four different, older configurations in a row!
This killed me in a presentation this morning. I added a role for a focus group to see a page, and then when those users went to the page, some of them could see the page, some couldn't. Hitting f5 changed things on or off, seemingly randomly.
I cleared host cache and cache is on moderate. Cleared IE temp files, changed to check for new content each visit. Nothing.
Set cache to none, and my site ground to a halt. Had to turn that back on.
Mar 22, 2006 06:57 PM|j7mitch|LINK
Mar 22, 2006 10:28 PM|jkhammond|LINK
1) Is this a known issue?
I changed caching to "light" from "moderate" and it seems that these problems have dropped off dramatically, although I had a report from one of my editors earlier that a few modules mysteriously dissapeared until she hit f5, so I know it still lingers.
It doesn't seem to happen on any of the "mature" pages - ie. pages that have been unchanged since before the 4.02 upgrade (i.e. <= 3.1). The only time I see this issue is when I either add/remove or even update a module on a page.
Keep in mind that I develop many of the modules used on the site (all .net 1.1 -> moving to .net 2.0 tonight).
If I see a method of reproducing the issue with a standard module, I will definitely post something.
Mar 23, 2006 11:16 AM|j7mitch|LINK
May 04, 2006 06:13 PM|IR0NMAN|LINK
May 04, 2006 06:37 PM|IR0NMAN|LINK
May 04, 2006 06:56 PM|j7mitch|LINK
This sounds like a local browser cache issue. Or possibly a proxy server that is caching.