Thread

Hello John,

I don´t have the MacBook with me in the moment so I can´t tell the exact error messages right now, but I remember the same or similar line numbers as listed above. (I also had quite a list.)

I was trying to set up a fresh sandbox using a brand new install of 20100810, got same errors with and without hotfix (and all caches empty). There are only three fields in the channel (title and two text areas). First I had no channel entry at all, then I thought maybe one is needed and entered a welcome entry. -> Same errors if I try to remove the Ping tab. Add-ons: SEO-Lite by bjornbjorn and PT fieldpack. (I got the same results with and without SEO lite).

John,

Similar to Wolfram, this is a local install on my MBP while I develop the site.  It’s a fresh install of 20100810 and with a handful of add-ons.  On the channel publish/edit page itself I’m only using Wygwam 2.1.2 (2.1.3 failed to display the wygwam field on the publish page so I went back a version until I could figure out why).

Wolfram and stubear,

There are some quirks (particularly this one) that may be impacting you that will be fixed in the next release. First, try removing the layouts for all groups to essentially reset to defaults.

Thanks for the info John.

Just to make the picture complete for you – I get exactly the same errors as listed above plus these:

A PHP Error was encountered
Severity: Notice
Message: Uninitialized string offset: 0
Filename: cp/content_publish.php
Line Number: 1552

A PHP Error was encountered
Severity: Notice
Message: Uninitialized string offset: 0
Filename: cp/content_publish.php
Line Number: 1552

A PHP Error was encountered
Severity: Notice
Message: Uninitialized string offset: 0
Filename: cp/content_publish.php
Line Number: 1566

A PHP Error was encountered
Severity: Notice
Message: Uninitialized string offset: 0
Filename: cp/content_publish.php
Line Number: 1566

A PHP Error was encountered
Severity: Notice
Message: Uninitialized string offset: 0
Filename: cp/content_publish.php
Line Number: 1574

A PHP Error was encountered
Severity: Notice
Message: Uninitialized string offset: 0
Filename: cp/content_publish.php
Line Number: 1577

A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /Applications/MAMP/htdocs/sandbox/xxxxxxxxx/codeigniter/system/core/Exceptions.php:171)
Filename: core/Common.php
Line Number: 428

Would be nice if there would be a hotfix addressing the issue(s).

Greetings, Wolfram

Thank you for your feedback. We’ll add to this thread when we have more info.

I just encountered the same problem when applying layout.

What versions and builds of EE are you using? v2.1.0 Build: 20100810
Are you using any third-party add-ons? no
Are you sites fresh installs or an upgrade from a previous version? fresh install
What were your PHP errors if different? same errors, a search brought me to this thread

Removing the layout cleared the errors. I have only 22 fields on one single page.

I can re-create the errors by just dragging and making smaller the first field, then ticking “Super Admins” and saving the layout.

A PHP Error was encountered
Severity: Notice
Message: Uninitialized string offset: 0
Filename: cp/content_publish.php
Line Number: 1544

A PHP Error was encountered
Severity: Notice
Message: Uninitialized string offset: 0
Filename: cp/content_publish.php
Line Number: 1544

A PHP Error was encountered
Severity: Notice
Message: Uninitialized string offset: 0
Filename: cp/content_publish.php
Line Number: 1552

etc.

As mentioned previously in the thread, there are some issues which should be fixed in the next build/version. Unfortunately, I don’t have an estimated turn around time for when the next build/version will be released. Thanks in advance for your patience.

I don’t know if the issue is related but I was getting a number of PHP errors with the NSM Add-on Updated accessory. I tried a number of things to solve that problem before stumbling across manually emptying the cache. Leevi Graham had suggested that the cache folder permissions might not be set correctly and after ensuring they were I thought that perhaps the cache itself could be the problem. To make a long story short, manually emptying the cache fixed that problem and it appears to have fixed the problem with custom publish layouts as well. I realize that correlation != causation but it’s always worth a shot because it’s possible this will fix the issue.

Thanks, stubear.

FWIW, I’m also getting this error. Any change that I make to the Publish Layout—hiding fields, removing tabs, moving fields between tabs—results in this error. Here’s my info:

EE Version: 2.1.0 Build 20100810
Third Party Add-Ons: Freeform, Playa
Fresh Install/Upgrade: Fresh install

Jason, as we mentioned earlier, there are some bugs in the most recent build. During regression testing, we’ll make sure to test vigorously.

I’m also having this issue. Is this fixed now in the most recent build, which appears to be in My Downloads ??

Hi KMDG,

Please do upgrade to the latest version and build making sure to use the appropriate set of upgrade notes in the documentation. The latest version is 2.1.1 and build 20101020.

Cheers

Greg