Activation of views module gives blank screen (on PHP5 server)

Forgot to mention: installation on PHP4 / MySQL 4.0 doesn't show this problem. Also I tried to raise the memory_limit of PHP from 32M to 64M to 128M to no avail.

Others have mentioned the error from the log file:

[client 127.0.0.1] PHP Fatal error:  %v%v() [<a href='function.require'>function.require</a>]: Failed opening required 'modules/views/modules/views_node.inc' (include_path='/usr/share/php5') in /srv/www/htdocs/viewtest/modules/views/views.module on line 18, referer: http://localhost/viewtest/?q=admin/modules"

You can read in my follow-up that raising the memory limit in PHP doesn't solve the problem.

On other setups (on several other [PHP4] servers) views works perfectly with me, on this particular setup (on this PHP5 server) views just gives a blank screen. Other (quite eloborate) Drupal installations on this server work fine.

I hope someone can give a clue about this problem. Thank you for your help.

OK, I've been debugging some things myself and found out that the following patch seems to solve the problem (in my installation [YMMV!]):

--- ../orig/views/views.module  2006-08-26 03:01:56.000000000 +0200
+++ views/views.module  2006-08-27 23:06:22.000000000 +0200
@@ -15,7 +15,8 @@ function views_init() {
     // The filename format is very specific. It must be views_MODULENAME.inc
     $module = substr_replace($file->name, '', 0, 6);
     if (module_exist($module)) {
-      require_once($file->filename);
+//      require_once($file->filename);
+      require_once('modules/'.$file->basename);
     }
   }
 }

It looks like there's a difference in the inclusion mechanism of PHP5 in comparison to PHP4.

@merlinofchaos: Yes, your change seems to work as well. Thank you for getting back.

I'd suggest using include_once instead of require_once. In the case of a missing include file the latter gives a blank Drupal while the former displays helpfull PHP errors in Drupal (but the site still works).

I see your patch is already included in the latest distribution. Thank you for the quick fixing.

Theoretically, a file can exist and appear in the list but cannot be read due to lacking permissions.

Wait, I'll test that hypothesis...

Indeed, changing permissions of a file so that the webserver cannot read them results in a blank screen. Whereas, if the file was included with "include_once" Drupal issues a warning.

Just realized that there are two other places in the module where require_once is used (lin 619 and 1003). These fail in my setup too. Prefixing the include strings with "./" fixes these.

I've tested the September 2, 2006 - 05:46 version of views 4.7 and the include problems seem to be fixed in php5. Thanks.