Module development and code questions

I am using 4.7 with access control, category permissions, and tagadelic.

Even if I access control content type by category permissions, it seems the same rule can not　be applied tagadelic (tagging cosmo).
Hence tagging cosmo ("tags in xxxx") appears to those who can not get access to that content type.
Appreciate if someone could offer some advice.

Regards,

I used form APIs to create a form page and after I clicked 'submit', I want still go to the same page and send the form values to this page so I can use $_POST['xxx'] to get it. How to do it? In the _submit function I do not know how to write...

I've recently been using nodeapi in my PayPal module to restrict access to parts of an advert before it is paid for. This was ideal for me as nodeapi can effect any kind of node type I was able to allow admins to choose which types should be paid for, including CCK created types.

This led me to wonder: Would it be possible to extend nodeapi to allow it to secure a site? Not just modify the node at various key stages as it currently does but allow it to completely prevent access to a node.

Is there a way to bypass the filtering of content from a code level? I've written a module and would like to bypass HTML filtering on a 2 specific fields, and those 2 only, but I'm unable to find a way to do this.

I don't think using the Input Filterting admin to create roles and such is the way to go. I thought perhaps referencing the $_POST vars directly would work, but it seems Drupal processes them before my module can get to them.

Anyone know of a way to get the raw posted content or bypass the filters? Thanks!

I just wrote a new module, and I'm looking for testers. I've not yet created a project, but it can be downloaded from CVS:

http://cvs.drupal.org/viewcvs/drupal/contributions/modules/volunteer_tim...

This is an add-on module for the event module, so you mut have event activated first.

I have been using a simple self-written module with my site for a while, and then I added some new database fields and functionality to improve it. I wrote the module_update_1() function and it worked perfectly. My question is should I leave the module_install() function as it was originally, or should the function be changed to create the table in its final form?