On 10/09/2012 09:35 AM, Ronald Kimball wrote:
Can you provide a self-contained set of Perl and TT files (perhaps reduced from your actual code) to reproduce this issue? Ronald
I can't believe it. I fixed it. And now I know why (at least part of why) the problem even exists. Just for giggles, I changed the variable name from 'shifts' to 'hours' that was passed to the template. And lo and behold! There it was. All my variable data. Now, I'm not entirely sure why, but it could be that 'shift', being a reserved perl word was being processed rather than used a varname.
I did have a set of code in the template that was FOREACH shift in shifts, but that didn't seem to affect getting the variable data to it. Is here some sort of deal in perl that could cause this with shift? Keep in mind, the variable has ALWAYS been shifts with an s. Honestly, it's the only thing I can think of that would possibly cause the problem.
-- 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
