-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Andreas Flack wrote:
> 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.

There used to be a simple .htc (this one I think:
http://dean.edwards.name/IE7/ )  file for fixing IE5.5 and IE6 css bugs.
 Would you mind trying the one mentioned above or another file like it
and see if the worst bugs are gone?

> 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.
These glitches should be added to the Trac - preferably with suggested
fixes or - if you got time - just fix them in svn.
<snip ..>
> 
> 
> 
> 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 :-).
I agree that it is a problem that we do not have a testversion of
Midgard/MidCOM that is installable for a user.

<snip..>

> 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 :-)
Life's hard, then you have to fix IE6 bugs.

Regards,
Tarjei
> 
> 
> 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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHTYeyYVRKCnSvzfIRAmCOAKClafU+zQds9+DCVRXMxbfSSDu8ngCgpbxF
FcRzIMGt26QSj/M/BDzQcvg=
=lA/3
-----END PGP SIGNATURE-----
_______________________________________________
user mailing list
[email protected]
http://lists.midgard-project.org/mailman/listinfo/user

Reply via email to