Thread

We have gotten a few third party developers asking about compatibility of their current Add-Ons with ExpressionEngine 2.0, so I am going to answer some of your questions as completely as I can at this point in time.

continue…

Good to see things progressing nicely.

Will you still be compatible with PHP 4?

In this blog entry Paul is talking about that:

And so, with the release of ExpressionEngine 2.0, we will be raising our PHP and MySQL requirements for ExpressionEngine, as it is an intelligent decision to use newer, more feature-rich versions while no longer working around problems and limitations of older versions.  We have not finalized what those requirements are yet, so please do not ask in the forums because we will be unable to tell you.  I will say that, currently, we still intend to support versions of PHP prior to PHP 5, whose share of the PHP market is not even close to being high enough to completely abandon the PHP 4.x branch.

Thanks for that.

With support ending for PHP4 at the end of this year it might be a good idea to migrate.

Oh boy. Mention of 2.0. EE is great now, but there are so many features that come <<this close>> to being perfect, but just aren’t quite there yet. Thing like file handling, image handling, static pages, WYSIWYG content entry, membership templates, creating links to other pages/content from within an entry. The extensibility of the system allows a good dev to get around nearly all of these, but many of these are still work-arounds. I can’t wait to see the direction 2.0 is going - we all have a lot of dreams for an ideal system! The best part is, with so many people wanting so many things, at least some of them will surely be answered!

Keep up the good work guys - I can’t wait to see what you have been cooking up in the labs!

we all have a lot of dreams for an ideal system!

It already is the ideal system isn’t it?!! 😊 😊

I know what you mean though and I am 100% positive that they will blow us away with whatever they have been cooking up locked away in their coding dungeons!! 😉

When I first saw ExpressionEngine back in 2006 I couldn’t believe how close to heaven I had come anyway but with the promise of 2.0 and new things afoot I simply can’t wait to see what they have done now.

Waiting with baited breath is all I can say!!

ExpressionEngine crew do remember to take breaks every now and then though! 😊

Best wishes,

Mark

With support ending for PHP4 at the end of this year it might be a good idea to migrate.

PHP Version Usage Statistics for November..  Such a requirement would likely help us lose about 70% of our current market, and thus it would be a very bad idea if you actually wanted EllisLab to be around for another year.

EE is the ideal system, for me anyway. I doubt I’ll use another CMS, EE is just so easy to tweak and change that it’s awesome.

Backwards compatibility ending sort of worries me, think I’ll buy my favourite developers a cup o’joe. Or tea. Whatever. 😊

Wow. I guess I better get back to cleaning up the code for the linklist module.

Sounds pretty exciting to be talking about EE 2.0!

OK - so yesterday, when making another post, I was mulling about making a snarky comment to the effect that being a pmachine / EE user since March 2002 surely makes me more than a ‘Junior’ member.

This question makes me glad I didn’t so so. Behold my ‘junior-ness’:

Is ‘backward compatibility’ the same as ‘upgrade path’? Does this mean that 1.x EE data (weblogs, entries, etc.) will not be sucked into EE v2?

(See - even the use of ‘sucked into’ reeks of junior-ness - right?)

Les

No, it is definitely not the same thing.  Further, all First Party EE modules and their related data will be updated to run in 2.0.  I have no idea what I said to make one think otherwise.

I have no idea what I said to make one think otherwise.

Probably nothing whatsoever.

The relationship between what other people say and what I think I hear is usually tenuous, at best.

I vote for a new forum member category - “Dolt’. It can be awarded to anyone like myself who can prove that there is such a thing as a stupid question…

Thanks for the clarification, Paul.

Les

Paul - I use quite a lot of PHP in my templates, but my PHP skills are ...erm… protozoanic?

So I would not be surprised to encounter some trouble when going to EE 2.0, however ...

Do you have any inputs on what we might expect from existing template-embedded PHP when we go to 2.0?

Do you have any inputs on what we might expect from existing template-embedded PHP when we go to 2.0?

All PHP in Templates is parsed through PHP’s own eval() function, so the way PHP works will not change.  And PHP in Templates is not going away either, obviously.

However, just like there are changes in how Add-Ons are written to access ExpressionEngine’s own internals, if you are doing the same (accessing EE’s internal classes and methods) in your Template’s PHP code, then that will have to be updated as well.