I like the new capability to pass hidden params as values without sending to the browser. However this is only supported if I create a function with "[form name]_submit". This is fine but such a function seems to require that the original form be rendered immediately after my processing code. I was unable to prevent this.
Thus, the "[form name]_submit" method of processing a form is not usable for interjecting a confirm form ("are you sure you want to...") between the form and its processing?
note that this would be nice (Not sure as tot he implementation details)
I needed your advice. Should I try to install 4.6 modules to a new 4.7.0-beta.x installaiton? What the implications would be? Do you think some of them would work as normal?
I've been working on a simple way to add a configurable contacts directory to Drupal sites. The contacts_dir.module didn't come across as very configurable if the module is used to power multiple sites from a single document root.
My solution is to allow the user to define their own contact card form using Flexinode. My module then works around the flexinode you've created to provide an interface to browse your contacts.
The upside of this is each contact is a Drupal node, so (in theory) other Drupal modules which work with nodes should work nicely.
Wondering if anyone could give me any insight as to the best solution for this situation.
I'm just in the process of setting up my first Drupal site for my department's intranet at work and am writing a module to authenticate users via their Unix account details (local and NIS). I've got the basics in place - it's treated as a distributed authentication method which calls an external perl script which does the authentication checks then returns the result.