Thread

Well, we really blew the “last of the old EllisLab releases,” aka the April 7th ExpressionEngine 2 release (2.1.3 and 2.1.4 Beta 20110406 builds). As the Product Owner of ExpressionEngine and on behalf of our entire team, I’m sorry this got into the wild and is causing problems for you. Its a great example of why we’ve changed our entire release process.

Here is what happened: There was an issue in the build script that caused the actual release to differ from the internal build.

Here’s what we’re doing to fix it and what you need to do to keep your site stable right now:

1. Current EE2 downloads in the store have been rolled back and are stable builds. If you need a copy of EE, the ones available are good (the prior release).

2. We’re manually rebuilding the EE2 release and giving it a test run this afternoon. If all goes well, we’ll have the new builds released tomorrow or earlier. We’ll update here if they are not ready for some reason.

We will update the blog as soon as the problem has been resolved along with sending the info out on Twitter.

So what does this mean in terms of current builds on this version?
Should they be rolled back, await another build update?

I have only one upgraded to this, so not too bad, but glad i did not have more!
Thanks, N

I did one site update to the new 2.1.3 build on Saturday, after the hot-fix was added to the distribution, and I can’t reproduce the errors in the members area. It’s an MSM install with three properties and it appears to be stable, but I would love to know if there are any files I should be replacing before my client stumbles on to some errors in the CP or the sites.

Please do keep up in the loop.

Hang in there Robin, you’ll get us through this one!

I’m pondering what I would do in the same situation.  I just checked and it looks like a fair number of files (well over 100) were affected.  When the repackaged versions go up, you will want to do a regular build update, not attempt to replace individual files. 

The types of issues- well, here’s an example: Non-existent class: Functions- that’s a case of a. a reverted file; b. a file with an incorrect permission on it.  Depending on your sever setup, the file permission quirk might have no effect (as I suspect is the case).

Basically, the build script didn’t handle branches well, manifesting in quirky file permissions in some spots and out of sync code in others.  I… would probably roll back a live client site.  It is just a build update, so there are no database issues and those are quick to do. 

Anything personal or not live?  I would wait.

And thanks for understanding 😉.

Unfortunately, this site was in 2.1.1 so I can’t roll back to a previous build.

Since the sites are up right now, I think I’ll wait for the new build of the new build (redundancy anyone?).

Thanks for the update Robin!

The new builds are up, now. You can grab them from My Purchases right now. I’m closing this thread to keep things focused. If there are new issues or if you want to comment on anything related to the build/release, I invite you over the new thread to do so. Thanks!