Back in the day, when I was doing support for Everyware, this was a very
common problem - especially with the newbies. As Witango is being not being
used by as many newbies, it would explain why we don't see this issue as
often anymore. But we all have lapses (and it gets worse as we get older);
an
I was cognitively impaired in two ways. I didn't know the push interfered with
cookie setting and I'd completely forgotten that I'd put a push on some actions
when I was debugging. So I didn't see it and didn't know it was important. I'd
spent too much time trying to come up with the conditions
Cookies are all about the HTTP header, and any TAF files which touch the
HTTP hearder, including setting cookies, cannot use any actions which are
marked "push."
Witango's "Push" is about equivalent to the flush buffer commands in other
languages; it empty's the accumulated "Results" and "pushes" i
AHA!
I'd put a push on an action when testing it. Thank you thank you.
On Nov 15, 2009, at 4:13 PM, Anthony Humphreys wrote:
> I know that any cookies won't get set when you have any actions "push"ed
> before the assignement. This is because the cookie is set in the HTTP header
> which is
I know that any cookies won't get set when you have any actions "push"ed
before the assignement. This is because the cookie is set in the HTTP header
which is sent when the first bit of HTML is sent by Witango to the browser.
You can set the cookie(s) using JavaScript at anytime you're also sending
;d like to see why this might be the case.
>
> Robert
>
> -Original Message-
> From: Roland Dumas [mailto:radu...@mac.com]
> Sent: Sunday, November 15, 2009 5:01 PM
> To: witango-t...@witango. com List
> Subject: Witango-Talk: the case of the disappearing cookie
Care to share the TAF? I'd like to see why this might be the case.
Robert
-Original Message-
From: Roland Dumas [mailto:radu...@mac.com]
Sent: Sunday, November 15, 2009 5:01 PM
To: witango-t...@witango. com List
Subject: Witango-Talk: the case of the disappearing cookie
I&#x
I could do that, but I put the assignment within conditional logic because I
don't want to set it every time.
On Nov 15, 2009, at 2:06 PM, Michael Heth wrote:
>
> On Nov 15, 2009, at 2:01 PM, Roland Dumas wrote:
>
>> just found one more clue: If an assignment is made within IF/ELSEIF/THEN
>
On Nov 15, 2009, at 2:01 PM, Roland Dumas wrote:
just found one more clue: If an assignment is made within IF/ELSEIF/
THEN logic, it expires at the completion of the taf. If it is made
outside of any conditional actions, it sets.
Anyone seen this before?
Long time back but don't remem
I'm going batty. A simple enough thing: setting a cookie. Whether I do it with
an assign action or an <@assign> tag, the following occurs
a taf with JUST the assignment works. The cookie is set. I can set it, re-set
it, change the expiry. It behaves as expected in a single step taf.
Put that a
10 matches
Mail list logo
