Module development and code questions

I just applied this patch for the survey and forms modules to get it working with 4.7 (cvs). But I see no way to create fields? Any advice?
http://drupal.org/node/43346

Hi! In Drupal 4.6, the $category parameter to hook_user allowed you to have separate areas for different kinds of data to be entered. However, 4.7 doesn't seem to be doing this. As a result, my forms never get displayed, because I'm keying off of the category. Is this no longer the way to do things? Why is the $category parameter never set to anything besides 'account'?

Thanks,
Ricky

The CiviCRM team has released an integration between the Citizenspeak module and CiviCRM. Feel free to give it a try and see how you can integrate your modules with a full-featured constituent relationship management system. Note this integration works with CiviCRM 1.5, which is the current development version avaliable from svn.

http://wiki.civicrm.org/confluence/display/CRM/CitizenSpeak+Module

Comments and improvements welcome.

I'm installing the ecommerse module and can someone tell me what the difference is between the two submodules:
paypal Process payments using paypal.
paypalpro Process payments using the PayPal Pro API.

Thanks.

I've got a module going that was running fine until this morning. Suddenly, required fields aren't throwing errors if they aren't filled out. The end result is that whole nodes can be generated without required content.

Where should I be looking to track down this problem? I've rolled my module back to several previous versions and they're all suddenly behaving this way. I have not installed any new modules, nor have I enabled/disabled any modules.

Any ideas?

Hi,

I'm currently writing a new product type called rentable product for the ecommerce package,
but I can't get to understand how the Forms API really works.

Here's parts of my code for now:

function theme_product_rentable_view(&$node, $teaser = FALSE, $page = FALSE) {
  
  $price_string = '<div class="price"><strong>'. t('Price') .'</strong>: ' . module_invoke('payment', 'format', product_adjust_price($node)) . '</div>';
  $node->teaser .= $price_string;
  $node->body .= $price_string;
  
  $link = l(t('Check availability '),'rentable/availability/'.$node->nid);
  $node->teaser .= $link;
  $node->body .= $link; 
  
  return $node;
} 

When a rentable product is created, this puts a link on the bottom of the product body.
Clicking on the link is controlled by the following function:

function rentable_menu($may_cache) {
  $items  = array();

  if (!$may_cache) {
      
    $items[] = array(
	  'path' 	 => 'rentable/availability/' . arg(2),
      'title'    => t('Product availability'),
      'callback' => 'rentable_check_availability',
      'access'   => true,
      'type'     => MENU_CALLBACK);
  }

  return $items;
}

The next function then invokes a callback to rentable_check_availability():

function rentable_check_availability(){
$output = '';

if(!is_numeric(arg(2))){
drupal_set_message('Product not selected','error');