Tarjei Huse schrieb:
Andreas Flack wrote:
Henri Bergius schrieb:
Hi!
On Nov 27, 2007 3:58 PM, Andreas Flack
<[EMAIL PROTECTED]> wrote:
Turning the new content caching mechanism on and off doesn't have any
influence on this. Before the update, the site ran for almost a year on
2.6 without having this problem. I didn't make any changes to the
website configuration, so I wanted to ask if there where any changes to
the way cache (or expires, or whatever) headers are set or if anyone
has
any idea what else might cause this problem.
The content cache and caching headers sent by MidCOM are two different
things (though the 'content' module deals with both).
Try adding this to your style:
$_MIDCOM->cache->content->enable_live_mode();
This should kill all browser/proxy caches.
Yeah, it works, although I still wonder why this is necessary in 2.8
and not in 2.6 (unless of course if this was the default for all
requests in 2.6). Also, won't this negatively affect page load times
if the browser isn't allowed to cache anything any more?
(BTW, we could consider doing that for Asgard)
Well, ATM Asgard is completely unusable on IE6 anyways, so if this is
really the only browser affected by this issue, maybe it would be
easier just to do a browser detection in the _can_handle phase and die
with the message "install a real browser first" or something like that
:-)
Heh. I guess that policy would last until someone emails the list with:
"I have recently deployed 2.8 on a production site ... the company I did
the site for has an IE6 only policy" .
Yeah, well, I was only kidding of course. But seriously, have you tried
to use Asgard (PEAR version) with IE6? Most stuff has reduced
functionality at best or simply doesn't work at all, and the CSS has
numerous glitches that make some pages quite unusable. So, until a brave
soul with an IE6 installation and some free time on his/her hands looks
at this, IE6 effectively cannot be used for Asgard.
BTW: IE7 has a few problems with Asgard as well, but from what I can
tell, the number of things working is greater than the number of broken
features.
As web-developers we'll have to deal with IE6 for at least two years
more. We could add a warning to Asgard (you are using an insecure
browser) but in the end we'll need to have an if_ie6() function to make
sure that Asgard works for IE6 as well.
Even two years seems wildly optimistic. From what I read (and see on
people's machines), IE6 is still one of the most popular browsers, as
incredible as it seems. F.x.:
http://www.thecounter.com/stats/2007/November/browser.php:
48% IE6
32% IE7
13% FF
http://www.w3schools.com/browsers/browsers_stats.asp
34% IE6
21% IE7
36% FF
http://www.xitimonitor.com/fr-fr/barometre-des-navigateurs/firefox-septembre-2007/index-1-1-3-110.html
66% IE, 1/3 of which is IE7
27% FF
So, one could argue that MidCOM is only fully usable on one third of the
browser software that's out there and in use. In conjunction with the
fact that it only runs on LAMP and needs root access (or some
equivalent) to the server for installation, this makes it kind of hard
to sell to technically interested customers (but maybe I just haven't
found the right pitch yet :-).
Fortunately, there are those who don't care about theses issues or even
know what the consequences are, but unfortunately they are the same
people to who you can't really explain that their browser is at fault
and not the server when they see wrong data (from stale caches f.x.).
If you work with larger firms, this is especially problematic, since
they are (at least the ones I know in Germany) almost always exclusively
on IE6 and corporate IT usually completely locks up the PCs, so you
can't even tell your customers to install FF and use it if they want to
do administrative stuff on their website (and even if it was possible
it's IMHO a bit too much to ask that they install a new application just
to maintain some intranet website that'll have 100% IE hits anyways).
So, yes, I agree that IE6 has to be supported, but from my perspective,
IE6 and Midgard has been a problematic combination for anything
developed after Aegir. My workaround has so far been not to use anything
AJAX: It's nice and shiny, but also slow and hard to debug, and you
have to debug everything because it never works out of the box on IE6.
This worked quite well so far, or at least up until 2.8 and the cache
header problem...
Sorry if this sounds a bit like a rant, I guess I had to explain how to
empty browser caches to too many people the last few days :-)
Bye,
Andreas
Regards,
Tarjei
Bye,
Andreas
Andreas
/Henri
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user
