BlogJava-

︻┳═一Java

-随笔分类-PHP

Windows下IIS+PHP 5.2的安装与配置

Eric.Zhou — Wed, 07 Jan 2009 09:05:00 GMT

Windows下PHP的安装虽然简单，但如果不注意方法，仍然会让你头疼。此外，PHP 5.2版本与之前4.x版本也有一些不同，所以有必要记录一下，避免下次忘记了这样的安装配置方法。

步骤一：下载php 5.2 for windows的安装包，解压至C:\php。注意此解压目录可以是在任何盘下，然而目录名不能包含空格；
以下是php5.2的文件目录：
c:\php
   |
   +--dev
   | |
   | |-php5ts.lib
   |
   +--ext                 -- extension DLLs for PHP
   | |
   | |-php_bz2.dll
   | |
   | |-php_cpdf.dll
   | |
   | |-..
   |
   +--extras
   | |
   | +--mibs             -- support files for SNMP
   | |
   | +--openssl          -- support files for Openssl
   | |
   | +--pdf-related      -- support files for PDF
   | |
   | |-mime.magic
   |
   +--pear                -- initial copy of PEAR
   |
   |
   |-go-pear.bat          -- PEAR setup script
   |
   |-fdftk.dll
   |
   |-..
   |
   |-php-cgi.exe          -- CGI executable
   |
   |-php-win.exe          -- executes scripts without an opened command prompt
   |
   |-php.exe              -- CLI executable - ONLY for command line scripting
   |
   |-..
   |
   |-php.ini-dist         -- default php.ini settings
   |
   |-php.ini-recommended -- recommended php.ini settings
   |
   |-php5activescript.dll
   |
   |-php5apache.dll
   |
   |-php5apache2.dll
   |
   |-..
   |
   |-php5ts.dll           -- core PHP DLL
   |
   |-...

步骤二：将c:\php目录下的php.ini-recommended（或php.ini-dist文件，官方推荐为前者）复制到当前目录，并修改文件名为php.ini；

步骤三：编辑php.ini。主要修改如下两行的值：
extension_dir = "c:\php\ext"
doc_root = "c:\inetpub\wwwroot"

修改时需要删除掉这两行行首的;注释。extension_dir的值为php安装目录下的ext目录，doc_root的值为IIS设置的主目录；

步骤四：设置环境变量。在Path后添加如下的值：
;:\php
然后重启计算机。

步骤五：打开Internet信息服务，找到“默认网站”，将网站停止。然后打开“属性”页。在“属性”页中找到“主目录”标签，单击“配置”按钮，添加应用程序映射。其值分别为：
可执行文件：c:\php\php5isapi.dll
扩展名：.php
其余不用修改，确定后，重新启动默认网站；

步骤六：在c:\inetpub\wwwroot下新建一个文件hello.php。输入内容：

    World

保存后，打开浏览器，输入地址：http://localhost/hello.php。如果网页中显示Hello world则说明安装正确。我们也可以在网页中通过查看hello.php的源代码，如果源代码中没有php代码，也说明安装是正确的。

Eric.Zhou 2009-01-07 17:05 发表评论

OG(Organic Group) 模块介绍

Eric.Zhou — Thu, 20 Dec 2007 02:21:00 GMT

Description
让使用者可以建立并管理他们自己的群组。每一个群组可以拥有自己的成员，并有一个群组首页，让群组成员可以在此张贴文章、彼此交流。
有的群组需要管理者审核后才能加入，或甚至需要透过邀请才能加入。群组可以拥有自己的版型、语系、分类等，有多个设定项目，并可与View模块整合。
Enable users to create and manage their own 'groups'. Each group can have subscribers, and maintains a group page where subscribers can post into. Posts may be placed into multiple groups (i.e. cross-posting) and individual posts may be shared with non-subscribers or not. Membership to groups may be open, closed, moderated, or invitation only. Add-on modules are available for group image galleries, group calendars, group vocabulary, group stores, and so on.

Groups may choose their own theme and language. Groups have RSS feeds, and so on.

Installation
安装以后，需要新建一个内容类型，比如：groups，然后把这个groups内容类型与OG关联（进入Organic groups configuration，设置Group home page 为groups 内容类型）。

相关模块：
------------------------------------------------------------------
OG Actions

http://drupal.org/project/og_actions
The og_actions module is a collection of 5 actions for use with the actions module and workflow module. These actions facilitate the use of organic groups with the actions and workflow modules, allowing administrators to create rules to modify the organic group information for specific nodes.

---------------------------------------------------------------------------------
OG Aggregator

http://drupal.org/project/og_aggregator
可以让 Organic Groups 拥有自己的 RSS Aggregator。
A module to create individual aggregator for Organic Groups using Aggregator.
Key features
------------------
- Feed content filter (including keyword filter and excluding keyword filter)
- An individual feed page of every feed source is available
Requirements
------------------
- Aggregator module
- OG module

---------------------------------------------------------------------------------
OG Audience

http://drupal.org/project/og_audience
The OG Audience module provides an "audience" tab and/or a block on node pages that allows Organic Groups (OG) users to change the audience of existing content. A user can add a node to one or more of his subscribed groups. A group administrator can remove a node from his group(s).
Users with the proper permission can change the audience of a node even if they do not have the permission to edit the node.

---------------------------------------------------------------------------------
OG Author

http://drupal.org/project/og_author
This is a small module to set the authoring group for any group post.
This module has been sponsored by http://www.wiki9999.org/

---------------------------------------------------------------------------------
OG Block Visibility

http://drupal.org/project/og_block_visibility
可以设定区块仅出现在某个群组里，例如可以用来让每个群组拥有自己的导览选单，或是让群组可以强调自己推荐的内容等。
This module allows you to specify that a block should be visible only within a selected group. This can be used for many purposes, from providing each organic group with its own navigation menu, to allowing a group to highlight its own featured content, etc.

---------------------------------------------------------------------------------
OG Calendar

http://drupal.org/project/og_calendar
让每个群组都可以拥有一个活动行事历，仅显示该群组的活动。
This module provides each group with a calendar showing only the group's events.
Sponsored by Raven Brooks of BuyBlue.
Developed by CivicSpace Labs.

---------------------------------------------------------------------------------
OG Forum

http://drupal.org/project/og_forum
让每个群组都拥有一个讨论版，并限制为仅有群组成员可以检视该讨论区里的文章。
Creates a forum per organic group and restricts viewing forum nodes by group membership.
Go ahead and use the dev release from the 30th of August. It contains a bug fix to 2.0.

---------------------------------------------------------------------------------
OG Galleries

http://drupal.org/project/og_galleries
A module to create individual image galleries for Organic Groups using Taxonomy and Views. A public gallery is created, along with galleries for each group which are private to that group. Your galleries are controlled by a Views view, and you can set the url, fields, and filters as you like by changing the view. Node types can be image nodes, CCK nodes, or any other content type. Add items to the galleries by selecting a gallery when the node is edited.

---------------------------------------------------------------------------------
OG Gradebook

http://drupal.org/project/og_gradebook
Creates a gradebook per organic group and restricts viewing grades by group membership.

---------------------------------------------------------------------------------
OG Join Role

http://drupal.org/project/og_joinrole
The OG Join Role module simply adds a "join organic groups" permission to the Organic Groups module. A use case for this would be if you have a site where only members of a certain role are allowed to join an organic group.
The module is written in an all-or-nothing sort of way - either certain roles can join any and all groups or they can join no groups. It will not work on a per-group basis.
In addition to granting/denying permission to join a group, the module also modifies any text and/or links to join a group unless the user has the proper role. For example, the module removes any "og/subscribe" links on the page and replaces them with "nicer" text that you define in the admin settings.

---------------------------------------------------------------------------------
OG Minutes

http://drupal.org/project/og_minutes
This module makes Organic groups and Minutes work together. It allows to filter users so that the list of potential attendees in Minutes shows only the members of the group(s) to which the related event belongs.

---------------------------------------------------------------------------------
OG moderated posts

http://drupal.org/project/og_moderate
This module moderates public posts from organic groups module. Moderated posts will be hidden from anonymous visitors. Moderation needs to be done by node administrators or another module.

---------------------------------------------------------------------------------
OG Project

http://drupal.org/project/og_project
Allows the Project issue tracking module to function properly on a site that has Organic groups enabled. Without this module, the issue tracker does not work if you enable organic groups.

---------------------------------------------------------------------------------
OG promote

http://drupal.org/project/og_promote
Promote users that join certain groups to a special role.
Choose one role that all users who join the groups you select will be promoted to. Should a user leave that group, he will be demoted again.

---------------------------------------------------------------------------------
OG Public Access

http://drupal.org/project/og_public_access
The OG Public Access module allows Organic Groups (OG) administrators to control public access to their groups' content. This module does not require group administrators to be granted the site-wide administer nodes permission.
The use case for this module is for a site with teams of writers submitting content privately in their groups, and editors controlling what is allowed to go public in specific groups.

---------------------------------------------------------------------------------
OG Roles

http://drupal.org/project/og_roles
This module allows you to, for each group type, specify a list of roles that group administrators are allowed to assign.

---------------------------------------------------------------------------------
OG Teampage

http://drupal.org/project/og_teampage
This module provides a table view with all members (subscribers) of an organic group.

---------------------------------------------------------------------------------
OG User Roles

