CiviCRM Community Forums (archive)

Recently I upgraded one site from CiviCRM 4.1.3 D6 to CiviCRM 4.3.4 D6 as that is far as the DB upgrade would make it successfully on this old server we are migrating from.

Since the upgrade, recurring contribution transactions do not notify CiviCRM upon successfully charging the card. This client is using Authorize.net payment gateway.

According to the CiviCRM docs found here:
http://wiki.civicrm.org/confluence/display/CRMDOC/Authorize.net+Configuration#Authorize.netConfiguration-AutomatedRecurringBilling

it seems this behavior is to be expected

If you fail to do this, one-time contributions will succeed normally, and recurring contributions will be processed successfully by Authorize.net, but the contribution status will be stuck at Pending.

I tested browsing to that URL in a web browser and it comes up with an error stating:

Could not find valid configuration dir, best guess: /home/clientweb/members/sites/members.clientorgname.org/modules/civicrm/../../sites

Actually the CiviCRM config file is in this directory:
/home/clientweb/members/sites/members.clientorgname.org

So how does one correct the path which authorizeIPN.php expects the CiviCRM config file to be located at?

I am thankful,