Thread

A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_title
Filename: content/publish.php
Line Number: 130
” id=“hold_field_
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_title
Filename: content/publish.php
Line Number: 130
” style=“width: 100%; display: none;”> 
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_title
Filename: content/publish.php
Line Number: 136
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_title
Filename: content/publish.php
Line Number: 137
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_title
Filename: content/publish.php
Line Number: 142
” >
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_title
Filename: content/publish.php
Line Number: 144

A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_title
Filename: content/publish.php
Line Number: 151
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_title
Filename: content/publish.php
Line Number: 156
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_body
Filename: content/publish.php
Line Number: 130
” id=“hold_field_
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_body
Filename: content/publish.php
Line Number: 130
” style=“width: 100%; display: none;”> 
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_body
Filename: content/publish.php
Line Number: 136
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_body
Filename: content/publish.php
Line Number: 137
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_body
Filename: content/publish.php
Line Number: 142
” >
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_body
Filename: content/publish.php
Line Number: 144

A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_body
Filename: content/publish.php
Line Number: 151
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_body
Filename: content/publish.php
Line Number: 156
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_id
Filename: content/publish.php
Line Number: 130
” id=“hold_field_
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_id
Filename: content/publish.php
Line Number: 130
” style=“width: 100%; display: none;”> 
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_id
Filename: content/publish.php
Line Number: 136
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_id
Filename: content/publish.php
Line Number: 137
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_id
Filename: content/publish.php
Line Number: 142
” >
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_id
Filename: content/publish.php
Line Number: 144

A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_id
Filename: content/publish.php
Line Number: 151
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_id
Filename: content/publish.php
Line Number: 156
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_topic_id
Filename: content/publish.php
Line Number: 130
” id=“hold_field_
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_topic_id
Filename: content/publish.php
Line Number: 130
” style=“width: 100%; display: none;”> 
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_topic_id
Filename: content/publish.php
Line Number: 136
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_topic_id
Filename: content/publish.php
Line Number: 137
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_topic_id
Filename: content/publish.php
Line Number: 142
” >
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_topic_id
Filename: content/publish.php
Line Number: 144

A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_topic_id
Filename: content/publish.php
Line Number: 151
A PHP Error was encountered
Severity: Notice
Message: Undefined index: forum_topic_id
Filename: content/publish.php
Line Number: 156

Removing the layout, then refreshing the layout, the removing the forums tab, and reworking the publish page layout and re-saving appears to get rid of the PHP warnings. And it looks like I’ll need to do this for all channels.

Basically every channel’s publish page has to be re-done with this Version as with a previous one.

There are some cases where this is true, and I suspect the Forum tab is a culprit. Not ideal, for sure. But once you do this for the channel are you getting further errors?

Hi Brandon, once I redo the page layout, it works fine. It appears that both the forums and pages module tabs that kicked out the PHP errors on this update.

Thing is, we support well over 150 installs of EE and our sites probably have 10 to 15 channels each. Some of our custom publish page layouts are a bit involved and having to reset all those layouts each time there’s a new version of EE is really time consuming and unfortunately, it non-billable hours in our business model, so it’s a loss to us that will quickly add up to a few thousand dollars each time we do a version update that requires us to do this.

What should be a 20 minute software update turns into a 40 minute one while we have to reset the publish page layouts for each channel and that time adds up quickly when you have as many sites to update as we do.

This is now a recurring issue with the default product breaking on update, breaking the primary tool we sell to our clients (the publishing area), breaking our client’s confidence in EE when they see the all those errors, wasting valuable developer’s time and cutting into our revenue.

Couldn’t there be a function written for the Installer that deals with these changes on update?

EE’s better than this. I shouldn’t have to worry about EE breaking my work on an update, that’s one of the reasons I choose EE. What can we do to make this situation better?

Same issue for me, and I do not have a Forums tab. I do however have the Pages tab, if that is the culprit.

This is a pretty nasty bug if you change the publish page layouts a lot. I will not update any other sites until this is corrected, as we have custom layouts for everything.

Kurt,
I can replicate this to some extent can you go ahead and create a Bug Report please and reference this thread.

Fuel,

Your issue is more more than likely the same Bug so Kurt’s report will be enough in this case.

Hi John,

Remember this?

You are upgrading from a Beta version to the full release though and I don’t expect this issue to appear ever again for any subsequent versions now it is out of Beta.

<evil laughter>hehehehehehehe</evil laughter>

This issue is back from the dead to haunt me: http://ellislab.com/forums/viewthread/161571/#776335

The Bug Report is: 14798

I had the same problem, and I don’t have Forum or Pages tabs.

The error I get is field_type when trying to use the API.

(worked before update to 2.1.2)

A PHP Error was encountered

Severity: Notice

Message: Undefined index: field_type

Filename: api/Api_channel_fields.php

Line Number: 256

although I’m not sure if this particular error is related as I see the file api/Api_channel_fields.php was changed since the last version… aargh.

Link to bug report: https://support.ellislab.com/bugs/detail/14798/

Looks like Greg is attacking it.

Paul, did you have saved publish layouts?

Jason, how are you getting the error? We may need to split out your question to another thread.

Yes I had saved publish layouts.
I cleared them out and re-saved them, but looking at them now the layout is as I saved it but the “eye” icons are all open, but loads of the fields are hidden.

I think this is one of the final straws for me, I’m seriously thinking of giving up on EE2. I’ve been bashing my head against a brick wall at every stage of developing a new site. I’ve spent the day going over every thing I want to do, and in every case EE1.6 does it at least as well and in many cases it does it better. The file manager and file handling is worse than 1.6 and the heavy use of javascript in the control panel makes it clunky and slow.

Just want to say that this happened for me, too, with my clients’ sites. Anything that had a custom publish layout had to have its layout removed, then redone. Then it worked after that, but this process shouldn’t occur every time I upgrade/update EE.

I wish I had your confidence that this will not happen again Lealea.

Attached is a screen shot showing the eye icons all open but with most of the fields hidden. It is all working correctly but those icons show that all is not right.

I got these errors, too. I’m lucky I only had one channel. Thanks Kurt.

Same problem here on 2 channels. I also can not preview any layouts anylonger.

same problem