Glue code in Drupal 7

Track: 
Implementation and Config
Experience: 
Intermediate

"Glue code" is those few lines of code in a custom module that get your project from 90% done to 100% done -- without hacking core or any contrib modules. It's what lets you adapt your Drupal project to your client's needs, giving them full satisfaction, even for small but important details.

Putting glue code separate from the rest in a custom module that makes use of Drupal's many APIs has been a best-practice for many releases already. However, developers switching from one version of Drupal to the next one will need to adapt. There are new APIs, new modules, new possibilities, but also new issues that one is confronted with.

In this session, we will look at how to resolve practical examples based on projects that one could encounter as a professional Drupal developer.

Intended audience: 

This session is targeted at people who are getting into Drupal 7 development, whether they have prior experience with older versions or not. We will be looking at code, so some programming experience is required.

Questions answered by this session
Question 1: 
What are "glue code" modules, and why should you use them instead of hacking core?
Question 2: 
Where do you put your custom code? How do you organize it?
Question 3: 
How do you use features in combination with glue code? What are the best-practices for automating your configuration deployment?
Question 4: 
How do you deal with the new language codes when modifying forms, nodes, fields, etc when using hooks? (something that wasn't necessary in Drupal 6, but is now required even for monolingual websites)
Question 5: 
What are examples of ways we can use the new APIs that weren't possible before?
3.94737
Your rating: None Average: 3.9 (19 votes)

Diamond Sponsors

 
VPS NET
Palantir.net

Platinum sponsors

 
Trellon
workhabit

Gold Sponsors

 
Chapter Three
Treehouse Agency
NorthPoint
Drupal Connect
HotDrupal.com
Microsoft
Duo