Hi John,
I’m using v2.2.2, here’s the current code:
<ol id="jobs">
{exp:super_search:results
channel='jobs'
redirect_post='yes'
num='10'
}
{exp:member:custom_profile_data member_id='{author_id}'}
<li{if sticky == 'y'} class="featured_job"{/if}>
{if sticky == 'y'}<h2>FEATURED JOB</h2><p>{/if}<br />
<div class="job_detail"><br /></p><h3><a href="http://{entry_id_path=job-search/job}">{title}</a></h3>
<p> {job_description}</p>
<p> <strong>{billing_company} | {job_location} | {job_pay_rate}</strong><br />
</div><!--job_detail--><br />
{if photo_url}{photo_url}{/if}<br />
<br />
</li></p>
<p>{/exp:member:custom_profile_data}</p>
<p>{/exp:super_search:results}</p>
<p></ol>
I’m already using {photo_url} which is the member’s profile photo as opposed to the avatar photo. If I’m logged out it works fine. But when a user is logged in I get the logged in users {photo_url} not the authors even if I specify the member_id in the custom_profile_data tag.
I was doing some more research and it seems you can only access custom fields when logged in, because the global member fields only show the current logged in user’s values.
I was thinking I might have to hard-code the photo_url in the entry when it’s created. I will be able to access the image but it means the images won’t be dynamic which might cause problems if a member needs to upload a new logo and nothing on the website changes.
Notes: Remember that the profile information for the current visitor to a page such as {screen_name}, {location}, {email}, etc. are always available in any template as Global Variables. Therefore, only use this tag if you need to show custom profile data (that is, fields that you have created in the Custom Profile Page) or member data for a specific user.