>Well as far as I'm aware it's been this way since the release of >ColdFusion MX and I'd be surprised if they changed it in 7 -- I think >it was actually intentional... the reason being that if you were to >use <cfinclude> or <cfmodule> inside of a function created with the ><cffunction> tag, the relative path to the included template or module >must be relative to the template containing the <cffunction> tag. I >personally still think getCurrentTemplatePath() should return the path >to the currently executing template (instead of the function >template), but I suspect relative paths for cfinclude / cfmodule have >something to do with why it produces that result. > >At this point there's a fair amount of code in use which observes the >difference, so "fixing" it would require many of us to modify our >existing code to check the version of CF to determine behavior. I >would be okay with that (although I might not like it), though some >people might be miffed. > >Actually I take that back -- if by "fixing" you mean making it always >return the path to the template in which the function is declared (not >called), then I'd be pretty royally upset over it -- because I can't >think of another way to generate that information (which is vitally >important to my code) if the behavior were changed in that direction.
Ha, okay, I'll let it be. I'll settle for fixing the documentation, instead. ;-) Thanks, Jamie ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Discover CFTicket - The leading ColdFusion Help Desk and Trouble Ticket application http://www.houseoffusion.com/banners/view.cfm?bannerid=48 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:202608 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
