Blog

You have created a Drupal View as a page and the View is working correctly as intended in the preview section in the View settings page. However when you visit the actual page it throws up a 'Page cannot be displayed' error after you had clicked on the View button on the Views settings page. So what is causing the problem and what could be the fix? Read on to see the solution. -->

Zyxware conducted a one day workshop on Python on 11th June at CDAC Trivandrum. The workshop was targeted at experienced developers who were about to take on a new Python project. The full day workshop was attended by 8 participants from CDAC, Trivandrum.

CSI Trivandrum and Zyxware conducted a one day workshop on Python on 28th July at Hotel Keys. The workshop was targeted at new developers who are interested in learning python. The full day workshop was attended by 28 participants from across different organisations in Trivandrum.

Banking application packages are probably the most complex software suites which demand high security, faster transactions per second, massive database storage system, and highly efficient multitasking to support thousands of concurrent users. Banking applications have multiple levels involved in performing an operation. For example, a banking application may have:

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.

Boost is a Drupal module that accelerates the performance of a site by efficient caching of pages. It can be enabled for all pages other than the ones which need to show constantly updating data (for example, a captcha box). NOTE: If you are looking on how to install and configure Boost for your Drupal website, go here: How to install and configure Boost caching module to speed up performance on your Drupal 6 site. Here we list some methods for testing the Boost implementation on a Drupal website: