I’ve found what appears to be a bug in the CBWIRE interceptor that causes WireBox’s afterInstanceCreation event chain to break during CBWire AJAX requests, preventing other WireBox lifecycle modules (like Mementifier) from running.
The problem
In interceptors/CBWIRE.cfc, there is this interceptor:
function afterInstanceCreation() eventPattern="^cbwire.*" {
return true;
}
During a CBWire AJAX request, the current ColdBox event is cbwire:Main.index, which matches the pattern ^cbwire.*. When any object is created via wirebox.getInstance() during that
request, WireBox fires afterInstanceCreation. This interceptor runs and returns true, which breaks the interceptor chain — preventing any subsequent listeners from executing.
Why this is a problem
afterInstanceCreation is a WireBox object creation event, not a ColdBox request lifecycle event. Unlike preProcess, postEvent, etc. (where blocking the chain makes sense to protect
CBWire’s request handling), afterInstanceCreation fires for every object WireBox creates, regardless of context.
The side effect is that modules like Mementifier, which rely on afterInstanceCreation to mix getMemento() into CFCs at creation time, stop working entirely when objects are created
during a CBWire AJAX request. Calling getMemento() on those objects results in a “method not found” error.
Is there an intentional reason for afterInstanceCreation to break the chain?
The other interceptors with return true make sense (protecting the CBWire request pipeline), but I can’t think of a reason why CBWire would need to prevent WireBox object creation events from propagating.
Thanks!