Users can create a module, say a Text/HTML, have it appear on the page, then click the Edit Text link and not only does the edit screen not show up, the entire module has disappeared. Press Ctrl-F5 and *maybe* the edit window shows up, maybe you have to refresh again. Okay, edit window appears, you make your edits, click update. Page loads - maybe no module at all, maybe module - pre text entry state, maybe everything's okay - it's a crap shoot. You get pissed off and finally get to the settings screen for the module. You click delete. Page refreshes - guess what? module is still there - but not really - because when you refresh the browser, the module has gone away.
Another favorite trick of my server to play on my admins is "batch the add commands". In this trick, the admin adds a module, the page reloads sans new module. The admin assumes they screwed up and tries the operation again. This time TWO modules! Lots of fun!
This is just an example of the wackiness that is driving my portal admins (and me) nuts. I'm quite sure it's not a client issue because my admins are geographically distant, on seperate machines, running all different flavours of browsers, but we're all experiencing the same pain (and all wanting to make me walk the plank!).
I've tried tweaking down the server caching to "light caching" but to no avail.
One thing I haven't thought of until now is the IIS compression. I went through the hoops of turning on IIS compression quite a while ago and the portal HAD been wroking fine with it on... however I'm curious if any of you other people in the same situaiton have turned on IIS compression. If we are going to track down the culprit for this problem, I think we all need to find someting in common with our installations.
Any new thoughts?
Marc
*bump*