Will do, but right now I'm checking didBacktrack() in the page that
calls the long response page, and if it's true and the order was paid,
the "next" button will send them to another page. So far, it's working
great with IE 8, Firefox 3.5 and Safari 4.
You will have to walk through that did
You will have to walk through that didBacktrack message and see which
path it is taking and why.
Chuck
On Jun 8, 2010, at 10:58 AM, Pascal Robert wrote:
This is not what's happening in my testing so far. With Firefox on
Windows, if I backtrack on the long response page, I get back on the
This is not what's happening in my testing so far. With Firefox on
Windows, if I backtrack on the long response page, I get back on the
page where the long response page was called, and if the user call the
long response page again, the code in performAction is performed
again, which create
you can always use the ajax long task stuff, which would not generate a
backtrack entry for each of these refresh states, which is probably what your
users would expect anyway (back = go back to the page prior to the long
operation)
On Jun 8, 2010, at 1:39 PM, Anjo Krank wrote:
> How is that a
How is that a problem? The only thing the users *might* see while backtracking
is "50% done" followed by "45% done" followed by "51% done" after the next
refresh?
Cheers, Anjo
Am 08.06.2010 um 19:26 schrieb Pascal Robert:
> BTW, how I found out that users are backtracking is because I saw
BTW, how I found out that users are backtracking is because I saw this
in Apache logs :
GET /cgi-bin/WebObjects/Depot.woa/1/wo/1kbJaKnAptsgyX6WIPYrOM/
28.WOMetaRefresh
GET /cgi-bin/WebObjects/Depot.woa/1/wo/1kbJaKnAptsgyX6WIPYrOM/
29.WOMetaRefresh
GET /cgi-bin/WebObjects/Depot.woa/1/wo/1kb
Look like this :
/cgi-bin/WebObjects/Depot.woa/1/wo/a5wsIRHrgb2vaKM3n3WaHg/
9.WOMetaRefresh
What is the URL for the long response page (the URL they are
backtracking to)? Which path is it taking through that method?
Chuck
On Jun 8, 2010, at 8:04 AM, Pascal Robert wrote:
This is so grea
What is the URL for the long response page (the URL they are
backtracking to)? Which path is it taking through that method?
Chuck
On Jun 8, 2010, at 8:04 AM, Pascal Robert wrote:
This is so great. Deadlocks are now gone in our app, but I noticed
that some users are using the back button i
This is so great. Deadlocks are now gone in our app, but I noticed
that some users are using the back button in the app. So I looked at
ERXSession.didBacktrack(), and this is working fine for "normal"
components, eg if I backtrack on a normal component, didBacktrack()
returns true.
Proble
