For you info !
The scenario is:
1.tcf collects data into an array and before showing
the list it calls for each row a Custom Tag (2.tcf) which look for existing
files in a specific directory, which is being done with a file action. Then
1.tcf displays the list and the user can click on a row and get a detail page.
If the user then use the ‘Back’, ‘Backspace’ or a _javascript_ back code they sometimes get the page ‘Warning
page has Expired’.
I found out the reason was that if the 2.tcf didn’t find the file it
generates an error (which the error.html part took care of), but because that
error
the user got the ‘Warning page has Expired’ page. It works fine if
the call to 2.tcf comes from a .taf file instead.
I don’t know if this is the right behaviour or a bug, but a had to recode to solve it.
-----Ursprungligt
meddelande-----
Fr�n: Bengt Bredin [mailto:bengt[EMAIL PROTECTED]se]
Skickat: den 12 maj 2004 12:59
Till: Witango-Talk
�mne: Witango-Talk: Page has
expired
Hi all !
I have a question about calling a Custom Tag from within a tcf.
>From inside a .tcf and <@rows>……I call a Custom Tag <@Check_File_Exists filepath='xxxxxx’>
to see if
corresponding .pdf file exists for that <@currow> and that works fine.
On the html page being produced I also have other links to press and if
I do that a receive a new html page with detail information,
but� if I press ‘Backspace’
or ‘Back’ on my browser to go back to the previous page I get
‘Warning page has Expired’.
I have tried to clean out my temporary internet files but with no success.
If I don’t call the Custom Tag from within the .tcf then it works
again.
What is it that I don’t get here ?
Do I have to check all rows for pdf files before showing the page or what ?
/Best regards
Bengt Bredin