http://drupal.org/project/og_user_roles
This module allows you to assign group-specific roles to users which are restricted to the groups they are in. In other words, using this module, you can assign the role "contributor" to a user in a group, and the user will only have the permissions of that role while he is in that particular group.
Requires og.module and og_forums.module.
Read the history of this module: http://drupal.org/node/87679
Other features of this module allow you to:
1. Assign a default role to all new users who sign up to your site.
2. Notify group admin of new group subscribers. Requires mimemail.module.
3. Set a default "Founder" group role for users who create groups.
4. Set a default group role for new subscribers to a group.
5. Create subgroups. Requires og_subgroups.module.
6. Comes with it's own access control for optionally integrating the taxonomy access control (TAC) and organic groups (OG) modules. See: http://groups.drupal.org/node/3700.
7. Supports Content Access (http://www.drupal.org/project/content_access) and Access Control List (http://www.drupal.org/project/acl) access control modules. See http://groups.drupal.org/node/5392
8. Works with OG Vocabulary (http://www.drupal.org/project/og_vocab) module. See this issue: http://drupal.org/node/162649

---------------------------------------------------------------------------------
OG Vocab

http://drupal.org/project/og_vocab
让每个群组都可以拥有自己的分类（vocabularies）。
Provide each organic group with its own vocabularies.

Eric.Zhou 2007-12-20 10:21 发表评论

模块介绍：Book Review

Eric.Zhou — Wed, 19 Dec 2007 08:17:00 GMT

http://drupal.org/project/bookreview
一个新的节点类型，内建多个与书籍数据相关的字段，包括书名、封面图片、出版者、作者、网站连结、版权、ISBN、页数、价格、摘要、目录、评论等，并可连结到外部的网络书店。
定义了特殊的书评节点，方便发布图书评论。
The book review module allows a site to publish book reviews. A book review is simply a glorified node, providing custom fields that are appropriate to writing a book review.

Eric.Zhou 2007-12-19 16:17 发表评论

模块介绍：Article

Eric.Zhou — Wed, 19 Dec 2007 03:59:00 GMT

http://drupal.org/project/article
将任意类型的节点根据类别（taxonomy）整理在一起集中显示，如生活类有3篇，技术类有4篇等。用户可以按照分类浏览。
The article module allows for nodes of any type to be organized and displayed in a centralized location. This allows the site administrator to organize nodes of several different types in one place. The user can navigate the nodes by selecting different categories in the taxonomy tree associated with the article module.

Eric.Zhou 2007-12-19 11:59 发表评论

模块介绍：Admin RSS

Eric.Zhou — Wed, 19 Dec 2007 03:48:00 GMT

http://drupal.org/project/adminrss
提供包含待审核的节点和响应的RSS feed，方便管理者随时得知网站的最新状况，快速做出反应。
The AdminRSS module creates RSS feeds for the administrative information for Drupal websites.
These feeds are protected with a keystring that must be set in admin/settings/adminrss page.
The resulting pages can then be read at:
adminrss/node/keystring - RSS feed for unapproved nodes
adminrss/comment/keystring - RSS feed for unapproved comments
This can be most useful if you are managing a number of different drupal websites and rather than visiting each one to see if there are comments/nodes that need to be approved you can use an RSS reader to find out.
Thanks to Fredrik Jonsson and Gabor Hojtsy for their modules adminblock and commentrss which were heavily cribbed from to develop this module.

Eric.Zhou 2007-12-19 11:48 发表评论

模块介绍：Admin block

Eric.Zhou — Wed, 19 Dec 2007 03:45:00 GMT

http://drupal.org/project/adminblock
用于帮助管理员方便的监管评论和文章。如果你的站点设置成发文需要审批，那么管理员每次都要进入内容管理查看审批队列。而此模块将通过区块显示所有等待审批的评论和文章队列，一目了然，可以方便快速地完成审批
提供一个区块，用来显示所有待审核的响应和节点。每一个项目都有自己的编辑与删除连结，便于快速管理。
The adminblock module enables admins to display a block with the comments approval queue and the node moderation queue. Each item gets their own edit link and delete link for quick administration.

Eric.Zhou 2007-12-19 11:45 发表评论

模块介绍：freelinking

Eric.Zhou — Tue, 18 Dec 2007 09:38:00 GMT

简介：: freelinking 模块为输入格式增加一个过滤，为已经存在或者将要存在的内容建立链接，它能够自动地为关键词建立链接，能够通过 “wiki 风格” 为内容提供链接。
链接：: http://drupal.org/project/freelinking

Eric.Zhou 2007-12-18 17:38 发表评论

模块介绍：Forum Access

Eric.Zhou — Tue, 18 Dec 2007 09:37:00 GMT

简介：

这个模块让你可以将某个论坛设置为私有，你可以决定那个用户角色可以浏览、编辑、删除和发表帖子，还可以为每个论坛版面设置版主。

这个模块需要 ACL 模块。

链接：

http://drupal.org/project/forum_access

Eric.Zhou 2007-12-18 17:37 发表评论

为分类以及分类信息的CRUD操作添加邮件通知功能

Eric.Zhou — Tue, 18 Dec 2007 06:03:00 GMT

/**
* Implementation of hook_taxonomy().
*
* Sends email when changes to vocabularies or terms occur.
*/
function taxonomymonitor_taxonomy($op, $type, $array = array()) {
$to = 'vipzhour@163.com';
$name = check_plain($array['name']);

// $type is either 'vocabulary' or 'term'.
switch ($type) {
  case 'vocabulary':
   switch($op) {
    case 'insert':
     $subject = t('Vocabulary @voc was added.', array('@voc'=>$name));
     break;
    case 'update':
     $subject = t('Vocabulary @voc was changed.', array('@voc'=>$name));
     break;
    case 'delete':
     $subject = t('Vocabulary @voc was deleted.', array('@voc'=>$name));
     break;
   }
   break;
  case 'term':
   switch($op) {
    case 'insert':
     $subject = t('Term @term was added.', array('@term'=>$name));
     break;
    case 'update':
     $subject = t('Term @term was changed.', array('@term'=>$name));
     break;
    case 'delete':
     $subject = t('Term @term was deleted.', array('@term'=>$name));
     break;
   }
}

// Dump the vocabulary or term information out and send it along.
$body = print_r($array, TRUE);

// Send the email.
drupal_mail('taxonomymonitor-notify', $to, $subject, $body);
}

Eric.Zhou 2007-12-18 14:03 发表评论

模块介绍：audio

Eric.Zhou — Mon, 17 Dec 2007 07:25:00 GMT

简介：

audio 模块允许有权限的用户上传音频文件，它使用 getID3 library 来读写 ID3 meta-tag 信息。

这个模块还附带一个 XSPF Flash 播放器。

链接：

http://drupal.org/project/audio

To install the audio module
---------------------------

1. Extract the 'audio' module directory, including all its subdirectories, into
your sites/all/modules directory.

2. Install the getID3 package - optional but recommended. MAKE SURE YOU READ
THE SECURITY NOTE BELOW!

   a. Download the project getId3 version from SourceForge.net. The latest
      version tested with the audio module is 1.7.7. Earlier versions contain
      bugs that will cause you headaches.

b. Extract the archive into the sites/all/modules/audio/getid3 directory. When you're
finished the directory structure should look something like:

        drupal/
          sites/
            all/
              modules/
                audio/
                  getid3/
                    README.txt
                    [...]
                    getid3/
                      getid3.php
                      write.php

c. *** IMPORTANT ***
     YOU MUST DELETE THE 'demos' FOLDER OF THE ID3 LIBRARY. FAILURE TO DO SO
     OPENS UP A MASSIVE SECURITY HOLE AND MAKES YOUR SITE EXTREMELY VULNERABLE
     TO ATTACKS!

3. Enable the audio, audio_getid3 and audio_image modules on the
admin >> build >> modules page. The database tables will be created
automagically for you at this point.

4. Go to admin >> settings >> audio and check that the path to the getID3
package is configured correctly. If you follow the above directory
structure, the path should be "sites/all/modules/audio/getid3/getid3/".

Eric.Zhou 2007-12-17 15:25 发表评论

The Filter System

Eric.Zhou — Thu, 13 Dec 2007 02:05:00 GMT

// $Id$

/**
* @file
* A silly module to assist whizbang novelists who are in a rut by providing a
* random sentence generator for their posts.
*/

/**
* Implementation of hook_filter().
*/
function creativejuice_filter($op, $delta = 0, $format = -1, $text = '') {
switch ($op) {
    case 'list':
      return array(
        0 => t('Creative Juices filter'),
        1 => t('The name of my second filter'),
      );

    case 'description':
      switch ($delta) {
        case 0:
          return t('Enables users to insert random sentences into their posts.');
        case 1:
          return t('If this module provided a second filter, the description for that second filter would go here.');
        // Should never return here as value of $delta never exceeds the last index of the 'list' array.
        default:
          return;
      }
      break;

    case 'settings':
        // No settings user interface for this filter.
      break;

case 'no cache':
return FALSE;

case 'prepare':
return $text;

case 'process':
return preg_replace_callback("|\[juice!\]|i", 'creativejuice_sentence', $text);

default:
return $text;
}
}

/**
* Generate a random sentence.
*/
function creativejuice_sentence() {
$phrase[0][] = t('A majority of us believe');
$phrase[0][] = t('Generally speaking,');
$phrase[0][] = t('As times carry on');
$phrase[0][] = t('Barren in intellect,');
$phrase[0][] = t('Deficient in insight,');
$phrase[0][] = t('As blazing blue sky poured down torrents of light,');
$phrase[0][] = t('Aloof from the motley throng,');
$phrase[1][] = t('life flowed in its accustomed stream');
$phrase[1][] = t('he ransacked the vocabulary');
$phrase[1][] = t('the grimaces and caperings of buffoonery');
$phrase[1][] = t('the mind freezes at the thought');
$phrase[1][] = t('she reverted to another matter');
$phrase[1][] = t('he lived as modestly as a hermit');

$phrase[2][] = t('through the red tape of officialdom.');
$phrase[2][] = t('as it set anew in some fresh and appealing form.');
$phrase[2][] = t('supported by evidence.');
$phrase[2][] = t('as fatal as the fang of the most venomous snake.');
$phrase[2][] = t('as full of spirit as a gray squirrel.');
$phrase[2][] = t('as dumb as a fish.');
$phrase[2][] = t('like a damp-handed auctioneer.');
$phrase[2][] = t('like a bald ferret.');

foreach ($phrase as $key => $value) {
$rand_key = array_rand($phrase[$key]);
$sentence[] = $phrase[$key][$rand_key];
}

return implode(' ', $sentence);
}

/**
* Implementation of hook_filter_tips().
*/
function creativejuice_filter_tips($delta, $format, $long = FALSE) {
if ($long) {
    // Detailed explanation for http://example.com/?q=filter/tips page.
    return t('The Creative Juices filter is for those times when your brain is incapable of being creative. These time comes for everyone, when even strong coffee and a barrel of jelly beans does not create the desired effect. When that happens, you can simply enter the [juice!] tag into your posts...');
}
else {
    // Short explanation for underneath a post's textarea.
    return t('Insert a random sentence into your post with the [juice!] tag.');
}
}

Eric.Zhou 2007-12-13 10:05 发表评论

Poormanscron（调用cron任务）

Eric.Zhou — Tue, 11 Dec 2007 11:58:00 GMT

Poormanscron:
通过用户的浏览来调用cron任务，使不能设置crontab的站点也能简单地解决cron运行的问题。

A module which runs the Drupal cron operations without needing the cron application.

For every page view, this module checks to see if the last cron run was more than 1
hour ago (this period is configurable). If so, the cron hooks are executed,
and Drupal is happy. These cron hooks fire after all HTML is returned to the browser,
so the user who kicks off the cron jobs should not notice any delay.

Eric.Zhou 2007-12-11 19:58 发表评论

Taxonomy Access Control（管理用户对不同类别文章的访问权限）

Eric.Zhou — Tue, 11 Dec 2007 11:47:00 GMT

Taxonomy Access Control:
管理用户对不同类别文章的访问权限。

Access control for user roles based on taxonomy categories (vocabulary, terms).

Automatically controls access to taxonomy terms and nodes (based on their category terms)
Configuration page for each user roles
Five permission types (View, Update, Delete, Create, List)

http://drupal.org/project/taxonomy_access

Eric.Zhou 2007-12-11 19:47 发表评论

Smiley（表情符）

Eric.Zhou — Tue, 11 Dec 2007 11:15:00 GMT

Smiley:
使用表情符，自带了一些基本的表情符，用户可以自己添加。

Eric.Zhou 2007-12-11 19:15 发表评论

Excerpt（摘要模块）和Side Content（边栏导读）

Eric.Zhou — Tue, 11 Dec 2007 11:05:00 GMT

Excerpt:
摘要模块。Drupal发布内容时只能用正文的开头作摘要，然后根据设定自动截取摘要。启用摘要模块就可以不受此限制，发布内容时将单独有一个摘要栏供作者随意填写。
Side Content:
在发布节点内容时可以将部分内容选择性的显示在边栏的区块里，可以用于强调某部分内容，类似有的书籍或杂志的边栏导读。

Eric.Zhou 2007-12-11 19:05 发表评论

Working with Blocks

Eric.Zhou — Tue, 04 Dec 2007 03:50:00 GMT

1．Understanding How Blocks Are Themed

During a page request, the theme system will ask the block system to return a list of blocks for

each region. It does this when generating the variables to send to the page template (usually

page.tpl.php). To gather the themed blocks for the left and right sidebars, Drupal executes the

following:

$sidebar_left = theme('blocks', 'left');

$sidebar_right = theme('blocks', 'right');

// And any other regions exposed by hook_regions().

You might remember that theme('blocks') is actually a call to theme_blocks(). Here’s what theme_blocks() actually does:

function theme_blocks($region) {

$output = '';

if ($list = block_list($region)) {

foreach ($list as $key => $block) {

$output .= theme('block', $block);

}

return $output;

}

2．Using the Block Hook

function hook_block($op = 'list', $delta = 0, $edit = array())

// $Id$

/**

* @file

* Implements various blocks to improve pending content workflow.

/**

* Implementation of hook_block().

function approval_block($op = 'list', $delta = 0, $edit = array()) {

switch ($op) {

case 'list':

$blocks[0]['info'] = t('Pending comments');

$blocks[1]['info'] = t('Unpublished nodes');

return $blocks;

case 'configure':

// Only in block 0 (the Pending comments block) can one

// set the number of comments to display.

if ($delta == 0) {

$form['approval_block_num_posts'] = array(

'#type' => 'textfield',

'#title' => t('Number of pending comments to display'),

'#default_value' => variable_get('approval_block_num_posts', 5),

);

}

return $form;

case 'save':

if ($delta == 0) {

variable_set('approval_block_num_posts', (int) $edit['approval_block_num_posts']);

}

break;

case 'view':

if ($delta == 0 &&user_access('administer comments')) {

// Retrieve the number of pending comments to display that

// we saved earlier in the 'save' op, defaulting to 5.

$num_posts = variable_get('approval_block_num_posts', 5);

// Query the database for unpublished comments.

$result = db_query_range('SELECT c.* FROM {comments} c WHERE c.status = %d ORDER BY c.timestamp', COMMENT_NOT_PUBLISHED, 0, $num_posts);

// Preserve our current location so user can return after editing.

$destination = drupal_get_destination();

$items = array();

while ($comment = db_fetch_object($result)) {

$items[] = l($comment->subject, 'node/'. $comment->nid, array(), NULL, 'comment-'. $comment->cid). ' '. l(t('[edit]'), 'comment/edit/'. $comment->cid, array(), $destination);

}

$block['subject'] = t('Pending comments');

// We theme our array of links as an unordered list.

$block['content'] = theme('item_list', $items);

}

elseif ($delta == 1 && user_access('administer nodes')) {

// Query the database for the 5 most recent unpublished nodes.

// Unpublished nodes have their status column set to 0.

$result = db_query_range('SELECT title, nid FROM {node} WHERE status = 0 ORDER BY changed DESC', 0, 5);

$destination = drupal_get_destination();

while ($node = db_fetch_object($result)) {

$items[] = l($node->title, 'node/'. $node->nid). ' '. l(t('[edit]'), 'node/'. $node->nid .'/edit', array(), $destination);

}

$block['subject'] = t('Unpublished nodes');

// We theme our array of links as an unordered list.

$block['content'] = theme('item_list', $items);

}

return $block;

}

drupal_get_destination()

This function remembers the page you were on before you submitted a form, so after you update the comment form to publish or delete a comment, you’ll be automatically redirected from whence you came.

Eric.Zhou 2007-12-04 11:50 发表评论

The Theme System

Eric.Zhou — Tue, 04 Dec 2007 01:29:00 GMT

theme-name_breadcrumb()

theme-engine_ breadcrumb()

theme_ breadcrumb()

Defining Additional Template Files

First, create a file within your theme directory named breadcrumb.tpl.php. This is the new template file for breadcrumbs. Because we wanted to change the

tag to a tag, go ahead and populate the file with the following:

That’s easy enough for a designer to edit. Now you need to let Drupal know to call

this template file when looking to render its breadcrumbs. Inside template.php, override theme_breadcrumb() as you did previously, but this time you’re going to tell this function to use the template file instead of just the function:

function mytheme_breadcrumb($breadcrumb) {

if (!empty($breadcrumb)) {

$variables = array(

'breadcrumb' => implode(' -> ', $breadcrumb)

);

return _phptemplate_callback('breadcrumb', $variables);

}

The magic inside this function is happening with _phptemplate_callback(). Its first parameter is the name of the template file to look for, and the second parameter is an array of variables to pass to the template file. You can create and pass along as many variables as you need into your template files.

Defining New Block Regions

function mytheme_regions() {

return array(

'left' => t('left sidebar'),

'right' => t('right sidebar'),

'content_top' => t('content top'),

'content_bottom' => t('content bottom'),

'header' => t('header'),

'footer' => t('footer')

);

}

To print out the content top region in your page template, use .

Eric.Zhou 2007-12-04 09:29 发表评论

Working with Nodes

Eric.Zhou — Tue, 04 Dec 2007 01:28:00 GMT

Creating a Node Module

1．Creating the .info File

Let’s also create the joke.info file and add it to the joke folder.

; $Id$

name = Joke

description = Provides a joke node type with a punchline.

version = "$Name$"

2．Creating the .install File

function joke_install() {

switch ($GLOBALS['db_type']) {

case 'mysql':

case 'mysqli':

db_query("CREATE TABLE {joke} (

nid int unsigned NOT NULL default '0',

vid int unsigned NOT NULL default '0',

punchline text NOT NULL,

PRIMARY KEY (nid,vid),

UNIQUE KEY vid (vid),

KEY nid (nid)

) /*!40100 DEFAULT CHARACTER SET UTF8 */ ");

break;

case 'pgsql':

db_query("CREATE TABLE {joke} (

nid int unsigned NOT NULL default '0',

vid int unsigned NOT NULL default '0',

punchline text NOT NULL,

PRIMARY KEY (nid,vid),

UNIQUE KEY vid (vid),

KEY nid (nid)

)");

break;

}

function joke_uninstall() {

db_query('DROP TABLE {joke}');

}

3．Creating the .module File

function joke_perm() {

return array('create joke', 'edit joke', 'delete joke');

}

/**

* @file

* Provides a "joke" node type.

/**

* Implementation of hook_node_info().

function joke_node_info() {

// We return an array since a module can define multiple node types.

// We're only defining one node type, type 'joke'.

return array(

'joke' => array(

'name' => t('Joke'), // Required.

'module' => 'joke', // Required.

'description' => t('Tell us your favorite joke!'), // Required.

'has_title' => TRUE,

'title_label' => t('Title'),

'has_body' => TRUE,

'body_label' => t('Joke'),

'min_word_count' => 2,

'locked' => TRUE

)

);

}

function joke_menu($may_cache) {

$items = array();

if ($may_cache) {

$items[] = array(

'path' => 'node/add/joke',

'title' => t('Joke'),

'access' => user_access('create joke'),

);

}

return $items;

}

function joke_access($op, $node) {

global $user;

if ($op == 'create') {

return (user_access('create joke'));

}

if ($op == 'update') {

return (user_access('edit joke') && ($user->uid == $node->uid));

}

if ($op == 'delete') {

return (user_access('delete joke') && ($user->uid == $node->uid));

}

function joke_form($node) {

// Get metadata for this node type

// (we use it for labeling title and body fields).

// We defined this in joke_node_info().

$type = node_get_types('type', $node);

$form['title'] = array(

'#type' => 'textfield',

'#title' => check_plain($type->title_label),

'#required' => TRUE,

'#default_value' => $node->title,

'#weight' => -5

);

$form['body_filter']['body'] = array(

'#type' => 'textarea',

'#title' => check_plain($type->body_label),

'#default_value' => $node->body,

'#rows' => 7,

'#required' => TRUE

);

$form['body_filter']['filter'] = filter_form($node->format);

$form['punchline'] = array(

'#type' => 'textfield',

'#title' => t('Punchline'),

'#required' => TRUE,

'#default_value' => $node->punchline,

'#weight' => 5

);

return $form;

}

function joke_validate($node) {

//Enforce a minimum word length of 3.

if (isset($node->punchline) && str_word_count($node->punchline) <= 3) {

$type = node_get_types('type', $node);

form_set_error('punchline', t('The punchline of your @type is too short. You need at least three words.', array('@type'=> $type->name)));

}

function joke_insert($node) {

db_query("INSERT INTO {joke} (nid, vid, punchline) VALUES (%d, %d, '%s')",

$node->nid, $node->vid, $node->punchline);

}

function joke_update($node) {

if ($node->revision) {

joke_insert($node);

} else {

db_query("UPDATE {joke} SET punchline = '%s' WHERE vid = %d", $node->punchline, $node->vid);

}

/**

* Implementation of hook_delete().

function joke_delete(&$node) {

// Delete the related information we were saving for this node.

db_query('DELETE FROM {joke} WHERE nid = %d', $node->nid);

}

/**

* Implementation of hook_load().

function joke_load($node) {

drupal_add_js('misc/collapse.js');

return db_fetch_object(db_query('SELECT punchline FROM {joke} WHERE vid = %d', $node->vid));

}

function joke_view($node, $teaser = FALSE, $page = FALSE) {

if (!$teaser) {

// Use Drupal's default node view.

$node = node_prepare($node, $teaser);

$node->guffaw = str_repeat(t('Ha!'), mt_rand(0, 10));

// Now add the punchline.

/**

$node->content['punchline'] = array(

'#value' => theme('joke_punchline', $node),

'#weight' => 2

);

}

if ($teaser) {

// Use Drupal's default node view.

$node = node_prepare($node, $teaser);

}

return $node;

}

function theme_joke_punchline($node) {

$output = '

'.check_plain($node->punchline). '

$output .= '

'.check_plain($node->guffaw). '

return $output;

}

Eric.Zhou 2007-12-04 09:28 发表评论

Working with Users

Eric.Zhou — Mon, 03 Dec 2007 06:32:00 GMT

1．Introduction to hook_user()

Implementing hook_user() gives your modules a chance to react to the different operations performed on a user account, and to modify the $user object. Let’s examine the function signature:

function hook_user($op, &$edit, &$user, $category = NULL)

The $op parameter is used to describe the current operation being performed on the user account and can have many different values:

• after_update: Called after the $user object has been saved to the database.

• categories: Returns an array of categories that appear as Drupal menu local tasks when the user edits the user account. See profile_user() in profile.module for an implementation.

• delete: A user has just been deleted from the database. This is an opportunity for the module to remove information related to the user from the database.

• form: Inject an additional form field element into the user edit form being displayed.

• insert: The new user account is about to be created and inserted into the database.

• login: The user has successfully logged in.

• logout: The user just logged out and his or her session has been destroyed.

• load: The user account was successfully loaded. The module may add additional information into the $user object.

• register: The user account registration form is about to be displayed. The module may add additional form elements to the form.

• submit: The user edit form has been submitted. Modify the account information before it is sent to user_save().

• update: The existing user account is about to be saved to the database.

• validate: The user account has been modified. The module should validate its custom

data and raise any necessary errors.

• view: The user’s account information is being displayed. The module should return

its custom additions to the display as an array. The view operation ultimately calls

theme_user_profile to format the user profile page. More details on this shortly.

The $edit parameter is an array of the form values submitted when a user account is being created or updated. Notice that it’s passed by reference, so any changes you make will actually change the form values.

The $user object is also passed by reference, so any changes you make will actually change the $user information.

The $category parameter is the active user account category being edited.

■Caution Don’t confuse the $user parameter within hook_user() with the global $user object. The $user parameter is the user object for the account currently being manipulated. The global $user object is the user currently logged in.

2.The User Registration Process

Add a legalagree.module

function legalagree_user($op, &$edit, &$user, $category = NULL) {

switch ($op) {

// User is registering

case 'register':

//Add a fieldset containing radio buttons to the user registration form

$fields['legal_agreement'] = array(

'#type' => 'fieldset',

'#title' => t('Legal Agreement')

);

$fields['legal_agreement']['decision'] = array(

'#type' => 'radios',

'#options' => array(t('I disagree'), t('I agree')),

'#default_value' => 0,

'#description' => t('By registering at %site-name, you agree that

at any time, we (or our surly, brutish henchmen) may enter your place of

residence and smash your belongings with a ball-peen hammer.',

array('%site-name' => variable_get('site_name', 'drupal')))

);

return $fields;

case 'validate':

// Make sure the user selected radio button 1 ('I agree').

// the validate op is reused when a user updates information on

// The 'my account' page, so we use isset() to test whether we are

// on the registration page where the decision field is present.

if (isset($edit['decision']) && $edit['decision'] != '1') {

form_set_error('decision', t('You must agree to the legal agreement before

registration can be completed.'));

}

return;

case 'insert':

// Record information for future lawsuit.

watchdog('user', t('User %user agreed to legal terms', array('%user' => $user->name)));

return;

}

3．Adding Data to the $user Object

Loginhistory.module

function loginhistory_user($op, &$edit, &$account, $category = NULL) {

switch($op) {

case 'login':

// Record timestamp in database

db_query("INSERT INTO {login_history} (uid, timestamp) values (%d, %d)", $account->uid, $account->login);

break;

case 'load':

// Add the number of times user has logged in.

$account->loginhistory_count = db_result(db_query("SELECT COUNT(timestamp) as count FROM {login_history} WHERE uid = %d", $account->uid));

break;

case 'view':

// Add a field displaying number of logins.

$items['login_history'] = array(

'title' => t('Number of logins'),

'value' => $account->loginhistory_count,

'class' => 'member'

);

return array(t('History')=>$items);

}

Loginhistory.install

function loginhistory_install() {

switch ($GLOBALS['db_type']) {

case 'mysql':

case 'mysqli':

db_query("CREATE TABLE {login_history} (

uid int NOT NULL default '0',

timestamp int NOT NULL default '0',

KEY (uid)

)/*!40100 DEFAULT CHARACTER SET UTF8 */");

break;

case 'pgsql':

db_query("CREATE TABLE {login_history} (

uid int_unsigned default '0',

timestamp int_unsigned NOT NULL default '0',

KEY (uid)

)");

break;

}

function loginhistory_uninstall() {

db_query("DROP TABLE {login_history}");

}

4．Simple External Authentication

Let’s implement a very simple external authentication module that might be used inside a company where simple usernames are used. Suppose your company only hires people named Dave, and usernames are assigned based on first and last names. This module authenticates anyone whose username begins with the string dave, so the users davebrown, davesmith, and davejones will all successfully log in.

/**

* Implementation of hook_auth()

function authdave_auth($username, $pass, $server) {

// Does username begin with 'dave'?

if (substr(drupal_strtolower($username), 0, 4 ) == 'dave') {

// Make a global variable to note that we did the authentication.

global $authdave_authenticated;

$authdave_authenticated = TRUE;

return TRUE;

}

else {

return FALSE;

}

If a row in the users table does not exist for this user, one will be created. However, no e-mail address has been provided at login like it was for Drupal’s default local user registration, so a module this simple is not a real solution if your site relies on sending e-mail to users. You’ll want to set the mail column of the users table so you will have an e-mail address associated with the user. To do this, you can have your module respond to the insert operation of the user hook, which is fired whenever a new user is inserted:

/**

* Implementation of hook_user()

function authdave_user($op, &$edit, &$account, $category = NULL) {

switch($op) {

case 'insert':

// New user was just added; if we did authentication,

// look up email address of user in a legacy database.

global $authdave_authenticated;

if ($authdave_authenticated) {

$email = mycompany_email_lookup($account->name);

// Set email address in the user table for this user.

db_query("UPDATE {users} SET mail = '%s' WHERE uid = %d", $email,

$account->uid);

}

break;

}

Eric.Zhou 2007-12-03 14:32 发表评论

Working with Databases

Eric.Zhou — Mon, 03 Dec 2007 02:02:00 GMT

Defining Database Parameters

$db_url = 'mysql://username:password@localhost/databasename';

■NoteIf you are in a situation where you are writing a stand-alone PHP script or you have existing PHP code outside of Drupal that needs access to Drupal’s database, you will want to want to call include_once ('includes/bootstrap.inc') and then call drupal_bootstrap(DRUPAL_BOOTSTRAP_DATABASE) to generate an active connection. At that point, you can use db_query(), as explained in the next section.

Performing Simple Queries

db_query('SELECT * FROM {joke} WHERE vid = %d', $node->vid);

db_query("INSERT INTO {joke} (nid, vid, punchline) VALUES (%d, %d, '%s')",

$node->nid, $node->vid, $node->punchline);

db_query("UPDATE {joke} SET punchline = '%s' WHERE vid = %d", $node->punchline,

$node->vid);

db_query('DELETE FROM {joke} WHERE nid = %d', $node->nid);

Retrieving Query Results

There are various ways to retrieve query results depending on whether you need a single row or the whole result set, or you are planning to get a range of results for internal use or for display as a paged result set.

1．Getting a Single Value

$sql = "SELECT COUNT(*) FROM {node} WHERE type = 'blog' AND status = 1";

$total = db_result(db_query($sql));

2．Getting Multiple Rows

$sql = "SELECT * FROM {node} WHERE type = 'blog' AND status = 1";

$result = db_query(db_rewrite_sql($sql));

while ($data = db_fetch_object($result)) {

$node = node_load($data->nid);

print node_view($node, TRUE);

}

The preceding code snippet will print out all published nodes that are of type blog. (The status field in the node table is 0 for unpublished nodes and 1 for published nodes.) We will cover db_rewrite_sql()shortly. The db_fetch_object()function grabs a row from the result set as an object. To retrieve the result as an array, use db_fetch_array(). The practice of retrieving rows as objects is common since most developers prefer its less verbose syntax.

3．Getting a Limited Range of Results

$type = 'blog';

$status = 1;

$sql = "SELECT * FROM {node} n WHERE type = '%s' AND status = %d ORDER BY

n.created DESC";

$result = db_query_range(db_rewrite_sql($sql), $type, $status, 0, 10);

4．Getting Results for Paged Display

$sql = "SELECT * FROM {node} n WHERE type = 'blog' AND status = 1 ORDER BY

n.created DESC"

$result = pager_query(db_rewrite_sql($sql), 0, 10);

while ($data = db_fetch_object($result)) {

$node = node_load($data->nid);

print node_view($node, TRUE);

}

// Add links to remaining pages of results.

print theme('pager', NULL, 10);

Although pager_query() is not really part of the database abstraction layer, it is good to know when you need to create a paged result set with navigation. A call to theme('pager') at the end will display the navigation links to the other pages. You don’t need to pass the total number of results to theme('pager') because the number of results is remembered internally from the pager_query() call.

5．Deleting Tables on Uninstall

The Administer ➤ Modules page has an Uninstall tab that not only allows modules to be disabled,but also removes their data from the database. If you want to enable the deletion of your module’s tables on this page, implement the uninstall hook in your module’s .install file. You might want to delete any variables you’ve defined at the same time.

function annotate_uninstall() {

db_query("DROP TABLE {annotations}");

variable_del('annotate_nodetypes');

}

6．Writing Your Own Database Abstraction Layer

First, we make a copy of includes/database.mysql.inc and rename it as

includes/database.dnabase.inc. Then we change the logic inside each wrapper function to map to DNAbase’s functionality instead of MySQL’s functionality. When all is said and done, we have the following functions declared in our file:

_db_query($query, $debug = 0)

db_affected_rows()

db_connect($url)

db_decode_blob($data)

db_distinct_field($table, $field, $query)

db_encode_blob($data)

db_error()

db_escape_string($text)

db_fetch_array($result)

db_fetch_object($result)

db_lock_table($table)

db_next_id($name)

db_num_rows($result)

db_query_range($query)

db_query_temporary($query)

db_result($result, $row = 0)

db_status_report($phase)

db_table_exists($table)

db_unlock_tables()

db_version()

Eric.Zhou 2007-12-03 10:02 发表评论

The Menu System

Eric.Zhou — Mon, 03 Dec 2007 02:01:00 GMT

Access Control

Usually menu access is controlled by defining permissions inside the

module using hook_perm() and testing those permissions using user_access().

function mymenu_perm() {

return array('receive greeting', 'receive goodbye');

}

function mymenu_menu($may_cache) {

$items = array();

if ($may_cache) {

// Define a static menu item.

$items[] = array(

'title' => t('Greeting'),

'path' => 'mymenu',

'weight' => -10,

'callback' => 'mymenu_hello',

'callback arguments' => array(t('Hi!'), t('Ho!')),

'access' => user_access('receive greeting')

);

$items[] = array(

'title' => t('Farewell'),

'path' => 'mymenu/goodbye',

'callback' => 'mymenu_goodbye',

'access' => user_access('receive goodbye')

);

}

return $items;

}

Assigning Callbacks Without Adding a Link to the Menu

Often you may want to map a URL to a function without creating a visible menu item. You

can do this by assigning the MENU_CALLBACK type to your menu item, as in this example from

node.module:

$items[] = array(

'path' => 'rss.xml',

'title' => t('RSS feed'),

'callback' => 'node_feed',

'access' => user_access('access content'),

'type' => MENU_CALLBACK

);

Displaying Menu Items As Tabs

In Drupal’s admittedly obscure menu lingo, a callback that is displayed as a tab is known as a

local task and has the type MENU_LOCAL_TASK or MENU_DEFAULT_LOCAL_TASK. The title of a local

task should be a short verb, such as “add” or “list.” Local tasks usually act on some kind of

object, such as a node, user, or workflow.

Local tasks must have a parent item in order for the tabs to be rendered. A common practice

is to assign a callback to a root path like milkshake, and then assign local tasks to paths that

extend that path, like milkshake/prepare, milkshake/drink, and so forth. Drupal has built-in

support for two levels of tabbed local tasks.

function milkshake_menu($may_cache) {

$items = array();

if ($may_cache) {

$items[] = array(

'path' => 'milkshake',

'title' => t('Milkshake flavors'),

'callback' => 'milkshake_overview',

'access' => TRUE

);

$items[] = array(

'path' => 'milkshake/list',

'title' => t('List flavors'),

'type' => MENU_DEFAULT_LOCAL_TASK, //默认选上此menu

'access' => TRUE,

'weight' => 0

);

$items[] = array(

'path' => 'milkshake/add',

'title' => t('Add flavors'),

'callback' => 'milkshake_add',

'type' => MENU_LOCAL_TASK,

'access' => TRUE,

'weight' => 1

);

$items[] = array(

'path' => 'milkshake/list/fruity',

'title' => t('Fruity flavors'),

'callback' => 'milkshake_list',

'type' => MENU_LOCAL_TASK,

'access' => TRUE,

);

$items[] = array(

'path' => 'milkshake/list/candy',

'title' => t('Candy flavors'),

'callback' => 'milkshake_list',

'type' => MENU_LOCAL_TASK,

'access' => TRUE,

);

}

return $items;

}

function milkshake_overview() {

$output = t('The following flavors are available...');

// ... more code here

return $output;

}

function milkshake_add() {

return t('milkshake add');

}

If you want the menu item to show up in the administrative menu block, you have to make

the type a MENU_NORMAL_ITEM instead of a MENU_LOCAL_TASK. And if you want it to show up in both

places, use the following:

'type' => MENU_NORMAL_ITEM | MENU_LOCAL_TASK

Programmatically Modifying Existing Menus

1．Wrapping Calls to Menu Items

/**

* Implementation of hook_menu().

function mymodule_menu($may_cache) {

$items = array();

if (!$may_cache && module_exist('devel')) { // Make sure devel.module is enabled.

$items[] = array(

'path' => 'devel/cache/clear', // Same path that devel.module uses.

'title' => t('Wrap cache clear'),

'callback' => 'mymodule_clear_cache',

'type' => MENU_CALLBACK,

'access' => user_access('access devel information') // Same as devel.module.

);

}

function mymodule_clear_cache() {

drupal_set_message('We got called first!');

// Wrap the devel function normally called.

devel_cache_clear();

}

2．Deleting Existing Menus

$items[] = array(

'path' => 'node/add',

'title' => t('This should not show up'),

'callback' => 'drupal_not_found',

'type' => MENU_CALLBACK

);

Adding to Existing Menus

$items[] = array(

'path' => 'admin/user/user/eradicate',

'title' => t('Eradicate all users'),

'callback' => 'mymodule_eradicate_users',

'type' => MENU_LOCAL_TASK,

'access' => TRUE

);

Eric.Zhou 2007-12-03 10:01 发表评论

创建annotate module

Eric.Zhou — Thu, 29 Nov 2007 07:41:00 GMT

1. 在sites/all/modules下面创建一个annotate文件夹

2. 创建annotate module的信息文件(annotate.info)

; $Id: annotate.info v 1.1.2.3 2007/06/18 23:06:32 dww Exp $

name = Annotate

description = Allows users to annotate nodes.

package = Example

version = 5.5

//dependencies = node blog

project = "annotate"

datestamp = "1193367002"

3. 创建annotate module的实际的module功能文件(annotate.module),所以的功能都在此文件中定义.

// $Id$

/**

* @file

* Lets users add private annotations to nodes.

* Adds a text field when a node is displayed

* so that authenticated users may make notes.

4. 这时候到Administer➤ Site building➤ Modules中就可以看到刚才添加的annotate模组.但这时候激活它在导航栏里面是看不到annotate设置菜单的.

5. 实现Hook(钩子),添加一下代码,重新激活annotate模组,这样就可以看到在Administer➤ Site configuration下多了一个Annotation settings菜单

/**

* Implementation of hook_menu().

function annotate_menu($may_cache) {

$items = array();

if ($may_cache) {

$items[] = array(

'path' => 'admin/settings/annotate',

'title' => t('Annotation settings'),

'description' => t('Change how annotations behave.'),

'callback' => 'drupal_get_form',

'callback arguments' => array('annotate_admin_settings'),

'access' => user_access('administer site configuration')

);

}

return $items;

}

6. 上面有行'callback' => 'drupal_get_form'代码,还有一行 'callback arguments' => array('annotate_admin_settings'). 这里当用户通过http://www.example.com/?q=admin/settings/annotate访问的时候,将会调用drupal_get_form()函数,并且通过它的form ID annotate_admin_settings来调用annotate_admin_settings()函数.所以我们要自己定义这个方法.

/**

* Define the settings form.

function annotate_admin_settings() {

$form['annotate_nodetypes'] = array(

'#type' => 'checkboxes',

'#title' => t('Users may annotate these node types'),

'#options' => node_get_types('names'), //返回所有node类型组成的数组

'#default_value' => variable_get('annotate_nodetypes', array('story')),

'#description' => t('A text field will be available on these node types to make

user-specific notes.'),

);

$form['array_filter'] = array('#type' => 'hidden');

return system_settings_form($form);

}

7. 实现hook_nodeapi(),当Drupal对node做各种各样的操作的时候对调用此函数.

/**

* Implementation of hook_nodeapi().

function annotate_nodeapi(&$node, $op, $teaser, $page) {

switch ($op) {

case 'view':

global $user;

// If only the node summary is being displayed, or if the

// user is an anonymous user (not logged in), abort.

if ($teaser || $user->uid == 0) {

break;

}

$types_to_annotate = variable_get('annotate_nodetypes', array('story'));

if (!in_array($node->type, $types_to_annotate)) {

break;

}

// Add our form as a content item.

$node->content['annotation_form'] = array(

'#value' => drupal_get_form('annotate_entry_form', $node),

'#weight' => 10

);

}

8. 下面我们要定义annotate form,作为页面现实内容

/**

* Define the form for entering an annotation.

function annotate_entry_form($node) {

$form['annotate'] = array(

'#type' => 'fieldset',

'#title' => t('Annotations')

);

$form['annotate']['nid'] = array(

'#type' => 'value',

'#value' => $node->nid

);

$form['annotate']['note'] = array(

'#type' => 'textarea',

'#title' => t('Node'),

'#default_value' => $node->annotation,

'#description' => t('Make your personal annotations about this content

here. Only you (and the site administrator) will be able to see them.')

);

$form['annotate']['submit'] = array(

'#type' => 'submit',

'#value' => t('Update')

);

return $form;

}

9. 到目前为止对于annotate的内容我们还有做处理.从这里开始,我们就要把annotate的数据存储到数据库里面,很多module里面都有.install文件,该文件就是创建数据库表文件.我们要创建一个annotate.install文件

// $Id$

function annotate_install() {

drupal_set_message(t('Beginning installation of annotate module.'));

switch ($GLOBALS['db_type']) {

case 'mysql':

case 'mysqli':

db_query("CREATE TABLE annotations (

uid int NOT NULL default 0,

nid int NOT NULL default 0,

note longtext NOT NULL,

timestamp int NOT NULL default 0,

PRIMARY KEY (uid, nid)

) /*!40100 DEFAULT CHARACTER SET utf8 */;"

);

