blog

I'm starting work to bring a drupal site towards PCI compliance and I thought it might prove handy to document it.

Sadly, I must work towards Self-Assessment Questionnaire D, which is not short. This post is going to focus on Requirement 8: Assign a unique ID to each person with computer access.

I've been working on a relatively complex multi-step form for a while now. It takes a URL argument that represents a set of stored options to control display and behavior. Thanks to $form_state['storage'] that is pretty easy to grab once and keep through all the steps.

great chance for get wederly lyshowe stunn 15 minn G E S start out b ck is wsoonoittle ve offshides cincinnat realtsonga his backing

Here's a little snippet for hook_form_alter that will put another "Save" button right below a comment preview. This way users don't have to scroll all the way down past the edit form to save a comment after preview, it's right there.

This is for Drupal 6.

There's been some buzz about Drupal certification programs recently. Whoever takes up that task, if anyone does, I hope they implement focused certification instead of some monolithic certificate.

Server configuration, themes, module development, site architecture, and the like are all sufficiently advanced topics to merit their own certification. Breaking it down like that might also help realize certification programs sooner, if organizations could focus on developing a program just for the topics they specialize in instead of the whole of Drupal.

Attached is a module that requires anonymous comments to have the supplied email address verified before they enter the normal comment workflow.

In my experience, wysiwyg editors, at least FCKeditor and TinyMCE, won't work if scripts are loaded at the bottom of the page. However, it's great to have the scripts down there for the perceived performance boost.

So, conditional statements in the page.tpl.php to the rescue!

Made a little amusement: Birds That Should Exist.

Another patch today at Google Analytics to allow for segmentation by Organic Groups. I'll give the same rationale I gave there here: Segmentation by OG seems like a good idea because they tend to indicate user interests, and are usually aggregate so they don't violate the Google TOS.

I revisited some of the techniques I was using for a contracts management system for a speaker solicitation and event tracking tool. Once again, node references are creating a parent/child relationship, this time between solicitations for events and events themselves.