Have you been working on our local machine on a new project. Now you are at the point where you need to get your initial progress where the client can do some content entry, or perhaps a second developer is going to start working with you, or perhaps a themer needs to start accessing the code... what ever the reason for needing to broaden the development environment, that's one option for what you can do.

We are going to utilize our local machine, WebEnabled, and unfuddle. The goal being revision controlled files, in an accessible setting (http://).

This is the tale of a sites with their own classified ads, when they wanted to track how often users who post a classified, were "contacted". Their goal was to be able to see if the classified were successful, based on the volume of responses to the classified ads. A great idea... now I have to implement it.

The setup and layout for this content type is pretty basic.. The Classified Listing is displayed as a panel. The top half is info about the listing (node), and the bottom half is a contact form (send user email form), that sends and email to the user who posted the listing, from the logged in user.

Last week I wrote about preprocess functions and wanted to do a little follow-up because I was having even more fun making changes, adjustments, and alterations.  There is so much here for themers, there is an excess of options and they can be organized and structured very well.  Again, as I often say, I do not profess to be a php-guy (I continue to get better, and using it daily now, someday I will be where I want to be with it...) so this structure and framework has been completely awesome for me.  So what's next with preprocess...

The less tpl files the better.  Don't get me wrong... LOVE the tpl file, can't live without the tpl file... If I need several tpl files, let's do it... but, in some cases, one tpl file can provide enough power and flexibility to handle several content types, and keep the job of a themer a little easier.. o.k., not easier, but a little cleaner for my tastes.

The magic is the preprocess functions.  Here's a little about the preprocess function.

Last year I would have tried to approach this problem with some kind of image/text replacement... This year it's a whole new ballgame.  The Drupal theming layer is like an onion and I continue to pull back the outer pieces and get to better and better stuff.  Maybe it is more like a Parfait (thanks Donkey from Shrek) ;)

So here's what I wanted to do. Drupal gives us a teaser output with comment links.

3 comments  |  2 new comments

I came across this little extra nugget while looking for some stuff for preprocessing. How many times have I typed out base_path and path_to_theme... With this little gem I am just a few keys faster, and lovin it.

function themename_preprocess(&$vars, $hook) { $vars['theme_path'] = base_path() . path_to_theme() .'/'; }

The user login block is one of the most common blocks on any Drupal site. It might be in this region, or that region, or this header, footer, or block... the idea of this post is that it is that you, at some point, you will probably want to theme it... and maybe you'll use this post to help you through. I have spent part to the day working with a flexible way to make the user login block a little cooler. Specifically, I wanted it horizontal, and I wanted to change some of the values, and finally some css to finish it off... and eventually some jQuery if I can find the time. Through this process I was once again reminded of the power of Drupal.