This forum is for less technical discussions about the Drupal project, not for support questions.

Node bug?

I'm trying to create a contact form (using the form_mail module) but it isn't working as expected. The page doesn't acknowledge the post and simply displays the main page.

In an effort to create the simplest form possible, I created a new "page" node in php mode and added the following code.

Roles, groups, permissions

Apologies for dumbness but... I understood that 4.5 would include node-level permissions amongst other things. I've just installed CVS and can't find any such anywhere. I've trawled through the documentation, and it looks to me as if 4.5 in fact just includes a framework, and that in order to get the node-level permissions, I would in fact have to download and install node_perm module or some such. Please can someone help with three questions:
1) Is this indeed the case?
2) Will this still be the case when 4.5 is released?

Keeping the repository clean

Contributers to drupal might remember that last release the contribution module was cleaned up after a new release.

The plans are to do this again after the new 4.5 release. The last time there was some confusion about why and how this would be done so if you are a contribution maintainer, or are looking for a way to help Drupal, read this carefully.

Because we allow everyone with good modules or themes, to keep those in the contributions, these are not always up to date. After a new release, modules or themes are often not updated, simply because there is no-one to do so. This is confusing, people try to install old modules quite often, resulting in errors, or a non working site. Also, for a lot of people it is not clear that a module is not maintained, so they might not see that there is a great opportunity to help! And because Drupal does not work with backwards compatible releases, old modules will most certainly not work on a new release without modification. For content we do have backwards compatibility, of course.

Contributions will be removed if:

  • they do not have a HEAD branch (i.e. those that are created for a single release only).
  • they are more that two releases old
  • they were not updated for two releases

Note that removing does not throw them away for good. They will still be accessible in the attic of the repository.

Drupal handling of sessions

In one of my drupal site (Drupal 4.4 and php 4.3.8), session variables are stored. But in my other site (Drupal 4.4 and php 4.1.2), they are not. Both are running on linux (former is on red hat and the latter is on debian).

But I guess this is not because of php version because I tried to create a script (outside Drupal) and run it against both sites, and it did stored session variables.

Im thinking, is this because of php settings? Or the different version of linux.

Can someone have an idea? Please help me. Thanks...

addressbook? adding fields to the 'user' table?

I found the drupal 'user' table and the 'data' field which contains the hash of the user profile info, but I'm looking to include more information the what is currently stored in this hash. However this doesn't contain all the fields that I want to get from the users. What I'm looking to do is to have an "organization" field and Organization description field, plus several others. How will drupal 4.4.2 deal with if I add fields to the user' table? Is there a better way of doing this? Is there an address book functionality module?

Limiting the ability to edit content from a specific group

I'm giving drupal a test drive on my home linux box to see if can do what I'm looking to do, I have to say I really like drupal so far. I The groups module would have appeared to be what I want, but I'm wondering of an assigned role would do the trick. I'm looking for a way that a group of people, a family for example, could edit ONLY each other's content and no one other families data. Is this possible? Would the group module, when working again, be able to do this? Is there another way I can get this functionality?

Pages

Subscribe with RSS Subscribe to RSS - General discussion