Discussions What are your hopes for EE2.0?

Jamie Pittock / 28th January, 2009
EE2.0 is coming! Lockdown is here. Drum roll everyone…

Seriously, during the last quarter of 2008, things went a little crazy. Every other thread on the ExpressionEngine forums (I exaggerate slightly) seemed to be someone asking, yelling, pleading, prophecising something about the upcoming release.

Thankfully this year so far it seems that someone (Leslie?) has managed to sit people down, grab them by the shoulders, and very slowly and calmly told them that everything is going to be OK. Everyone’s breathing seems to be back to normal again.

What is it that we don’t have now but we think we’ll have once EE2.0 is out? What is it that we’re all hoping for?

In my mind 2.0 is all about the move to CodeIgniter. That might be a really obvious thing to say but this whole process, the time, and the money EllisLab are spending on this, is all about getting EE on to this new codebase. If the dust settles and I find out we’ve got the same thing as before only this time we’re on CodeIgniter then I’ll be very happy…because I know that’s where the fun starts. Where we go from there is the really exciting bit. EE2.1 is where the really cool shit is at!

But back to now…

If I had to pick one I’d say when I upgrade or install EE2.0 I’d love to be able to just create one variable for my server path and use that throughout the control panel and add-ons. All upload, template, theme, image, add-on paths would all use it. That’s it. I’d die happy for just that one thing. Being able to create different environments for my configuration based on development, staging, and live setting would be the icing on the cake.

So come on then, let’s have it. What are your hopes for EE2.0?

  • Jamie Pittock

  • Jamie is a designer of the internet and spends his days building websites and walking his dog.  He’s running a workshop at this years FOWD London titled “Building beautiful websites with ExpressionEngine” which you should definitely try and get to.  If not you can find him talking shit micro-blogging on Twitter

Comments

  • Site wide server paths and entries listed by categories with custom fields would be nice :)

    Oh yes did I mention a proper file manager? That too.

  • Jamie,

    First off, its great to see Jambor-ee back! Second, you’re really spot on with this article. One of the planned EE 2.0 update posts is tentatively titled “what to expect” and covers a lot of the information you bring up here.

  • I’m definitely with Jamie on the need for a single configurable server path that updates everywhere. For now I make use of dEEploy helper, which at least gets everything onto a single page.

  • I hope for a easy way to customize the look&feel; of the backend…my clients always complain about the unfriendly interface…they look for an easier way to publish their information.

    Finger crossed!

  • For those of us who want to use EE on the majority of the projects, I think an easier, customisable way of setting up an EE site that can then be rolled out for any new install. I guess having a CodeIgniter backend should make it easier for this to be written, but I’ve always found it a pain to have to upload extensions/modules/plugins for each site I do.

    Speaking of which, a function whereby extensions and modules can call home to check whether or not a new version exists (similar to the way WordPress does it) would be great too (I know the LG extension exists for this, but I think this should be part of EE’s core, out-of-the-box functionality).

  • I’d like to see member profile templates and data fully integrated and compatible with the main templating system.

    That and a more semantic approach to ‘out-of-the-box’ markup.

  • Just being able to add images, attachments and links to a text area without feeling like you have to hack into government servers would be nice.

  • Nice to see you back!

    I think making the editor stuff easier on clients would be great. So, making file and image upload easier, adding links, and all that other stuff easier would be awesome.

    Also agreed about the path issue. Setting that in a million places is a pain. I always forget one or two.

  • Ditto your call for one system-wide server path variable.

    Other than that, I’d love the Pages module to get a bit of work – preferably:

    • tags for nested menus, breadcrumbs, etc.
    • reordering of the pages in the back-end
    • add page under this one

    I know these kind of things can be done using third-party extensions, but I really would like it out of the box.

  • Better group handling would be great. Specifically being able to assign a member to multiple groups. This single feature would solve so many problems in using EE for many different kind of member driven sites.

  • A one-click new version update would be fantastic (following wordpress’s lead)!!

    Ditto for better file upload management for clients’ usage. In fact there are a few basic enhancements to the CMS which really benefit clients, that I’m currently having to install plugins for each time. I really think these should be built in to the basic EE install E.g. Publish improve, Tab forward, Add Sitename, Edit menu, MH File.

  • A mobile version of the backend would be great!

  • ExpressionEngine 2.0 will be released when its done! However, the release will not be a surprise. Currently we plan to release 2.0 in three phases. First, there will be a Developer Preview for EE Add-on Developers. The primary purpose of this release is to give EE add-on developers the time they need to update their add-ons for 2.0. Second, there will be a invitation beta. The purpose of the beta will be to stress test 2.0 in a wide variety of situations. And third will be the official public release.

  • Здравствуйте друзья!
    Хочу представить вашему вниманию один очень популярный сайт в рунете – gi-gi.info
    На нём Вы смотжете всегда увидить свежие приколы , анекдоты и многое многое другое :)
    Желаю приятного просмотра ;)

Comment Form

  • Should you care, Gravatars are enabled.

  • We will link to the URL but we utilise the 'nofollow' attribute value.

  • pmCode is disabled. Textile formatting is available. Code blocks should be wrapped with <pre> and <code> tags. Always play nicely.

Advertisment (Want to advertise here?)