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.

Using custom field as primary entry title - any drawbacks?

March 20, 2013 11:04am

Subscribe [2]
  • #1 / Mar 20, 2013 11:04am

    tomjeatt

    19 posts

    I’m working on a project which leans very heavily on Playa and Structure, and is (unavoidably) going to result in a lot of duplicate entry titles. My original plan was to use the title field as the, um, title field and then create a custom field for each channel which could be used for a second, more descriptive title. These could then be pulled into the Edit Channel Entries screen using Zenbu. As Playa only lists content by title, however, this turned out to be a bad idea so I’ve switched the roles around: the title field is now used descriptively but not pulled into any of the templates, whereas each channel has a {[channel_name]_display_title} custom field, which is pulled into the templates.

    Are there any drawbacks to this? I can’t really think of any (Structure will handle custom fields for navigation and page titles) but my approach feels a bit hacky.

  • #2 / Mar 20, 2013 3:48pm

    Rob Allen

    3105 posts

    No drawbacks at all, that’s quite a common method. For instance often when I do something like “testimonials”  the Title field is used just as a backend reference but not used in the front end.

  • #3 / Mar 21, 2013 5:22am

    tomjeatt

    19 posts

    Thanks Rob - that’s what I was hoping, so it’s always nice to get a bit of reassurance!

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

ExpressionEngine News!

#eecms, #events, #releases