Client asked an interesting question the other day: if there's a license error on the site, can we redirect to a graceful error page?
They've had MAC problems (primary problem: they keep giving us the wrong one), and they're freaked out that a licensing error can show up on the page like it does. If they have a licensing problem, they want to display an error page.
Well, licensing errors aren't catchable. Near as I can tell, the warning is inserted through a response filter.
Is the fact that there is an error exposed anywhere in the API? If so, I could detect that in the PageInit of a base page, and send them to an error page. Or even just raise an exception and let .Net error handling take care of it.
Client asked an interesting question the other day: if there's a license error on the site, can we redirect to a graceful error page?
They've had MAC problems (primary problem: they keep giving us the wrong one), and they're freaked out that a licensing error can show up on the page like it does. If they have a licensing problem, they want to display an error page.
Well, licensing errors aren't catchable. Near as I can tell, the warning is inserted through a response filter.
Is the fact that there is an error exposed anywhere in the API? If so, I could detect that in the PageInit of a base page, and send them to an error page. Or even just raise an exception and let .Net error handling take care of it.