By anithegregorian on

I am quite new to Drupal (should I say a fresher, never worked in it before). I am originally a Delphi developer, but I was fascinated over developing Web applications in Jan 2008. I began with developing with my first E-Commerce application based on Zen-Cart which is insanely hard to fit in to your theme, Quite the reverse of Drupal :) I do not know if the Zen-Cart developers know anything about Drupal, how its made, how the API's work or how insanely easy and powerful it is to be themed?

But all the accolades and appreciation that I've heard and seen on the net for Drupal forced me to use this amazingly powerfull and flexible piece of CMS to create a new Project which was to be based on a CMS. Im sure I have not made a mistake by choosing Drupal over Joomla, phpNuke or any other CMS for that matter. Whilst learning Drupal in the development of the CMS I was making I came across a very frustrating problem that sucked my blood for almost two days.

The problem started appearing after some time, to be precise when I enabled the Caching module and enabled Caching on drupal Nodes. When I sumbit any Book, Story, Page etc... Drupal sends the data successfully to the database but after that it just blanks out ie. It does not return to the success page.

⋅ Categories: Drupal 6.x

Comments

matt_harrold’s picture

matt_harrold commented

When you say "blanks out", do you mean:

1. The server never returns .. it just hangs forever (until you hit 'reload').

2. The returned page is a blank white screen (the WSOD .... white screen of death).

3. Some other disturbing behaviour (spinning heads, lights flickering, etc).

If it's the WSOD, try increasing your PHP memory limit ... you might be running out of memory. Search the Drupal site for "PHP Memory" or "WSOD" or something similar for a solution.

Adding "php_value memory_limit 20M" to your .htaccess file should fix any memory problems (if that is your problem).

Otherwise, I recommend checking your Apache error logs for the exact error message that's giving you grief.

anithegregorian’s picture

anithegregorian commented

There I was left in disarray, agogy, and scratching my head how its behaving like this. Then I came across an article over output buffering in PHP (I dont remeber where I found it) but it solved my problem. So, heres the solution for you folks.

NOTE: This worked on Drupal 6.0 even with Caching enabled on Nodes, Blocks and everything you may want. I just enabled Output_Buffering = ON in my php.ini and added a few lines of code in the page.tpl.php in my theme (NOTE: You should not touch the default Drupal theme, instead add this line in your customized, default theme which should be in \sites\all\theme\YOURTHEME folder). This should be done right before everything in your page.tpl.php add one line:

ob_start();

This should be the first line of code in your page.tpl.php. Now at the end of the page right before closing the tag write these two lines:

print $closure

ob_end_flush(); exit;

and youre done.