Oh this is tricky!!! Make sure you <@SETCOOKIES><@USERREFERENCECOOKIE> in local$httpHeader!!!
>Nope, that was the *other* problem, with the user. > >This problem (with the misbehaving links after file actions) is >everywhere. > >I tried resetting the local$httpHeader in a Results page just after the >branch to the WriteFile.taf - doesn't work. It's branching back >*before* it opens the file (i.e., if I reset the httpHeader, the results >display as html rather than causing a File Download). That explains why >I get garbage in the file from actions after the branch. > >There's some problem with the browser losing its reference. If I click >"back" after the links get hung up, they will work again, but open a new >browser window. > >If I target the href links for the report to a new window, the links in >the main window are OK. So one possible workaround is to retarget all >the report links. That leaves a blank browser window hanging open; I'm >thinking I could probably find some javascript to fix that. > >I'm starting to wonder if this may have something to do with that >%^@#$!&*!! inline frame. The links within the inline frame have always >continued to work, just not those in the menu outside the inline frame. >I've got other problems with that setup, too (e.g., I can't get the left >& right menus to refresh when changes are made in the center pane inline >frame). I don't use frames, so I'm not sure what will happen if I >change it from a page with inline frame to a three-frame page, but I'm >thinking about giving it a whirl. > >I'm off to do some research on frames and javascript. > >Thanks very much for all the ideas and information. It's certainly been >a learning experience! > > > >> -----Original Message----- >> From: Scott Cadillac [mailto:[EMAIL PROTECTED]] >> Sent: Friday, February 07, 2003 12:41 PM >> To: [EMAIL PROTECTED] >> Subject: Re: Witango-Talk: Hanging after Write (was User Woes) >> >> >> Hi Jamileh, >> >> Nobody else is having this problem, and this is MSIE right? I >> use MSIE exclusively for all my applications (can't you tell >> :-) and so in my experience, every once-in-a-while I have >> discovered that the rendering engine of MSIE can become >> corrupt and requires a complete re-install or upgrade. >> >> This is usually due to the user installing some "crap" >> software from the internet. Didn't you say this guy was a >> developer wannbe? >> >> Good luck. Cheers.... >> >> ----- Original Message ----- >> From: "Wilcox, Jamileh" <[EMAIL PROTECTED]> >> To: <[EMAIL PROTECTED]> >> Sent: Friday, February 07, 2003 10:51 AM >> Subject: RE: Witango-Talk: Hanging after Write (was User Woes) >> >> >> OK, two more clues: >> >> It's definitely clicking the Save button that causes the >> problem; links quit working even if I cancel and don't save the file. >> >> Since the center section (where the reports list displays) is >> an inline frame, when I click the browser Refresh button, it >> resets both menus and the center pane. The center section >> returns to the initial page as if I were just entering the >> website from login (so if I'm on a form, that disappears and >> the 'welcome' page shows). That fixes the links. >> >> If I right-click Refresh just in the center pane section, it >> doesn't reset the whole page; just that pane resets and only >> to the current file (so the same form is still displayed, but >> all data-entry is erased). However, it still fixes the links. >> >> >> There must be something that's not resetting after the file >> write/read/delete operations, something that's preventing >> standard browser operation. I just don't know how to figure >> out what it is. >> >> >> >> > -----Original Message----- >> > From: Wilcox, Jamileh >> > Sent: Friday, February 07, 2003 11:42 AM >> > To: '[EMAIL PROTECTED]' >> > Subject: RE: Witango-Talk: Hanging after Write (was User Woes) >> > >> > >> > >> > >> > I've got the purgecache working in the WriteFile.taf. >> However, when it >> > returns from branching, unless I have a Return after the branch, it >> > picks up the following HTML in the Reports.taf and appends >> it to the >> > file. If I try to put the purge in the Reports.taf, it causes all >> > sorts of problems, such as disappearing the initial >> report-selection >> > html. >> > >> > Is there some possibility that I need to reset the >> httpHeader info in >> > the initial file (Reports.taf) after the branch returns >> from the other >> > file (Write.taf)? If so, to what? >> > >> > Could that cause this strange problem with href links that don't >> > work?? >> > >> > Thanks. j >> > >> > >> > > -----Original Message----- >> > > From: Scott Cadillac [mailto:[EMAIL PROTECTED]] >> > > Sent: Thursday, February 06, 2003 5:52 PM >> > > To: [EMAIL PROTECTED] >> > > Subject: Re: Witango-Talk: User Woes >> > > >> > > >> > > Hi Jamileh, >> > > >> > > Here's a tip that is usually helpful: >> > > >> > > In most versions of MSIE, using the "Refresh" button from the >> > > toolbar triggers MSIE to reload the latest 'cached' >> content from the >> > > "Temporary Internet Files" folder on the user's computer. >> Typically >> > > MSIE will determine cache rules on it's own and usually errors on >> > > the side of caution and cache things longer than usual. >> > > >> > > But....if you right-click on your page and choose >> "Refresh" from the >> > > popup context menu, it will usually override this and get >> the latest >> > > content (that has not expired yet) from your LAN proxy >> cache (if you >> > > have one). I find this a bit more helpful, because most >> proxies will >> > > expire content when they are supposed to. >> > > >> > > Learning everything you can about expiring your TAF >> output via the >> > > Local$httpHeader is very important with dynamic >> > applications. >> > > >> > > >> > > As for your CSV thing, try putting the <@assign name="httpHeader" >> > > .....> tag on the very first line of the last Results >> Window in your >> > > TAF - and on the same line put <@PURGERESULTS> and your >> CSV output >> > > variable afterwards. This will eliminate any garbage spaces and >> > > such. >> > > >> > > Oh, and turn debugging off in the file. >> > > >> > > Hope this helps. Cheers..... >> > > >> > > >> > > ----- Original Message ----- >> > > From: "Wilcox, Jamileh" <[EMAIL PROTECTED]> >> > > To: <[EMAIL PROTECTED]> >> > > Sent: Thursday, February 06, 2003 3:37 PM >> > > Subject: RE: Witango-Talk: User Woes >> > > >> > > >> > > Phil - would having him hit Refresh in his browser do the same >> > > thing? (That would be easier over the phone than changing IE >> > > settings). >> > > >> > > On the csv problem, in the WriteFile.taf, I'm doing this: >> > > >> > > <@assign name="httpHeader" scope="local" >> value="Content-Type: <@var >> > > local$filetype><@crlf>Content-Disposition: attachment; >> > > filename=<@dq><@var >> > > local$IncomingRFName><@dq><@crlf><@userreferencecookie><@crlf>"> >> > > >> > > >> > > Thank you!! >> > > >> > > >> > > > -----Original Message----- >> > > > From: Phil Wade [mailto:[EMAIL PROTECTED]] >> > > > Sent: Thursday, February 06, 2003 4:23 PM >> > > > To: [EMAIL PROTECTED] >> > > > Subject: Re: Witango-Talk: User Woes >> > > > >> > > > >> > > > Jamileh, >> > > > Try turning the cache in IE to check for changes "every >> > > visit to the >> > > > page". This is in the settings of "Temporary Internet >> files". IE >> > > > defaults to automatic, but it has been my experience that >> > > with highly >> > > > dynamic sites, IE does not always see changes to pages >> > > immediately if >> > > > set to automatic. Your system may be logging him on and >> > > the browser >> > > > is returning the error that is now cached in his >> browser. You can >> > > > also control this on the server by expiring the content faster. >> > > > >> > > > With your csv issue, are you modifying the http header? >> > > > >> > > > Phil >> > > > >> > > > On 7/2/03 9:12 AM, "Wilcox, Jamileh" >> > > <[EMAIL PROTECTED]> wrote: >> > > > >> > > > > Another oddball case (it's one of THOSE days). >> > > > > >> > > > > I've got a user (PC technician) who swears he gets an >> > > > "invalid login" >> > > > > message when he puts his username into this application, >> > > > even at the >> > > > > 'forgot password' prompt. I can put in his username and >> > > > password and >> > > > > get logged in just fine; the app mailed him a new >> > password when I >> > > > > tried the 'forgot password' with his username. >> > > > > >> > > > > He also swears that he's cutting and pasting the >> > username & reset >> > > > > password directly from the email, which is what I'm doing. >> > > > Of course, >> > > > > he was typing the info in when I was on the phone with him. >> > > > > >> > > > > I've been on the phone with him, and he's been very >> helpful. He >> > > > > thinks maybe it's named pipes in SQL, or cookies in his >> > > browser, or >> > > > > because the browser is sending his username as a token to >> > > > the server, >> > > > > or ... (he's learning Cold Fusion, can you tell?) >> > > > > >> > > > > Can anyone think of *any* possibility that I should check >> > > > before I go >> > > > > across campus to his office and cut & paste the >> %#$^~! fields in >> > > > > myself? I'm not very familiar with the logs, but I don't >> > > > see anything >> > > > > in them that would even touch on this. >> > > > > >> > > > > Thanks. j >> > > > > >> > > > > >> > > > >> > > >> > >> ______________________________________________________________________ >> > > > > __ >> > > > > TO UNSUBSCRIBE: send a plain text/US ASCII email to >> > > > [EMAIL PROTECTED] >> > > > > with unsubscribe witango-talk in the >> message body >> > > > >> > > > ______________________________________________________________ >> > > > __________ >> > > > TO UNSUBSCRIBE: send a plain text/US ASCII email to >> > > > [EMAIL PROTECTED] >> > > > with unsubscribe witango-talk in the >> message body >> > > > >> > > >> > > ______________________________________________________________ >> > > __________ >> > > TO UNSUBSCRIBE: send a plain text/US ASCII email to >> > > [EMAIL PROTECTED] >> > > with unsubscribe witango-talk in the message body >> > > >> > > ______________________________________________________________ >> > > __________ >> > > TO UNSUBSCRIBE: send a plain text/US ASCII email to >> > > [EMAIL PROTECTED] >> > > with unsubscribe witango-talk in the message body >> > > >> > >> >> ______________________________________________________________ >> __________ >> TO UNSUBSCRIBE: send a plain text/US ASCII email to >> [EMAIL PROTECTED] >> with unsubscribe witango-talk in the message body >> >> ______________________________________________________________ >> __________ >> TO UNSUBSCRIBE: send a plain text/US ASCII email to >> [EMAIL PROTECTED] >> with unsubscribe witango-talk in the message body >> > >________________________________________________________________________ >TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] > with unsubscribe witango-talk in the message body > Bill Conlon To the Point 345 California Avenue Suite 2 Palo Alto, CA 94306 office: 650.327.2175 fax: 650.329.8335 mobile: 650.906.9929 e-mail: mailto:[EMAIL PROTECTED] web: http://www.tothept.com ________________________________________________________________________ TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED] with unsubscribe witango-talk in the message body
