Thread

ExpressionEngine 1.6.7 has just been released, a security and maintenance release that is recommended for all users.  We want all of our users to know that we’re committed to continuing to support 1.x even as our efforts are thrust fully into 2.0.  ExpressionEngine 1.x is a platform you can continue to use and rely on now and in the future.  To that end, at this late cycle in its life come two new extension hooks that will give even greater power to third party developers wanting to do things with the bread and butter tag of ExpressionEngine, the weblog entries tag.  Additionally a long-standing feature request of making {parent_id} available for category tags has been fulfilled.  Many bugs have been fixed, and an important security update is included.  We will continue to provide updates to the 1.x product line as necessary to keep our high standards of quality, because we know that you have many important clients using it (including yourself!), and will for some time.

See the Change Log for full details on this release.

Permalink

thanks for your efforts, at first.

i personally am not mentally engaged into 1.6.x anymore. i use it, it works very well (as it did the last years) - but i never would buy any extension for 1.6.x, recommend 1.6.x to anybody or relaunch my site with 1.6.x. this would be an anachronism in my opinion.

Hi Derek,

Thanks for the updates. I for one am very very appreciative of the fact that you are still updating and placing a lot of time and effort into the existing branch of ExpressionEngine. To be working on this and the new version at the same time is a remarkable feat and not one that goes unnoticed.

Brilliant work guys, thanks.

Best wishes,

Mark

thanks for your efforts, at first.

i personally am not mentally engaged into 1.6.x anymore. i use it, it works very well (as it did the last years) - but i never would buy any extension for 1.6.x, recommend 1.6.x to anybody or relaunch my site with 1.6.x. this would be an anachronism in my opinion.

EE 1.6 is an excellent product and new sites are launched on it everyday. Given its broad user base, 1.6.x will have a long life even after 2.0’s release. It would be irresponsible (on a grand scale) for us not to support it.

The paradox is that you recommend it even while not recommending it, i.e. “it works very well” yet people shouldn’t use it? Don’t get me wrong, I understand where you’re coming from, we just disagree. Fair enough 😊

The two need extension hooks are fun but i would prefer a better one: weblog_entries_query (or weblog_entries_sql). So you can fetch data based on custom filters.

That’s a bit too close to the gears, as it were.  And of course, you can always build a module that takes advantage of the weblog module’s tags, but build the query yourself - that’s essentially what the search module and weblog calendar tag do, though they still use the weblog module to do so.

Could you elaborate on what this item from the changelog means? Thanks.

* Tweaked XHTML Typography to handle some edge-cases.

Could you elaborate on what this item from the changelog means? Thanks.

* Tweaked XHTML Typography to handle some edge-cases.

Things like this bug report and a few other esoteric tweaks when content is entered a certain way.

EE 1.6 is an excellent product and new sites are launched on it everyday. Given its broad user base, 1.6.x will have a long life even after 2.0’s release. It would be irresponsible (on a grand scale) for us not to support it.

Hi Les,

I understand that your response to my upcoming question is necessarily going to be a little vague, as there are a lot of variables involved, but when you say that 1.6.x will have a “long life” after the release of 2.0 - what sort of ‘long’ are you talking about? 😊

Long as in, say, a couple years top? Or long as in, say…five years?

Also, I’m assuming that when you say that you will continue to support 1.6.x , you are, mainly at least, talking in terms of security patches? Is that correct?

I understand that your response to my upcoming question is necessarily going to be a little vague, as there are a lot of variables involved, but when you say that 1.6.x will have a “long life” after the release of 2.0 - what sort of ‘long’ are you talking about? 😊

Long as in, say, a couple years top? Or long as in, say…five years?

Also, I’m assuming that when you say that you will continue to support 1.6.x , you are, mainly at least, talking in terms of security patches? Is that correct?

We plan to support 1.6.x as long as its the responsible thing to do. For example, we supported our former blogging application pMachine Pro for over 3 years after we stopped selling it. This included technical support, bug fixes, and security updates. The last to go were the security updates. After some years the need to support it simply ceased and finally security updates weren’t needed either, at which point we officially retired it.

We plan to take a similar approach with 1.6.x as well.

Thanks for the continued support and hard work on EE. The class here in San Antonio took a moment to look over the new release post. Keep it up and Thank YOU!

…at which point we officially retired it.

We plan to take a similar approach with 1.6.x as well.

Makes me feel quite sad when you say it like that Leslie 😉

I know we are getting a much great beast in 2.0 but still feels like we will be losing a very close friend.

…at which point we officially retired it.

We plan to take a similar approach with 1.6.x as well.

Makes me feel quite sad when you say it like that Leslie 😉

I know we are getting a much great beast in 2.0 but still feels like we will be losing a very close friend.

I think 1.x will be around a long time post 2.0, so no need for sadness yet. EE’s install base v. pM is significantly larger… not just by a little bit.

We plan to support 1.6.x as long as its the responsible thing to do.

Good news. Thanks.

For example, we supported our former blogging application pMachine Pro for over 3 years after we stopped selling it.

Ah ... That triggered waves of happy nostalgia.  😊

ExpressionEngine 1.6.6 - © Copyright 2003 - 2008 - EllisLab, Inc.
Script executed in 0.4503 seconds   10 SQL queries used
Build:  20090122

...??? Who should reupload files…? Me or EE?