$success = TRUE;

break;

case 'pgsql':

db_query("CREATE TABLE annotations (

uid int NOT NULL DEFAULT 0,

nid int NOT NULL DEFAULT 0,

note text NOT NULL,

timestamp int NOT NULL DEFAULT 0,

PRIMARY KEY (uid, nid)

);"

);

$success = TRUE;

break;

default:

drupal_set_message(t('Unsupported database.'));

}

if ($success) {

drupal_set_message(t('The module installed tables successfully.'));

} else {

drupal_set_message(t('The installation of the annotate module was unsuccessful.'),'error');

}

10. 这里要到数据库system表里把annotate给删了,然后重新激活annotate模组.添加提交事件.

* Save the annotation to the database.

function annotate_entry_form_submit($form_id, $form_values) {

global $user;

$nid = $form_values['nid'];

$note = $form_values['note'];

db_query("DELETE FROM {annotations} WHERE uid = %d and nid = %d", $user->uid, $nid);

db_query("INSERT INTO {annotations} (uid, nid, note, timestamp) VALUES (%d, %d, '%s', %d)", $user->uid, $nid, $note, time());

drupal_set_message(t('Your annotation was saved.'));

}

11. 为了实现在现实annotate的时候读取数据库里面的数据现实,这里要修改一下前面的hook_nodeapi函数.修改以后的为:

