We use cookies to improve your experience. No personal information is gathered and we don't serve ads. Cookies Policy.

ExpressionEngine Logo ExpressionEngine
Features Pricing Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University
Log In or Sign Up
Log In Sign Up
ExpressionEngine Logo
Features Pro new Support Find A Developer
Partners Upgrades
Blog Add-Ons Learn
Docs Forums University Blog
  • Home
  • Forums

Undefined index: field_id_60

Development and Programming

dgtlmkt's avatar
dgtlmkt
10 posts
about 6 years ago
dgtlmkt's avatar dgtlmkt

I’m getting the following notice:

Undefined index: field_id_60 ee/legacy/libraries/channel_entries_parser/components/Custom_field.php, line 101 Severity: E_NOTICE

This happens with a Fluid field that is a Relationship with a channel. Custom field 60 does exist and is in use in other parts of the site, but not by the related field.

How should I go about troubleshooting this? EE 5.2.2.

       
mcfarlandonline's avatar
mcfarlandonline
3 posts
5 years ago
mcfarlandonline's avatar mcfarlandonline

Did you have any luck with this? I’m running into the same issue only there’s no relationship field at play. I have a grid field within a fluid field that seems to be the culprit.

       
Pigtail Dencil's avatar
Pigtail Dencil
117 posts
4 years ago
Pigtail Dencil's avatar Pigtail Dencil

I’m getting something similar now too, as well as this PHP error mesage:

Cannot modify header information - headers already sent by (output started at ee/legacy/core/Exceptions.php:120)

Anyone of you managed to sort this? I read elsewhere that the server’s ICU version may be at fault.

       
dgtlmkt's avatar
dgtlmkt
10 posts
4 years ago
dgtlmkt's avatar dgtlmkt

Sorry mcfarlando and Pigtail, I never did. In fact, shortly after running into it I abandoned EE as the solution for my shop. Absolutely not a real solution for most projects.

I don’t know what ICU is. My EE environment was built on an AWS instance using PHP 7.3 I believe.

I’m willing to bet the rebuilding your structure will correct the problem, but that’s also not a realistic solution. In my case, my use of Fluid and Relationships was so complex that I think EE couldn’t keep up with it anymore.

I’m sorry I don’t have the answer.

       

Reply

Sign In To Reply

ExpressionEngine Home Features Pro Contact Version Support
Learn Docs University Forums
Resources Support Add-Ons Partners Blog
Privacy Terms Trademark Use License

Packet Tide owns and develops ExpressionEngine. © Packet Tide, All Rights Reserved.