Hi
I'm determining an optimal approach to handling errors and http errors
in a Fusebox site.
The problem is made non-trivial by the fact that some URLs considered
valid by Active4D / fusebox will be defined as invalid by the dynamic
part of the site (e.g. items not found by queries or other content
items which do not exist, even though a valid circuit is identified).
I've solved this by directing output to a 404 page in the root circuit
(using layout switching) and using "set response status(404)".
As far as I can see, there are 3 more scenarios to handle (considering
the above case as [1] )...
[2] - syntax errors (already dealt with using the fusebox.handleError
approach)
[3] - regular 404's generated by Active4D
[4] - "circuit not found" errors generated in the fusebox core (I'd
like these to ultimately be served back as 404 http errors, not syntax
errors)
The problem I have is therefore how best to make the handling of [3]
and [4] consistent with the first case (even though the original
request may be non-fusebox).
I'm thinking of using something like using fusebox.sendfuseaction to
invoke the Fusebox-based 404 layout from the Active4D.ini registered
error page (or http error page).
Am I thinking about this wrongly ? Is there a simpler way to do it ?
Thanks in advance for any remarks anyone might have on this general
subject.
Regards
Peter
_______________________________________________
Active4D-dev mailing list
[email protected]
http://list.aparajitaworld.com/listinfo/active4d-dev
Archives: http://vasudev.aparajitaworld.com/archive/active4d-dev/
