>>"The current page" refers to the currently processing template. In other words, the included template that is currently processing.
Yes, this sounds logical; the problem is when there is another include inside the first include. Logically, the included code is executed like if it was inside the including code, not the included template. Everything works like if the code is included FIRST, then executed from the including template, not the contrary. Then it looks illogical to me that the address of the second level include is calculated relatively to the place the included code was BEFAORE it was included and executed. It should be calculated relatively to the first template that declares the first level include. >>want to use <cfinclude> in a template, you use the relative path to the one that you want to include, based upon the location of the file that you are writing the <cfinclude> That's the problem: the first level include is made for a template in a mapping. Then it is not possible to call the second include relatively. I solved the problem by calculating the actual path from variables. -- _______________________________________ REUSE CODE! Use custom tags; See http://www.contentbox.com/claude/customtags/tagstore.cfm (Please send any spam to this address: [EMAIL PROTECTED]) Thanks. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting, up-to-date ColdFusion information by your peers, delivered to your door four times a year. http://www.fusionauthority.com/quarterly Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:259571 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4
