Thread

EE 2.2.1. Seems to be an error in the php code. Possible bug?

Hi Britchie,

We’ve had luck with folks resetting their layout to get rid of the error.

If that doesn’t do it, this also looks like it could be an error related to the old themes folder still being present. Could you ensure that you remove your themes folder (backing up any folders inside it that were added to it), and make sure you upload a fresh themes folder from the latest release’s download?

Mine’s a clean installation - I dropped the DB, erased the old EE v 1.6 files completely and installed EE 2.2.1 fresh. All of the add-ons from Solspace (FreeForm) and Pixel&Tonic; (Matrix/Wygwam) are the latest too.

I’ll try the ‘reset’ suggestion and let you know if it works OK.

So this was a completely fresh installation of 2.2.1, and the publish pages looked like that from the start? Hmm…

Have you tried globally disabling extensions and seeing if it continues to present itself?

Does this occur in all channels’ publish pages or just certain channels? If you create a new channel with nothing but the standard channel fields, does the problem still present itself?

I tried the ‘reset’ suggestion and this has solved the problem (for now).

To answer your questions: The error occurred in just one channel. I did not try globally disabling the extensions. I disabled/uninstalled the PT_Switch (1.04) extension thinking this might be the culprit but to no avail.

FYI - I had the same problem on a local (MAMP) installation of the site. In this instance I upgraded EE from version 2.1 to 2.2.1 and the error appeared, again in one of the channels only but I was not able to identify which add-on, if any might be causing this. As a precaution for the production site I decided to go for a clean install in case this was caused by a legacy file/folder during the upgrade process.

One other factor, which I don’t think is the cause, is that I only create a single Field set for all of the channels I use and employ the layout options to order and show/hide the fields I require for a particular channel. I find this works well in reducing duplication of field types in different channels and with template/tag naming conventions, can speed core EE configuration for new projects, aka re-use (I’ve yet to venture into Git).

Glad to see the reset suggestion worked. I’m not sure yet what’s causing this error to happen, but I’m glad we have a workaround. If you see this happen again, please feel free to open up a new thread about it by clicking the button below!