Thread

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.

Makes perfect sense, and is reassuring to boot - thanks.

Heh, I hope I’m on the right path, I adapted CI’s active record class to EE because I figured we would get something like that in 2.0—and thus, multi-DB capability.  So is this a good idea for future proofing plugins, modules, etc?

I believe I answered that with the my reply to the “Any hint at what changes are being made in ExpressionEngine 2.0?” question in the main entry.

All that aside, the next release of CI is having Active Record expanded a bit, so I would not mind seeing what changes you have made.

*shrug* my changes probably aren’t too major.  I just grabbed the mysql driver and put most of it in the active record driver, along with the db driver parts that were relevant.  Changed the querys to call EE’s DB class (so it could keep the EE logging, etc.).  Since the db driver extends the mysql driver, most of the method calls didn’t even have to change. 

I didn’t innovate anything unusual, if that’s what you are asking.

Oh, darn.  I was hoping you had put in every kind of JOIN and perhaps had some CREATE TABLE magic in there.  Man, you got my hopes up…

Heh, no, though I DID use an older version of the active record join command, the current one is buggy.  There was a thread on that long ago I pointed it out in the CI forums, I hope the next version of CI fixes it. 

That said, if you’d like, I could take a whack at adding all that in.

I believe D’Allard has seen that thread.

No, I think you should be fine as I have great faith in the power of the name “Derek”.

I’m curious to hear what kinds of features people are asking for. Is there a definitive wishlist somewhere?

I find it hard enough to keep up with new features that keep getting added, so I haven’t had enough mental energy to think about a wishlist.

Feature Requests is the only list made public and if past releases is any indication, Ellis Lab does pay attention to that forum.

[Post removed by the CTO as it had absolutely nothing to do with Third Party development and was a combination rant and feature request.]

This will be interesting.  I suspect that many people will not be able to upgrade right away as developers get their code caught up (or perhaps some items never will get updated.)  For instance, many of the sites I have worked on rely on Solspace modules.  None of those sites will be updated until Mitchell gets around to updating them.  If he is extremely busy at the time, who knows how long that will take.

Even more of a pain will be modules that are created by solo developers are not available to the public.  If I want to upgrade on a site with my own module then I will have to upgrade the module as well.  This could create quite the backlog for people in this situation. 

This may not be a concern as I am not one to rush to new versions just to have the latest and greatest.  But the problem might be in support issues.  The support policy of the forums is that users must be using the latest version.  If users are not able to upgrade because they are waiting on updates from developers then will they still be able to receive support?  Will the last 1.x EE release continue to be available for people who heavily rely on modules waiting to be updated?  Will security vulnerabilities be fixed if found in 1.x?

This is probably more doomsday than will actually happen but it could create some problems.  I also believe that these are acceptable issues for a better system and developers simply need to update or the modules discarded but the reality is that not everyone will be able to upgrade right away.

Also, will the developer preview be available to everyone?

Many of these questions will be answered at a future date, John.

Thanks Paul, Ellislab has never done us wrong and Rick seems to have super powers for anticipating developer issues.  Not too worried about it.