I heard that EE 2.0 doesn’t support IE6. That’s the main reason I haven’t jumped into the newer version of EE. V1.6 works for me right now.
Bill
Bill
------Original Message------
From: Joe Muscara
Sender: email@hidden
To: Freeway Discussion List
ReplyTo: Freeway Discussion List
Subject: Re: Expression Engine 2.0
Sent: May 29, 2009 07:30
atelier’s advice is good. I know many of us like to jump on the upgrade bandwagon, myself included. Sometimes it’s wise to stick with what works at least until you’re sure the new version will work or you can take the time to fix whatever issues may come up with the transition.
As far as how EE 2.0 will affect the EE Action Suite, we will not know until we get our hands on the new EE.
Just to clarify here – it doesn’t support IE6 for access to the admin
console pages. It certainly can be used to make a Web site that IE6
can stammer over. That’s not going to change, and is certainly under
your control (choosing which sorts of wizzy effects to include, what
sort of layout structure to use in your templates, etc.). But using
IE6 to administer an EE2 site will end badly. Since that’s a
“teachable moment” for your client, it’s not a very big deal. I
actually use the GetFirefox Action on my Admin pages just to remind my
clients not to edit their site using IE (any version).
Walter
On May 29, 2009, at 10:52 AM, email@hidden wrote:
I heard that EE 2.0 doesn’t support IE6. That’s the main reason I
haven’t jumped into the newer version of EE. V1.6 works for me
right now.