You need to show “Search” text to the respective field in search form. When user clicks on this field, the text should disappear.

Solution:

Disappearing hint in search field using JavaScript

Add (or change) the following function in template.php file of fa current theme:

function phptemplate_preprocess_search_theme_form(&$vars, $hook) {
$form_default = t(‘Search’);
$vars['form']['search_theme_form']['#value'] = $form_default;
$vars['form']['search_theme_form']['#attributes'] = array(
‘onblur’ => “if (this.value == ”) {this.value = ‘{$form_default}’;}”,
‘onfocus’ => “if (this.value == ‘{$form_default}’) {this.value = ”;}”
);
}

Using jQuery for hiding the hint in search field

• In the settings of a current theme, enable showing of a search string – see admin/build/themes/settings
• Add (or change) the following function in template.php file of a current theme:
  

  function phptemplate_preprocess_search_theme_form(&$vars, $hook) {
  $theme_path = drupal_get_path(‘theme’, ‘arthemia’);
  $vars['form']['search_theme_form']['#value'] = t(‘Search’);
  drupal_add_js($theme_path. ‘/search_box.js’);
  }

• Create search_box.js file in a folder of a current theme with the following code:
  

  var active_color = ‘#000′; // Colour of user provided text
  var inactive_color = ‘#ссс’; // Colour of default text
  $(document).ready(function() {
  $(“input.form-text”).css(“color”, inactive_color);
  var default_values = new Array();
  $(“input.form-text”).focus(function() {
  if (!default_values[this.id]) {
  default_values[this.id] = this.value;
  }
  if (this.value == default_values[this.id]) {
  this.value = ”;
  this.style.color = active_color;
  }
  $(this).blur(function() {
  if (this.value == ”) {
  this.style.color = inactive_color;
  this.value = default_values[this.id];
  }
  });
  });
  });

Useful links:

• Theme Drupal 6 Search Box
• Customizing the search form using jQuery

First make sure that multilanguage is set for your site and an ability to translate nodes is enabled.

Then you should:

1. Open the required node for editing and set a path: “home”.
2. Make the same for all translations using the same value of a path (“home”)
3. Open “Site information” page admin/settings/site-information and specify a path to main page (“home”)
4. Save settings and check languages switching on the main page.

Possible problems:

If you receive this message:

user warning: Duplicate entry ‘home-en’ for key 2 query: UPDATE url_alias SET src = ‘node/126′, dst = ‘home’, language = ‘en’ WHERE dst = ‘home’ in /home/ … /modules/path/path.module on line 108.

Then you already used such path synonym but for a page that is neutral to language.

You can try to change path synonyms here: admin/build/path. Find your path synonym and delete it, if language column shows “All”.

How to show node on the home page in one language

If you wish to shoe a node in home page of multilanguage site always in one language, you should open admin/settings/site-information and specify system path to the node instead of path synonym there:

node/10

Solution

• Open page.tpl.php file in current theme folder
• Find “$logo” line in this file – this is logo output. Site name output is usually about somewhere.
• Find how the link is formed. Usually it is
  

  echo check_url($base_path);

  or

  print $base_path;

• Replace it with:
  

  echo url(‘<front>’, array(‘absolute’ => TRUE));

That is all!

Solution
There are no old URLs anymore, but the can be used. We should create 301 redirect from old URL to a new one.

Alternatives

• Redirect from old URL to new one in .htaccess file
• Redirect from old URL to new one with the help of Pathauto and Global Redirect modules

Redirect from old URL to new one in .htaccess file

The simplest method:

add

RewriteCond %{REQUEST_URI} ^/old_url_1.html
RewriteCond %{REQUEST_URI} ^/old_url_2.html
RewriteCond %{REQUEST_URI} ^/old_url_3.html
RewriteCond %{REQUEST_URI} ^/old_url_N.html
RewriteRule ^(.*)$ http://site.ru$1 [R=301,L]

in .htaccess file (in the site root) after:

<IfModule mod_rewrite.c>
RewriteEngine on

Redirect from old URL to new one with the help of Pathauto and Global Redirect modules

The other method is to use Pathauto module with Global Redirect. Create one more synonym for a node in admin area. When calling this snonym, Global Redirect will redirect to main node alias.

In this case data is stored in database and Drupal would be loaded for redirect. So performance will go down. And if you wish to disable such redirect, it will take you more time.

Solution

• Open Content Types
• Select the desired content type and open it
• Find Submission Form field set or just clear “Body Field Label” field
• Save

You will not see the main text (Body) on a form and when viewing node anymore.

Solution:

