Want to get Lullabot article, videocast, and podcast announcements delivered right to your in-box? Let us know your email address (we won't share it) and we'll let you know when anything exciting happens.

Subscribe to our bi-weekly audio podcast - The Lullabot Drupal Podcast, our daily interview snippets - Drupal Voices, our periodic videocasts, or everything. Just choose your favorite podcast-listening application or service and click away!


Podcast 78: Drupal Screwups and Common Mistakes

  • Artist: Lullabot
  • Title: Podcast 78: Drupal Screwups and Common Mistakes
  • Album: Drupal Podcast
  • Year: 2009
  • Length: 85:13 minutes (33.32 MB)
  • Format: Mono 44kHz 54Kbps (VBR)

Addi Berry, Angie Byron, Jeff Eaton, Karen Stevenson, and Jeff Robbins talk about their own screwups as Drupal newbies and common mistakes often seen when creating Drupal sites. The podcast includes a long list of common site building, coding, and Drupal project planning mistakes, screwups, and kerfuffles. If you're new to Drupal, please, learn from our mistakes!

Pick of the week: Migrate module

Links:

Comments on this post will automatically be closed three months from the original post date.

Comments

no transcription ?

hello,

could it be possible to have some transcriptions of your podcasts and voices please ?

they seem great but as a techncian always on work, my time is halas pretty little to hear from you :)

Use crowdsourcing to transcribe

Maybe someone can put these podcasts on jobspooler.com (a Drupal site by the way) and have them transcribed. You can slice the audio file into a bunch of small sections and have a bunch of people transcribe them quickly. It costs a bit, but you determine the price per piece.

Transcriptions for Accessibility

Transcriptions and subtitles aren't just for convenience -- they are essential for accessibility. And, of course, there are all sorts of general usability advantages, too (such as search, being able to find a specific point to start watching/listening, etc.)

Beautiful podcast! It was

Beautiful podcast! It was both funny and interesring. Loved the part about "using taxonomy on everywhere". Great job

No transcriptions in multiple languages?

Could we please have transcriptions in multiple languages? My time is limited, and it would allow me to practise my German or Spanish while polishing my Drupal skills. Thanks.

Maybe you can write a module

Maybe you can write a module to do that automatically ;)

The One True Solution to Every Drupal Problem

Ah, memories. I went from:

  • "Taxonomy solves every problem" to "Taxonomy is obsolete! Everything's a node, even categories!"
  • "Whatever output you want, you can get it by hacking template files" to "Every page is a View, preferably with other views embedded in the header & footer, even if it's a list of one node!"
  • "Every page is a Panel" to "Panels is a false god! Yea verily, I say unto you, do not forsake blocks and regions!"

... and so many more temporary absolute universal truths. Drupal development is like a never-ending religious flame war with yourself. Looking forward to what Drupal 7 will bring.

  • "Everything's a field!"
  • "Modules are only for APIs and building blocks. Everything else should be a Feature!"
  • ...

If listeners to this podcast

If listeners to this podcast are left wanting more, I wrote about worst case scenarios for new Drupal administrators at http://knurl.us/url/7k2huja

Meanwhile, to skip the news and introductions, jump to 16:16. For the tip of the week (great pick, by the way!), skip to 18:58.

Did I hear wistfulness?

It was funny listening to you guys laugh at yourselves and the silly mistakes you made (some of which I am still in the process of making). It all seemed so sensible back then though, didn't it?

Svn content vs config

Hi guys,
really enjoyed the podcast and was interested in hearing about how you can work locally on a versioned copy of your site and publish changes to the live site.
The issue being that locally you might install a new module which would change the database but by the time you are ready to publish the remote site will have more content added by users.
How can you make versioned changes upload changes along with required database changes without losing the latest content from your users.
Regards
grant