Re: Witango-Talk: New WiTango Install Problem - user scope variables disappear

[Dave Machin]

Actually, I'd already done that.  In fact, here's the entry in witango.ini:   "DEFAULTSCOPE=user" - that's the right one?   Also, these variables are explicitly scoped as 'user' scope - plus, the problem is intermittent and doesn't happen all the time. ----- Original Message ----- From: [EMAIL PROTECTED] To: Multiple recipients of list witango-talk Sent: Wednesday, November 20, 2002 5:16 PM Subject: Re: Witango-Talk: New WiTango Install Problem - user scope variables disappear Your default Scope is setting to "request" Change it in the "witango.ini" to "User": DEFAULTSCOPE=user Then it works fine - after restarting the Server...   mit freundlichen Gr��en, with best regards   Daniel Richardy   ________         European Witango Distributor       __________   SoftDes GmbH - St. Georgener Strasse 13 - D 79111 Freiburg Web: www.softdes.de                    Mail:  [EMAIL PROTECTED] Phone: +49 - 761 - 4 555 666         Fax: +49 - 761 - 4 555 660 _________________ www.witango.net  ___________________ ----- Original Message ----- From: Dave Machin To: Multiple recipients of list witango-talk Sent: Thursday, November 21, 2002 12:39 AM Subject: Witango-Talk: New WiTango Install Problem - user scope variables disappear I'm running a new install of WiTango 5 and am having a strange intermittent problem.   Every now and then the user scope variables seem to disappear and the page does not function correctly.  If I refresh they will often reappear.  I haven't really found any rhyme or reason for when this happens.   Here is a WiTango Debug portion of the page when it works correctly:   [Application File] [176] START /ebay/survey.taf Witango_Server_5 _function=nextq A1=1 c_Scale_Boolean=0 Next_Q_id=2 Previous_Q_id=1 Submit=Next Total Length of Postargs: 62  [user$ Vars] [177] DaveNextQ=1; variableTimeout=30; Seperated_string_array=; No_Q_Left=0; MSCF=[Object: 0217FDC8]; Survey_id=172; aPrefix=<TABLE BORDER="0">; Survey_idExists=1; User_id=-3927; starting_question=1;  [If Action] [177] If_survey_has_started  [Results Action] [177] All_pages_header   When the page fails the top of the debug looks like this:   [Application File] [185] START /ebay/survey.taf Witango_Server_5 _function=nextq A1=1 c_Scale_Boolean=0 Next_Q_id=2 Previous_Q_id=1 Submit=Next Total Length of Postargs: 62  [If Action] [185] If_survey_has_started  [Else Action] [186] Else_innit_and_start_the_survey   Notice that the [user$ Vars] section is missing?  Those variables don't seem to exist all of a sudden and the page misbehaves.   We've been running Tango 2000 on this machine (W2000 Server service pack 3) just fine - this just started happening with the upgrade.  I did change the default scope for variables from 'request' to 'user' to be backward compatible with existing .tafs.  I also still have Tango 2000 installed on the machine (I've had to switch back).   Any ideas? Dave Machin