DRUPAL TUTORIAL INSTALL
DRUPAL TUTORIAL REGISTRATION

The hook weвЂ™ll be using is: hook_form_alter(). Now that we know the form id of the form weвЂ™ll be overriding, we can get started leveraging that with some of DrupalвЂ™s magic. You should see some hidden form fields вЂ“ weвЂ™re looking for the one with the name=вЂќform_idвЂќ вЂ“ this element holds the formвЂ™s unique identifier which we'll be using in our module. Use firebug to inspect the the HTML for the form. Head on over to user/register on your Drupal site.

First, we need to figure out which form weвЂ™ll be overriding. LetвЂ™s start with adding our new fields to the form. Remember, it should be installed at the following path: sites/all/modules/custom/form_overrides. At this point, itвЂ™s safe to navigate on over to Admin > Build > Modules and enable your module. Finally, the вЂќcoreвЂќ line tells Drupal which versions this module will work with. The вЂќnameвЂќ and вЂќdescriptionвЂќ lines tell Drupal the human-readable name/description of our module as it will be displayed on the Module Configuration page. The first line вЂќ: $Id$вЂќ is a CVS identification tag вЂ“ itвЂ™s not super important because we wonвЂ™t be submitting this to the Drupal community, but itвЂ™s still good practice. info file вЂ“ explanation following:Дescription = Adding some custom form overrides.

form_overrides.module: where all the Drupal magic happens.

form_: this simple file tells Drupal about our module вЂ“ the name, what versions its written for and what it does.

Inside this new directory, IвЂ™ll create two files: So IвЂ™ll create a new directory called form_overrides within our custom folder.

IвЂ™m going to call this custom module Form Overrides since weвЂ™ll be doing just that. Second, if we ever hand off the site to another development team or directly to a clientвЂ™s IT team, this will help them keep things straight. This serves a dual purpose: First, it lets anyone working on our team know that the modules inside this directory are indeed custom and written by CHROMATIC.

DRUPAL TUTORIAL INSTALL

So I install all of my contributed modules (Views, CCK, etc.) at sites/all/modules and all of my custom modules at sites/all/modules/custom. I like to keep all of my custom modules in a separate directory from all of my contributed modules. Let's jump right in! Create the module files/directory Here's what the end result will look like: Add an administration panel to Drupal that will allow the client to change the вЂњTerms of AgreementвЂќ text.

DRUPAL TUTORIAL REGISTRATION

Add validation to that same form to ensure that the new user has agreed to the terms before allowing registration.

Add a вЂњTerms of AgreementвЂќ fieldset/textarea to the User Registration form.

I mapped out exactly what my custom module was going to need to do: This text needed to be embedded right within the form, so a simple block or popup wouldnвЂ™t do. In addition, the client wanted the ability to edit the вЂњTerms of AgreementвЂќ text whenever they needed to. That is, if you know how and where to tap in.Д«asically, I needed to add a вЂњTerms of AgreementвЂќ section to the default User Registration form that ships with Drupal 6 and user.module. Last week, I was working on some Drupal form customizations and validations for a clientвЂ™s site (launching soon) and thought IвЂ™d share how you can easily alter Drupal forms.

Drupal tutorial