My contact Mark came from a tech background. This really made explaining options a breeze and he had a very realistic expectation of what could be expected. He wanted to stick with the current site design and navigation with incorporating a modern CMS (content management system) so that they could manage the site’s content on their own.

After a short meeting and review, it became pretty apparent that Drupal would be a perfect fit for their CMS needs. I gave him a quick Drupal demo and he agreed as well. He was actually very much impressed and excited with what Drupal would offer them out of the box.

I also suggested that they try out Dreamhost for their hosting needs. Dreamhost offers free hosting for non-profits, and free is very hard to beat. I wasn’t sure if the free shared hosting plan would be good enough to support a Drupal site, but thus far it’s been great and looks to be a perfect fit for them.

The majority of their content needs were rather basic, but they did want the ability to upload and share mp3′s of their weekly sermons. Thankfully there were some great modules available that we were able to build upon.

Here’s a list of the modules used by their site:

• audiofield
• calendar
• ctools
• date
• entity
• file_entity
• libraries
• media
• pathauto
• token
• views
• views_slideshow
• webform
• wysiwyg

As you can see most are the standard site modules, but the audiofield was a new one to me and really solved the issue of uploading and playing mp3 files. It worked great.

I built the site on the Zen theme, which really made things easy to get started. Just chunked up their existing site into regions and blocks and styled things up from there.

After meeting with them to train them on using Drupal to manage their site, they were extremely pleased and enthusiastic to get started. It really felt great to know that I was able to deliver such and excellent solution for them at a very affordable price. I’m really glad I took on this project and can’t wait to see how well they do keeping content up to date.

It was fairly difficult finding the tag to add to enable quantity on checkout, so I figured I’d share in case someone else ran into the same issue. Official documentation was eventually found.

It’s a very basic input that must be included with the form:

<input type="hidden" name="undefined_quantity" value="1">

<input type=”hidden” name=”undefined_quantity” value=”1″>

That’s all, just include that with the form and you’re all set.

I wanted to display all the child pages of a Page as an unordered list. I initially tried using the WP_Query function to make this work. I tried creating a loop and feeding it some parameters, but kept getting no results.

Upon some further searching I did come across the wp_list_pages() function. I’m not sure why I didn’t begin with this, but for some reason I was set on using WP_Query.

There’s a ton of parameters and some great examples found on the wp_list_pages() page.

Here’s the little bit of code I added to a template to output the child pages as a list. Notice that the parent page’s id is the 32 that you will see as a parameter below. Enter whatever your parent page’s id is in it’s place.

wp_list_pages('sort_column=menu_order&title_li=&child_of=32');

Doesn’t really get much easier that that.

A Draft was showing up for only 1 user that a Draft that she had sent to me to publish was still being reviewed by me. This wasn’t the case, however no matter how many times we tried to remove the .LCK file or edit the page again etc. it was still telling her that I was still reviewing it. So she could no longer edit that page, yet any other user could.

We deleted traces of the draft on the server then her local machine. However, her Contribute would recreate the draft status. So after much work, we finally went to her Draft Console and right mouse clicked on the Draft and viewed properties.

Up opened a wonderful little video stating the drafts filename (it’s a pretty crazy random string) as well as the URL path to where this phantom Draft existed on the server.

Once we had this path, we were able to delete the remnants of this Draft from the server and all is well again. Damn you Contribute, damn you to hell.

Just create a template file titled:

field–[field_name].tpl.php

and save it in your theme’s directory:

/sites/all/themes/[your_theme]/

You can get the field name on the Content Type screen, Structure > Content types > [your_content_type]

Then you just enter your markup in the field–[field_name].tpl.php file that you’ve created.

You can use the field.tpl.php file located in /modules/field/theme/field.tpl.php as a starting point.