I won't bore you with the gory details of Drupalcon SF, as it seems every other blog on the Drupal planet is doing (yes, we KNOW it's coming up and we know for sure that it will be AWESOME).
In honor of Drupal's 9th birthday, I decided to record the happy birthday song for Drupal! Starring my brother singing and me on accordion.
Node access is a big topic for many websites - restricting what content a user can view. However, for many people, such as myself (until last night), it's a big and scary topic. What I intend to do in this post is to reduce the scary factor and try to explain it (with code samples).
I was working on a site today and needed to code a pager (the query was too complex for views). The most logical thing (which I looked for) was a tutorial on coding pagers in Drupal. Unfortunately, I was unable to find one, so I'll post a tutorial here.
Drush Make, a module of mine, has been making waves in the Drupal community since it was released. Its primary goal is to take a file defining a list of modules and themes, or in Drush Make lingo, projects, and create a fully operational Drupal site out of them. Now you can use these same Drush Make files in installation profiles and they will be properly packaged on drupal.org.
Installation Profiles traditionally have been a piece of PHP code that tells Drupal what to do when the site is installed. When one used to download that install profile, they would just get that file. If the install profile author wanted modules used besides code module (for example, a WYSIWYG), one would have to download it after they download the profile. However, Drush Make has changed this.
Drupal.org, using Drush Make as a backend, now allows modules and themes to come with profiles, all in the same file. This represents a major step in installation profiles, as now they are much more useful.