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.

channel_fields.field_content_type on 2.2.2?

November 22, 2011 3:09pm

Subscribe [2]
  • #1 / Nov 22, 2011 3:09pm

    cmcnabb

    13 posts

    We have an install of EE v2.2.2 where we needed to create a channel field of type “integer” and verify the type from the database. This was possible by using the “channel_fields.field_content_type” field in the past, but this field is no longer being updated.

    There is a “field_content_type” value encoded in channel_fields.field_settings. Was this intentional or should I file a bug report?

  • #2 / Nov 23, 2011 2:19pm

    Kevin Smith

    4784 posts

    Hi cmcnabb,

    I’m not sure if it’s a bug or not. I’d be glad to bring in the devs to discuss what was changed and why, but first I do need to get some more context for what you’re talking about here. How would you create the integer field, and what do you mean “this field is no longer being updated”?

    Please give me a better picture of what you’re talking about, and I’d love to help answer this for you!

  • #3 / Nov 23, 2011 9:48pm

    cmcnabb

    13 posts

    Hey Kevin,

    Sorry for the confusion. I am as used to dealing with the EE database as the CMS. Here are the steps to see what I see:

    1) “Channel Fields”
    2) Pick a field group
    3) “Create a New Channel Field”
    4) Select “Text Input” as the Type
    5) Scroll toward the bottom of the page

    You will find a select box that is labeled “Field Content.” This box *used* to change/update the database field channel_fields.field_content_type. Now it creates a “field_content_type” entry in the MIME-encoded data of the channel_fields.field_settings column.

    Have a great Thanksgiving!

  • #4 / Nov 29, 2011 3:43pm

    Kevin Smith

    4784 posts

    Thanks for the clarification, cmcnabb. I’ve asked Robin to take a look at this and provide an explanation for us both. Thanks for your patience while we await an answer!

  • #5 / Nov 29, 2011 3:54pm

    Robin Sowell

    13255 posts

    Ah- yes, it was intentional, mostly to be consistent with the other field settings.  It was moved…. in 2.1.5- with a note in the ‘Developers’ section of the changelog:

    Moved the ‘field_content_type’ data in exp_channel_fields to the settings array for native field types that need it. The field_content_type field will be removed in the future.

    We didn’t remove the old field at the time out of concern 3rd parties might be using it- but it’s deprecated and all core pays attention to is the serialized array.

    Hope that clarifies!

  • #6 / Dec 01, 2011 2:17pm

    cmcnabb

    13 posts

    Thanks, Robin! I had missed that entry in the Developer’s notes.

  • #7 / Dec 01, 2011 4:33pm

    Robin Sowell

    13255 posts

    😉  It’s easy to miss unless you know exactly what to look for.  Glad that cleared it up- and thanks for bringing it up.  It’s always good to double check when unsure!

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

ExpressionEngine News!

#eecms, #events, #releases