Details
Details
Assignee
Michael Offner
Michael OffnerReporter
Ben Nadel
Ben NadelPriority
Labels
New Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Affects versions
Created 25 September 2021 at 09:57
Updated 29 September 2021 at 13:20
This is a strange one, so I am not exactly sure how to word it. It appears that using
caller.thread
to assign a value to thethread
scope from within a custom tag corrupts the `thread` scope, moving it out of the thread context and into thevariables
scope. Reproducing it is quite easy.Imagine this custom tag -
MyTag.cfm
:All it is trying to do is assign a value to the
thread
scope from within the custom tag context.Now, let’s consume this custom tag from within a thread:
Notice that in our thread body we’re making two
thread
scope assignments, one before, one after the custom tag invocation. Now, if we run this, we get the following:Super weird, right?!
And, If I remove the custom tag call, both
thread
scope assignments go back to the correct place.