jjk697

Hi,

This is a bug. It’s because in the admin manual payment file, a php array is treated as an object. To fix it, go into the file:

payments/evr_admin_payments-post.php (around line 80… not exactly sure as I’ve heavily modified my files) and change this block of code:

$ReplaceValues = array($payment_dtl->payer_id, $payment_dtl->first_name,$payment_dtl->last_name,$payment_dtl->payer_email,stripslashes($event_dtl->event_name), $company_options['company_email'], $payment_link, $payment_dtl->mc_gross, $payment_dtl->txn_id, $payment_dtl->txn_type,$payment_dtl->address_street, $payment_dtl->address_city, $payment_dtl->address_state,$payment_dtl->address_zip,$payment_dtl->address_country, $event_dtl->start_date, $event_dtl->start_time,$event_dtl->end_date,$event_dtl->end_time);

to this

$ReplaceValues = array($payment_dtl['payer_id'], $payment_dtl['first_name'], $payment_dtl['last_name'],$payment_dtl['payer_email'], stripslashes($event_dtl->event_name), $company_options['company_email'], $payment_link, $payment_dtl['mc_gross'], $payment_dtl['txn_id'], $payment_dtl['txn_type'], $payment_dtl['address_street'], $payment_dtl['address_city'], $payment_dtl['address_state'], $payment_dtl['address_zip'], $payment_dtl['address_country'], $event_dtl->start_date, $event_dtl->start_time, $event_dtl->end_date, $event_dtl->end_time);

Note that the event_dtl elements don’t need to be changed, as they are php objects. While you’re in there also change the line a few above it to:

$payment_link = evr_permalink($company_options['return_url']). "id=".$payment_dtl['payer_id']."&fname=".$payment_dtl['first_name'];

to fix the same error. Then also update payments/evr_admin_payments-update.php for the same two bugs.

There are several places in the code, for example in

public/evr_public-confirmation.php and
evr_ipn.php

where the “From” field for the email headers is set to $company_options[‘company’] which is not a field in the database. Rather it should be $company_options[‘company_name’]. It’s minor because it only affects the From field in the emails sent out, but it’s an easy fix.

This is intentional. I think there’s a little confusion over the use of “Attendee.” The person who signs up will always be primary on the registration. The true “attendees” of the event are listed under that person’s name in the database in the serialized “attendees” field.

It would be productive to think of the person’s name who signs in with name and address etc. as the Registrant (that’s how I’ve relabeled the order forms, etc. for my page). You could send a confirmation email with the attendees listed, but it would take modifying the code. It is meant to go to the registrant since presumably they paid.