Author Topic: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues (Read 4840 times)

backdrifting · August 19, 2009, 05:05:41 am

I'm running Drupal 6.13. When I try and run my modules admin list here at /admin/build/modules I get the infamous white screen. The rest of my site loads without issue - just the modules list is giving me problems. I try refreshing and it still does not load. I have boosted my php memory limit to 300M and it's still happening.

This site is running on Siteground server with PHP 5.x. I'm also running CiviCRM 2.2.7. CiviCRM is running fine.

What I did that may have caused the above:
Yes, 300M is being used. I checked phpinfo. I've configured my settings.php to query multiple dbs per this article:

http://drupal.org/node/18429

This is due to having a Drupal db and a CiviCRM db. In order to use Views2 with CiviCRM I need to allow the Drupal db user to SELECT from the CiviCRM db - I've done this and added the following table prefix array (per this article: http://wiki.civicrm.org/confluence/display/CRMDOC/Views2+Integration+Module) - it works - I can see the CiviCRM Views I've built. But as soon as I enable this array I get the white screen on my modules admin. I'm assuming that adding that array is consuming too much memory. What do you suggest? Is there a better method of doing this?

I know that array is causing the issue. If I delete it and set my table prefix back to the default everything runs fine and my admin modules screen loads.

I bumped memory limit up to 300M and same thing - still throws a white screen. So adding that array code per the wiki.civicrm.org article is causing the issue. This looks like a bug in the code.

Any suggestions for making Views2 and Civi integration work without causing these performance issues?

-backdrifting

Donald Lobo · August 19, 2009, 06:20:55 am

please avoid reposting the same issue multiple times. i deleted the previous topic

lobo

jalama · August 20, 2009, 06:22:40 am

I haven't seen anything like this, or experienced it myself. Is there any chance you civi and drupal db's are on different servers?

backdrifting · August 20, 2009, 12:30:08 pm

No, same server.

-backdrifting

DanilaD · August 22, 2009, 09:30:40 pm

I prefer to avoid modules screen and use drush to enable/disable modules. More reliable and fast for me.

backdrifting · August 24, 2009, 09:08:23 am

Yes, this is a good idea however I have admin users who are not up to speed on using Drush. So I need to be able to load the modules admin page. Plus, I do think performance-wise that it would be more reliable if Drupal and/or CiviCRM was not causing this issue since it only occurs when I add that CiviCRM/Views array. So it definitely appears to be a bug of some sort.

-backdrifting

Donald Lobo · August 24, 2009, 09:30:04 am

yes this is a bug. would be good for you/your developer to dig into the code and figure out what part of the code is consuming all that memory. If i had to guess its somewhere in the drupal code

(since drupal controls that page completely). You might want to file an issue along with a patch once you figure it out

lobo

backdrifting · August 25, 2009, 06:44:01 pm

I'll report it on the Views issue queue I guess at drupal.org. However the admin module page is loading fine for me if I remove the CiviCRM array code ... so wouldn't this point to the bug being with CiviCRM?

-backdrifting

Donald Lobo · August 26, 2009, 05:57:46 am

yes it is a bug somewhere in Civi or Drupal or Views2. We wont know till someone finds out what/where/why

seems like you are affected by it, so in the spirit of open source might be beneficial for someone else if you can investigate and figure out whats going on and why. I suspect issues filed will remain filed in the issue queue for some time

lobo

backdrifting · August 26, 2009, 05:20:46 pm

Ok, so should I file this as an official bug/issue with CiviCRM as well?

-backdrifting

Donald Lobo · August 26, 2009, 05:23:34 pm

no

we like issues to be filed when we are quite certain that it is a civicrm issue. we dont seem to have that problem on our servers / install of views2. if you can trace the issue and figure out where the problem is please file and issue along with a patch

lobo

backdrifting · August 30, 2009, 06:24:50 am

Since you're not experiencing the issue on the CiviCRM servers, can you detail exactly how you have the array placed - is it in your Drupal settings.php file? Did you do any other customization in settings.php that is different than how I have ours configured? Seems odd that your config is working and mine is not, when I'm following the exact same instructions per the CiviCRM docs.

-backdrifting

backdrifting · August 30, 2009, 06:28:29 am

So after I set my db query to multiple dbs in my settings.php file, should I then use this code (per the Drupal.org doc as per above) to set it back to my default db?

<code>
<?php
db_set_active('mydb');

db_query('SELECT * FROM table_in_anotherdb');

//Switch back to the default connection when finished.
db_set_active('default');
?>
</code>

This is where I'm a bit confused. Are you doing this switch on your servers? Maybe this is causing the issue if I'm not doing the switch back to the default db?

Any suggestions on this?

Thanks,

-backdrifting

adshill · August 30, 2009, 01:31:23 pm

If I can add my two pence to this...

I had up until today a siteground server that was running D6.13 and Civi 2.2.7 (Atom 1.6). I reported the problem previously that with a reasonable number of contrib modules, and civicrm, the modules page gives WSOD.

I have done a lot of research into this and also tried to do a lot of finding the route of the problem but all I could get to was that when I disable civicrm, the WSOD goes away. Re-enabling this it comes back.

Having moved the site locally I realised that the issue was performance of the server also, because everything functioned as expected on my local machine (although module screen does also take a good few seconds to load).

It sounds like on one point you have isolated an issue with performance in Civi, however I believe a big part of the problem here is actually with Drupal 6, and the way it delivers the module page. I draw your attention to:

http://drupal.org/node/193366

There are more than one post like this on drupal relating to the performance of the modules page. There are patches there. We took the easy option of upgrading our resources rather than delve into the code at this time. We haven't the developer resources at this time to devote to helping. However I think that the issue is not just a Civi one, but also a Drupal one.

It is worth mentioning that you may need to increase your timeout times in php.ini and also in mysql in order to help with this, while the modules page is slow, it usually loads after a while - but it can take between 30-45 seconds, so if your timeouts are short (as siteground defaults) then this could help.

In general, I think there are some major questions around drupal and civi performance (although in D7 and Civi3 I think this is a big focus of attention) however without significant time focus on these issues they will not be fast resolved. I hope in future months we can help contribute for this as the cost of resources grows significantly to deliver innovative or complex solutions.

Donald Lobo · August 30, 2009, 04:59:10 pm

civicrm does not use drupal's db connections. U dont need to use db_set_active etc (or at least we dont)

note that the views2 integration is done jointly with the community. As such there are folks in the community who know a lot more about this than we do

lobo

CiviCRM Community Forums (archive)

News:

Author Topic: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues (Read 4840 times)

backdrifting

CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

Donald Lobo

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

jalama

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

backdrifting

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

DanilaD

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

backdrifting

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

Donald Lobo

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

backdrifting

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

Donald Lobo

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

backdrifting

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

Donald Lobo

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

backdrifting

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

backdrifting

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

adshill

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues

Donald Lobo

Re: CiviCRM 2.2.7 and Drupal Views2 integration causes other Drupal issues