Drupal 6.x

Since I have been struggling with this for a while, I think it's time I do something about it. I've seen that other people have tred to address the issue, but no clean solution has yet been found.

Bbackground: a client needs to set up e-mail addresses for her website users. On my server I have an installation of Postfix Admin (http://sourceforge.net/projects/postfixadmin/) that she can surely use, but this poses two problems:

1. she will have 200+ users, and Postfix Admin allows creation of one account at a time. A real pain;
2. the created accounts will still be disconnected from the users' Drupal accounts, which might confuse most users.

I have thought of a couple of solutions where custom-made PHP pages would tap into the Postfix database, but they would end up being very unclean, not scalable, ultimately undrupallike (assuming that's a word).

The best solution would be to take Postfix Admin and make it into a real Drupal module. I am aware of most (if not all) difficulties, among which:

• Postfix Admin manages multiple domains;
• the Postfix database is, obviously, different from the Drupal database;
• Postfix tends to store cleartext passwords (someone correct me if I'm wrong – although I've found a small workaround for this).

Hi All,

Not sure if my question makes sense, but will ask anyway.

My question is how to determine whether the new content type, uses the node architecture or just uses the Drupal API (security, forms API, DB...) but store it outside the node tables?
Are there any general rules outlined for it?

These are the thoughts that brought up the above question.

While drupal supports generating different content types dynamically, any customization and additional fields could be added by writing a module (assuming no CCK is used). In general, the modules can extend the base node feature (title, description and etc..) and store the extra details in new relevant tables created.

While it is tempting to put everything as a node to use the "node power" of drupal, it is probably not a good idea to put everything as a node.
Various reasons like performance and data storage should be considered.

For example, the private message module it does not add the content to the node. It makes sense is just some private data shared between few users. A blog is a content type, which is shared among users and also something that stays for a longer duration.

If I set up a forum on my Drupal based site, is there a way for the forum administrator to have "canned responses" he can use ? Thx.

in 6.x rc2 I installed Ability theme in /sites/all/modules
It is configured in settings to not default to any theme...so I should be able to detect it in /admin/themes not sure about that path...

I will not detect it if I place it in /modules folder.

Any ideas?

The problem is that I can't get my own form elements to show up in the Block specific settings menu. There is only the default Block specific settings field, Block title.

Below is my testapp.module file, which is not ready and made following the tutorial ("07. Create a module configuration (settings) page" was a little hard to follow)

If someone could just tell me how to modify the code to get the textfields to appear in the Block specific settings, that would be awesome..

Hi there,

I'm developing the geobrowser module. http://drupal.org/project/geobrowser - check out a working version at http://mapping.uvic.ca/?q=geobrowser

I would like some advice on the node info pop-up viewer. Right now it is an iframe - I decided on the iframe because I wanted a fully interactive node-view where users can edit nodes etc. right in the iframe.