/**

* Implementation of hook_nodeapi().

function annotate_nodeapi(&$node, $op, $teaser, $page) {

switch ($op) {

case 'view':

global $user;

// If only the node summary is being displayed, or if the

// user is an anonymous user (not logged in), abort.

if ($teaser || $user->uid == 0) {

break;

}

$types_to_annotate = variable_get('annotate_nodetypes', array('story'));

if (!in_array($node->type, $types_to_annotate)) {

break;

}

// Get previously saved note, if any.

$result = db_query("SELECT note FROM {annotations} WHERE uid = %d AND nid = %d", $user->uid, $node->nid);

$node->annotation = db_result($result);

// Add our form as a content item.

$node->content['annotation_form'] = array(

'#value' => drupal_get_form('annotate_entry_form', $node),

'#weight' => 10

);

}

这样在重新激活使用一下就可以了!

Eric.Zhou 2007-11-29 15:41 发表评论

把玩Drupal模組： Hook System運作簡介

Eric.Zhou — Thu, 29 Nov 2007 05:23:00 GMT

週二, 2006-05-09 20:07 — jimmy
模組系統是drupal很重要的運作方式，drupal依靠著少少的核心程式，便能讓模組能做到任何事情。

drupal只有21個檔案在include裡頭，每次必會loading進來，其他的全都放在modules。
也就是說，除了那幾隻檔案以外，全部的東西都把他當成module在寫。諸如CMS最基本的功能，文章管理、評論、討論區、分類...等的功能，全部都寫在module裡，include裡頭所提供的是各種api，檔案處理函式、資料庫存取、表單生成...等等，這樣的分層，module便可以專心的開發各種功能。

當然，這樣的架構不夠令人注目。有許多web app架構，對於模組（module）、插件（plug-in）...等的運作，通常是讓他們各自為政，自己幹自己的事情。多是用核心提供的object和function，加上module自己額外的code，達到module要做到的額外功能。但是drupal的核心運作卻不是如此。

drupal處理使用的程式為modules/user.module。如果今天想要在看使用者資料的同時，也想看看所有使用者過去發表文章的list，那該怎麼寫呢？

直接一點，更改user.modue，在顯示時，順便去文章資料庫抓相關的資料？然而這樣卻不是一個好方式，今天任何想要對使用者增加新功能的時候，都得trace一次user.module的code，看懂他在幹啥，然後把新的code安插在合適的地方... 最後可能增加user.module的複雜度，增加維護那支module的難度，共同開發時，更是一個危險的方式。

第二種方式，重寫一個新的瀏覽頁面，重新寫一個SELECT的語句，讓SELECT的時候除了使用者資訊，也把文章資料一起抓出來，然後顯示到不同的頁面。但是這樣很浪費，明明跟user.module重複的功能達到一半以上，那是不是之後要新增功能，都得重寫一次呢？

上面兩種方式在drupal中也都可以達成，然而熟悉Drupal的人卻不會如此。Drupal的開發者很聰明，他的模組系統（module system）考慮到了模組再利用這一點，每個模組都視為可以再利用的資源，只要寫module的人想寫，透過模組系統便可以跟所有的module交互作用。

第三種方式以modules/user.module為例，他即是處理包含新增、修改、刪除、註冊、登入....等所有與使用者相關的功能。在進行每個重要的功能時，user.module都會呼叫一個函式去掃所有的module，看看是否有其他的module要在user.module進行此動作時，也進行一些其他想要做的事情，這就是drupal重要的Hook System。
example:
在drupal user.module裡頭可以找到如下的程式碼

function user_view($uid = 0) {
// ... skip
// moudle_invoke掃描所有的module
// 看看有沒有modulename_user這個function
// 有個話就看'view'這個功能的部份要加上什麼
foreach (module_list() as $module) {
if ($data = module_invoke($module, 'user', 'view', '', $account)) {
// do something...
}
}
// ... skip
}

所以，第三種方式，不用重寫，也不用改到user.module，只要自己新增module和寫一個function，便可以輕鬆讓瀏覽使用者資訊時，加上過往文章。
example:
新增自己的module，與hook system緊密運作
新增sample.module

function sample_user($type, &$edit, &$user, $category = NULL) {
if ($type == 'view') {
return /*過往文章，型別為一陣列*/;
}
}

