On Tue, Oct 9, 2012 at 10:49 AM, Mark Haney <[email protected]> wrote:
> 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. 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
_______________________________________________ templates mailing list [email protected] http://mail.template-toolkit.org/mailman/listinfo/templates
