The Stack Overflow podcast is back! Listen to an interview with our new CEO.

Hot answers tagged

3

I found the solution to my issue. The php.ini was causing another issue with my site. When I renamed it, I was able to import as expected.


3

You should double check your civicrm_settings.php file. Particularly the section on File System Paths. Make sure the setting $civicrm_root is the correct path to civicrm for the new server. Hope this helps...


2

WP Engine is a quirky host--it makes lots of configuration decisions for you with the goal of optimizing for WordPress sites, but that often makes things more difficult for CiviCRM. This is in stark contrast to Linode, where you have full control over your hosting configuration. A 500 error could be any number of things; you'll need to find a log message ...


2

I don't know of any way to limit the processes. Importing is a large task since it's hitting so many fields, tables, etc. That means a lot of processes regardless of how many records you're importing. Shared servers often times have too low of limits to be able to fully use CiviCRM without running into issues. It's why we finally ended up just getting our ...


2

This appears to be identical to CRM-20558. Upgrading to 4.7.20 or applying the fix there should solve your problem. Note that CiviCRM is not tested against PHP 7.1, so you may want to consider using PHP 7.0 instead.


2

Ahh did you upgraded to unstable version of CiviCRM? The last stable release i see is 5.4.1. Try replacing the civicrm code base to 5.4.1 and then update the civicrm_domain.version to 5.4.1 and also truncate all cache tables and anything under template_c folder.


2

CiviCRM isn't spawning processes directly, that's probably apache, or your web server. When using the web interface to do CiviCRM imports, and many other activities, CiviCRM uses some clever techniques to avoid things timing out, but that have other trade-offs in server requirements. This is probably not the only place where you might run into trouble. FWIW,...


1

I am switching to DigitalOcean. Works fine there. Bye bye Arvixe.


1

A workaround would be to clone your website to your localhost development environment, do the import there, then replace the live database with the one from localhost. If you need to retain the live URL throughout this process, you can point it to localhost by editing your hosts file. [Aside: this is a good way to do CiviCRM upgrades too, since it is far ...


1

OK so in reviewing the requirements in the documentation, it seems that version 4.6.x was the last version that states explicitly it is compatible with Joomla 2.5 AND 3. The latest documentation (which I'm assuming is for 4.7?) says Joomla 3 is required. But the download site clearly says "Download 4.7.27 for Joomla 2.5x/3x". I'll try a rollback to 4.6....


1

First, let the record show that I am an idiot. After uploading 4.7.23 (the new version) to /wp-content/plugins, I neglected to copy the pre-existing civicrm.config.php into /wp-content/plugins/civicrm4.7.23/civicrm ... thereby depriving the system of (at very least) a working value for $civicrm_root. It was suggested to me that my civicrm.config.php was ...


Only top voted, non community-wiki answers of a minimum length are eligible