Drupal

I was moving some Drupal Commerce work from a local development environment to an integration and staging server this week, and realized that Commerce really does lack in its ability to have configuration featurized. I found the Commerce features module, which initially seemed like it would be quite helpful. Unfortunately, most of the commerce configuration that I was looking at is not featurizable using this module.

EntityFieldQuery is a class that can be used to... query entities... by field! And, other things too.

Today I needed to get a list of all nodes, of a certain type, ordered by title. One might go to the database for this, but I decided to do things the 'right' way, by leveraging the Drupal 7 entity system.

As the Drupal Core accessibility maintainer, I from time to time have people ask me about the accessibility of different contributed modules. Several times in the past I've been asked about the accessibility of Panels (where I assume the person means cTools Page Manager as well). Only this week have I had the need to use Panels and Page Manager. This is by no means a thorough review, but my observations as a screen-reader user.

Yesterday, while doing some work on a Drupal 7 site, I ran across the PHP error:

Fatal error: Exception thrown without a stack frame in Unknown on line 0

At first this seemed like the worst error message I could possibly receive. Not knowing where to start I did some research and ran across a blog article suggesting that I wrap the entirety of index.php in a try / catch block.

Yesterday I was asked if I could investigate how to disable a Drupal Commerce checkout pane depending on the contents of the order. Having never used Drupal Commerce before yesterday the task seemed a bit overwhelming. Thanks to good documentation and help from #drupal-commerce on IRC, I came up with the following.

Slides from my DrupalCamp Toronto 2011 session: HTML5 and the Drupal 8 HTML5 Initiative. Thanks to @Jacine for assistance with information for some of the slides.

Presented 2011-11-12.

HTML a Timeline

* 2000: XHTML 1.0, W3C Recommendation
* 2004: HTML5, WHATWG begins work
* 2007: HTML5, W3C starts HTML Working Group
* 2008: HTML5 Working Draft, W3C

Last week I wrote an article stating that I was planning on performing a jQuery UI accessibility review. Plans have not changed, and I am still planning on performing this review, with the help of several others who have stepped up and offered to help, next week, starting on November 7. This quick article will outline my plan for organizing and performing the review.

I love jQuery and I like jQuery UI. There has been a lot of accessibility work done to improve jQuery UI (including the jQuery ARIA Hackathon), but there is still work to b done.