Remove “Block Configuration” Option in Account Page in Drupal 6

In Drupal 6, it shows the “Block Configuration” for Navigation by default for all user accounts. It is useless and confusing for most of the users in our case.

Without knowing what it is, it would be hard to turn it off in the backend. It is as simple as two steps required in the backend.


Firstly go to “Administor” >> “Site Building” >> “Blocks”, and then click on “configure” button next to the “Navigation” block:


Then click on “Users cannot control whether or not they see this block”, and save the settings.


Now the annoying block configuration is gone:


Hope it helps..

Remove ‘The content of this field is kept private and will not be shown publicly.’ Form Help Text in Drupal 6

Using profile module, I have set up a number of fields for user information. Because they are for members’ profile only, I set them as private field in the backend, but when user is editing the form in the frontend, each field shows help text “The content of this field is kept private and will not be shown publicly.” underneath.


This looks especially ugly when you have lots of fields to show and my client requested to remove it completely.

There are a couple of ways to remove it, but for my purpose, it is as simply as remove the code generated this text.

Open file /modules/profile/profile.module and simply comment out line 340:

function _profile_form_explanation($field) {
  $output = $field->explanation;

  if ($field->type == 'list') {
    $output .= ' '. t('Put each item on a separate line or separate them by commas. No HTML allowed.');

  if ($field->visibility == PROFILE_PRIVATE) {
    //$output .= ' '. t('The content of this field is kept private and will not be shown publicly.');

  return $output;

You might also want to use String Overrides module for Durpal 6 if you don’t feel to modify the source code.

Disable Drupal Comment Preview Button

Drupal 6 only allows you to set the comment preview button be either “Required” or “Optional”, but does not allow you to turn it off totally. But you can turn it off easily by updating your theme’s CSS file.

To hide the preview button, add the following to your theme’s CSS:

#comment-form #edit-preview {
    display: none;

Hope this helps..

WordPress vs Joomla 2013 [INFOGRAPHIC]

I have tried both WordPress & Joomla before when I was trying to learn the new CMSes several years ago. My very first impression was that WordPress was so easy to pick up straightaway without getting too much detail, however, Joomla was totally the opposite. It was really hard to understand and it took lots of steps to get one page setup.

A few years has passed and I am stick with WordPress. It works great and meets all my needs, so I have not re-tried with Joomla since then. Red Giant Design has kindly produced an infographic compare those two CMSes in detail. And again, it proved my original theory / experience.

WordPress v Joomla - Infographic by Red Giant Design

I have also tried Drupal recently and found that it is quite easy to use and learn. And I am currently building a website for my friend using Drupal. From my personal point of view, WordPress is great for personal blog, while Drupal & Joomla are designed mainly for building business / commercial website using CMS tools.

I hope they (Red Giant Design) can produce another infographic detail the differences between the three would be awesome.

Keep up the good work!


Drupal Error “The selected file /tmp/******* could not be uploaded”

Have you ever encountered the following error in Drupal:

“The selected file /tmp/filesisAcp could not be uploaded, because the destination is not properly configured.”

I got this error after setting up Google Map on the contact us page to display office locations. This is caused by “file” directory permission issue in my Drupal installation directory.

To verify the error, go to Administer >; Site Configuration >; File System:

Drupal will complain that the directory “sites/default/files” is not writable. Simply log into the web server and chmod the directory from Drupal root directory:

chmod 777 sites/default/files

This should resolve the error we saw before.