CiviCRM Community Forums (archive)

We're using civicrm 3.3.5 on Drupal for an event.  The event is paid, and punches out to Paypal Standard. We're using default system messages for events. We're having great success with civi as usual, with one issue that I wanted to raise.
 
I've noticed that when we use pay later, the emailed receipt (HTML) looks perfect.
When we punch out to paypal, however, the receipt has two content errors:

Error #1.   The fees are is a blob of text and the receipt doesn't show the price labels.  The appear in one line:
$ 240.00 Adult (solo) - basic housing -  No - $ 0.00  No - $ 0.00 -
i.e. it's not clear that "No" refers to bus options.

where as it looks the following this when we choose pay later - it's a nicely formatted table.  Note that it includes the Item, Qty, Each Columns:

Item    Qty    Each    Total
Retreat Price - Adult (solo) - basic housing - $ 240.00  Adult (solo) - basic housing     1    $240.00    $ 0.00
Bus to retreat from NYC - No - $ 0.00           1    $ 0.00    $ 0.00
Bus to NYC from retreat - No - $ 0.00        1    $ 0.00    $ 0.00
Total Amount    $240
 
Error 2. The other strange thing is that when we punch out to paypal, the profiles shown in the email are wrong.  We use two profiles for each of the primary participant and secondary participants.  When we punch out to paypal, the receipt shows the profiles for the secondary participant on the primary participant's confirmation email, even if the primary selected to sign up only 1 participant - him or herself. In other words, the additional participant shouldn't be referenced at all in the receipt.

If the user chooses pay later, it works as expected - the primary participant profile is rendered.

--
The data in the civi admin views appears to be correct.  It reflects all of the fields filled in by the users that are present in the primary profile.

As a side note, we recently added the http://drupal.org/project/civievent_discount module to our instance (though this receipt issue is happening with this module enabled or disabled).  I wanted to try to see if the correct behavior was related to pay now vs. pay later.  Using the event discount module, I created a 100% discount and checked out completely as an end user, registering for the event, but avoiding paypal and avoiding selecting pay later.    In that case, the receipt rendered correctly.

Any suggestions, ideas, requests for additional information etc. would be much appreciated.

Thanks,

Aaron