Thread

I’m working on a site that’s been around for a few months. I just added a new field (called branch_spanish) to the Branch weblog type. When I try to display it in a template (using {branch_spanish} then it just displays that (i.e., just “{branch_spanish}”) rather than what’s actually entered for the field.

I know this is the expected behavior for when the field with that name doesn’t exist, but I’ve verified that that name is correct and I’m calling it in exp:weblog:entries for the correct weblog type).

Any ideas on where I could look for answers? I’ve already flushed caches, which is the only thing I could think of.

Thanks in advance for any help.

can you post your template code here? You’re sure that {branch_spanish} is in the {exp:weblog:entries} tags, right?

The actual template is very long (since it’s doing a zip code proximity search), but here’s the relevant part:

{exp:weblog:entries weblog="branch" entry_id="<?php echo $entry; ?>" limit="1" show_future_entries="yes" show_expired="yes" dynamic="off" disable="categories|member_data|pagination|trackbacks"}
    <li><a href="http://{title_permalink=locations/branch}" title="{title}">{title}</a> <?php echo "(" . round($distance, 1) . " miles)"; ?>

        {branch_address}

        {branch_city}, {branch_state} {branch_zipcode}

        <strong>P:</strong> {branch_phone}
        
{branch_spanish}
    </li>
{/exp:weblog:entries}

If you need to see the full template, see http://pastie.org/867462

Thanks!

Just so I’m sure I understand…

You have a weblog called “branch”
You also have a custom field group associated with that weblog, right?
and you added a new custom field {branch_spanish} to that same custom field group.

And the branch_spanish entry field is appearing just fine in the publish/edit pages…

Is this all correct?

@julie, yep, that’s all 100% correct. I can provide screenshots of anything if that’s helpful.

I’d be happy to take a look-see if you want to PM me a temp user/pass. I had this problem once, and I remember there were some extra spaces either in the template or the field names. I can’t remember exactly but I’d be happy to take a quick look…

Sent! Thanks so much.

I stripped out just the relevant code and put it in a new template for you. That field renders correctly out of the complicated template… so I’d start slowly adding info back in to see what breaks it…

oh - pm’d you the template name/location…

Julie, thanks a lot for the help. With what you did, I was able to narrow it down to that specific template. I can literally have the exact same template code in that template and the one you set up, and yours works and that one doesn’t. I also made sure that the options for both were the same.

Any ideas? I’m trying to see if the developer had any template specific code anywhere that would prevent a field from rendering in that template, but I can’t find anything.

and you changed the search form to submit to the sample template? If so, I’d try a select-all copy/paste and see if that fixes it. Otherwise, delete the old template, create a new one as a duplicate from the temp (if you want meaningful template names, of course!)

Figured it out. Unchecking “Cache SQL Queries” solved it, even though I had been flushing all caches all along. Thanks for all your help!

congrats!