Version number in Documentation nodes

This comment written Sept 25, 2005; Current release of Drupal is 4.6.3

I am setting up a website for a small non-profit, primarily to give them the benefit of being able to easily edit their website, and perhaps to take advantage of other CMS features in the future. This means I'm not concerned about setting up comments or forums or votes at this point, but my primary focus is changing the 'look' to what we want. Drupal looks pretty good, so I've installed it, and have now started reading the documentation to figure out what I need to do to put together a theme for our site.

However, it seems that the documentation for Drupal doesn't follow a particular version of the software; this means that documentation, for example, for the Theme Developer's Guide, will have some pages written for 4.7, others written for 4.5.x, and others for 4.6.x, but the end reader won't know which version a particular page is talking about unless the author expressly mentions it in the body. To make it more confusing, when you go from one node to the next, the documentation may well be for a different version than what you are using - but nothing tells you this.

For example, the second node in the Theme Developers Guide,,, does indicate, in the text that it is talking about a feature - regions - that is not introduced until 4.7, which at the time of writing is CVS. If you keep clicking on to the 'next' page in the documentation, one might assume that each subsequent page is still talking about 4.7, as there isn't any further mention of versions. However, in the phptemplate documentation, at, there is a comment that the documentation is out of date as of 4.6.x - presumably the page in question was written for 4.5.x. So now a reader is thinking - what about all the other pages I just read through? What version were they talking about? Are the instructions different for the version I am using?

theme_comment missing from themeable functions in documentation

I'm new round here, but shouldn't this page:

Be linked to from here:

and, while we're at it, here:

It took me ages to work out how to theme the comments!

Drupal Licensing information needs a handbook page

Currently the description of Drupal Licensing is limited to the following passage in About Drupal » Background » Mission of the Handbook pages:

Open source. Drupal is based on the open source philosophy of collaborative free software development and is licensed unde the GPL. Drupal is itself open source and builds on and supports other open source projects. Specifically, Drupal is coded in the open source scripting language PHP and supports as primary data sources the open source database formats MySQL and Postgresql.

Given this weekend's discussions and earlier remarks there seems to be a need for "official clarification".
The information should:

(a) method of integrating PHPinfo within Drupal site

Just a method for people who wants to show PHPinfo inside Drupal

PHPinfo Description:

Outputs a large amount of information about the current state of PHP. This includes information about PHP compilation options and extensions, the PHP version, server information and environment (if compiled as a module), the PHP environment, OS version information, paths, master and local values of configuration options, HTTP headers, and the PHP License.

go to
Admin>content>create>page (or sniplet)
copy and paste the code below

files permissions instructions need updating
I'm not quite sure how old these instructions are, but they need some updating. In my 4.6.3 installation all my files need chmod 404, this document suggests 400.

Drupal Presentation

Hello Drupal Friends,

My name is Will and I work as an Online Manager for a music marketing company in NY. It's my job to service websites with tools that are used to build robust content for various websites that feature and support music content. In this case I provide sites with Bios, Photos, A/V content and links, Tour Info, ect. for them to create unique content for their sites. We have two main focus points: 1.) To build connections between similar sites in order to foster a strong online community; 2.) To help webiste build robust content and increase site traffic. We do this because record lables hire us to distribute their music on the web. Instead of just mailing albums to sites, we've taken to really understanding the type of content individual sites need and use, and to building relationships with content developers.

In order to drag my company into the 21st Century kicking and screeming I sought out a usefull solution to orgnaize my clients content, distribute information, collect feedback, and provide detailed tracking and reporting completely online. I found Drupal to be the answer to all of my needs and then some. I've been working with other Drupal friends to create an interactive portal for both clients and websites to share and exhange information. The first step in building this portal was to address the needs of everyone involved. I did this by conducting surveys and speaking to many people on both side one on one. My work as gained some attention and I've been asked to speak at this year's 2005 CMJ Music Festival.


Subscribe with RSS Subscribe to RSS - Deprecated - Documentation