SugarChimp

Save Your Team Countless Hours. SugarChimp syncs your lists in both directions so you can work in your preferred app. Segment and group your Mailchimp subscribers based on Sugar data so you can market to the right people at the right time. Compatible with all versions and editions of Sugar and SuiteCRM. Created by Fanatical Labs, 2023 SugarCRM Partner Award Winner.

Free Trial

By clicking you consent to share your profile with the developer

#531 - Installation issue with Mailchimp API

Closed Installation created by clickelement 10 years ago

Error Log: The MailChimp api key failed to save: API call to helper/ping failed: SSL certificate problem: unable to get local issuer certificate

It won't let me proceed with installation. Which SSL certificate is it having problems with mine, or mailchimps?

Fanatical Labs Provider Affiliate
10 years ago

Hi there, usually it's your web server certificates that are having issues when this occurs. And it occurs most often when running on IIS.

If this is the case you may want to give this guide a look: http://curl.haxx.se/docs/sslcerts.html

In short, you'll need to set cacert.pem to curl.cainfo.

1) download http://curl.haxx.se/ca/cacert.pem and save it somewhere. 2) update php.ini -- add curl.cainfo = "PATH_TO/cacert.pem"

If you need more help with this, I can reach out via email and setup a time for a screenshare if you like.

reply
clickelement
10 years ago

OK I got it to work thanks.

reply
- Fanatical Labs Provider Affiliate
  10 years ago
  
  Good to hear! Let us know if you need anything else!
  
  reply
Henry
10 years ago

This helped meto , but now i have the problem that the links point to my servers root instead of the folder where i installed the api.

All my links point to the root's www but i installed it in http://M.Y.I.P/mcapi2-php-examples/ , but the links goto http://M.Y.I.P/lists or http://M.Y.I.P/reports Thanks in advance

reply
- Fanatical Labs Provider Affiliate
  10 years ago
  
  Hi Henry, I'm not sure I'm going to be much help on this one. This seems like a web server related issue.
  
  You may want to try StackOverflow (http://stackoverflow.com) or ServerFault (http://serverfault.com) for a question like this.
  
  reply
sahar
10 years ago

Hi there, We had the same issue and we took the steps suggested to overcome the SSL certificate problem. Now the CRM is not showing up on the browser and we have the following error in our phperrors.log file: Undefined index: sugarchimp_logger in [FILES PATH]\htmlroot\modules\SugarChimp\includes\classes\SugarChimp\Helper.php

Can you please help us with this?

reply
- Fanatical Labs Provider Affiliate
  10 years ago
  
  Hello sahar,
  
  First thing to do is turn off PHP Notice messages which isn't recommended to have on in production. This can be done by editing php.ini and changing error_reporting to:
  
  error_reporting = E_ALL & ~E_NOTICE
  
  This will require restarting Apache after the change.
  
  The root cause of this specific notice that you are seeing in phperrors.log is in that file you have there. On line 33 of Helper.php change this line:
  
  if ($sugarchimp_logger == 'debug')
  
  To:
  
  if (isset($sugarchimp_logger) && $sugarchimp_logger == 'debug')
  
  We will get this added into the next release which is due out next week.
  
  reply
sahar
10 years ago

Thank you for your quick response. We made the change in the helper.php file. We don't get any more notice on our errorlog file but still the whole crm is not working. Is there any chance that the module is causing some other issues to the system?

reply
- Fanatical Labs Provider Affiliate
  10 years ago
  
  Hi again, this is a really strange issue. We've never had anything like this reported in the past.
  
  Nothing in SugarChimp should cause what you're seeing. My guess is that it's more related to the server side issues you were seeing with your url routing, htaccess, or something related.
  
  What version and edition of Sugar are you running? And what version of SugarChimp do you have installed?
  
  Thanks!
  
  reply
sahar
10 years ago

Hi You were right. The problem was caused by another file that we had manipulated by mistake. It's now working just fine. Thank you for your support.

reply
- Fanatical Labs Provider Affiliate
  10 years ago
  
  Glad to hear you figured out!
  
  reply