Kev,

Got another one for you:

When using the ACTIONS syntax, any use of the Message VariableType seems to jack up the javascript for the post back..

I have tried putting it 1st in the list, and last.. either way some of the data is not making it into the javascript post...

Here is the syntax I am using:

<a {ACTIONS,"Done",Done,Message,"Sent",state[ModuleID],Session} />Send</a>

This fires the message but doesn't set the session.

I am trying to set a Session State and then trigger a message. The reason this is important is the Query is needing to read the Session to determine what 'page' to show.

this is the preferred manor i would like to use...

<a {ACTIONS,"Sent",state[ModuleID],Session,"Done",Done,Message} />Send</a>

However, the Message is never triggered...


I have even tried the ,, syntax used in the ACTION tag...

<a {ACTIONS,"Sent",state[ModuleID],Session,"Done",Done,,Message} />Send</a>

This doesn't work either...



Any assistance here would be great...

I'll have to take a look at the ACTIONS syntax to verify. However, the problem here is most likely the missing tabid. The action format is Name,Value,TABID,Type so you would have no TABID but a empty value separating the Value and Type. ACTIONS is similar to this, except the final parameter of ACTIONS is the TABID. So - in your case you will want to assign your Session values, then raise the message like this:

<a {ACTIONS,"Sent",state[ModuleID],Session,"Done",Done,Message,} />Send</a>