CiviCRM Community Forums (archive)

Well, i agree it's not a very nice error message and that's a general problem.

As a specific problem - you could intercept it before it gets to CiviCRM [say in your theme, if you're using Drupal] and do something nicer there.

In terms of the general solution - i'd want to distinguish between the two cases:

a. what is essentially a useability issue [e.g. your example], in which case you'd want to use something like logintoboggan's "show a login form whenever a user doesn't have adequate permissions for a page and isn't logged in".

b. a security response [e.g. if the profile is actually not something anyone else should even know about, i.e. an administrative only profile], in which case it should instead be a standard permission denied kind of page instead of a fatal error.

In even more general terms - I'd like the code base as a whole to stop taking the approach that if something unexpected happens to throw a fatal error. A little nuance in handling unexpected input would make CiviCRM a much better experience.

Hi,

Is there an example of a custom error handler ?

X+

P.S. and I'd like to distinguish between anonymous (not logged in) users and users that don't have the proper rights, to be able to display a different error msg.