這就是drupal把眾多主要功能都寫成module的原因，讓所有模組之間都可以交互利用，或是寫給別人利用，或是利用別人的module，像積木一樣推砌成想要的功能，卻又不浪費資源。

參考資源：
詳細的用法在：
http://drupaldocs.org/api/head/function/hook_user
Module developer's guide：
http://drupal.org/node/508

Eric.Zhou 2007-11-29 13:23 发表评论

模块介绍：jRating

Eric.Zhou — Thu, 29 Nov 2007 03:49:00 GMT

简介：

这个模块使用 jQuery 技术为节点提供评分功能，当 javascript 被禁止时，使用标准形式，如果启用 javascript 就可以通过图片 (如五星) 动态进行评分。

这个模块能够与 views 模块协作，它提供一个 views 字段，让评分结果可以通过 views 显示。

链接：

http://drupal.org/project/jrating

Eric.Zhou 2007-11-29 11:49 发表评论

Drupal的Captcha

Eric.Zhou — Thu, 29 Nov 2007 03:49:00 GMT

大家在访问我的博客留言的时候，总是会发现有一个“考考智商”，很多人和我说，“这个太侮辱我的智商了！”，其实这个题目只是和大家开一个玩笑，但是放这个的真正目的是为了防spam。
啥是Sapm呢？百度百科的解释是：
-----------------------------------
SPAM是stupid person advertesing method的简称,意思为兜售信息[邮件，广告，新闻，文章]，非索要信息。基本与垃圾邮件（junk mail）同义

