On 5/27/14 11:15 AM, "Aparajita Fishman" <[email protected]> wrote:
> >> Our site >> uses your default page. Does the plugin output that response > >Yes. You have to create your own page. See the demo database for examples >and read the "Error Handling" chapter of the docs. I'll look at the demo db. I've read the Error Handling chapter in the docs. Quick tests with a custom error handler and a test page with an intentional syntax error allow me to see it fire. What I haven't been able to do is QUIT 4D from within Active4D. I tried by calling the command, and by calling our method that gracefully shuts down but either cause the 4D Remote instance to hang w/ no response. > > >> That code is -1. The only error code with that value is "A4D Not >> Executable". > >That is a 4D error code, not an Active4D error code. In that case will it be possible to detect this in my custom error handler? What will $a4d_err_type be? If there isn't it may not be worth it to develop custom error pages. Over the years I've done a lot of work to make our sites robust. The one thing I could never solve was how to gracefully handle low-level 4D errors such as the rare client-server disconnect. Thanks, Brad > >Regards, > > Aparajita > >_______________________________________________ >Active4D-dev mailing list >[email protected] >http://list.aparajitaworld.com/listinfo/active4d-dev >Archives: http://active4d-nabble.aparajitaworld.com/ > _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
