Obsolete

This module is now obsolete. I no longer maintain it.

Drupal 5 doesnt have a nice easy way for module developers to drop .tpl.php files in their module directories for use with modules that do a lot of output. I have no idea why. Drupal 6 has this but 5 does not. So I've created a module that allows module users to mimic the features of drupal 6 without the need to modify drupal 5 core files. It's not identical or perfect but its about as close as you can get without actually upgrading to 6 which may not be a path you can take because maybe some of your modules dont have a D6 version. Also, this system doesnt lock you into a '$content' variable like the normal drupal page template does. It allows you to create the '$content' using the $vars variable. $vars is an array that contains values that come straight from your module. There is also a custom_template.php file that allows themers to inject stuff into the $vars variable as well just like they would with drupal's template.php. Here's a small list of what this module allows you to do:

Create template files in your own Module directory (these can then be overridden by files of same name in current template dir as usual)
Send variable directly to a template (something not possible in d5 and I dont even think d6 does this either, though not sure on that).

Disable the option to re-use CCK fields (prevents splitting fields into separate tables when new fields are added to a content type).

Implements a new form element named taxonomy_widget for selecting a vocabulary and then a term within that vocabulary. The term list is dynamically populated by jQuery when a vocabulary is selected.

FeedAPI Comments is a FeedAPI add-on for aggregating comments to your site.

The uc_webform_productize module is designed to be paired with the webform_associate module. Currently the code is alpha and appears to be working. The objective is to create a uc product node that is paired with content types used by webform_associate. This product should then be added to the cart each time a webform submission is created. It then stores the webform nid, submission id and the order_id in a many to 1 relationship.

This functionality is all complete so I need some help going around the rough edges and make sure it's good to go. Paired with webform_associate, this module goes a long ways toward making event registration in Drupal quite simple.

Currently this is Drupal 6 only, I have no intention of doing this same dev for D5.

Currently:

• Allowing you to pick node types that have webform associations
• Appending the necessary form elements to accept price
• Auto-creating product nodes associated with the proper node type
• Editing of existing information
• Successfully adding an associated product node to the shopping cart
• Submission to Transaction tracking (many to one)

Needed: (in order of importance)

• Permissions checking. I would VERY MUCH like help here.