Articles

The default behavior of drupal_redirect_form in Drupal 6 is to redirect the user to $_GET['q'] when an explicit redirect location is not set in $form_state['redirect']. So any form submission from a Drupal page with additional querystrings like in a paginated form (for example admin content listing forms or admin comment listing forms) will result in the querystrings being lost. This can be frustrating when you administer content from such forms as you have to click the pager link and go back to the previous page after form submission. This can easily be fixed by adding a submit handler for the form in question and setting form_state redirect correctly.

The default comment moderation system in Drupal 6 is crude at best primarily because of the limitation of the admin comment listings. The information that is shown by default are 'Subject', 'Author', 'Posted in', 'Time' and 'Operations'. Now the main objective of comment moderation is to reject spam comments. None of these fields give any information about whether the comment is a spam comment or not and you will have to view each comment by going to the edit view of the comment and then approve or reject the comment. This is a very laborious and frustrating process. You have three options to solve this problem and get a better comment administration interface - one is to create a comment view, another is to alter the default comment administration form and the third is of course a custom solution for comment administration.

This is how you would normally render a view display passing filter inputs via code: $view = views_get_view('view-name'); $view->set_display('display-name'); $view->is_cacheable = FALSE; $filter_1 = $view->get_item('display-name', 'filter', 'filter_1_id'); $filter_2 = $view->get_item('display-name', 'filter', 'filter_2_id'); $filter_1['value'] = "value1"; $filter_2['value'] = "value2"; $view->set_item('display-name', 'filter', 'filter_1_id', $filter_1); $view->set_item('display-name', 'filter', 'filter_2_id', $filter_2); dpm($view->render());

Blocks are regions on a Drupal website that show small but significant pieces of content. Blocks are an important component from the perspective of a Drupal website. Blocks are usually assigned to regions in a page and they are supposed to be printed on a page. However there are many instances where you might want to print a block within a content. It is not directly possible to assign a block to a region within content (node in Drupal speak) as you can do with a page. But as with everything in Drupal there is a way to do that.

How to test the site in maintenance mode in Drupal 6 and Drupal 7? During many instances there are occasions where you would like to take the Drupal site offline before your testers run through the various testing procedures.

Sony have released the price lists of Sony Vaio Laptops for the month of August 2012. The prices are given as follows..

”rsync” is an open source utility in Linux/Unix primarily used for synchronising files/directories over the networks. You can also use it to backup/copy folders between machines. It is particularly made use of to while administering servers connected to the internet. The term “rsync” itself refers to “remote-synchronise”.

On a WHM/cpanel VPS server the httpd.conf is automatically generated from cpanel scripts based on templates and you are not supposed to change this file directly. Any changes that you make in the httpd.conf file will be lost when cpanel re-generates the file or when cpanel is updated. This is an inconvenience especially when your application requires you to make virtualhost modifications in the configuration. However cpanel provides an alternative way to edit the httpd.conf file.

When you untar large tar files even as the root user on your VPS you might run into the error "Cannot change ownership to uid NNN, gid NNN: Disk quota exceeded". This is because the extracted files from the tar archive is being attempted to be created with the original UID and GID as on the system where the tar archive was created. Now if the UID is not already present on the new VPS or if the UID corresponds to a user without a lot of disc quota available the above error will be triggered preventing extraction of the tar.gz archive.

Most of us must be familiar with the names 'dig' and 'whois'. If not, these are two commands used to find the details of domains. You just have to type in dig domainname or whois domainname to get a comprehensive set of info on the domain. What if you have not just one or two domains to check about. How about a 1000 domains and you want to know the details of each?