Yesterday we added permission so only authenticated users will be able to access our test page. Today we're moving on to introducing theming and templates. Up until now, you'll notice that we're generating our test page's html code inside the function dfacebox_test_form. This is valid, but instead we're going to take advantage of Drupal's theming capabilities.

For Drupal to be able to recognize our theming function, we need to implement hook_theme. It returns an array of theming function together with its arguments.

As promised, after my Python bragging we're going to resume and wrap-up everything on our dfacebox module. If you still remember, our test page is accessible to anonymous users (users that are not registered). You don't normally exposed module settings or test pages like this so instead, we're going to apply some restriction so only those that have permission to access it will be able to view except for the root account which pretty much can do everything.

I was looking for some updates regarding the Drupalcon like event this coming december on the Philippines group at drupal.org but instead there was an announcement about Drupalcon Asia-Pacific Organizers Group (DCAPO).

As the 3rd and hopefully the last part of our Drupal module development series, we're going to create the actual link function that enabled support for facebox and some test page to demonstrate our function. First of all, the purpose of this function is to add the rel attribute on any links for Facebox to recognize it. Now Drupal has this l function which is used in creating links and has a 3rd optional parameter where in we can set the rel attribute, but I'm kinda lazy so instead of doing that, we're going to create a function.

Last time I gave the contents for dfacebox.info file so today we'll concentrate more on dfacebox.module. The first thing we need to do is to define a constant MODULE_PATH which holds the path to our module, this way we could access our module's path easily.

Its been 4 days since my last post and it wasn't even related to Drupal. Before I get the feeling of breaking my promise, here's an introduction to module development in Drupal.

 Every week, I spend most of time on Drupal but lately I've been so attached to Ruby so I wasn't able to post anything related to Drupal. Ruby is like an addiction, you should use it with caution otherwise you'll find yourself struggling your way back to whatever you're used to. 

I was checking some files from a project so as usual after logging-in, I poke around a bit and suddenly stumble across the administration area. Normally I would just mosey along and continue poking but the administration UI was just so awesome!

As a devleoper I also deal with theming sites and as far as theming is concerned, I really like Zen as my base theme.

On my work today, I was assigned to create a theme for some mockups that client has made. So I went ahead and visit the Zen link to download it. After downloading, like most of what's happening in Drupal, I don't memorize or I haven't yet the steps in creating the subtheme. So I browse the docs for creating a subtheme and there was a link at the top saying how to automate the process.