I figured out _part_ of the problem. This is still running on v5. I looked at the v5 docs and that version doesn't support the $a4d_err_code variable. I had that in my error handler. By removing it the custom error page now runs. This is another good reason to upgrade.
I cannot get a custom HTTP status page to display though. -- Brad On 5/27/14 2:28 PM, "Perkins, Bradley D" <[email protected]> wrote: >Aparajita, > >Thanks. The demo code uses fusebox. We don't use that. > >Knowing $a4d_err_type will be A4D Error Type Database, and $a4d_err_code >should be -1 will help me develop something. > >My problem now is that I can't seem to set an error page. I have a custom >error page that is in > >web/errors/errorHandler.a4d, where web is the Active4D web root. > >I have set Active4D.ini to > >error page = <web>/errors/errorHandler.a4d > >I'd also want to replace the default HTTP error pages with some of our >own. If I have custom .a4d status pages in web/errors/, e.g., >web/errors/404.a4d, I would change Active4D.ini to > >http error page = <web>/errors/<status>.a4d > >I've set both of those in Active4D.ini and neither seem to have any >affect? >I have created a test page with an intentional syntax error and am still >seeing the default Active4D error response. >The same thing happens if I throw("some error"). >If I request an Active4D page that does not exist I'm still getting the >default Active4D 404 status page and not the custom 404.a4d. > >Am I missing a setting that is overriding mine, or have I set them >incorrectly? > >-- Brad > > >On 5/27/14 1:11 PM, "Aparajita Fishman" <[email protected]> >wrote: > >>> 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. >> >>It probably hangs because it's in the middle of a web request. You'll >>have to add some kind of custom response header that you can look for in >>a post execute hook within 4D, then try quitting from there. >> >> >>>>> 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? >> >>$a4d_err_type will be A4D Error Type Database, and $a4d_err_code should >>be -1. >> >>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/ > _______________________________________________ Active4D-dev mailing list [email protected] http://list.aparajitaworld.com/listinfo/active4d-dev Archives: http://active4d-nabble.aparajitaworld.com/
