[rt-users] AT_SiteConfig.pm not read after upgrade to AT1.2.3, RT3.6.3

[Ryan Fox]

More of an AssetTracker question than RT, but the AT list is still down, 
and this probably (hopefully?) has some parallels to RT.

After upgrading this weekend from RT3.4.4, AT1.2.1 to RT3.6.3, AT1.2.3, 
it appears that my AT_SiteConfig.pm is not being read.  Specifically, my 
custom statuses do not appear, only the default statuses do.  Also, 
default status I have marked as inactive still appear.

Permissions on the file and its parent directories look ok.  It is at 
least readable by all.

dr-xr-xr-x  3 root  wheel   512 Dec 10 18:51 .
drwxr-xr-x  3 root  wheel   512 Dec 10 18:51 ..
-r-xr-xr--  1 root  wheel  2199 Dec 13 08:33 AT_Config.pm
-r-xr-xr--  1 root  wheel   481 Jan 29 10:04 AT_SiteConfig.pm

I have attached the file in question.  Does anyone have any suggestions 
for troubleshooting this?  I'm logging debug out to file, and I don't 
see any errors related to this.

Thanks,
Ryan



-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: AT_SiteConfig.pm
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20070129/68a96cda/attachment.ksh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: rfox.vcf
Type: text/x-vcard
Size: 276 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20070129/68a96cda/attachment.vcf>