Group 42

The steps for programmatically creating a node are:

• Create a PHP object representing the node data
• Save the object using the node_save() function

While the mechanics are simple, there is an important responsibility involved. The Drupal work flow does data validation before calling the node_save() function; node_save() does no validation. By calling node_save() directly your code takes the responsibility for providing valid data.

Drupal 7 Changes

A quick note for those of you familiar with Drupal 6. You'll notice two changes in Drupal 7:

Body Field Is No Longer Special

In Drupal 6 the body field was special. Specifically, it had a different data structure than other fields and it always existed, even if it wasn't used. With Drupal 7 the body field is a standard field provided by core and is truly optional.

Language

Language specification is required for the node and some fields.

Basic Node Creation

The following code assumes an unchanged Drupal 7 Standard installation and will create a Drupal 7 article node.

Blocks in Drupal 6 (and 5) always felt a little less loved than other portions of Drupal. While the node and theming APIs offered straightforward and often elegant methods to modify behaviour without modifying other peoples' code, blocks weren't so fortunate. Lacking API support, working with blocks often meant writing ugly code. Last week helping with the Drupal Block API documentation I discovered this has changed in Drupal 7. I thought I'd share what I learned.

The information I'll discuss is a summary of the block information from:

• Converting 6.x modules to 7.x (http://drupal.org/node/224333)
• Converting 6.x modules to 7.x - Categorical (http://drupal.org/node/394070)
• Block API Documentation: block.api.php
• Examples Module: block_examples.module (From: Examples for Developers project)

An example, like a picture, is worth 1000 words. Until recently Drupal programming examples existed but were spread among documentation pages, blog posts, and the Drupal CVS repository; some searching required. That changed in late 2009 with the introduction of the Examples for Developers module. Its purpose: "to provide high-quality, well-documented API examples for a broad range of Drupal core functionality". Now you can find high-quality, working Drupal 6 and 7 code examples in one place, many with SimpleTests.

The Examples for Developers Module, or simply Examples Module, is actually a collection of modules. Each sub-module contains a single, specific example of how to use an API or implement a feature. At the time of writing there are 17 examples:

Drupal's scripting abilities just keep getting better and better. Since publishing my Drupal Command Line Script Template last year I've moved exclusively to the Drush php-script (scr) command. The script template article still gets a lot of page views - perhaps because with all the functionality in Drush it's easy to miss the scripting feature - so posting an update seems like a good idea.

Drush Scripting Advantages/Disadvantages

The advantages of using Drush over using my original template are:

• Drush takes care of creating the Drupal environment for the script to run in, which is the only function the template served. Using Drush factors out the environment common code, eliminating redundant code in individual scripts.
• Drush makes it easy to place the script files in a directory outside of the Drupal website home directory. Placing script files outside the website home directory eliminates a whole range of security issues.
• The Drush code that creates the Drupal environment is reviewed by the community, making it far more robust than something a single person could create or maintain on their own.
• When the code required to create the Drupal environment changes you don't need to update individual templates, just Drush.

When image-sets are discussed it's usually in the context of a full featured photo gallery, but there's another common use: including a set of images with the content of a node. For example, product images with a product node or a "mini" photo album with an article. The CCK ImageField combined with a jQuery module like Thickbox makes adding image-sets to nodes easy. Here's how.

Overview

This "recipe" describes how to add a gallery style photo-set to a node. This photo-set stands apart from the node content as a set of thumbnails which can be clicked on to display the full-size version. The Thickbox slide-show feature is also implemented so viewers are able to step through the full-size version of the pictures without exiting the viewer. Although Thickbox is used, this technique should be easily adoptable to different plug-ins.

An example of the technique can be seen here: Finding the Blue Whale

Finding the time to really learn the tools we use can be difficult, but sometimes opportunity breaks the door down. This was the case at the Pacific Northwest Drupal Summit with Jeff Griffith's presentation Hacking Komodo for Drupal Development. In his presentation Jeff presented a buffet of features that can make you faster in Komodo Edit (and in most cases, the Komodo IDE). Jeff made his presentation slides available and there's a full video of his presentation at the PNWDS site: Hacking Komodo for Drupal development.

Here are some quick notes from Jeff's presentation. They don't cover everything, but do include things like enabling jQuery autocomplete, handy extensions you can install, and running command line scripts from inside Komodo.

Configuration

• Make sure you have PHP configured, or you won't get PHP autocomplete

  

• Create a Komodo project file in your top level Drupal directory to get autocomplete on Drupal functions OR Add the Drupal system directories using the library includes feature.

• If you're using jQuery, you can enable jQuery function autocomplete using the API Catalogs jQuery Javascript library.

  

Anyone who's tried to explain Drupal's content feature-set to the uninitiated appreciates the amount of territory that needs covering as well as the challenges inherent in presentation depth and order. J. Ayen Green takes up the challenge in his book, Drupal 6 Content Administration, published by Packt Publishing. Packt graciously provided me a copy for review.

The stated purpose of Drupal 6 Content Administration is "a quick-start guide that best serves Drupal Content Editors." Green is serious about the audience and serious about the content focus. The discussion and examples are firmly rooted on content and live in the user interface, using language targeted to the audience; except for the appendix, there are no digressions into unrelated topics like site administration, SEO, or account management.

The book's content falls into three broad categories: authoring/formatting content, methods for displaying content, and managing content. Each subject has a short introduction and explanation, and almost all include an example of something that can be implemented with step-by-step instructions for doing so. Green has made an interesting decision, the step-by-step instructions assume the Drupal site has already been configured and he does not digress into a discussion on configuring the modules required for the example.

In a presentation at the September 2009 meeting of the Vancouver League of Drupaliers (Vancouver's Drupal user group) core Drupal Developer and Now Public Development Team Lead Károly "CHX" Négyesi spoke about the importance of APIs in Drupal 7. If you're serious about scalability APIs are no longer an optional convenience. For some this may not be an issue, for others this could be a mindset change. Károly also discussed some other Drupal 7 improvements like functional testing.

This is a video of his presentation.

Drupal 7 APIs: A Mindset Change for Scalability

This video can also be viewed directly at: Drupal 7 APIs: A Mindset Change for Scalability

Last week was Mozilla Service Week and local Mozilla Messaging Technical Support Lead Roland Tanglao organized a Vancouver event at the offices of Agentic. At this point many Drupalistas are probably thinking: Wait a minute, is this the same Roland who used to work at Bryght? Yes, yes it is. And Vancouver readers are probably thinking: Wait a minute, Mozilla has an office in Vancouver? Yes, yes they do. I suspect Roland's short time there has already raised their community profile by a number of hundreds of percent.

The event was primarily Drupal focused, but all topics were welcome. As luck would have it, there was a excellent mix of technical resources and people with questions. It was a wonderful mix of round table, Q & A, and birds-of-a-feather.

Half of the Vancouver Participants (Wish I had wide angle)

A very big thank you and props to Agentic's Darko Hrgovic and Phillip Djwa for an excellent job hosting and facilitating. And a big thank you to Roland for organizing.

Drupal RSS functionality is spread out, and so is information on it. After first accumulating mental notes, which turned into a collection of written notes and code snippets, I realized there's a lot to be said on the topic. A single overview covering all things RSS seemed like a useful idea. This is a starting point covering many things RSS. I invite you to leave a comment if you have anything to add, a great reference or blog post, or if I've gotten something wrong.

"Out of the box" RSS

• RSS is configured and controlled at Administration > Content management > RSS Publishing
  
  
• The default RSS URL is rss.xml (e.g. www.example.com/rss.xml)
• The default RSS feed selects content using the same selection criteria as the /node path ("/node" is the default front page setting). It contains the content of any node that's both "Published" and "Promoted to front page".
  
  
  
  The exact content and number of nodes is determined by the RSS settings.
• There is no provision to theme a node's RSS output in the PHPTemplate theme engine. Your node.tpl.php file is ignored when the feed content is rendered.
• Because of the above point, double check the RSS feed output of any feed containing nodes you've created or modified with CCK.
• Every taxonomy term automatically gets a feed (whether you want it or not)
• The is no provision in the Drupal base installation (core) to publish comments in a RSS feed. A contributed module (RSS Comments or Views) is required. More on this later on.
• The RSS feed will only be published on the front page. More on this later.