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.
The Metatag module and Site Verification module help setup site verification and social media integration. However social media is rapidly changing, more often than those submitting patches (or modules getting releases.) Or, hell, you're like me and think it's pointless to add a contrib module for a simple use case (note: I rock Metatag on this site.) One such case is Pinterest site verification.
I'm writing a book! Mid May I began work on a book called "Getting Cozy with Drupal Commerce." Commerce is a robust module with a lot of power under the hood, unfortunately many of its features can be confusing or frustrating. Why? Because its architected to be flexible and extensible.
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.)
When using Drupal we all know there are two themes: default and administrative. By having two diferent 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. Chances are, at least in all of my cases, you have "Use the administrative theme when editing or creating content" checked. There's just one drawback: what if one specific node (or other entity for that matter) should be edited through the default theme?