Unlike other CCK versions, fields manipulating becomes easier in CCK version for Drupal 6.

• You need to create a field with the help of CCK user interface first.
• Then you should use var_export() PHP-function, to get a dump of node field in the form of array.
  

  var_export(content_fields(‘field_ИМЯ_ПОЛЯ’, ‘ТИП_КОНТЕНТА’));

  See API: http://drupalcontrib.org/api/function/content_fields

Yyou will get a large array. You can copy your code there and use it in the following way:

$field = array (
‘field_name’ => ‘field_translator_note’,
‘type_name’ => ‘feature’,
‘display_settings’ =>
array (
4 =>
array (
‘format’ => ‘hidden’,
),
2 =>
array (
‘format’ => ‘hidden’,
),
3 =>
array (
‘format’ => ‘hidden’,
),
‘label’ =>
array (
‘format’ => ‘hidden’,
),
‘teaser’ =>
array (
‘format’ => ‘hidden’,
),
‘full’ =>
array (
‘format’ => ‘hidden’,
),
),
‘widget_active’ => ’1′,
‘type’ => ‘text’,
‘required’ => ’0′,
‘multiple’ => ’0′,
‘db_storage’ => ’0′,
‘module’ => ‘text’,
‘active’ => ’1′,
‘columns’ =>
array (
‘value’ =>
array (
‘type’ => ‘text’,
‘size’ => ‘big’,
‘not null’ => false,
‘sortable’ => true,
),
),
‘text_processing’ => ’0′,
‘max_length’ => ”,
‘allowed_values’ => ”,
‘allowed_values_php’ => ”,
‘widget’ =>
array (
‘rows’ => ”,
‘default_value’ =>
array (
0 =>
array (
‘value’ => ”,
),
),
‘default_value_php’ => NULL,
‘label’ => ‘Translator\’s note’,
‘weight’ => NULL,
‘description’ => ”,
‘type’ => ‘text_textarea’,
‘module’ => ‘text’,
),
);
// Load CCK –file where content_field_instance_create() function is defined
module_load_include(‘inc’, ‘content’, ‘includes/content.crud’);
// Add a few content types to the field and use this loop:
foreach (array(‘TYPE1′, ‘TYPE2′, ‘TYPE3′, ‘TYPE4′) as $type) {
// … and change content type in the proper field.
$field['type_name'] = $type;
  content_field_instance_create($field);
}

Create backup copy of php.ini file (in /etc/php5).

Create executable file:

# remove all php packge
sudo aptitude purge `dpkg -l | grep php| awk ‘{print $2}’ |tr "\n" " "`
# use karmiс for php pakage
# pin-params:  a (archive), c (components), v (version), o (origin) and l (label).
echo -e "Package: php5\nPin: release a=karmic\nPin-Priority: 991\n" | sudo tee /etc/apt/preferences.d/php > /dev/null
apt-cache search php5-|grep php5-|awk ‘{print "Package:", $1,"\nPin: release a=karmic\nPin-Priority: 991\n"}’|sudo tee -a /etc/apt/preferences.d/php > /dev/null
apt-cache search -n libapache2-mod-php5 |awk ‘{print "Package:", $1,"\nPin: release a=karmic\nPin-Priority: 991\n"}’| sudo tee -a /etc/apt/preferences.d/php > /dev/null
echo -e "Package: php-pear\nPin: release a=karmic\nPin-Priority: 991\n" | sudo tee -a /etc/apt/preferences.d/php > /dev/null
# add karmic to source list
grep ‘main restricted’ /etc/apt/sources.list|grep -v "#"| sed s/lucid/karmic/g | sudo tee /etc/apt/sources.list.d/karmic.list > /dev/null
# update package database (use apt-get if aptitude crash)
sudo apt-get update
# install php
sudo aptitude install -t karmic php5-cli php5-cgi
# or (and) sudo apt-get install -t karmic  libapache2-mod-php5
sudo aptitude hold `dpkg -l | grep php5| awk ‘{print $2}’ |tr "\n" " "`
#done

Execute:

php_installed=`dpkg -l | grep  php| awk  ‘{print $2}’ |tr "\n" " "`

This will save list of additional packets and libraries which are to be re-installed after downgrade. You can easy view them:

echo $php_installed

Run the script created earlier.
Execute:

sudo apt-get install $php_installed

This works for many packets but not for phpmyadmin which requires php5-mcrypt. They both are in "universe" repository  instead of "main restricted". Threfore you should add this to /etc/apt/sources.list.d/karmic.list:

sudo gedit /etc/apt/sources.list.d/karmic.list

