Do you re-use any of those variable names anywhere else in your template or in an another template that gets included by it or generated by the same perl script? I've found that variable name re-use can sometimes lead to weird things like this (and I ended up adding code on the perl side to unset things).
-jesse On Oct 9, 2012, at 12:05 PM, Mark Haney <ma...@abemblem.com> wrote: > On 10/09/2012 11:31 AM, Ronald Kimball wrote: > >> >> I would guess that the problem was not with the variable named 'shifts', >> but with the variable named 'shift'. Without being able to see your >> actual template, it is difficult to say exactly what was happening. >> >> Ronald > > I can assure you that I kept the word 'shift' in the FOREACH loop. The only > thing I changed was the variable that was being passed to the template. In > fact, I just ran it again to double check. Still no errors. > > > -- > > Mark Haney > Software Developer/Consultant > AB Emblem > ma...@abemblem.com > Linux marius.homelinux.org 3.5.1-1.fc17.x86_64 GNU/Linux > > _______________________________________________ > templates mailing list > templates@template-toolkit.org > http://mail.template-toolkit.org/mailman/listinfo/templates _______________________________________________ templates mailing list templates@template-toolkit.org http://mail.template-toolkit.org/mailman/listinfo/templates