CiviCRM Community Forums (archive)

Our site became inaccessible when we installed the Drupal Rules and Entity modules. We'd get different errors indicating maximum execution time exceeded and maximum memory allocated when we'd try refreshing. As soon as I disabled these modules, these errors disappeared and the site worked fine.

The Rules and Entity modules are both in Beta, so I've been patiently awaiting a production release to move forward. However, I'm at the point where I need these modules to build the site as desired. So I thought I'd try to figure out if those modules alone were causing the issue or if there was some other conflicting module. And after enabling and disabling a number of modules, what I seem to have determined is that the combination of CiviCRM Views Integration with Entity is causing the issue.

Here's what I found:

With Entity enabled:

• If CiviCRM is enabled and Views is disabled, the site works fine.
• If CiviCRM is disabled and Views is enabled, the site works fine.
• If CiviCRM and Views are both enabled, site is inaccessible.
• If CiviCRM and Views are both enabled, but I rename the sites/all/modules/civicrm/drupal/modules/views directory, the site works fine.

Finally, If I disable Entity and enable CiviCRM and Views, the site works fine.

So, while CiviCRM Views Integration does not depend on Entity, it somehow conflicts with it. Any thoughts on why or how?

If your issues are maximum execution time exceeded and maximum memory allocated exceeded, then this is not a conflict per se, rather this is a resources issue. Sounds like you simply need to allocate more CPU and memory resources to this site.

That thread definitely helps! Thanks!

Hershel, don't think it's a resource issue as others seem to be experiencing the same issue and I've tried increasing resources to no avail.