Thread

Hi,

Not meaning to rock the boat, but we’ve just purchased a brand spanking new copy of EE2.1 (after building 5+ sites using EE1, including building custom modules etc) and most of us at the company are feeling slightly disheartened about the product to be honest.

I was the most excited about the leap to EE2, as I mainly deal with the front-end section of our sites, and wanted to get to grips with the new control panel and the other features baked in to EE2.

Unfortunately, this has not been the case.

We are currently working on one of our most high profile, and probably our biggest site we’ve done, and thought that now that EE2 had a final release, it would be a great time to showcase not only our talent but also EE2 as a platform for stability and security.

Instead, myself and our module developer have had nothing but headaches. The things that EE2/CodeIgniter does well, it does them incredibly well, but then there are things that make you think, “woah, why did I just fork out $250 on this?”. Today, we had to have a long and hard think to decide whether we stick it out or go back to 1.6.9 for this project. That shouldn’t be a decision we have to make.

For example, why can’t I rename a Field Group without having to manually rename it in the database? Why, when having Daylight Savings Time on, and editing a channel entry, does it change the time 2 hours ahead? Does EllisLab hate people who observe DST?

We’re massive fans of EE here, and really want to move forward with 2 rather than 1, but feel EE2 is not quite ‘production ready’ yet.

Would love to hear others’ thoughts on the subject,

Thanks!

Hey Rob!

We’ve notice a few “quirks” in 2.1, as well. The most annoying one for us has been the issue of the time automatically jumping 2 hours ahead each time we edit an entry.

Some of the issues that you’ve indicating, I believe, were meant to be corrected in the newest build, which was released today, actually. I haven’t installed it yet to test it, but I know that EllisLab is working hard to iron out bugs as they crop up.

We’re getting a few EE 2.1 sites put together for production now. Yes, there are a few bugs, but I have yet to encounter anything that is more than a minor annoyance. So far, nothing has been a show stopper for me, and since I know EllisLab works hard at fixing these issues, I’m not concerned about putting EE 2.1 to use in a production environment.

Lance
Green Egg Media

I’m currently on my 4th 2.1 site (one of those is a 3 site MSM jobby) and there’s been nothing major that has got in the way. Sure there are some minor niggles like the 2 hour jump but they will be fixed in due course.

By now for me the benefits of 2.1 far outweigh the 1.6 branch unless it’s an extreme case like needing an addon that hasn’t been ported to 2.1 yet.

Thanks for the replies guys, it’s good to know that other people are using 2.1 for production projects and that you haven’t brought up any more evil bugs like the 2hour jump.

Onwards and upwards, as they say!

I’m in the same boat as the rest of the guys - I’m working on my 6th EE 2.x site (previous 5 have been built on the beta version) and none of had any issues. The only issues I encountered, which have all been fixed up to now, was the image pre-code that wasn’t working in beta and then recently the 2 hour jump difference.

All my clients, and their end-clients, have been extremely happy using EE over WordPress or Joomla!