Agaric has added the following modules to our development git repository. Alphabetical order:

http://drupal.org/project/coder
http://drupal.org/project/coder_tough_love
http://drupal.org/project/deadwood
http://drupal.org/project/devel
http://drupal.org/project/enabled_modules
http://drupal.org/project/export_node
http://drupal.org/project/hooker

If you want to use Drupal sessions and the logged in user object from a straight PHP script not at Drupal root but somewhere in subdirectories in a site, you will probably need to do something like I endend up doing in profiles/scf/switch.php to impersonate the Drupal site root directory.

In fact, I think the partial installation profile idea might need something like this.

There's a hook for that! The logically named hook_requirements lets you set requirements for each module.

To make these requirements apply to an installation profile, simply put your implementation of hook_requirements in the .install file of a module that is required by that installation profile.

See and report to:

How to disable "Add new comment" at teaser part, but "Read more" remains
http://drupal.org/node/151648

Hi Brian,

benjamin-agaric: a Views 2 question-- we have two content types (one for images, one for posts) connected to the same vocabulary, we would like a view of the images (actually a CCK field on a node type) where the link from the image goes to the single post tagged with that term. Now I'm thinking this is such an edge case I should just do it in the theme like always. But--

Using FileMerge to compare (Mac OS X graphical diff), no differences between the page.tpl.php in the scf_base theme and the page.tpl.php I have in scf.module.

But the site doesn't look the same at all. That means the reason moving template files to the theme layer failed is because I am not calling them right.

Had to put them in hook_theme_registry, of course.

In Drupal 6, the way watchdog() is used has changed a bit.

It's all defined in the API, of course, but some things could use a little more clarification.

Here's the function definition as a starting point:
http://api.drupal.org/api/function/watchdog/6

Without further ado...

So of course the first thing I want to do in Drupal after I get it
installed, while Jess is working on theming our new site (which sounds
like going through a time machine back to 1999, since many of the
available themes are hideous, use tables and are not cross-browser
compatable...), I want to add a new field to the entry form for my new

How to in Views 2: Using a taxonomy term associated with a node as the argument in your block view. In the original Views module, the PHP Argument handling code was a collapsed fieldset that opened to reveal a textarea in which to input code. In Views 2 this is still necessary, unless we're missing out on some uber-advanced method, but harder to get to.

We are certain it must exist though:

After directly replacing just the icon location (changing sites/example to sites/default and nothing else) in the theme settings (global and theme-specific) of a site recently updated from Drupal 5 to Drupal 6, the menu for the site disappeared with array_merge errors in two lines in the ./includes/theme.inc file.