ExpressionEngine 2.0 is built on CodeIgniter.

CI 1.6.0 Changelog…

MySQL driver now requires MySQL 4.1+

Guess EE 2.0 requirements will also need upgraded from MySQL 3.23.32

CodeIgniter requires 4.1+, so it’s very likely.

Doesn’t anyone know that ExpressionEngine 2.0 is being developed in Australia?

Don’t you wish
Hm, perhaps they meant Austria? You know we get confused a lot

Ingmar Greil - 16 July 2008 04:55 AM

Don’t you wish
Hm, perhaps they meant Austria? You know we get confused a lot

Well summer starts in December and ends in February here

Just thought I’d give you guys a little extra time.

Who said anything about Earth summers?

I wrote:

CI 1.6.0 Changelog…

MySQL driver now requires MySQL 4.1+

Guess EE 2.0 requirements will also need upgraded from MySQL 3.23.32

inparo - 15 July 2008 10:42 PM

CodeIgniter requires 4.1+, so it’s very likely.

CodeIgniter has a work around -> Seems MySQL 3.23.32 can still be used with CI 1.6.x

Wonder if this might still work with EE 2.0

<update> Guess need to switch to a different host.

Derek Jones - 16 July 2008 11:33 AM

Who said anything about Earth summers?

I knew the dev team were all aliens otherwise how could they bring out such an awesome product!

Just as long as you aren’t from either Neptune or Pluto or Summer could be really really long!!

Keep up the great work though, your interplanetary friends here are looking forward to this one and we know that whatever you come up with will be totally awesome!!

Best wishes,

Mark

To be honest, I’ve always read the projected release date of “summer” as “October at the earliest”. I’ll be pleasantly surprised if EE2 ships earlier, but if it’s fall or winter it’s no big deal to me.

EL doesn’t have a history of releasing on a public schedule and I don’t know what internal deadlines there have been—other than EE 1.6.0 and MSM if I remember correctly, which was pushed out the door in time for SXSW 2007. I also recall that EE 1.6.0 had a flurry of build updates, seemingly more so than any other release. What I’m trying to say here in a rather clumsy way is that while I’m fully prepared to be an early adopter and take my chances, I’d rather if EE2 misses a self-imposed deadline or two and ships as solidly as possible than have it ship on time and be a mess.

Ditto that sentiment completely!

Mark

+1

Rick,

You’re killing me.  You post a “sneak peak” to get us all excited… I’m squirming in my seat, and just give us something!  Just slap something together and give us a Beta.  The anticipation is killing me!

          Mark

elwed - 16 July 2008 01:41 PM

To be honest, I’ve always read the projected release date of “summer” as “October at the earliest”. I’ll be pleasantly surprised if EE2 ships earlier, but if it’s fall or winter it’s no big deal to me.

Well summer is gone.  September is gone.  October is gone.  Thanksgiving is just around the corner (tomorrow?).  Rick, I’m going to be knocking on your door soon!

Could we make EE 2.0 an early Christmas present?  My birthday is in December…

elwed - 16 July 2008 01:41 PM

I’d rather if EE2 misses a self-imposed deadline or two and ships as solidly as possible than have it ship on time and be a mess.

I’ve always been an early adopter.  I’m a pioneer… Give me a Beta, and let me find the bugs!

        Mark

when i saw an e-mail from Expression Engine in my mail box i was like OMG 2.0 out
but it was the Expiry e-mail >_<

Make it Christmas present to all members ..

now i’ll go to renew my account

My bits goes to the first days of 2009, just to start good a new year.
EllisLabs team likes comemorative dates (remember the 2008.08.08 release? - best luck day to chinese people and the screencast of EE 2.0 like 2008.04.01, Fool’s Day)...

So, i think with in the Christmas or New Year Day we will have it nice news (i hope)...heheheh

I have to admit that I’m getting a bit disappointed by the delay and the lack of an estimated ship time. There’s a toy project I have in mind for which EE2 would probably be a perfect fit. I suppose it could be done with either EE1 or CI, but the real winner would be EE filling the gaps for CI.

I saw some real improvements to the Admin UI in that video, but there were some really important things that were left untouched. It doesn’t seem that your user research has involved editorial people and non-tech-savvy site owners too much (or maybe I am being presumptuous?). These are our clients who hire us to build their websites.

A basic example is nomenclature. Names exist that may have relevance to engineers, but not to end users. How do you keep an entry from being published”, you mark it “closed.” Why not just have a “publish” state? Also the use of the word “weblog” is very confusing. Even those who write your tutorials have noticed this, as they make reference to it:

Note: In our user guide and throughout the program you’ll find the use of the word “weblog”. If you are not using EE to manage a weblog then simply substitute the word “section” for it instead. A “weblog” in ExpressionEngine can be thought of as a “section” of your site.

http://expressionengine.com/docs/overview/weblogs.html

Then why not just change “weblog” to “section” in the UI?

In EE you have made a tool that is really developer friendly, and that is important. But you really need to look at how this UI fits into the workflow of the end users, editors and site owners—our clients. In choosing a content management systems for my clients, it is crucial that I select a system with an administration UI that really pays attention to them. Based on the 2.0 preview video, EE still has a ways to go to achieve that.

MikeQué - 17 December 2008 08:48 PM

A basic example is nomenclature. Names exist that may have relevance to engineers, but not to end users. How do you keep an entry from being published”, you mark it “closed.”

It is your task as a developer to create an environment that your users are comfortable with. If you want to use a custom status, that is easy to do, for example.

Then why not just change “weblog” to “section” in the UI?

Why not indeed? There is an option to do just that. That said, “weblog” will change to “channel” in the near future.