Cornered development

The most active student in the class was an experienced C# developer. He had never worked with PHP before, and, really, didn't seem like he was going to start any time soon. He was mostly there to get a sense for how to integrate Drupal with his company's product for museums.

Although install profiles are a good vehicle for productizing Drupal, it can actually be incredibly useful to integrate the install profile concept into the ordinary development workflow of all your Drupal sites.

In Drupal we use object-oriented page and form callbacks to ease our programmning burden This is a nice improvement that allows us to encapsulate the functionality of one or many page callbacks into objects

For a recent client project we need to track whether a user registering on the site had recently seen an ad promoting registration. If the user clicked on the ad and immediately

I've been playing with the idea of automatically generating Drupal themes from static HTML/CSS/JS using annotations in the HTML markup. I put together a basic proof-of-concept of a tool to generate a Drupal theme, ctools layout and style plugins, and view modes and templates.

Today, I will talk a bit about access control. Specifically, what options you as a module developer have for controlling access to nodes and individual fields. 

First create your view like you normally would. The screenshots in this example, we are using a view of Content (aka Nodes), but this should be the same process for any entity type.