9

I think I found the issue. If your CiviCRM is installed via buildkit there is a file ~/buildkit/app/civicrm.settings.d/100-mail.php which sets the CIVICRM_MAIL_LOG to /dev/null. This doesn't allow Civi to communicate to MTA (Mail Transfer Agent). The first solution is to comment out //if (!defined('CIVICRM_MAIL_LOG')) { // define('CIVICRM_MAIL_LOG', '/...


9

You can specifically set the value of [civicrm.files] in civicrm.settings.php with code like this: global $civicrm_paths; $civicrm_paths['civicrm.files'] = array( 'url' => 'https://example.com/foo', 'path' => '/var/www/example.com/foo', ); If you don't set the value, then Civi will try to find it automatically, but this doesn't work in all ...


8

Disabling security notifications hides the notice from your users, but it won't hide your sites from attackers. Turning off the warning supports a scenario where those sites are at risk longer. Here's how we handle it for our hosting clients - Create a recurring item in your calendar for the CiviCRM security release dates, first and third Wednesday each ...


6

This is what works for me but not sure if it is necessary based on the following http://wiki.civicrm.org/confluence/display/CRMDOC/Moving+an+Existing+Installation+to+a+New+Server+or+Location : Edit civicrm.settings.php with new database info Delete all template files in templates_c/ Make sure there are no references to civicrm database in drupal setttings....


6

This is a preference you can set, but it's not exposed in the web interface. There's a section of civicrm.settings.php that documents it. In case you've upgraded from an older version of CiviCRM that doesn't have it, I'm including it here: // Opt-out of announcements by the CiviCRM core team for releases, paid services, events, etc. Separate each ...


6

Normally you don't install from github you would get it from https://civicrm.org/download and then follow the instructions at https://docs.civicrm.org/sysadmin/en/latest/install/drupal7 If you are looking to do development it might be easiest to start here instead: https://docs.civicrm.org/dev/en/latest/tools/buildkit/


5

I dug further into the changes that WPE does to the file structure. It looks like the new magic method of determining the file location using [civicrm.files] is failing. See https://github.com/civicrm/civicrm-core/blob/master/Civi/Core/Paths.php I am able to get both 4.6.13 and 4.7.2 running on WPE by adding the following to my civicrm.settings.php file ...


5

Change all cron jobs and scripts that use the site key for authentication Reenter any passwords, specifically payment processors and mail/sms passwords All prior checksums sent in the last 7 days (if that value has not been changed), will no longer work A grep for SITE_KEY in the code base will uncover a few more things :)


4

Any source of unknown data should be fine - I'd use a command like this just because it's quicker: head -n 1000 /dev/urandom | md5sum


4

And once again I had found out the answer on my own, took a lot of time though... it is in components and administrator's civicrm.setting.php (both php file!) just simply change both localhost (see the photos below) into your server IP Simple as that (yeah I'm so noob TwT), I wish this can help those who have the same problem like mine, apology for my bad ...


4

The /wp-content/plugins/civicrm/civicrm path is for CiviCRM versions older than 4.7. For a new install you should find it under /wp-content/uploads/civicrm


4

After hours of trying to figure out the issue, i have been able to fix this by changing the Theme in Drupal. When i made the Theme into a default theme the upgrade page showed with no issues.


3

Whilst this may not be a good idea if you don't have infrastructure to keep on top of upgrades & security issues, the setting can be found in: Administer > System Settings > Misc. the notifications are set in the dababase in the civicrm_setting table (along with lots of other useful little settings :)) From the "name" column, we can ascertain that: ...


3

Easiest thing to do is upgrade in stages, go from 4.0 to 4.1, then to 4.2 then you can try straight up to 4.6 This approach should mean you dont hit too many issues


3

The recommended location is wp-content/uploads/civicrm/civicrm.settings.php. The deprecated location, still supported as of April 2017, was wp-content/plugins/civicrm/civicrm.settings.php, but this is both easy to break on upgrade ("whoops, I removed the old plugin and the settings files, and I don't have backups!") and on some sites is not a writeable ...


