Comments on: Getting the Expected Results for GetCurrentTemplatePath() in a Custom Tag. http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/ Exploring Life Through Math, Algorithms and Code Mon, 30 Aug 2010 20:08:05 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Tweets that mention Getting the Expected Results for GetCurrentTemplatePath() in a Custom Tag. - Elliott's Development Blog -- Topsy.com http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/comment-page-1/#comment-16404 Tweets that mention Getting the Expected Results for GetCurrentTemplatePath() in a Custom Tag. - Elliott's Development Blog -- Topsy.com Wed, 28 Apr 2010 02:37:45 +0000 http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/#comment-16404 [...] This post was mentioned on Twitter by aanooj. aanooj said: @aanooj Getting the Expected Results for GetCurrentTemplatePath() in a Custom Tag. - Elliott's Development Blog: http://bit.ly/cmPArO [...] [...] This post was mentioned on Twitter by aanooj. aanooj said: @aanooj Getting the Expected Results for GetCurrentTemplatePath() in a Custom Tag. – Elliott's Development Blog: http://bit.ly/cmPArO [...]

]]> By: Steve Bryant http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/comment-page-1/#comment-16236 Steve Bryant Fri, 15 Jan 2010 21:23:28 +0000 http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/#comment-16236 This is really nice! This solves a small issue that I have been having for some time. Thanks Elliott (and Ben for linking to it)! This is really nice! This solves a small issue that I have been having for some time.

Thanks Elliott (and Ben for linking to it)!

]]> By: Ben Nadel http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/comment-page-1/#comment-16219 Ben Nadel Thu, 14 Jan 2010 15:08:02 +0000 http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/#comment-16219 Elliott, I know it's been like 2 years since this blog post; but, I just used it in a new and (what I think) exciting way: http://www.bennadel.com/blog/1813-Invoking-A-ColdFusion-Function-With-A-Closure-Like-CALLER-Based-Variable-Binding.htm Elliott, I know it’s been like 2 years since this blog post; but, I just used it in a new and (what I think) exciting way:

http://www.bennadel.com/blog/1813-Invoking-A-ColdFusion-Function-With-A-Closure-Like-CALLER-Based-Variable-Binding.htm

]]> By: Gary Gilbert http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/comment-page-1/#comment-16113 Gary Gilbert Fri, 21 Nov 2008 12:37:04 +0000 http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/#comment-16113 I blogged about something similar to this back in February but dealing with functions in components calling a function in another component. http://www.garyrgilbert.com/blog/index.cfm/2008/2/4/What-Function-Called-My-Function But your solution is a lot more elegant and you don't need to artificially throw an error to get it. I blogged about something similar to this back in February but dealing with functions in components calling a function in another component.

http://www.garyrgilbert.com/blog/index.cfm/2008/2/4/What-Function-Called-My-Function

But your solution is a lot more elegant and you don’t need to artificially throw an error to get it.

]]> By: Vid http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/comment-page-1/#comment-16111 Vid Fri, 22 Aug 2008 02:43:39 +0000 http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/#comment-16111 Very nice. It works in CF8 on IIS too. I've had to rely on CGI.PATH_TRANSLATED in the past. Very nice.
It works in CF8 on IIS too.
I’ve had to rely on CGI.PATH_TRANSLATED in the past.

]]> By: Ben Nadel http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/comment-page-1/#comment-10347 Ben Nadel Thu, 24 Apr 2008 13:50:28 +0000 http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/#comment-10347 @Elliot, Any ideas on how to get the Page object of the calling template from within a CFC? I am trying to get at the internal functions, which are available via: GetPageContext().GetPage() Ex. GetPageContext().GetPage().ImageBlur() However, these seem to only be available from a CFM page, not a CFC. In the CFC, the GetPage() object does not have these built-in CF functions. I need to access "ImageBlur()" in a dynamic way from within a CFC (otherwise I would just call the built-in method directly). Thanks. @Elliot,

Any ideas on how to get the Page object of the calling template from within a CFC? I am trying to get at the internal functions, which are available via:

GetPageContext().GetPage()

Ex.

GetPageContext().GetPage().ImageBlur()

However, these seem to only be available from a CFM page, not a CFC. In the CFC, the GetPage() object does not have these built-in CF functions.

I need to access “ImageBlur()” in a dynamic way from within a CFC (otherwise I would just call the built-in method directly).

Thanks.

]]> By: Elliott http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/comment-page-1/#comment-5611 Elliott Fri, 11 Jan 2008 10:22:56 +0000 http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/#comment-5611 Ben, To be honest I'm not sure. I assume you mean like if you cfinclude the other template? Or do you mean cfcs? I'll dig around in there to see where that information comes from. Ben,
To be honest I’m not sure. I assume you mean like if you cfinclude the other template? Or do you mean cfcs?

I’ll dig around in there to see where that information comes from.

]]> By: Ben Nadel http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/comment-page-1/#comment-5583 Ben Nadel Thu, 10 Jan 2008 13:05:19 +0000 http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/#comment-5583 Elliott, I know we haven't touched on this in a while, but someone asked me a related question. With a custom tag, you can easily grab the context of the calling template using the CALLER scope. However, do you know if there is anything in the page context that gives that information such that it can be used from template to template without custom tags? Is there any sense of "caller" stored in the page context itself? Elliott,

I know we haven’t touched on this in a while, but someone asked me a related question. With a custom tag, you can easily grab the context of the calling template using the CALLER scope. However, do you know if there is anything in the page context that gives that information such that it can be used from template to template without custom tags?

Is there any sense of “caller” stored in the page context itself?

]]> By: Ben Nadel http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/comment-page-1/#comment-466 Ben Nadel Tue, 17 Jul 2007 21:56:00 +0000 http://www.elliottsprehn.com/blog/2007/07/17/getting-the-expected-results-for-getcurrenttemplatepath-in-a-custom-tag/#comment-466 Elliott, This is cool stuff. Just the other day, I also saw someone mess around with the ... oh wait, I just checked and that was YOU also :) Dang, you really get this PageContext structure. Elliott,

This is cool stuff. Just the other day, I also saw someone mess around with the … oh wait, I just checked and that was YOU also :) Dang, you really get this PageContext structure.

]]>