Home
collective.logbook (0.4)
- collective.logbook download link: http://plone.org/products/collective.logbook/releases
- Homepage of collective.logbook: http://plone.org/products/collective.logbook
- collective.logbook repository: https://svn.plone.org/svn/collective/collective.logbook
- Description source: https://svn.plone.org/svn/collective/collective.logbook/trunk/README.txt
Advanced persistent Error Logging for Plone.
Motivation
Plone generates for anonymous users an Error Page which contains an error number. But what to do with this error number?
You have to log into your plone site, go to the ZMI, check the error_log object and probably construct the url by hand to get ther proper error with this error number, like:
http://your-plone-site/error_log/showEntry?id=1237283091.10.529903983894
If you are lucky, you will find the error. If not, and the number of occured errors exceeded the number of exceptions to keep, or maybe a cronjob restarted your zope instance, then....
Hmm, not really smooth this behaviour.
Wouldn't it be better to have a nice frontend where you can paste the error number to a field and search for it? Keep all log persistent, also when zope restarts? Keep only unique errors and not thousand times the same Error? Get an email when a new, unique error occured, so you know already what's going on before your customer mails this error number to you?
If you think that this would be cool, collective.logbook is what you want:)
