Articles

• Working With DateTime Objects in Drupal 8 & 9 3/5/2021

  When working with dates in Drupal, all information is stored in the database as seconds since Jan 1, 1970 (GMT). This means that times will be stored in GMT timezone, which is 4 or 5 hours shifted relative to EST. In most cases, modules do a good job shifting times back to the correct timezone, but if you need to do something custom outside a field formatter, you may have to handle timezone shifting on your own.

  For instance, consider a node type event. We can use core's Date Range field type to store the start/end datetime objects, but the node type's display settings use the "Default (All Day)" display format which leads to dates displaying the date on both the start & end datetimes (e.g. Mar 5, 2021 4pm - Mar 5, 2021 8pm).

• Starting a New Drupal Project 4/12/2019

  My favorite characteristic of Drupal as a CMS is its one-two punch of flexibility & extensibility. You can make Drupal do just about anything you want, and for many purposes, you might not even need to touch code. While the options available are effectively infinite, there are a few things I do every single time I start a new project.

  At Midnet, we are working primarily in Drupal 8 now. We still do maintenance on Drupal 7, 6, and even 5 sites, but new projects are almost exclusively in Drupal 8 now. To allow our entire development team to jump in and bang around on a project there are a few standards we’ve built upon.

• The Start of Something New 3/6/2019

  A few weeks back, I ran across an article rattling off a number of reasons web developers should have a blog, and the two that stuck with me were “to learn something new” and “to kickstart your career”.

  They say you never fully understand a topic until you are able to explain it. Blogging is a low barrier to explaining things.