Module development and code questions

hello,

I've just installed the latest release of acidfree + patch for the filemanager.
I put the dir 'acidfree' in the modules 'dir'.
I activated the filemenager module, no problem. I activated the acidfree module, and I have plenty of warnings (=errors ?) :
warning: Invalid argument supplied for foreach() in /var/www/sdb/4/b/poulette1976/drupal.4.6.3/modules/acidfree/acidfree.module on line 113.

When I click on create content, I have the same message.

When I click on 'acidfree media', I have :
warning: Invalid argument supplied for foreach() in /var/www/sdb/4/b/poulette1976/drupal.4.6.3/modules/acidfree/acidfree.module on line 113.
warning: array_keys(): The first argument should be an array in /var/www/sdb/4/b/poulette1976/drupal.4.6.3/modules/acidfree/acidfree.module on line 1440.
warning: in_array(): Wrong datatype for second argument in /var/www/sdb/4/b/poulette1976/drupal.4.6.3/modules/acidfree/acidfree.module on line 1440.

When I try to create an album, I have a white page with the messages :
warning: Invalid argument supplied for foreach() in /var/www/sdb/4/b/poulette1976/drupal.4.6.3/modules/acidfree/acidfree.module on line 113.
user error: Access denied for user 'poulette1976'@'212.27.63.117' to database 'poulette1976'
query: LOCK TABLES sequences WRITE in /var/www/sdb/4/b/poulette1976/drupal.4.6.3/includes/database.mysql.inc on line 66.
warning: Cannot modify header information - headers already sent by (output started at /var/www/sdb/4/b/poulette1976/drupal.4.6.3/includes/common.inc:384) in /var/www/sdb/4/b/poulette1976/drupal.4.6.3/includes/common.inc on line 192.

I installed forward.module for drupal 4.63 and it's working fine, but it would really be great if the email that is sent could include the node/page title and maybe even a teaser/excerpt instead of just the url. I've searched for possible solutions, but can't find any previous discussions on it. I'm guessing that I need to get data based on the $nid and print it, but can't figure out how to do it. Can anyone help? Thanks.

I am using the 4.6 releas of the Stock Quote Module. Obviously, it allowes individual users (if so configured) to input their own stock portfolio. What I would like to do is have the administrator configure a "stock portfolio" that displays for all users in a block. Has this been done or any way do do this?

Thanks

I probably put this question in the wrong place.

Content on my site is for registered users. The Events module still allows access no matter what I do. I don't see Events show up under Access Control. Is there a way to close off Events for non-registered users?

I developed my first module and translated it (in french). But I note that the access permission do not appear in the POT file, and thus they are not translated in the access control administration page. How do I translate them?
I used the same syntax as for user.module:

I'm working on a club module with the following features:

Allow authorised users to:

- create clubs
- join clubs
- leave clubs
- view club content only if they are a member of the club
- post content to clubs only if they are a member of the club

Progress so far:

club.module is based on a clone of forum.module.

new content type: 'club' - nodes posted via the club are tagged as type 'club'.
new vocabulary 'club'
clubs are taxonomy terms with vid = 'club'
nodes posted to clubs are tagged with type = 'club'.
new table {club} (like {forum} and {club_user} which gives membership level of club.
users can create, join and leave clubs.

Add small change to tracker.module and comment.module to hide nodes of type 'club' (not happy with this as it's too specific - would like a more generalised solution). Also need to change ... umm ... node.module I think to exclude 'club'-type nodes from "popular content" block.

I'm having problems working out how to disable searches of 'club' nodes for non-club members.

Ideas I've had to do this:

1) Exclude clubs from the index:

Hack search to exclude 'club'-type nodes when indexing. Nasty.

Add a club_cron() function to post-delete search terms pointing to 'club'-type nodes. Problem is that can't control the order that modules hook_cron() is called, and club_cron would need to run last, so this would need a hack to module.inc:module_list(). Nasty.