ExpressionEngine CMS
Open, Free, Amazing

Thread

This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.

The active forums are here.

Updating Field Settings throws PHP error after upgrading from EE 1.7.1

February 20, 2012 7:14pm

Subscribe [6]
  • #1 / Feb 20, 2012 7:14pm

    Matt68000

    3 posts

    Yesterday I updated our site to EE 2.4.0 from EE 1.7.1. Today I noticed that I’m unable to update Field Settings for a custom field group under CP > Home > Administration > Channel Fields > Edit Field. When I click the Update button I get this error message:

    A PHP Error was encountered

    Severity: Notice

    Message: Undefined property: Api_channel_fields::$config

    Filename: libraries/Api.php

    Line Number: 283


    Fatal error: Call to a member function item() on a non-object in <full path removed for security reasons>/public_html/system/expressionengine/libraries/api/Api_channel_fields.php on line 1261

    I don’t get this error when updating fields in the Default Field Group, however. Also I should note that we’ve renamed our system folder (not shown above for security reasons)

    Any ideas?

  • #2 / Feb 21, 2012 7:16pm

    Sean C. Smith

    3818 posts

    Hi Matt68000,

    I want to help you out with this, but need a little more information. When you did the upgrade to 2.4.0 were there any errors? Does this error happen on clicking the field group in question or a particular field within the group? If within the group what is the field type and can you edit the same field type in a different field group?

    Sean

  • #3 / Feb 22, 2012 4:34pm

    Matt68000

    3 posts

    Hi Sean,

    Thanks for your reply. To answer your questions:

    I didn’t see any error messages during the upgrade to 2.4.0. Everything seemed to go smoothly, although afterward I did notice that we’d been bitten by this bug so I made the suggested change to line 1268 of system/expressionengine/modules/channel/mod.channel.php.

    I don’t get any errors clicking on my field group names. The errors happen when I try to update the Field Settings for a specific field within a field group (CP > Home > Administration> Channel Fields > Edit Field > Field Settings). When I click the pink Update button I get the error, regardless of whether I’ve actually changed any of the field’s settings or not.

    I haven’t checked all of my field groups and fields, but so far I’ve noticed the error for some—but not all—Text Input fields, and some—but not all—Date fields, across different field groups. In other words, Text Inputs can be updated in some field groups but not others, and the same for Date fields.

  • #4 / Feb 24, 2012 3:04pm

    Kevin Smith

    4784 posts

    It sounds like it might be a problem with a particular field type since it’s happening with a specific field within a field group. I’d like to get a closer look at this if that’s possible. Be on the lookout for an email from me.

  • #5 / Feb 26, 2012 7:03pm

    vibe9

    96 posts

    I’m getting a similar error on a site I just updated from EE 2.2.1 to 2.4.0 (it was formerly a 1.6.x site) before that.

    A PHP Error was encountered
    
    Severity: Notice
    
    Message: Undefined property: Api_channel_fields::$config
    
    Filename: libraries/Api.php
    
    Line Number: 283
    
    Fatal error: Call to a member function item() on a non-object in /.../system/expressionengine/libraries/api/Api_channel_fields.php on line 1261

    Thanks!
    Terry

  • #6 / Feb 27, 2012 1:14pm

    Shane Eckert

    7174 posts

    Hello vibe9,

    I will ask Kevin about what he found working with this case. Kevin or I will get back to you.

    Cheers,

  • #7 / Feb 27, 2012 6:47pm

    Kevin Smith

    4784 posts

    Looks like this was the result of a bug, which I’ve reported here along with the solution. Terry, go ahead and give that a try and let me know if it still gives you any fits.

  • #8 / Mar 11, 2012 12:57pm

    Sean G

    8 posts

    Excellent!

    Fix worked for me, Kevin! Glad to see the bug is fixed in upcoming release.

    Thanks,
    Sean

  • #9 / Mar 12, 2012 1:32pm

    Kyle Cotter

    730 posts

    Glad to see you got it working, Sean.

    Terry,

    Was the solution Kevin linked to able to help you out?

    Keep us posted.

    Thanks.

.(JavaScript must be enabled to view this email address)

ExpressionEngine News!

#eecms, #events, #releases