Final email...the only way I can get my error page to work
consistently with Safari and with Firefox is to set the error page in
the Active4D.ini file.
Setting via the command "set error page" in application start or
session start appears to me to have issues (if I set it on every page
it works) so somehow A4D is losing (not "loosing") the setting.
Is there anyway to return the current setting for error page
(something like get error page)?
M.
On 11 Apr 2007, at 21:25, Michael Kaye wrote:
I still think something strange is happening. I feel like I'm going
round in circles....here is the latest.
Launch the database and with safari load a page with an error in
it. My error page appears correctly....now reload the page either
using the reload button in the browser window or by re-typing the
url. This time I get the Active4D error page.
After that doesn't matter what errors occur, I get the A4D error page.
Quit Safari and re-open the "error" page and I get my error page
again....reload and A4Ds...and so on in circles.
I assumed it was a caching problem so I tried with Firefox and this
just made matters worse. With Firefox I never ever see my error page.
Log is reporting no problem apart from the one I expect to see in
my "error page". My pages
Any one any thoughts. I know deep down it is not an A4D issue but
there is something not right going on here....
M.
BTW I found setting the error page in Application Start does not
work...
On 11 Apr 2007, at 18:36, Michael Kaye wrote:
Ahem...as I asked you to do several messages ago... ;-)
I know my mistake, I thought I had increased the logging number
but I hadn't saved the file. Apologies...
Works for me. Try nothing but a4d.debug.dump locals in your
custom page and see what is there.
OK as long as I know it should work, it probably is something else
I've done.
I'm going to call it a day as I'm obviously not with it today...
Thanks, Michael.
On 11 Apr 2007, at 18:12, Aparajita Fishman wrote:
I had an included page in my custom error page and this page
itself had an error. Didn't notice until I upped the error
logging to 4 and kept an eye on the log.
Ahem...as I asked you to do several messages ago... ;-)
I don't seem to be able to reference the error page variables in
my new custom error page.
Works for me. Try nothing but a4d.debug.dump locals in your
custom page and see what is there.
Regards,
Aparajita
www.aparajitaworld.com
"If you dare to fail, you are bound to succeed."
- Sri Chinmoy | www.srichinmoylibrary.com
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
_______________________________________________
Active4D-dev mailing list
[email protected]
http://mailman.aparajitaworld.com/mailman/listinfo/active4d-dev
Archives: http://mailman.aparajitaworld.com/archive/active4d-dev/
