Thursday, June 5, 2014

Why Display Suite is a bad idea

And why Code Fields are an even worse idea

You start out with three content types and a couple of view modes and everything is hunky-dory. Then the customer has some specific requirements and you say to your self – "Hey, that's kind of a weird thing to do but what the heck, I'll just do a code field and get it done!"
Of course, this continues throughout the project and you keep adding view modes and code fields to fulfil the reqs because once you've started down the DS + code fields road there's just no stopping it.

A year later, the Customer comes back with some new requirements. The site is going to be relaunched with multiple languages. And you're like – "Fuck yeah! i18n FTW!". Until you realize that all those sweet code fields are all like UND UND UND UND and you really should have written those umpteen gazillion tpls instead.

So, Display Suite? No.
Code Fields? No.

2 comments:

  1. I know your frustration, but display suite is a good idea. You should only use print t('") inside Code fields. Greetings

    ReplyDelete
  2. Lol so true, Anon. +1 that. Also who uses 'und' or LANGUAGE_NONE anyway? "Entity API" module ftw.

    ReplyDelete