cfwindow and coldbox

I think I know the answer to this, but when calling events with SeS url’s in the source attribute of the cfwindow. It seems to add extra url params.

Is there or does anyone know how to use coldbox with this?

Just using the standard cfwindow tag, not via JS. But if it is easier in JS, any examples?

Hi Andrew,

Please would you explain a bit more, which additional params for

I just tried as following (my test App have SES turned on)

<cfwindow source="/dspbloglist"> (SES route)

<cfwindow source="/index.cfm?event=ehblog.dspbloglist"> (standard way
calling a specific event)

its works for me.


It might be something to do with my courses, but this will not call the
correct handler. In fact no handler is called.

<cfwindow source="/index.cfm/handler/action/id"> (SES route)

However this works fine...

<cfwindow source=" index.cfm?event=#handler#&action=#action#&id=#id#"> (none
SES route)

I am also having another issue with caching. I think it is caching.

I have an event that is layout->view->view with a cfwindow in that view, the
window opens fine, and sends fine (well not SeS though) however when I
destroy() the cfwindow and try to recreate it.

It caches the result page, yet the views are told not to cache.

Any ideas?


This has nothing to do with the ColdBox cache, but with the CFWindow tag.
CFWindow tag (js) caches the page.....

Here, someone else with the same problem:

didn't read the link so maybe it's addressed in there, but you can get
rid of the cache behavior by passing refreshOnShow=true

That's what I was looking for, but it doesn't work.

As for the other guy, what he was referring to is that when a window is
created. If it is hidden, the location size etc. Is still held in its
object, hence when you show it again it shows exactly has it was when

Now I stated that I destroy the window, hence the issue the other guy was
having is not an issue with me. I am at a loss to explain this, I know it
has something to do with refreshOnShow as that is how I do it in extJS. But
when I looked at the extJS1.1 docs, I couldn't see that as a config option.

I know I am missing something, just don't know what it is.

Maybe you're looking for this:

    <meta http-equiv="expires" content="Mon, 06 Jan 1991 00:00:01 GMT">
    <meta http-equiv="pragma" content="no-cache">
    <meta http-equiv="cache-control" content="no-cache">

Already have that in my code as well.

If anyone is interested, no it wasn't a Coldbox cache error, nor was it
really a Coldfusion one either. The problem lied in the destroy function for
the window. I missed the second element, which I would have thought
defaulted to true.

Which it didn't :frowning: