Published by Mijingo

movie icon image

EE Insider Blog

Spend your time learning and developing sites with ExpressionEngine and we'll use this blog to keep you informed of all the news related to ExpressionEngine and CodeIgniter.

» Read more in the Archives.

» Have a tip? Send us your EE news.

Learn ExpressionEngine Today

Over a series of 8 videos, watch and learn as Ryan builds an entire ExpressionEngine website from beginning to end. Get started now.

Keep EE Up-to-date

In light of recent happenings in the Wordpress community, this may seem like a time to champion ExpressionEngine and do a dance. While it’s true that ExpressionEngine developers are beautiful, kinder and live fuller lives than most other CMS developers, we are still subject to the same security risks. Do not ignore the update notification when you log into the control panel.

So please take a moment and ensure that you, your clients and friends have updated their ExpressionEngine copy to the latest version 1.6.8 and that your extensions are all up to date as well. If you encounter problems with an extension and the current version of EE, please file a bug report with the extension’s respective developer. Some add-ons will notify you of new updates; a handful of developers now use Leevi Graham’s Addon Updater. If you use Solspace add-ons, they have an updater, too.

Protect yourself now.

Posted on Sep 08, 2009 by Kenny Meyers

Filed Under: News

James02:49 on 09.08.2009

I wonder if anyone is working on a one click updater for EE similar to WP’s updater. Having one or two EE sites to update is one thing, but when you have 20 or 30, updating is less than trivial.

E. Christopher Clark03:29 on 09.08.2009

This would be easier if you didn’t have to pay $19.99 a year to do it. In fact, the fact that updates are not free is one of the main reasons I’m leaving EE for WP in the near future. And that’s been a hard decision to make, because I love EE and have been a dedicated user of it (and PM before it) for years.

Richard Lomas04:59 on 09.08.2009

I actually tend to agree about the non-free updates.

I think the upgrades to 2.0 should obviously be paid, but the fact that you don’t get free upgrades all the way through the point release you purchased is very non-standard and a major turn off.

James06:24 on 09.08.2009

Perhaps I should clarify: I have no problem paying for updates at all! It helps support a crack team in developing a sound product. Furthermore, I would have no issue with my License number being verified to enable a one-click type update. Currently I use a custom script that handles the entire EE update (except the final database update) on servers that give me shell access. The sites that don’t give me shell access are the sites I would fancy a one-click web-based updater.

E. Christopher Clark08:07 on 09.08.2009

@Richard - Yes, obviously big updated like 2.0 should be paid. But I think all updates between 1.0 and 2.0 should be free/included with the initial purchase.

@James - I want to support the crack team and do so whenever finances allow. The problem is the finances don’t often allow, and that leaves me with an outdated, possibly hackable version of the CMS running my site. Maybe if there were a way to make security-related updates free and keep any new features behind the $19.99 wall?

mirkob15:43 on 09.08.2009

I hate updating the system, picking up all right folders, copy again the extension, languages, modules. I’d like to have a simpler way or at least I’d like to have only one folder where all and only ee files are stored. Third party files are store in separated folders. Any news about this in 2.0?