CiviCRM Community Forums (archive)

I want to add something to the bottom of the contribution dashboard to show contributions (& pledges) by related contacts. I'm not sure the smarty syntax for accessing chained APIs... i.e

{crmAPI entity="relationship" action="get" var="relationships" contact_id=$contactId api_contribution_get=array('contact_id'=>2262) }

nb:: the contact_id is probably going to be '$value.contact_id_a' rather than a number. To make relationship api useful in this context I'd almost need to receive back

'cid'=>             (the id I passed in - this happens now)
'contact_id_a'   (per the table - could be either way around)
'contact_id_b'   (per the table - could be either way around)
'contact_id'       (the Other contact id - ie. the one that isn't what I passed in  - otherwise I have to compare 'cid' against ;contact_id_a & b to find this out. Could be called something different but contact_id at least would chain in nicely & then api_contribution_get would just work....

Nah it didn't work. Looks like assigning arrays within smarty templates is even more painful than I realised

http://www.hackvalue.nl/en/article/125/static%20assignment%20of%20arrays%20in%20smarty%20templates

You're determined to get me using JSON aren't you

I think that something to assist with using arrays in smarty is definitely needed. Not sure if the { brackets would cause problems? But yeah, seems like a good approach.

In the meantime I got my code working without using nesting - this is CRM/Pledge/Page/tab.extra.tpl & shows pledges from related contacts on the contact's pledge tab (have also done for user dashboard)

{crmAPI entity="relationship" action="get" var="relationships" contact_id=$contactId  }
{if $relationships.values}
{foreach from=$relationships.values item=rel}
{if $rel.is_active == 0 }
{else}
{/if}
{if $contact_id EQ $rel.contact_id_a}
{crmAPI entity="pledge" action="get" var="pledges" contact_id=$rel.contact_id_b sort='create_date DESC'}
{assign var=relatedContact value=`$rel.contact_id_b`}
{else}
 {crmAPI entity="pledge" action="get" var="pledges" contact_id=$rel.contact_id_a sort='create_date DESC'}
{assign var=relatedContact value=`$rel.contact_id_a`}
{/if}



 {if $pledges.values} 
           
            {strip}
            <div class="header-dark" id="related-pledges">
                {ts}Pledges made by Related People{/ts}:
            </div>
            <table class="selector">
                <tr class="columnheader" id='relatedcontheader'>
                    <th>{ts}Contributor{/ts}</th>
                    <th>{ts}Amount{/ts}</th>
                    <th>{ts}Contribution Type{/ts}</th>
                    <th>{ts}Start date{/ts}</th>
                    <th>{ts}Status{/ts}</th>
                    <th></th>
                </tr>
                {foreach from=$pledges.values item=row}
                    <tr id='rowid{$row.honorId}' class="{cycle values="odd-row,even-row"}">
                        <td><a href="{crmURL p="civicrm/contact/view" q="reset=1&cid=`$row.contact_id`"}" id="view_contact">{$row.display_name}</a></td>
                        <td>{$row.pledge_amount}</td>
                        <td>{$row.pledge_contribution_type}</td>
                        <td>{$row.pledge_create_date|truncate:10:''|crmDate}</td>
                        <td>{$row.pledge_status}</td>
                        <td>{if $rel.is_active EQ 0}inactive relationship{/if}</td>
                    </tr>
                {/foreach}
            </table>
            {/strip}
 {/if}


{/foreach}
{/if}

new verb? to Lobo

new verb? to Lobo

In my experience, much much more common in the passive form:

"I asked a simple question but I've been loboed to write a test unit and a blog post".
See also "patch welcomed".

X+

{crmAPI entity="relationship" action="get" var="relationships" contact_id=$contactId api_contribution_get=array('contact_id'=>2262) }

...

{crmAPI entity="relationship" action="get" var="relationships" contact_id=$contactId api_contribution_get="{'contact_id':2262}" }

So, if I'm reading correctly, the problem is that {crmAPI} accepts a flat parameter list, but we need to pass a tree of params into civicrm_api(). One approach is to treat each parameter-name as a path expression with some delimiter ("/" or "." or "-" -- note that "_" won't work because we have too many CiviCRM API symbols which use "_"). For example, if ":" is the delimiter:

{crmAPI entity="relationship" action="get" var="relationships" contact_id=$contactId api.contribution.get:contact_id=2262}

To translate the flat key-value array into a tree, you can use CRM_Utils_Array::unflatten(). However, it may be hard to find a delimiter that satisfies the naming constraints of both Smarty and CiviCRM API.

If we're willing to add an extra Smarty helper, we could do something like:

{crmAPIx entity="relationship" action="get" var="relationships" contact_id=$contactId}
    {crmAPIx entity="contribution" action="get" contact_id=2262}
    {/crmAPIx}
{/crmAPIx}

(In that snippet, "crmAPIx" needs to be a Smarty "block" instead of a Smarty "function"; it's renamed to avoid conflicting with the current crmAPI.)

[Note: Comment edited to use "crmAPIx" instead of "crmAPI".]

return="field,field,field" works.

It works because you don't have a meaningful key.

For an associative array, I'd stick with json. I't's known, got the converter to array no matter the depth, you stick it in a string and it just works, without having to find a magic separator that is going to be not available on smarty 3;)

X+

You are right, starting to look really ugly if you have to backslash everything.

blocks look like an option, have to say I really never played with them, so not sure if they are limitations with it.

Why crmAPIx ? (I mean the x as a convention for the name)

X+