Deprecated - Drupal core

i would like to do the following: add a few lines to taxonomy_select_nodes in taxonomy.module so that i can call a url such as taxonomy/term/8/all/blog and get all blog posts of term 8.

what is have done so far is add some stuff to function taxonomy_select_nodes so that it now looks like this:


function taxonomy_select_nodes($tids = array(), $operator = 'or', $depth = 0, $pager = TRUE) {

if (count($tids) > 0) {
// For each term ID, generate an array of descendant term IDs to the right depth.
$descendant_tids = array();
if ($depth === 'all') {
$depth = NULL;
}
foreach ($tids as $index => $tid) {
$term = taxonomy_get_term($tid);
$tree = taxonomy_get_tree($term->vid, $tid, -1, $depth);
$descendant_tids[] = array_merge($tid, array_map('_taxonomy_get_tid_from_term', $tree));
}

if ($operator == 'or') {
$str_tids = implode(',', call_user_func_array('array_merge', $descendant_tids));
$sql = 'SELECT DISTINCT(n.nid), n.type FROM {node} n '. node_access_join_sql() .' INNER JOIN {term_node} tn ON n.nid = tn.nid WHERE tn.tid IN ('. $str_tids .') AND n.status = 1 AND '. node_access_where_sql() .' ';
if (arg(4)){
$sql .= 'AND n.type = ' . arg(4) . ' ';
}
$sql .= 'ORDER BY n.sticky DESC, n.created DESC';
$sql_count = 'SELECT COUNT(DISTINCT(n.nid)) FROM {node} n '. node_access_join_sql() .' INNER JOIN {term_node} tn ON n.nid = tn.nid WHERE tn.tid IN ('. $str_tids .') AND n.status = 1 AND '. node_access_where_sql();

Hi, folks

I need to seemlesly integrate drupal in a bigger site, so that users are automatically logged-in to drupal as soon as they log on the site.

What's the simplest way of doing this?

Btw, what happened to various authentication modules that once existed for drupal?

With Drupal growing and maturing as a project, a formal and explicit structure of roles and decision making would probably be appropriate.

I've recently attempted to capture current practice in the post "Proposed, draft guidelines for contributing to Drupal" and the book page "The Drupal community". But I was unclear on several areas, e.g., how are different types of decisions made in the project?, how are individuals accepted into specific roles (e.g., core developer)?.

I've been testing multiple virtual hosts running off a single copy of Drupal to see what are the minimum changes needed to do so. The approach outlined here turns out to be quite simple, mainly because Drupal is so well written in the first place. With my approach, it comes down to essentially moving includes/conf.php to index.php and commenting out the reference to that include in bootstrap.inc, and, providing 4 soft links in the virtual host doc root along with the modified index.php and that's all, run two or 2000 instances of Drupal at different vhosts (or just URLs on the same vhost) and each one can have a separate database, or not. This has not been extensively tested, and certainly not on production servers, but I am excited that it looks to be so simple to do this as I have agonized laboured extensively to do this with other packages over the years (various php-nukes thru to phpBB). The basic layout looks like...

// around line 430 in includes/bootstrap.inc
//include_once "includes/$config.php";

/var/www/drupal-1.vhost.lan ls -l
total 4
lrwxrwxrwx  1 root root   18 Aug 22 13:17 includes -> ../drupal/includes/
-rw-r--r--  1 root root 1428 Aug 22 13:42 index.php
lrwxrwxrwx  1 root root   14 Aug 21 17:41 misc -> ../drupal/misc/
lrwxrwxrwx  1 root root   17 Aug 22 13:17 modules -> ../drupal/modules/
lrwxrwxrwx  1 root root   16 Aug 21 19:45 themes -> ../drupal/themes/

I am trying to install drupal-cvs version (21st August) on to a postgres database. There appeared to be a number of errors in the database.pgsql file, so I have done a line by line comparison against the mqsql equivalent and hopefully made it the same, whilst correcting all the errors.

Not sure if its important, but I did re-order the table creation to be in the same order as the mysql version. It seems to me that doing so will help maintainability for the future - apologies to anyone if there was a reason that order was different.

I must stress, I haven't got drupal working yet, just managed to create the database without errors, so although the changes I made seemed sensible, they may well not be - as I don't have any knowledge of the internal working of drupal;

I've created a patch file. I hope it works within a code block


--- database.pgsql 2004-08-21 00:53:59.000000000 +0100
+++ /home/alan/roo/drupal/database/database.pgsql 2004-08-21 23:52:45.000000000 +0100
@@ -29,69 +29,11 @@
CREATE INDEX accesslog_timestamp_idx ON accesslog (timestamp);

--
--- Table structure for authmap
---
-
-CREATE TABLE authmap (
- aid SERIAL,
- uid integer NOT NULL default '0',
- authname varchar(128) NOT NULL default '',
- module varchar(128) NOT NULL default '',
- PRIMARY KEY (aid),
- UNIQUE (authname)
-);
-
---
--- Table structure for blocks
---

I'd like to see a fuller treatment of Drupal aims, structure, and process. What are the aims of the Drupal core, how are decisions made, how can new members contribute? This would be valuable to provide a clear frame of reference for Drupal community members. This could go into the Dupal handbook, likely in the "General information about Drupal" and "Developer's guide" sections. In particular, I could see the existing information in the handbook (bug reports, feature suggestions, creating and sending your patches, etc.) reorganized under a general section of "How to contribute". Towards that end, I've drafted the following for discussion and revision.