CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • Drupal Installations (Moderator: Piotr Szotkowski) »
  • WSOD when installing new CiviCRM 3.4 on Drupal 6.22
Pages: [1]

Author Topic: WSOD when installing new CiviCRM 3.4 on Drupal 6.22  (Read 1109 times)

rflemin

  • I post occasionally
  • **
  • Posts: 73
  • Karma: 2
    • DCRCA (DC Recovery Community Alliance)
  • CiviCRM version: 3.3
  • CMS version: Drupal 6.26
  • MySQL version: 5.1.26
  • PHP version: 5.2.6
WSOD when installing new CiviCRM 3.4 on Drupal 6.22
August 09, 2011, 09:22:16 am
I have tried repeatedly to do a fresh install of CiviCRM 3.4 on a recently-upgraded Drupal 6.22. I think I have followed all the instructions and cleaned out all the old CiviCRM files before reinstalling. I get the page that says it is successfully installed, but when I check on Configuration checklist, I get the White Screen of Death. Searching WSOD in the Forums hasn't led me to a solution, just sympathy with other people who get to the WSOD by other paths. I'd really like to move up to CiviCRM 4 and Drupal 7, but, at least for Drupal, I have to do this intermediate step. I really need to get CiviCRM working to support a number of upcoming events and activities in the non-profit where I volunteer. I'm no expert, but I'm all we've got. Can anybody help? Please!

Hershel

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4640
  • Karma: 176
    • CiviHosting
  • CiviCRM version: Latest
  • CMS version: Mostly WordPress and Drupal
Re: WSOD when installing new CiviCRM 3.4 on Drupal 6.22
August 09, 2011, 11:36:31 am
Do you have an existing CiviCRM with data you need to preserve? If not, then just upgrade Drupal and then afterward, install CiviCRM.

But if you do have CiviCRM data, then can you tell us what error is listed in the error log for your WSOD?
CiviHosting and CiviOnline -- The CiviCRM hosting experts, since 2007

See here for the official: What to do if you think you've found a bug.

rflemin

  • I post occasionally
  • **
  • Posts: 73
  • Karma: 2
    • DCRCA (DC Recovery Community Alliance)
  • CiviCRM version: 3.3
  • CMS version: Drupal 6.26
  • MySQL version: 5.1.26
  • PHP version: 5.2.6
Re: WSOD when installing new CiviCRM 3.4 on Drupal 6.22
August 09, 2011, 02:40:51 pm
Thanks for you help on another thread. I don't know how to get into my error log data, but I'll try to find out.

rflemin

  • I post occasionally
  • **
  • Posts: 73
  • Karma: 2
    • DCRCA (DC Recovery Community Alliance)
  • CiviCRM version: 3.3
  • CMS version: Drupal 6.26
  • MySQL version: 5.1.26
  • PHP version: 5.2.6
Re: WSOD when installing new CiviCRM 3.4 on Drupal 6.22
August 10, 2011, 07:33:17 am
I've learned how to get into the error logs. In the process, my ISP told me that they show these errors"

[Tue Aug  9 17:33:52 2011] [error] PHP Fatal error:  Call to undefined function
hash() in /usr/home/dcrca/htdocs/dcrca.org/drupal/includes/bootstrap.inc on line 625
[Tue Aug  9 17:42:12 2011] [error] PHP Fatal error:  Call to undefined function
filter_var() in /usr/home/dcrca/htdocs/dcrca.org/drupal/sites/all/modules/civicrm/CRM/Utils/Rule.php on line 379[/color]

This sort of sounds to me like CiviCRM is trying to access something that isn't there in the latest (6.22) version of Drupal. Is this something I can fix (edit/eliminate the call, or whatever) or could I solve it by (as suggested elsewhere with a similar problem) installing Drupal 6.20 and re-installing CiviCRM 3.4.5? The trouble with that is that I would like to upgrade Drupal to 7.7 and I have to start from 6.22 to do that. Does CiviCRM 4.n play nice with Drupal 7.n?

Thanks for any help. I'm really trying to Save The World here and CiviCRM could be a great lever if I can get it to work, but I've spent two days on this and need to either fix it or find another lever.

Hershel

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4640
  • Karma: 176
    • CiviHosting
  • CiviCRM version: Latest
  • CMS version: Mostly WordPress and Drupal
Re: WSOD when installing new CiviCRM 3.4 on Drupal 6.22
August 10, 2011, 07:39:47 am
filter_var is a PHP function, nothing to do with Drupal:

http://php.net/manual/en/function.filter-var.php

ask your host if they can properly configure (or upgrade) your PHP to enable this function.
CiviHosting and CiviOnline -- The CiviCRM hosting experts, since 2007

See here for the official: What to do if you think you've found a bug.

rflemin

  • I post occasionally
  • **
  • Posts: 73
  • Karma: 2
    • DCRCA (DC Recovery Community Alliance)
  • CiviCRM version: 3.3
  • CMS version: Drupal 6.26
  • MySQL version: 5.1.26
  • PHP version: 5.2.6
Re: WSOD when installing new CiviCRM 3.4 on Drupal 6.22
August 12, 2011, 07:42:28 am
I talked to my ISP and he moved the site to a different server that supported HASH, but that didn't solve the problem. I reloaded an older version of CiviCRM -- no joy. He restored an old backup from when everything worked - no joy. Then I read an error message that said I had to make a file deep in the /sites/default/files folder writable. I thought I had done that when I made the whole folder writable, but I noticed a checkbox that said something like "make changes recursively". I checked the box and ran the changes. Now I can get into CiviCRM! Never underestimate the ignorance of the newbie and his power to miss things that are obvious to the experts.
Thanks for all the help -- you folks may not have solved my problem, but you gave me the encouragement to keep trying.

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Installing CiviCRM »
  • Drupal Installations (Moderator: Piotr Szotkowski) »
  • WSOD when installing new CiviCRM 3.4 on Drupal 6.22

This forum was archived on 2017-11-26.