OK I had posted a scathing post in the Workflow forum this morning only to realize it was my own **** fault - once again. This 6.1 upgrade is killing me. Here's the story, and this might be useful to some other people who tend to do stupid things like me.
In 6.1 they made these swell new special paths where you can put your custom perl modules so that when upgrades occur, they won't get overwritten by the upgrade. Cool eh? Not so fast.
Originally I had all my custom modules in the same place as the TeamSite specific modules (.../iw-home/iw-perl/lib/perl5/site_perl/5.005/TeamSite), so whenever I referenced one of my modules (say NikeUtils.pm) I would do it like this in my code:
use
TeamSite::NikeUtils;
Simple enough. But now with these swell new paths, I no longer need the
TeamSite:: part in my use statements. Well I do this friggin' everywhere. So I had to go through and remove that
TeamSite:: part from every **** script I have. Otherwise the script barfs because it can't find the module. I know what you're thinking. Why not just put a TeamSIte directory in my swell new path and put my custom modules underneath that so I didn't have to change anything? That's bush league, in my opinion. So I am in the process of going through every one of my scripts and fixing this one line.
I forgot that my template based email .tpl files have perl embedded and reference my module - which is why I thought template based email didn't work in 6.1. Once I fixed my use statement it worked and I deleted my scathing post.
So anyway, be aware of this if you do things the same way I did. If not, thanks so much for reading this useless nonsense. Don't you have anything better to do?
Dave SmithSr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com
