Drupal WYSIWYG Best Practices

Matthew Vaughan wrote an informative article on how to setup wysiwyg in Drupal. Not easy to get it all right!

Until Drupal 8 arrives, setting up effective WYSIWYG content editing falls to us developers. For many developers, figuring out the available options and their pros and cons can be difficult. Their main goal is to have a usable site up and running as soon as possible. Over the years, I've settled on a recipe that seems to work well for most clients. Other developers that I know often use a similar setup.

Following the recipe, you get easy linking to internal nodes, inline images, and image cropping.

Kalabox: an “Integrated workflow solution for people who use Drupal.”

Doug Vann supported Kalabox, sounds like a useful idea:

KALABOX uses the tagline, “Advanced Dev tools For The People.”

I love this! I’ve always been the kind of geek who was happiest when technology makes a difference, like when introducing new technology makes humans happier and more productive! And this is exactly what Kalabox is already doing AND wants to do a whole lot more of.

The tagline is catchy, but the full definition, of what Kalabox is, gets me equally excited:

Kalabox is an “Integrated workflow solution for people who use Drupal.”

Content-Driven Commerce

The Commerce guys make the case for a unified customer experience and content-driven commerce:

Commerce Guys has been promoting the value of content-driven commerce for many years, and we are thrilled to see more and more people talking about this shift occurring in eCommerce.

What is content-driven commerce?

In particular, they point out that companies who differentiate themselves by providing a unified user experience to tell their story should consider a tightly integrated solution that provides both a rich Content Management System (CMS) and a flexible eCommerce transactional engine.

And why is it important?

Drupal 8 and the slow death of IE8

David Corbacho writes about the too slow demise of IE8:

And the community and Dries, decided almost at the same time to embrace ECMAScript 5, jQuery 2 and drop IE8 support. The change record was modified (to include IE8 as not supported). And we all rejoiced, specially front-end developers. Yay!

During the discussions in 2012-2013 we thought that IE8 usage will drop fast (we wanted to believe that). But the reality hurts, This is a chart from StatCounter (IE8 has a 4.71% usage in March 2014) ... From netmarketshare.com, the trend is even worse. IE8 has still 21.14% of the browser share on March 2014.

Drupal 8 won't be out for a while, so perhaps the problem will be less significant.

Adding Facebook Open Graph tags to your Drupal site

Daniel Sipos writes on adding Facebook Open Graph tags to your Drupal site:

I'm sure by now you know that people share pages on Facebook and you want your site to be shared as much as possible. You also know that a little teaser information is made available on Facebook when you share these pages (title, image, short description).

But have you ever noticed that with some sites, when you share pages on Facebook, or like/recommend them, some random, unintented image gets used in this teaser. Or the description is not correct, or even the title is not right. Facebook is quite good at picking the right elements to show there but sometimes it doesn't manage by default. And you can't expect the random user who shares your page to make adjustments to the text or title. So what do you do? You use Open Graph meta tags.

Essential Drupal development tools

Blair Wadman gives his list of Drupal development tools. In our opinion Drupal developers should use at least half of this list, if not more:

You can build Drupal websites with just a few tools, such as a code editor, browser and dev environment. While it is not necessary to use additional tools, tools do make your life easier and can save you a tonne of time and improve the quality of your work. So let’s take a look at the essential tools to use to develop with Drupal.

Digging Deeper into Drupal Page Caching

Brian Osborne has a very informative article on the Drupal page cache:

... I wanted to provide a more comprehensive look at Drupal's core caching, explaining how some of this stuff is actually working under the hood. ...

Page caching is when Drupal takes the entire rendered output of a page request and stores it in the Database (or another cache store, defaults to DB). Cached pages only apply to anonymous traffic - meaning users that are not logged in and do not have any "session" data (like a product added to a shopping cart). Since the page is rendered once and stored in its entirety in the cache, there is no opportunity to change the content. Dynamic content for logged in users like a simple welcome message, or a list of items in a shopping cart, can't work in tandem with Drupal's built in page caching.

Use the full power of Drush

Artyom Miroshnik gives a nice overview how powerful and easy to use drush can be. He covers:

  1. Drush out-of-box commands
  2. Drush contrib commands
  3. Drush Aliases
  4. Improve your workflow with drush


Try using Drush wherever it’s possible and you will save your time!

We agree!

What I Learned Today: Drupal Behat Breakpoints

Jonathan Jordan of Metal Toad on breakpoints in the Drupal Behat Extension:

Today I learned that the Drupal Behat Extension provides an extremely useful step definition for debugging. Breakpoints!

  Then I break

It allows you to stop at a certain point in the test scenario so you can take a closer look at what is going on in the browser. When you are ready to move on, you just hit enter in your terminal window.

Rules 7.x-2.5 has a fatal flaw: edited rules disappear

As we just ran into this issue, we would like to warn all customers not to upgrade to Rules 2.5, or install the patch if you have done so. Else, if you edit or disable rules, they will disappear without a trace.