deb http://archive.ubuntu.com/ubuntu/ karmic universe
deb http://archive.ubuntu.com/ubuntu/ karmic-updates universe
deb http://archive.ubuntu.com/ubuntu/ karmic multiverse
deb http://archive.ubuntu.com/ubuntu/ karmic-updates multiverse

Execute:

sudo apt-get update

All packets should be updated.

You can automate this process replacing line 10 (above) with this one:

egrep ‘(main restricted|universe|multiverse)’ /etc/apt/sources.list|grep -v "#"| \
sed s/lucid/karmic/g | sudo tee /etc/apt/sources.list.d/karmic.list > /dev/null

Enjoy!

Solution

Drupal 5.х

IN Drupal  5.x, when storing book page, a record is created in “node” table of “book” type and the respective record is created in “book” table (nid) to define relation to a parent page. If parent is set to 0, this book is from top level. So simple!

All module info is stored in one table:

CREATE TABLE book (
        vid int unsigned NOT NULL default ’0′,
        nid int unsigned NOT NULL default ’0′,
        parent int NOT NULL default ’0′,
        weight tinyint NOT NULL default ’0′,
        PRIMARY KEY (vid),
        KEY nid (nid),
        KEY parent (parent)
)

Drupal 6.х

IN 6.x "book" table contains only nid, bid and mlid fields now.

As you can see in Drupal interface, it is impossible to specify parent page on node/add/book page. You should select the existing book and NECESSARY parent page in this book.

Book module was changed to use new menu system

Book uses new menu system Drupal 6.x now ({menu_links} table) for storing and recovering book hierarchy. Any modules which worked through Book interface earlier have to be rewritten. All information stored  in a node by Book module is in $node->book property now.

Many API functions of Book module were changed. For example, book_recurse function was deleted. For the most cases it can be replaced with book_export_traverse but it has no $depth parameter.

Taтабle analysis in database

– `book` table structure

CREATE TABLE `book` (
  `mlid` int(10) unsigned NOT NULL default ’0′,
  `nid` int(10) unsigned NOT NULL default ’0′,
  `bid` int(10) unsigned NOT NULL default ’0′,
  PRIMARY KEY  (`mlid`),
  UNIQUE KEY `nid` (`nid`),
  KEY `bid` (`bid`)
) ENGINE=MyISAM DEFAULT CHARSET=utf8;

– `menu_links` table structure

CREATE TABLE `menu_links` (
  `menu_name` varchar(32) NOT NULL default ”,
  `mlid` int(10) unsigned NOT NULL auto_increment,
  `plid` int(10) unsigned NOT NULL default ’0′,
  `link_path` varchar(255) NOT NULL default ”,
  `router_path` varchar(255) NOT NULL default ”,
  `link_title` varchar(255) NOT NULL default ”,
  `options` text,
  `module` varchar(255) NOT NULL default ‘system’,
  `hidden` smallint(6) NOT NULL default ’0′,
  `external` smallint(6) NOT NULL default ’0′,
  `has_children` smallint(6) NOT NULL default ’0′,
  `expanded` smallint(6) NOT NULL default ’0′,
  `weight` int(11) NOT NULL default ’0′,
  `depth` smallint(6) NOT NULL default ’0′,
  `customized` smallint(6) NOT NULL default ’0′,
  `p1` int(10) unsigned NOT NULL default ’0′,
  `p2` int(10) unsigned NOT NULL default ’0′,
  `p3` int(10) unsigned NOT NULL default ’0′,
  `p4` int(10) unsigned NOT NULL default ’0′,
  `p5` int(10) unsigned NOT NULL default ’0′,
  `p6` int(10) unsigned NOT NULL default ’0′,
  `p7` int(10) unsigned NOT NULL default ’0′,
  `p8` int(10) unsigned NOT NULL default ’0′,
  `p9` int(10) unsigned NOT NULL default ’0′,
  `updated` smallint(6) NOT NULL default ’0′,
  PRIMARY KEY  (`mlid`),
  KEY `path_menu` (`link_path`(128),`menu_name`),
  KEY `menu_plid_expand_child` (`menu_name`,`plid`,`expanded`,`has_children`),
  KEY `menu_parents` (`menu_name`,`p1`,`p2`,`p3`,`p4`,`p5`,`p6`,`p7`,`p8`,`p9`),
  KEY `router_path` (`router_path`(128))
) ENGINE=MyISAM AUTO_INCREMENT=407 DEFAULT CHARSET=utf8 AUTO_INCREMENT=407 ;

$node->book analysis

