I'm saving and retrieving custom fields with the user information, but not using the profile module. So I've written the hook_user() function in my module and I can enter these new fields at registration of a new user and edit the account. I wrote my own load and save functions and everything loads and saves. Life is great.
One thing I miss in Drupal is a staging/testing function, to check new versions, modules, templates etc before putting it on the live server. So I'll try to write a module for this.
[First question: is someone already working on this?]
I'll give a outline of my plans here, hoping to get weak parts critizised and some questions answered.
As far as i can understand about the menu iteam's visibility to a particular user, when user has permission to visit that page and it is enabled by admin, then only it is showed in menu iteam unless otherwise it is not.
But what about if i want certain menu iteams to show only to authenticated users and not to anonymous users, evenif both has permission to see the page which that menu iteam crosspond to. And to generalise this problem, what about making menu iteam visibility based on "roles".
hello, I'm trying to create a new module for drupal, but I can't find in the handbooks how drupal works.
My project isn't a simple new node type, I need the hability to insert diferents types of information, and, process it in a certain moment.
I can't understand how the functions in the module file are called, or what happens when, for example, the settings form of my module (created by the settings hook) is sent. Who cares about the information? This is applicable to any form... ok, I can create my form.... but... what happens when click the "submit" button?