即是指在Internet上利用Email进行广播式的广告宣传的行为。这种行为给很多人的信箱里塞入大量无关或无用的信息，因此越来越受到人们的厌恶，在美国这已经属非法行为。

Spam最初来历:
spam即SPAM，原是一个罐装肉的牌子。对于这个牌子名字的来源有很多解释，官方版本说，它是”Specially Processed Assorted Meat”特殊加工过的混和肉。
这种SPAM肉有段时间非常普及，到了无处不在，令人讨厌的程度。后来（1970年）Monty Python剧团有个很流行的Sketch comedy（一种短小的系列喜剧）叫Spam，剧中两位顾客试图点一份没有SPAM的早餐，但最后却没能成功。
于是，许多年后的现在，Spam被用来统称互联网上到处散布垃圾广告消息的现象
-------------------------
其实说白了就是使用自动化的工具，在网上批量的发布一些广告信息，用Email，或者论坛，或者博客。
现在论坛在发帖的时候，都会有验证码之类的，也是为了防止Spam。
Drupal作为成熟的CMS，自然有很多人对其进行Spam骚扰，而Drupal也有很多的插件反Spam。

最常用的是Captcha模块。
安装好Captcha模块以后，我们会在用户管理目录下找到一个Captcha管理。这个管理看起来很简单，只有简简单单的几项。

