Blog

Keep Calm and Clear Cache

Drupal is great at a lot of things, one of those being the feeling of your head banging against the wall. Drupal can lead to some headaches when things just do not work right. Troubleshooting and debugging in Drupal doesn't have to be difficult, however. Yet, for some reason, every article I've ever found goes in too deep. I presented this at my user group Drupal 262 as a "back to basics" debugging and troubleshooting. This post will touch on basic troubleshooting, user permissions, and Drupal's cache.

Making Drupal compatible with Internet Explorer's Compatibility Mode

Internet Explorer is a deadly trap for web developers. In fact a good amount of time is allotted to just ensuring a website's experience is uniform across different versions of the browser. The problem plaguing Internet Explorer is that each version has generally been released alongside a new iteration of the Windows operating system. With this life cycle certain operating systems get left behind (the dreaded era of Windows XP with IE8 is finally, somewhat over.) However! Despite the hopefully death of Internet Explorer 8 developers must worry about compatibility mode.

Changing the Drupal theme based on path

When using Drupal we all know there are two themes: default and administrative. By having two different themes site managers have a better user experience by knowing "this is public," and "this is administrative." It also proves beneficial to have specific administration themes due to the kinds of content and forms that a site manager has to interface with. Drupal does provide the option of letting site builders decide if adding or editing a node takes place in the default theme or the administrative theme.

Custom custom Drupal entity view modes (without the bloat!)

When it comes to Drupal I love entities. Entity display modes provide simplicity in managing how your content is displayed. I used to be hardcore "Fields only" when it came to using Views and displaying content. Yeah, it gives you more control, but it is a pain in the ass when you have to replicated your field settings multiple times (if you have to.) Wouldn't it be super easy to just say "Hey Views, render this entity!" and BAM it is all there for you.