Post installation

I'm looking for a php snippet that might take say (x) events in a specific cateogry and siplay then in a page or node. Any takers?

I have a certain node type (cck) that is to be created by authenticated users.

These nodes will eventually be organized by taxonomy, but this task is left to admins, not the node creator.

So, in the node creation form (if node is being created by authenticated user), no taxonomy settings would appear.

After node is created, admin would edit it, and then the taxonomy settings would be visible and be applied.

Is this possible anyhow?

In forum, where i can customize the options of Forum like a: comments per page, ordinance of posts (more recents and older) and list types.

I did not find where these fields/options are generated. I need to customize the functions that this fields/options calls, because they are not functioning in my Drupal.

Thanks!

Hi,

First question:

First of all Im wondering if I should moderate (unpublish) by default the first couple of stories from new members, just to make sure thay are not spammers submitting porn urls or whatever...

The workflow would be: 1) authenticated user submits first node --> it gets unpublished and sent to moderation queue

2)admin(or editor) sees the node and votes for it, thus publishing it (and leaving it in the node moderation queu, but thats another story.)

3) after one or two stories the user gets a new role where he can post without being unpublished and checked first...

I want to do this cause I fear to let full control to the members, as Im afraid that spammers will flow to add their bogus stories..

Do you have any other solutions to suggest on a way to control stories, maybe without unpublishing them?

Stories could be for example in moderation queue by default and then published to their CATEGORY home page after a couple of votes...

which leads to question number 2:

How can you protect a site like that from the digg.com effect (friends digging friends, manipulation of results by small groups, etc...)

In my example I could post new stories in a moderation queue and the say for example that after 3 votes the node is added to the 'popular news' page, thus removing it from the moderation queue...

What can protect me from the fact that a single user can open three accounts and boost himself with three different accounts... Or ask his friends to help him for example...

I have a document, currently being kept in a spreadsheet, that I would like to manage and edit within Drupal.

The document is a change control log consisting of many rows of issues-based events, and with columns such as: entry date/approval date/closed date/status/system/description/downtime/users affected

It is then displayed in a list, and, obviously, is sortable by these column headings.

Will the ecommerce module work using PayPal pro?