第一项的意思是，在有admin captcha权限的用户的Form下面加上Captcha管理链接。这样一般要勾上，这样的话，你就可以方便的修改每一处要加Captcha的地方了。
接下来的选项就是设置各个地方的Captcha。对于Captcha还有很多相关的模块，大家可以去Drupal上查到。有很多种，比如图片，比如算术，还有Riddler可以设置一些问题，比如一年有几个月之类的。可以对每一个Captcha Point设置一种Captcha检查方法。
在这里，要注意的地方是，如果想增加一个Captcha Point的话，就要把第一项打勾，然后以管理员身份去你要添加Captcha的Form，下面会有一个链接，点一下就好了。这个当时我找了好久，最好逼到了看了Captcha代码，准备去修改数据库的时候才发现，呵呵。
下面就是一些描述，还有另一个选项，选上以后，用户需要在每一次输入的时候都输入Captcha。
我们看到Captcha还有很多其他的设置信息，比如图片检查设置，Riddler设置，都比较简单，点几下就明白了。
对于Captcha的权限，有以下两个：一个是管理Captcha，一个是跳过Captcha检查。

Eric.Zhou 2007-11-29 11:49 发表评论

E-Mail field(cck邮件栏位)

Eric.Zhou — Wed, 28 Nov 2007 12:18:00 GMT

这个模块会为cck增加一个聚合栏位，用户可以在那儿添加feed，这个feed会加入到全站聚合里。
官方发布页： http://drupal.org/project/feedfield

Eric.Zhou 2007-11-28 20:18 发表评论

CCK Field Permissions(cck栏位权限)

Eric.Zhou — Wed, 28 Nov 2007 12:07:00 GMT

利用cck给某个内容类型建立了多个栏位，但你想有些栏位只给特定用户使用，怎么办？CCK Field Permissions这个模块就是解决这个问题的，你可以为单个栏位设置权限，允许特定用户组使用。
比如使用video_cck(cck视频栏位)给一个类型的node添加一个video field，这时候就可以控制一些用户可以添加视频，一些不可以添加视频。使用CCK Field Permissions，开启以后到Administer->Site configuration->CCK Field Permissions来设置对哪些node起作用，然后设置每个node的fields！想通过CCK Field Permissions控制的就打勾！保存！然后到User management->Access control里面设置控制！

下载地址：http://drupal.org/project/cck_field_perms

Eric.Zhou 2007-11-28 20:07 发表评论

video_cck(cck视频栏位)

Eric.Zhou — Wed, 28 Nov 2007 11:55:00 GMT

这个模块提供一个多媒体栏位，只要填入视频网址，即可自动播放。目前默认支持大多数英语视频网站，如：youtube。稍做修改，也可以支持国内视频网站的视频。

需要结合CCK模块一起使用！
启动以后到 Administer->Content management->Video CCK configuration下设置支持哪些网站视频！
下载地址：http://drupal.org/project/video_cck

Eric.Zhou 2007-11-28 19:55 发表评论

ApacheBench(ab)和eAccelerator使用配置

Eric.Zhou — Wed, 28 Nov 2007 09:33:00 GMT

ApacheBench(ab)
服务器负载太大而影响程序效率也是很常见的，Apache服务器自带有一个叫AB(ApacheBench)的工具，在bin目录下。使用这个轻巧的工具我们可以对服务器进行负载测试，

基本用法:

ab -n 全部请求数 -c 并发数测试url

例:ab -n 1000 -c 50 http://www.abc.com/a.php

得到结果类似于(后面颜色字为中文翻译):

Server Software: Apache/2.0.55
Server Hostname: localhost
Server Port: 80

Document Path: /1.php
Document Length: 82522 bytes #请求文档大小