Let’s create a document of Book type and execute a code there (input format should be PHP):

if ((arg(0) == ‘node’) && is_numeric(arg(1))) {
$node = node_load(arg(1));
var_dump($node->book);
}

Here is the result:

array(29) {
  ["mlid"]=> string(3) "409"
  ["nid"]=> string(2) "27"
  ["bid"]=> string(2) "56"
  ["menu_name"]=> string(11) "book-toc-56"
  ["plid"]=> string(3) "257"
  ["link_path"]=> string(7) "node/27"
  ["router_path"]=> string(6) "node/%"
  ["link_title"]=> string(20) "Содержание"
  ["options"]=> array(0) {}
  ["module"]=> string(4) "book"
  ["hidden"]=> string(1) "0"
  ["external"]=> string(1) "0"
  ["has_children"]=> string(1) "0"
  ["expanded"]=> string(1) "0"
  ["weight"]=> string(1) "0"
  ["depth"]=> string(1) "2"
  ["customized"]=> string(1) "0"
  ["p1"]=> string(3) "257"
  ["p2"]=> string(3) "409"
  ["p3"]=> string(1) "0"
  ["p4"]=> string(1) "0"
  ["p5"]=> string(1) "0"
  ["p6"]=> string(1) "0"
  ["p7"]=> string(1) "0"
  ["p8"]=> string(1) "0"
  ["p9"]=> string(1) "0"
  ["updated"]=> string(1) "0"
  ["href"]=> string(7) "node/27"
  ["title"]=> string(20) "Содержание"
}

Summary

• book table in Drupal 6.х contains bid field (Book id) which stores  nid of a page of the top book level.
• Every book page has mlid field (Menu links id) for connection with menu_links table.
  It is necessary because page hierarchy is now realized in menu_links rather than in booktable.
• Maximum inclusion is limited by 9 levels.

$node->book array elements

• mlid – id menu_links, allows Book module to connect to menu_links
• nid – node id
• bid – abbreviation of "book_id"
• menu_name – for all Book documents, always begins from "book-toc-" + nid of top-level document. menu_name is similar for all documents for one book.
• plid – mlid of parent (0 – top level)
• link_path – document address in menu
• router_path
• link_title – link text in menu
• options array(0) {}
• module – system module name. It is stored in menu_links.module
• hidden – hidden menu element
• external
• has_children – if there are child documents (0 – no, 1 – yes)
• expanded – if it is expanded (0- no, 1 – yes)
• weight – weight (it is used for sorting of one-level elements)
• depth – depth of inclusion (1 – top level)
• customized
• p1 – top level in menu hierarchy. Contains parent mlid
• p2 – hierarchy level. IN our case it contains mlid of current node
• p3 – 0 – if there are no child nodes.
• p4
• p5
• p6
• p7
• p8
• p9
• updated
• href – document address
• title – document header

Attention: You need configure input formats and add this to a format for this module to work.

Since this is a filter module, it only works on text that is passed through Drupal’s filter system. The biggest example of content passed through the filters are the body of content, blocks, and cck text fields where the user specifies an input format. It will not work on several areas including menus, site footers, mission statements, and profile fields.

If you wish to add nofollow to all external links you simply add your site to the "whitelist".

For more information on the motivation for this module see Just say NO(follow) Wikipedia links!

Installation

• The module is installed as usual
• You need activate "Nofollow list filter " in the required input formats.

Configuration

I found that there can be either whitelist or black list.

Thus you can:

• Forbid indexing ALL exterior links to exterior sites (select "whitelist" and don’t specify sites)
• Forbid indexing ALL links EXCEPT the defined ones (select "whitelist" and specify these sites)
• Forbid indexing links ONLY to specified sites (select "blacklist" and specify these sites)
• Allow indexing ALL links to exterior sites (select "blacklist" and do not specify the sites)

So much wisdom!

Solution

Tools:

• microformat rel="external nofollow", which is added to link body (for Google)
• embrace link with tag (for Yandex)

Modules for managing site links indexing:

• Links managing in taxonomy and menu
• Inserting rel="nofollow" white or black site list to external links
• Using of the standard feature of Filter module

Using of the standard feature of Filter module

Open the required input format (for example, /admin/settings/filters/1/configure)
Check "Protection against spam links"
Set "Sorting" for correct displaying of document body

Effect of this method applies to Filter module operational area. Especially these are fields where user can select input format…

Links managing in taxonomy and menu

Using nofollow module

White and black site lists to manage indexing

nofollowlist module allows creating white and black site lists. Links are indexed and NOT indexed respectivelly for sites from one of the list.