Drupal 4.7.x

I am using a small php snippet in my header to pull in various nodes for display in my header.

I use:

$node_id = 4;
$_node = node_load(array('nid' => $node_id));
$header_node = node_view($_node, false, true, false);

For some reason i don't get the node title when i do this - although i do get it when i display the node using:

mysite.com/node/4

Below there's a patch against 4.6.5 that allows the admin to toggle on/off the display of the "$user's blog" link in the main page and on each individual node.

Please include this feature in the next versions of Drupal. Thank you.

Why is the pathauto in cvs "4.6"? I thought there was a new cvs version that worked with 4.7.

Hi All.

I am trying to simply the task of posting a blog with some inline photos of trips, hikes, etc.

I wondered if there is a module, php, api, or combo of these that will automatically reduce an image's dimensions (eg, down to 512x384 px from 1280x1024 px) as it is uploaded/posted?

I am trying to remove Photoshop or ACDSee from the equation altogether.

Thanks!! :)

Hi, I have sucessfully got Drupal up and running, however I am unsure which version I should be using. I really need to use the Workflow module, but as far as I can tell, it is only for the 4.5.x branch and not the 4.6? Yet it says it is dependent on the actions.module which will only run under 4.6?

Basically I was wondering if someone could tell me what version of Drupal should be running to be able to get an extranet-type of system with the workflow module etc. Also if anyone has any tips with creating a workflow/approval content sort of system that would be great. Thanks.

This idea came to me after finding out no similar functionality exists in Drupal. I'm not a PHP programmer, so I'm asking for somebody's help in the creation of this module; more accurately, I'm asking for somebody to make it since I am not able to. Any help would be much appreciated.

Here's the rundown:
 - Used to restrict a Drupal site to specific IP addresses.
 - Can either: (ideally both options would exist and you would select which you want to use)
    1. Block those not on the whitelist from viewing the site at all. Those not on the whitelist are redirected.
    2. Check the user's IP when they attempt to login. If the IP's not on the whitelist, they can't login.
 - Accepts individual IPs or IP ranges.
 - IPs are not associated with specific user accounts as users may access from multiple locations and need two or more entries accordingly.

Basically it's like an opposite of the ban list in troll as far as concept goes. Maybe this could even tie into troll if the author would be interested in adding such a feature. Note that, no matter what, users would be allowed to login; the whitelist is just one step in their authentication process.