by Fanatical Labs

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

#2874 - 7.8.1 Killed our System

Closed Bug? created by mailchimp 7 years ago

Hi,

We tried to upgrade SugarChimp from 7.7.1 to the latest version 7.8.1 but during install the system crashed our on-demand instance, it was totally unusable. Sugar support stepped in and managed to get our system back on line. They put the following comments in the ticket once it was back up, our installation was unsuccessful and we are seeing errors in the sugarlog:

_**Thanks for reaching support. I was checking and the issue is that in the file "modules/SugarChimp/includes/classes/Mailchimp/API.php" there is a request for the file bellow that does not exist:

modules/SugarChimp/includes/vendor/Mailchimp/MailchimpV3.php

By commenting this line the instance access was restored. Can you please confirm that your access is restored?

After that, you can redirect this error to the SugarChimp team to see if they have any further advice :

PHP Fatal error: require_once(): Failed opening required 'modules/SugarChimp/includes/vendor/Mailchimp/MailchimpV3.php' (include_path='/mnt/sugar/7.7.1.0/pro:/mnt/sugar/7.7.1.0/pro/vendor:.:/usr/share/pear:/usr/share/php') in /mnt/sugar/shadowed/psigroup.sugaropencloud.eu/modules/SugarChimp/includes/classes/Mailchimp/API.php on line 12, referer: https://psigroup.sugaropencloud.eu/**_

Errors in the sugarlog are:

Tue Feb 14 09:13:28 2017 [23826][1][FATAL] Job afa61448-f295-11e6-87c3-06e555942243 (SugarChimp) failed in CRON run

  1. mailchimp member avatar

    mailchimp

    7 years ago

    Further to this our sugarchimp module now seems to be broken. When I go to Health Status in the admin panel I'm greeted with:

    **_HTTP: 500 Internal Server Error

    Unknown error._**

    In SugarChimp Configuration I can get as far as validating the API key before it drops to the above error.

    In field mapping it also drops to thye above 500 Internal Server Error.

    We need some help over here, Sales are processing click through links but they also drop to the 500 error.

  2. chad member avatar

    Chad Hutchins Verified Purchase

    7 years ago

    Hello, really sorry for the issue. We found the root cause of the issue. There is a misspelling in the file that we are trying to load: this modules/SugarChimp/includes/vendor/MailChimp/MailchimpV3.php should be modules/SugarChimp/includes/vendor/Mailchimp/MailchimpV3.php (notice the lower-case "c" in mailchimp)

    We will get a new package out to you very soon. This should resolve all of the issues you're seeing.

  3. chad member avatar

    Chad Hutchins Verified Purchase

    7 years ago

    Also, thanks for the detailed error response. That helped us know exactly what the issue was. The difficult part about this one is that some servers will allow the casing misspelling, so that is how this issue was missed.

    I'm currently testing the new package in the on-demand environment to make sure everything is working.

  4. chad member avatar

    Chad Hutchins Verified Purchase

    7 years ago

    I just updated the new package that corrects the issue. You can find the new package on your orders page here: https://www.sugaroutfitters.com/orders

    Download the package, go to Sugar > Admin > Module Loader and upload and install the new package (do not uninstall the old package). After doing this the 500 errors should go away.

    Let us know if you have any questions about this or if it does not fix the issue. Sorry again!

  5. fanaticallabs member avatar

    Fanatical Labs Provider Affiliate

    7 years ago

    Hi,

    I'm going to go ahead and close this case out. However, if you need anything else, don't hesitate to respond here or start a new case.

    Thanks!

This case is public. Please leave out any sensitive information such as URLs, passwords, etc.
Saving Comment Saving Comment...
Rating
Rating