Re: Stack overflow in self nested custom tag

2010-03-09 Thread Dave Watts
I'm using CF7.02 and I'm trying to create a custom tag that will be self nested, like:-     cf_ct1          cf_ct2               cf_ct2               /cf_ct2          /cf_ct2     /cf_ct1 And in cf_ct2, I'm trying to get the data of the parent tag and assigning to a variable in the

Re: Stack overflow in self nested custom tag

2010-03-09 Thread Chris Velevitch
On Wed, Mar 10, 2010 at 02:31, Dave Watts dwa...@figleaf.com wrote: Instead of having the processing done in the child tags, you can simply pass the data from those tags back to the parent tag during its end execution mode, using the CFASSOCIATE tag. This will let you do things that are a bit

Re: Stack overflow in self nested custom tag

2010-03-09 Thread Dave Watts
Doesn't that depend on what you're trying to achieved? I can image that's a good solution for simple nesting of tags, but not for highly complex nesting of an indeterminate number of different child tags, child of child tags and recursive nesting. No, actually, I find it easier especially in

Stack overflow in self nested custom tag

2010-03-08 Thread Chris Velevitch
I'm using CF7.02 and I'm trying to create a custom tag that will be self nested, like:- cf_ct1 cf_ct2 cf_ct2 /cf_ct2 /cf_ct2 /cf_ct1 And in cf_ct2, I'm trying to get the data of the parent tag and assigning to a variable in the current

Re: Stack overflow in self nested custom tag

2010-03-08 Thread Barney Boisvert
I haven't tested this, but I'd imagine that the CURRENT tag is on the tag stack (as it is with exceptions). Since getBaseTagData operates on names rather than offsets/indexes, it's going to match the current tag, and then return it's own data. So lvData is pointing at one of it's own scopes,

Re: Stack overflow in self nested custom tag

2010-03-08 Thread Chris Velevitch
On Tue, Mar 9, 2010 at 18:18, Barney Boisvert bboisv...@gmail.com wrote: I haven't tested this, but I'd imagine that the CURRENT tag is on the tag stack (as it is with exceptions).  Since getBaseTagData operates on names rather than offsets/indexes, it's going to match the current tag, and