CiviCRM Community Forums (archive)

I am posting this to a new topic here in case others may have the same or a similar problem.

AT last. I have a host who has enabled Innodb support.
I did a fresh install of Drupal 6.3 and civicrm 2.1 using civicrm-2.1.alpha1-drupal.tar.gz


Civicrm installed fine with no errors.

I am having a problem though.

When I go to the module admin page I get a blank page. I get the same with all civicrm pages.
If I disable civicrm, I get the module admin page just fine.

I have checked all ther permission and paths. everything is fine.
I have probably missed something somewhere, but am out of ideas.

Any ideas?

I have worked for weeks to find a site that will wowrk with both drupa 6.3 and civicrm. I really hope to see this working at some point.

Some of my configuration information:
cPanel Version 11.23.4-RELEASE
cPanel Build 26138
Apache version 2.2.9 (Unix)
PHP version 5.2.6
MySQL version 5.0.51a-community
Architecture i686
Operating system Linux
Kernel version 2.6.25.9-grsec

Thanks,

Jim

Thanks for responding MacRonin,
The memory is set at 32m I even bumped it up to 64m to test it. No change.
I set it back to 32 which is the server default.

It is a bit strange because everything else worked fine until I installed civicrm.

I tried downloading the stable version only to find out it was not friendly with 6.3 of drupal. LOL

Now I am thinking about using a previous version of drupal which will work with stable civicrm... LOL I want that program too bad I guess.

The first thing that I would check is your PHP memory setting. CiviCRM is a bit greedy with the RAM, and the WSoD(White Screen of Death) is frequently(not always) a shortage of memory.

If you install the Drupal module DEVEL it can tell you about your memory usage. Well at least on the pages that give you a response and not the WSoD.

I did the security upgrade to Drupal 6.4 and deleted the database for both drupal and civicrm. Did a clean install on Drupal 6.4 and on civicrm 2.1 .
Still have the same problem.

Memory is 32m which according to the installer should work.
I do not find  the Smarty work/cache folders. Can you clue me in on where they are at?

I have checked to make sure that permissions are set and that ownership is correct.

It does seem like there has to be an addressing problem somewhere.
I just have no idea where to find it.

I am only an end user and have no coding background, so I have to dig for the things that just pop up for the more knowledgeable folks.

I have to say that it sure seemed the 6.4 drupal loaded much smoother and faster. LOL Though it should. It is loading with basically an empty DB.

I don't know if this means anything or not but if civicrm is installed, after I click on the civicrm link one time and get a blank page, I get this error warning:

parse_ini_file() has been disabled for security reasons in home/veterans/public_html/
sites/all/modules/civicrm/packages/IDS/Init.php on line 88.

If I disable the module it goes away. I can also turn off error reporting and it goes away.
It just seems to be connected to civicrm for some reason.

I appreciate your input.

Jim

Quote

I tried downloading the stable version only to find out it was not friendly with 6.3 of drupal. LOL

Now I am thinking about using a previous version of drupal which will work with stable civicrm... LOL I want that program too bad I guess.

I just upgraded to 2.0 myself. I'd been stuck at 1.8 since my server was only running php4 and not php5, but now I'm on php5  Yup CiviCRM won't be compat with Drupal 6 till the 2.1 release. I don't mind the wait since I want the new CCK & Views to stabilize before I upgrade.

Since you were using a development version, I assume that you did the install manually and not via Fantastico.

Just since I am a bad typist and believe in Murphy's Law. I assume that you did a phpinfo() or something similar to verify that the memory increase took effect and that you didn't make a typo in the override parm.(I've made that mistake) It's the fact that you took down the modules page also that makes me think memory

My only other ideas at the moment is to make sure that the files paths are correct and the Smarty work/cache folders have the correct permissions. And maybe make sure that you have Drupal caching turned off. I'm not sure about it for 2.x but I know 1.8 had a problem with Drupal caching being turned on when running/processing the CiviCRM pages. Also do you have access to the Apache error log to see if PHP but out any error msgs when it died?

1. can u increase you php memoro to 64M

2. can you check your error_log or your drupal watchdog table and see what the error is

3. note that v2.1 just went alpha last week, so you wont find too many sites (if any) running drupal v6.x and CiviCRM v2.1 (or at least we strongly discourage it)

4. The parse_ini_file error should be resolved like this post says: http://drupal.org/node/103963

You can potentially find other solutions here:

http://www.google.co.nz/search?num=100&hl=en&newwindow=1&client=firefox-a&rls=org.mozilla%3Aen-US%3Aofficial&hs=7js&q=parse_ini_file()+has+been+disabled+for+security+reasons+PHP+IDS&btnG=Search&meta=

We use PHPIDS http://php-ids.org/, which uses that function

lobo