CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviContribute (Moderator: Donald Lobo) »
  • Payment Processor Issues with Multi-Site/Multi-Org Install
Pages: [1]

Author Topic: Payment Processor Issues with Multi-Site/Multi-Org Install  (Read 1066 times)

matthewdnye

  • I’m new here
  • *
  • Posts: 28
  • Karma: 1
Payment Processor Issues with Multi-Site/Multi-Org Install
July 23, 2011, 04:58:50 pm
I have configured a multi-site/multi-org CiviCRM 4.0/Drupal 7 install, and up until a little while ago I thought I had done everything correctly. I have separate Drupal child sites for each region all accessing a single parent installation of CiviCRM, with access control handled through groups.

I am in the process of testing out basic features and am attempting to set up an event. In order to do this I had to set up a payment processor, which in this case is FirstData/LinkPoint.

I configured the Payment Processor while logged into the parent organization, and assumed the child would inherent the entry; at first glance this appeared to be the case. When I set up the event as the child org, however, it said I needed to configure a payment processor.

When I went and actually edited the Payment Processor under the child site, the primary entry was there, but none of the actual details were entered as they were in the parent entry. I added them manually, so the Payment Processor entries look identical in both the parent and child orgs, but I am getting two different errors, which, in combination with the fact I thought I should only have to enter the information once make me very nervous.

When I select the Payment Processor in the event setup process I get the following errors:
    Notice: Undefined offset: 2 in CRM_Event_Form_ManageEvent_Fee->postProcess() (line 622 of /home/xxxxxx/public_html/sites/all/modules/civicrm/CRM/Event/Form/ManageEvent/Fee.php).
    Notice: Undefined offset: 3 in CRM_Event_Form_ManageEvent_Fee->postProcess() (line 622 of /home/xxxxxx/public_html/sites/all/modules/civicrm/CRM/Event/Form/ManageEvent/Fee.php).
    Notice: Undefined offset: 4 in CRM_Event_Form_ManageEvent_Fee->postProcess() (line 622 of /home/xxxxxx/public_html/sites/all/modules/civicrm/CRM/Event/Form/ManageEvent/Fee.php).
    Notice: Undefined offset: 5 in CRM_Event_Form_ManageEvent_Fee->postProcess() (line 622 of /home/xxxxxx/public_html/sites/all/modules/civicrm/CRM/Event/Form/ManageEvent/Fee.php).
    Notice: Undefined offset: 6 in CRM_Event_Form_ManageEvent_Fee->postProcess() (line 622 of /home/xxxxxx/public_html/sites/all/modules/civicrm/CRM/Event/Form/ManageEvent/Fee.php).


When I go to the live event registration page through the parent organization or the child site site I get the following:

Notice: Undefined property: CRM_Core_Payment_FirstData::$_processorName in CRM_Event_Form_Registration->preProcess() (line 390 of /home/xxxxx/public_html/sites/all/modules/civicrm/CRM/Event/Form/Registration.php).

I'd appreciate any help. I don't know if I missed something in the CiviCRM settings file, or if what I am trying to do won't work. I did upgrade to 4.0.4 but it made no difference.

Eileen

  • Forum Godess / God
  • I’m (like) Lobo ;)
  • *****
  • Posts: 4195
  • Karma: 218
    • Fuzion
Re: Payment Processor Issues with Multi-Site/Multi-Org Install
July 24, 2011, 12:25:56 am
Those messages (that start with Notice) refer to the coding standard rather than necessarily being indicative of errors.

Drupal 7 tends to turn on E-Notice level of warnings which many parts of CiviCRM are not yet compliant with.

Sometimes E-Notice warnings can point to coding errors but with CiviCRM it's much more likely that it's just coding style issues rather than errors.

If you search the forum (or google) for E-Notice in Drupal 7 you'll see how to stop E-Notice errors from displaying.

You should of course test anyway.

In multisite the payment processors have a domain entry in the domain table

Make today the day you step up to support CiviCRM and all the amazing organisations that are using it to improve our world - http://civicrm.org/contribute

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviContribute (Moderator: Donald Lobo) »
  • Payment Processor Issues with Multi-Site/Multi-Org Install

This forum was archived on 2017-11-26.