Thread

Sooo ... how did a beta get out the door without being tested with hugely popular add-ons like Matrix and Structure?

Yeah its not the best case scenario thats for sure… espescially after the last rollback

Any news on this yet? seems to be quite an issue, since lots of third party add ons are not working with this new beta version…

Hi, all.

We released a new build a few hours ago that was minimally tested with Matrix. I don’t have Structure so I don’t test with it. We do notify some third party devs ahead of time that a new beta is coming.

I’ve also tested with CP_Analytics, and it’s working too.

As we beef up our testing suite, we’ll start adding in more third party apps, and we’ll add Matrix installs to our regression testing.

Thanks in advance for your patience as we beef things up.

Thanks Sue… will grab it and see how it goes with the addons i have on my sandbox.

Sounds good.. We’ll be here.

Hi Sue… grabbed the (new build) but it seems to say the same in the CP once installed..

2.1.5 Build 20110510

Did the build number not change?

They didn’t change the build number…

Just checking through… problems with

Code Pack

Fatal error: Cannot access private property EE_Loader::$_ci_view_path in /Users/briancoult/Sites/sandbox-ee/manage/expressionengine/third_party/bridge/lib/addon_builder/addon_builder.php on line 948

Freeform

Fatal error: Cannot access private property EE_Loader::$_ci_view_path in /Users/briancoult/Sites/sandbox-ee/manage/expressionengine/third_party/bridge/lib/addon_builder/addon_builder.php on line 948

User

Fatal error: Cannot access private property EE_Loader::$_ci_view_path in /Users/briancoult/Sites/sandbox-ee/manage/expressionengine/third_party/bridge/lib/addon_builder/addon_builder.php on line 948

Also issue with CartThrob tooo…

Fatal error: Cannot access private property EE_Loader::$_ci_view_path in /Users/briancoult/Sites/sandbox-ee/manage/expressionengine/third_party/cartthrob/libraries/api/Api_cartthrob_payment_gateways.php on line 206

After changing

private $_ci_view_path; // deprecated, in here to force access errors
to
var $_ci_view_path; // deprecated, in here to force access errors

in /system/expressionengine/core/EE_Loader.php

as a temporary fix, it solves the issues, but when I edit any fieldset fields, I get a bunch of notices and warnings. This happens with all fields, even the out of box ee fields. The page loads, and the text and file field types seem to work fine, with their options displayed at the bottom.

Turns out it’s caused by matrix;

Temporary fix, to get going until a matrix update is released

/system/expressionengine/third_party/matrix/celltypes/file.php:

replace
form_dropdown(‘content_type’, $data[‘field_content_options_file’], $data[‘content_type’])

with
form_dropdown(‘content_type’, array(‘any’ => ‘Any’, ‘image’ => ‘Image’) , $data[‘content_type’])

/system/expressionengine/third_party/matrix/celltypes/text.php

replace
array(lang(‘content’), form_dropdown(‘content’, $data[‘field_content_options_text’], $data[‘content’]))

with
array(lang(‘content’), form_dropdown(‘content’, array(‘any’ => ‘Any’, ‘integer’ => ‘Integer’, ‘numeric’ => ‘Number’), $data[‘content’]))

Im a bit concerned really that a build is released without some form of proper testing, or at the least sent out to the thirdparty add on developers to test. I could understand if it was certain obscure add ons that had problems but not the likes of things such as

Matrix
Playa
NSM Add on Updater
FreeForm

which are widely popular and well used add ons… also what was the reasoning behind releasing another build a few hours later and not changing the build number?

To be honest, feels like im testing this for you at the moment 😊

True,

But besides Matrix, all the addons you mentioned didn’t cause any issues on my end… and I have many other add ons: CP Analytics, NSM Addon Updater, MSN reports, a few solspace add ons, devdemon add ons, and a few more obscure ones…

Matrix was the only one that caused issues on my end.

It looks like Sue tested with Matrix; for all I know, EllisLab might have tested with addons, maybe just not the same versions…

Hi Johan, thats because the first release of the build yesterday had the issues in… they released another build with same number a couple of hours later, which is what you will have downloaded no doubt.

So the initial release wasnt tested hardly at all…