Custom fields in default contribution/membership receipt showing as "Array"

[gozer]

Is anyone else having this problem with the default contribution/membership receipts?  Any ideas what can be changed in the template to fix this?

[Donald Lobo]

1. Are you on the latest version of civi, i.e. 4.2.7?

2. Can you create a contrib / member page with a simpler and smaller profile (just name and 1 custom field)

lobo

[gozer]

We're on 4.2.6 for Wordpress.  I'll upgrade, revert to default template, and test again.

[Donald Lobo]

you might want to revert to default template and see if that works

[gozer]

I'm using the default template.

[gozer]

I've upgraded to 4.2.7.  After doing so, I reset the template back to default and tested again.  I'm still getting the same issue in the email receipts.

Seems to be the smarty array of these custom variables is not getting setup correctly.  I don't mind helping out and fixing it, but I'm having trouble finding exactly what file assigns the array.

[Donald Lobo]

can you try with a simpler profile with just a few fields and see if you can narrow down the issue that way

if you want to get into the code, you might want to read: http://book.civicrm.org/developer/ Jump on IRC if you need help getting started

thanx for looking into this

lobo

[gozer]

I appreciate your attention to this, but I have a hard time believing it has anything to do with the number or type of custom fields. 

In every other respect, there's no problem with civi collecting and storing the data in those custom fields.  I believe the issue is isolated to the routine that prepares the array of custom variables and assigns the array to smarty to be used in that particular email template and in that particular loop.  Its as if the structure of the data being retrieved from the database is different than expected.  Therefore, the routine that prepares the data is simply putting the wrong label and value pairs together.  If I just knew where in the code that array is being built, it should be a relatively quick and easy fix.

[gozer]

Any help as to where I might find the code generating that list?

Thanks,
Gary

[Donald Lobo]

check:

CRM/Event/BAO/Event.php, function sendMail

lobo

[gozer]

I found where its being assigned to the smarty template, but it doesn't make sense.  Its assigning an integer value to the smarty variable, but its obviously replaced with an array somewhere.  I'm rarely have to deal with Smarty.  Are there filters, triggers, or events that ultimately use the custom_post_id to transform the variable into an array of custom values?

CRM/Contribute/BAO/Contribution.php

Code: [Select]

$template->assign('customPost', $values['custom_post_id']);

Template code:

Code: [Select]

     {if $customPost}
      <tr>
       <th {$headerStyle}>
        {$customPost_grouptitle}
       </th>
      </tr>
      {foreach from=$customPost item=customValue key=customName}
       {if ($trackingFields and ! in_array($customName, $trackingFields)) or ! $trackingFields}
        <tr>
         <td {$labelStyle}>
          {$customName}:
         </td>
         <td {$valueStyle}>
          {$customValue}
         </td>
        </tr>
       {/if}
      {/foreach}
     {/if}


[gozer]

I also found that CRM_Contribute_BAO_ContributionPage::buildCustomDisplay is called for the customPost fields, but does nothing to produce a label-value array.  But, it seems to work for "onBehalfProfile"

[Yashodha Chaku]

gozer :

When 'On behalf of ' profile is used, the membership record is created for the Org and not the Individual,
hence it makes sense to collect the membership data in the On behalf of profile rather than custom pre/post profiles.

Since your Membership Details has all the fields of type 'Membership', I would recommend you to move all such fields to your On behalf of profile and that should fix it for you.

Hope that helps!
-Yashodha

[gozer]

I moved the fields over to the on behalf of profile and about to test.  But, now the Formatting - Free HTML fields no longer work under that profile.  They don't even appear in the HTML source.  We used that to create separate sections within the profile.

[gozer]

I also noticed that our first payment option is selected but you have to select a different payment option and then reselect the original one again for the payment fields to appear.