Thread

Ah I see, my mistake… Must have downloaded it just after release, I installed right about a day ago…

Hence why i was concerned there was 2 versions of the same build 😊

Hello, all,

I apologize for the difficulties that you are encountering with the beta.

With that said, this is a beta release - it is out there, not for live sites, but for those that want to test out the system, offer feedback, and see what is going on.  It is also there for add-on developers to see if their add-ons will work and make any necessary changes prior to 2.2’s stable release.

We release this as a beta specifically so that developers have that time - if you are updating live sites with those add-ons, then that is discouraged, for sure, due to the beta status.

We are working on having an 8 week release cycle which will also include developer builds that add-on developers can use to test their add-ons work as well.

I hope that helps clarify about this release.  We certainly did a lot of testing on this, but you must always be careful with a beta release.

Let me know if you have any questions.

Tested upgrading 2.1.4beta (latest build) to 2.1.5beta and got similar problems as well as memory issues (local development machine)
Disabling all extensions and then re-enabling them seemed to get rid of the Matrix error I got.

Got a PHP Fatal error when clicking on Structure 3.0.1 module (Add-ons > Modules > Structure)
Got a PHP Fatal error when trying to edit an entry, this time the error refered to the Channel Images Add-on
The same error as mentioned in the first post of this thread + memory issues

Rolled back to 2.1.4. No problem, I knew 2.1.5 was a beta and had backups in place.

Honestly, Lisa, I have tried to keep a quiet point of view on this, but just wasted 2+ hours on a Saturday doing a trial update of 2.1.5, after waiting; and then using what is supposed to be the silently cleaned up version.

It is a complete fail: Matrix will not work, and apparently Structure either. Moonbeetle is as usual quite correct, and nice enough about saying it.

A developer’s release is surely what 2.1.5 is, not a beta. In fact, reading between your lines and the act of producing it, it is a force-the-developers release.

Even the source code says it is intended to force errors. Nice, for everyone trying to actually use it. And you gave no up-front warning at all.

This kind of thing has no business being presented for the many advanced EE application shops who may try it to help Ellis validate and tune its actual advances, much less all those individuals who are quietly and loyally trying to help you get through a patch of problems and needs.

While I am at it, I must feel it is clear that _NO_ release should be silently or otherwise re-released, without notification and a change at least of build numbers. Can doing this actually make any sense to those of you within Ellis, any of the times you have done it? If so, please put on the other hat, and think if it were done to you.

It’s very nice to hear how things are going to be all better. It’s very hard to understand how it takes months and months to engage a simple open-minded practicality which will avoid this kind of result, prior to the ‘official’ result.

To release with Sue saying, ‘Oh, we didn’t test on Matrix, etc., and we’ll be sure to do that in the future.’; well, that is rather remarkable.

I’m sorry if this seems harsh, and you may know I’m long-lived enough to understand any level of internal difficulty, personal error-fatigue, results of politics, etc.. So are others, clearly, and all try to help in the ‘family’.

But please do not do this again. Please do make some arrangement in a timely manner for 2.1.5, if you want at least some of us to pay attention in future to betas.

Regards, and yes, I am disappointed, this time.

Clive

p.s. I did consider that somehow the original release is stuck unchanged in a proxy some place, and so that I have been fighting with that, rather than the unofficial re-release.

But if so, that doesn’t change the basic premise you operated under in trying to force developers at the expense of the much wider community involved with betas; and it surely underlines why you must not silently re-release changed code.

Hi, Clive -

This is the last beta, we will be moving to developer builds, so it should not be an issue again in the future.

Again, this is not intended for mission critical or live sites, so please do bear that in mind when installing. 

-Lisa

p.p.s. Just so you know, yes, I did look into the ‘technical’ aspects behind this change, and there I really as well as silently shake my head.

ExpressionEngine is an application software system, and it really doesn’t do, to just change things about how it works in a way that breaks partner code, because some software ‘principles’ seem in danger. I will assure that there are always such ‘principles’ around, and that the game in many of them is simply puritanical boundary-defending.

I will also submit that a far more sophisticated use of intellect in software is to architect patterns of adaptation. In this case, there appears a very awkward situation built into the new-form EE2 which keeps it from enjoying the full usefulness of having CI present. Fine, design an adaptation. And don’t waste the time preventing what resourceful others have done to avoid barriers while you took the time to do this.

Is that enough said, for those who put forth their name and who didn’t, on creating this present situation?

If so, I submit that the same applies to all those ‘make a feature request’ denials of bugs, where the real bug is in the result of the coder choice, rather than whether the code ‘works’ as written.

If you want to be more than a ‘coder’, please think about the larger surround. That is where architects as well as exuberant architectures arise, full of vitality; where one moves into far more satisfaction and capability in our world of things, world of experiences, and world of persons.

p.p.p.s: Yes, concept changes and boundaries can be very important indeed, in getting those advances in real ability and results that we all enjoy. But again, let those come by adaptation, not by trying to force whole communities to do just what you say; to turn on a dime. Give their individuals the chances to do for themselves, on merits and in their needed time, and you’ll be really surprised, how much they engage and support what you’ve intended to give them.

Hi, Clive -

This is the last beta, we will be moving to developer builds, so it should not be an issue again in the future.

Again, this is not intended for mission critical or live sites, so please do bear that in mind when installing. 

-Lisa

Lisa, I do hear you, and clearly.

Yet, it is nothing to do with ‘mission critical or live sites’, when packages which are basic to development—and to Ellis Labs economics—are shut out of working.

Things are relatively quiet, so far. I wish for your sake that fixes get in, so they stay that way.

Personally, regards, Lisa. It’s your week-end too.

Clive

Hi Clive,

Thank you for your feedback and be assured that it is not falling on deaf ears. I’ll go ahead and close this thread now.

Cheers

Greg