3

Try setting your preferred timezone in civicrm.settings.php and/or wp-config.php? ini_set('date.timezone', 'Asia/Calcutta'); You might want to adapt the timezone you set as appropriate to your MySQL server. mysql -e 'SELECT @@system_time_zone;' I believe India does not observe daylight savings? For that and similar reasons it's probably better to match ...


3

Your drupal may be using a different mysql driver. CiviCRM recently migrated to requiring mysqli. See https://civicrm.org/blog/totten/psa-please-verify-php-extension-mysqli for more details.


3

See documentation on moving an existing installation to a new server or location on this link: https://wiki.civicrm.org/confluence/display/CRMDOC/Moving+an+Existing+Installation+to+a+New+Server+or+Location


3

tl;dr: Uncomment and fill in the define('CIVICRM_CMSDIR', '/path/to/install/root/'); in civicrm.settings.php. I traced through the functions that go toward building the URL for loadins crm.ckeditor.js. It seems there's a problem with the logic of the WordPress cmsRootPath function. I can't tell you what the specific issue you're having that's causing ...


3

Thanks Jon G for providing the solution to turn off the community messages. However, as one of the organizers of CiviCamp Brussels 2018, I am very happy with this feature. It's an effective way to reach civi users who are not on your own mailing lists and who might otherwise miss the event. They would miss an opportunity to engage with the community. And ...


3

I changed my cache plugin and that seemed to fix the problem.


3

It's really bad idea to customize CiviCRM core files when you can do thing using extensions. If you feel your customization fixes core issues than you should try to submit pull request against civicrm-core. If your changes are client specific than you can either move those files into custom php or custom template(again bad idea since its very difficult to ...


3

Have a look at the Developer Guide here: https://docs.civicrm.org/dev/en/latest/ as a start. If at all possible I would recommend trying to find an expert near you who would be able to give you a developer training. You would have to pay for it but it will probably save you a lot of exploration time :-)


2

At minimum you would need to upgrade to 4.4 - this is the current LTS version and is the oldest version which still receives security patches. As Parvez recommended, upgrading in stages is sometimes smoother, although 4 versions is not such a big jump that you can't necessarily do it all at once. Always back up your database first, and if jumping straight ...


2

Marsh's answer is correct for Civi 4.6. For versions 4.7+, go to Administer menu » Administration Console » System Status and press "Hide" next to the version check message. You can choose to hide the message for a week, a month, or forever. Note that hiding a non-security update will NOT hide a security update, but hiding a security update will hide both....


2

Since it's coming from include_once I suspect you have two civicrm.settings.php files. The correct location is sites/<default or example.org>/civicrm.settings.php If there's a file in sites/civicrm.settings.php, rename or remove it and see if that ends the errors. -- EDIT: OK, having reformatted your question I can see the file path isn't actually ...


2

There is no requirement to generate the SITE_KEY in the same way. (In fact, the algorithm changed in v4.6.3.) Rather, follow these requirements: Stick to alphanumerics Provide decent entropy (I think 90 bits would be decent, but there's no downside to going higher) For some better ways to generate a SITE_KEY: On Debian/Ubuntu-based systems, run: sudo ...


2

Looks like the menus did not build correctly. I would install this plugin https://wordpress.org/plugins/civicrm-admin-utilities/ You can activate and it allows for a menu rebuild and a cache flush. The file civicrm.settings.php is in uploads/civicrm I do see that you are on WP Engine, to be honest , I have not been able to install CiviCRM on WPE. ...


2

Supplementing Jason's answer for a Drupal installation: the file civicrm.settings.php will be found in your site's directory, e.g. drupal/sites/default/ or drupal/sites/mysite.com/ . Look for CIVICRM_DSN in civicrm.settings.php .


2

Ok, I figured it out and for the benefit of anyone who might Google search this same question, here's the answer. 1. Go to your webhost's file browser. 2. The file should be located in /public_html/wp-content/uploads/civicrm/civicrm.settings.php 3. Open the file with the code editor. 4. Modify the credentials string which contains the password and save.


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