Thread

I have a fresh 2.5 install. When I select Content > Edit from the Global Menu, I get a series of PHP errors:

A PHP Error was encountered
Severity: Notice
Message: Undefined index: 11
Filename: cp/content_edit.php
Line Number: 412

A PHP Error was encountered
Severity: Notice
Message: Trying to get property of non-object
Filename: cp/content_edit.php
Line Number: 412

A PHP Error was encountered
Severity: Notice
Message: Undefined index: 11
Filename: cp/content_edit.php
Line Number: 412

A PHP Error was encountered
Severity: Notice
Message: Trying to get property of non-object
Filename: cp/content_edit.php
Line Number: 412

A PHP Error was encountered
Severity: Warning
Message: Cannot modify header information - headers already sent by (output started at /private-path/codeigniter/system/core/Exceptions.php:170)
Filename: core/Common.php
Line Number: 408

If I select Content > Edit > Channel Name, none of these errors appear on a channel-filtered view. If I start from a filtered view and then select either “All” or “Filter by Channel” in the “Search Entries” dropdown to see all entries, the search query doesn’t execute… the spinning wheel just spins indefinitely.

Not sure if it is relevant, but this install is also running the latest version of CartThrob.

Hi Emily,

I am sorry you’ve bumped into this!

However, I was not able to replicate on ExpressionEngine 2.5.2 and I didn’t see anything in the bug tracker.

Are you on 2.5.0? And is /themes completely up-to-date?

Cheers,

Hi Dan,

I was on 2.5 and confirmed that my /themes/ were up-to-date. So I updated to the 2.5.2 and no luck.

As it turns out, and after staring at the Edit Entries view for a bit, I realized that there were records listed that didn’t have a channel. At some point during development, a channel must’ve been deleted and those records were still in the database and showed up on the Edit Channel Entries view.

Once I deleted those, the PHP errors went away. And this totally explains why the channel-filtered view wasn’t generating errors.

Anyways, simple solution, chalked up to user error.

Thanks for your help!

Hey Emily,

I am glad to hear that this is resolved. That rocks!

If you need anything else, please just let me know by opening a new thread.

Cheers,