New TBDUG Website

We've launched a new Drupal 7 TBDUG website. Although there was nothing wrong with the old website we decided to seize the opportunity while moving the website to a new host and give the site a face and feature lift. In actuality, it was best to start from scratch with a brand new site and just migrate the existing content over as needed.

The new site has been simplified by dropping the blog, forum and some other features and then consolidating them into a single Content Type called "Bulletins". Any member can post a new Bulletin and, once posted, an email will be sent to all members notifying them of the new post. This should be a great way to keep up-to-date on the TBDUG happenings. Of course, you can always unsubscribe from these notices in your TBDUG profile page.

The user profile pages have also been expanded to allow for entering more info into them. The vision is to have our member directory to be used for more local Drupal networking and connection with our members. Please take some time to review your current TBDUG profile page and add any further information that you'd like.

As needed, new features and functionality can be added going forward as this is just a start. Bring your ideas and comments to the next group meeting to discuss and implement.

Notify User of New Account always defaults to 'unchecked'


User.module (core)


Notify User of New Account always defaults to 'unchecked'.

I notice there is a debate / stalemate of people who have good reasons for either making it default TRUE for FALSE.


Notice also there have been many patches submitted (and rejected) based on either bad coding... or philosophical grounds... because they're attempting to simply change the default..

We would be providing a true solution: Let the admin choose for themselves... without having to write a module to change the default value. Make the default selector part of core!

What It Would Take

This would make a simple exercise for our meeting: Write a quick module that demonstrates how hooks work; a hook for the default value, and a hook to put a default selector in the configuration area.

Then... a discussion of how this would be properly submitted so it makes life easy for the maintainer to accept it.

Wouldn't it be cool if we wrote something that got accepted into Core? :)

Web Admin with Heavy Drupal Experience

If anyone is interested in a web admin position related to Drupal in the Tampa Area, there is a recruiter looking for someone to fill that role. (I'm posting this because currently I am working through TEKsystems as a contractor for Red Hat and he asked if I knew Drupalers in Tampa. :)

Here is his info:

Scott Listak, Technical Recruiter – Network Infrastructure Services
813.636.3754 slistak at TEKsystems dot com