Concurrency Level: 50 #并发数
Time taken for tests: 92.76140 seconds #全部请求完成耗时
Complete requests: 10000 #全部请求数
Failed requests: 1974 #失败的请求
(Connect: 0, Length: 1974, Exceptions: 0)
Write errors: 0
Total transferred: 827019400 bytes #总传输大小
HTML transferred: 825219400 bytes
Requests per second: 108.61 [#/sec] (mean) #每秒请求数(平均)
Time per request: 460.381 [ms] (mean) #每次并发请求时间(所有并发)
Time per request: 9.208 [ms] (mean, across all concurrent requests) #每一请求时间(并发平均)
Transfer rate: 8771.39 [Kbytes/sec] received #传输速率

Connection Times (ms) #连接时间
min mean[+/-sd] median max
Connect(#连接): 0 0 2.1 0 46
Processing(#处理): 31 458 94.7 438 1078
Waiting(#等待): 15 437 87.5 422 938
Total: 31 458 94.7 438 1078

其它参数:

-n requests 全部请求数
-c concurrency 并发数
-t timelimit 最传等待回应时间
-p postfile POST数据文件
-T content-type POST Content-type
-v verbosity How much troubleshooting info to print
-w Print out results in HTML tables
-i Use HEAD instead of GET
-x attributes String to insert as table attributes
-y attributes String to insert as tr attributes
-z attributes String to insert as td or th attributes
-C attribute 加入cookie, eg. 'Apache=1234. (repeatable)
-H attribute 加入http头, eg. 'Accept-Encoding: gzip'
Inserted after all normal header lines. (repeatable)
-A attribute http验证,分隔传递用户名及密码
-P attribute Add Basic Proxy Authentication, the attributes
are a colon separated username and password.
-X proxy:port 代理服务器
-V 查看ab版本
-k Use HTTP KeepAlive feature
-d Do not show percentiles served table.
-S Do not show confidence estimators and warnings.
-g filename Output collected data to gnuplot format file.
-e filename Output CSV file with percentages served
-h Display usage information (this message)

About eAccelerator
eAccelerator是一个的免费、开源的PHP模块，它能够为提供PHP加速、优化、加码、和动态内容缓存功能。它通过存储PH脚本编译后的状态而加快执行PHP脚本的速度，而不需要频繁的编译这个PHP脚本。而且它能优化PHP脚本，以提高执行PHP的速度。eAccelerator特色是减少了服务器负载、使PHP脚本加速1-10倍。
对应你的php版本下载相应的dll文件．如果是PHP 5.2.5请下载eAccelerator 0952 for PHP 5.2.5 eLoader 0952 for PHP 5.2.5

Attachment	Size
eAccelerator 095 Final for PHP 5.1.6	120 KB
095_final_useful _files.zip	41.97 KB
eAccelerator 0.9.5 Final for PHP 5.1.5	120 KB
eAccelerator 095 Final for PHP 5.1.6 Optimized for Size	108 KB
eAccelerator 095 Final for PHP 5.2.0	120 KB
eAccelerator 095 Final for PHP 5.0.5	120 KB
eAccelerator 095 for PHP 5.0.4 (OLDER PHP VERSION)	120 KB
eAccelerator 0951 for PHP 5.2.2	120 KB
eAccelerator 0951 for PHP 5.2.1	120 KB
eAccelerator 0951 for PHP 5.2.2 Built with VC2005 SP1	128 KB
eAccelerator 0951 for PHP 5.1.4	120 KB
eAccelerator 0951 for PHP 5.2.3	120 KB
eAccelerator 0951 for PHP 5.2.0 (OLDER PHP VERSION)	120 KB
eAccelerator 0951 for PHP 5.2.4	120 KB
eLoader 0951 for PHP 5.2.4	28 KB
0952_final_useful _files.zip	42.27 KB
eLoader 0952 for PHP 5.2.3	28 KB
eAccelerator 0952 for PHP 5.2.3	120 KB
eLoader0952_5.2.4.dll	28 KB
eAccelerator 0952 for PHP 5.2.4	120 KB
eAccelerator 0952 for PHP 5.2.5	120 KB
eLoader 0952 for PHP 5.2.5	28 KB

We have been using this PHP accelerator (0.9.5), on multiple servers, for a long time. It's used on some high traffic sites without any problem.
Install:
a) Download a copy of eAccelerator that is compatible with your version of PHP.
This can be an issue with eAccelerator. Sometimes it can take a little time before the Windows binaries are available for the most recent version of PHP.
b) Copy a compatible eaccelerator.dll to your PHP extensions folder (like:D:\php\ext replace with your actual folder location).
Make sure the configuration directive extension_dir in your php.ini is properly pointing to your extensions folder.
Like: extension_dir = "D:/php/ext"
//将dll文件复制到D:/php/ext下．
c) Create a folder (with the appropriate permissions) for the temporary cached files.
For example: D:\temp\eaccelerator
//创建tmp目录　权限可写
d) Add the following to your php.ini (as the first loaded extension):
.
;extension=php_yaz.dll
;extension=php_zip.dll
//编辑php.ini 在extension=php_zip.dll之后添以红字部分

[eaccelerator]
zend_extension_ts="D:\php\ext\eAccelerator0952_5.2.3.dll"
zend_extension="D:\php\ext\eAccelerator0952_5.2.3.dll"
eaccelerator.cache_dir = "D:\temp\eaccelerator"
eaccelerator.shm_size="64"
eaccelerator.enable="1"
eaccelerator.optimizer="1"
eaccelerator.debug ="0"
eaccelerator.check_mtime="1"
eaccelerator.filter=""
eaccelerator.shm_max="0"
eaccelerator.shm_ttl ="0"
eaccelerator.shm_prune_period="0"
eaccelerator.shm_only="0"
eaccelerator.compress="1"
eaccelerator.compress_level="9"
eaccelerator.keys= "shm"
eaccelerator.sessions="shm"
eaccelerator.c
zend_extension="D:\php\ext\eLoader0952_5.2.3.dll"
;;;;;;;;;;;;;;;;;;;
; Module Settings ;
;;;;;;;;;;;;;;;;;;;
.
.
e) Restart your Web Server.You can see..

Eric.Zhou 2007-11-28 17:33 发表评论

网站多语言版本－－Drupal

Eric.Zhou — Thu, 22 Nov 2007 06:53:00 GMT

在官方网站上看到有两个module可以实现国际化多语言版本，首先看到的是menutranslation，而此module只是实现了对menu实现的国际化多语言控制，显然不适合一般的要求，但这个module配置很简单，只需要加入i18n就可以了，基本不需要配置什么的。
与是就继续看了一下功能强大的localizer。此module需要自己配置很多。

Installation instructions (New installation: Localizer 1.10 on Drupal 5.1 and Drupal 5.2)

1. Download the latest Localizer module from http://drupal.org/project/localizer
2. Download the flags icons from http://www.speedtech.it/files/localizer-flags.tgz
3. Download pre-patched core files from
   http://www.speedtech.it/files/localizer-sites-all-5.1-1.10.tgz (Drupal 5.1)
   http://www.speedtech.it/files/localizer-sites-all-5.2-1.10.tgz (Drupal 5.2)
4. Extract localizer-5.x-1.10.tgz archive under sites/all/modules (create the modules directory if needed)
   This will create sites/all/modules/localizer that contains the Localizer-related module code.
5. Extract localizer-flags.tgz under sites/all/modules/localizer. This
   will create sites/all/modules/localizer/flags with the flag files in it.
6. Extract localizer-sites-all-5.1-1.10.tgz (or localizer-sites-all-5.2-1.10.tgz) under sites/all (it already
   has the modules and localizer directory, so the contents will go into
   sites/all/modules/localizer.
7. To the end of your sites/default/settings.php file, append and save
   (overwrite the file):
   $conf= array
   (
      'cache_inc' =>
      'sites/all/modules/localizer/system/includes/cache.inc',
   );
8. Login to your site as administrator (UID=1)
9. Under Administer > Site building > modules, enable all the
   Localizer-related modules you need. Click Save configuration.
10. Visit www.yoursite.com/update.php and run the update script.
11. Under Administer > Site configuration > Localizer to configure options.
12. Enjoy!

Upgrade instructions (Upgrade from older versions of Localizer to Localizer
1.10 on Drupal 5.1 and Drupal 5.2)

1. Download the latest Localizer module from http://drupal.org/project/localizer
2. Download the flags icons from http://www.speedtech.it/files/localizer-flags.tgz
3. Download pre-patched core files from
   http://www.speedtech.it/files/localizer-sites-all-5.1-1.10.tgz (Drupal 5.1)
   http://www.speedtech.it/files/localizer-sites-all-5.2-1.10.tgz (Drupal 5.2)
4. Login to your site as administrator and under Administer > Site
   building > modules, disable all the Localizer-related modules
5. Delete the old module/localizer directory (could be sites/all/modules/localizer)
6. Return the Drupal 5.x modules that you previously patched for
   Localizer versions prior to 1.10 to their original state. (In other
   words, download Drupal 5.x and extract the the following files from
   the tarball: block.module, menu.module, taxonomy.module, bootstrap.inc,
   and common.inc. Upload these to your site, overwriting the existing
   modules.)
7. Extract localizer-5.x-1.10.tgz archive under sites/all/modules
   (create the modules directory if needed) This will create
   sites/all/modules/localizer that contains the Localizer-related module code.
8. Extract localizer-flags.tgz under sites/all/modules/localizer. This
   will create sites/all/modules/localizer/flags with the flag files in it.
9. Extract localizer-sites-all-5.1-1.10.tgz (or localizer-sites-all-5.2-1.10.tgz) under sites/all (it already
   has the modules and localizer directory, so the contents will go into
   sites/all/modules/localizer.
10. To the end of your sites/default/settings.php file, append and
   save (overwrite the file):
   $conf= array
   (

'cache_inc' =>
'sites/all/modules/localizer/system/includes/cache.inc',

   );
11. Login to your site as administrator (UID=1)
12. Under Administer > Site building > modules, enable all the
    Localizer-related modules you need. Click Save configuration.
13. Visit www.yoursite.com/update.php and run the update script.
14. Under Administer > Site configuration > Localizer to configure
    options.
15. Enjoy!

按照它的说明文件，很快就可以实现国际化多语言版本的网站了!此module可以对node，block等等实现国际化!

Eric.Zhou 2007-11-22 14:53 发表评论