General discussion

Hey, folks. I'm the leader of a 3 year old online community called "Dreams in Digital" that hasn't even gotten off the ground yet. We have no web-site, no finished projects, nothing to show for it at all but 100MB of IRC logs and a crapload of knowledge on CMS's (such as Drupal).

I have done a proof of concept of the new i18n implementation, as I outlined in this previous forum. I've sent this to the dev list one week ago, but so far I haven't got any reply.

It is a module (i18n) and some small patches. Provides multilingual nodes, taxonomy and variables, for the moment, but it is enough to make a site look 'multilingual'. It doesn't require major database patches and it is not backwards compatible with old i18n, but only if you are using duplicated tables for languages.

Whilst deciding which CMS to use, I noticed that the Drupal site looked nice. So I installed it.

I was disappointed to find that the Drupal website template isn't available.

Why would the creators of drupal not want their users creating equally aesthetic websites with Drupal software? :s

I am just looking to create a simple but attractive website, as easily as possible. Please can other users direct me towards some attractive skins?

I have used mambo for my Counterstrike website, but I wanted to try something new.

Has anyone given and time or thought into extending the drupal user tables to allow for a more robust representation of groups. Let me define a term before I go any further. I don't mean a "Group" in the permission sense that you are probably thinking. I am thinking more along the lines of group based accounts.

Currently, Drupal has a login and password for a singler user. There is even a module, profile i think, that allows us to add additional fields to users. But a user cannot tie other people to their account. What I am getting at is a module that would add a family or small group based relationships to the user table. For example, in a previous life I designed a camper registration system for a summer camp where a parent would create an account that included thier spuse and children. The table structure would look somthing like this. One other thing, to keep things simple, the entire family operated under one UID/Password. This way for most dropul modules it would treat this family as one person.

User Table
UID
First Name
Last Name

Family Table
FID
Home Address
Home Phone

Parent Table
UID
FID
Email
Work #

Child Table
UID
FID
DateOfBirth
School Attended

I realize this is probably a specialize niche tool but I am just fishing for some general comments. Would this type of addition have wider implications for Non Profits? Small B

Hi,

I am setting up a site for a community of programmers and engineers here at work and am having trouble choosing the proper modules (being a Drupal newbie, I find the descriptions in the downloads section a bit lacking).

Here is what we need:
- a links module that will allow users to add to a list of links (it looks like the "weblink" module might be good for this - am I right?)
- a files module that allows users to upload files from their hard drives
- *two* news sections (one private for registered users only, and one public)

Hello all,

I'm just starting with Drupal and I'm already stuck. Here's what I want to achieve. Take a look at that site: http://www.webdesignfromscratch.com

Well, I'd like to create a similar structure in Drupal:

Basics
--- Web design process
------ Your goals
------ Think-then-do
------ etc...
--- How people use web pages
--- etc...
Tutorials
--- etc...
Case Studies
--- etc...

Each of those nodes should be able to contain an article and, more importantly, be accessed via its corresponding URL. Example:

/basics/
/basics/process/
/basics/process/goals/
/basics/usage/
/tutorials/

So, I've set up a test Drupal installation, enabled the needed modules and created two book pages - "Basics" and "Web design process". For "Basics" page I've set an alias "basics", for "Web design process" I've set an alias "process". The problem is that the URLs are not properly created. Now I have /basics/ and /process/ URLs, instead of /basics/ and /basics/process/. If I manually create the alias to be /basics/process/ - then it's ok. But it's a dumb solution to have to type in the whole tree of categories manually in the alias field and then a slight change in the trunk triggers a wave of problems in branches.

If that's the DEFAULT behavior... well... it's quite illogical... and could you point me to a module that alters that behavior to the manner I described? I just want Drupal to understand that process/ is a sub-article of basics/ and adjust the URL accordingly.