[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Phpgroupware-users] phpGroupware calendar and email

From: Chris Weiss
Subject: Re: [Phpgroupware-users] phpGroupware calendar and email
Date: Fri, 7 Jan 2005 11:04:00 -0600

the whitespace issue is a php one, it's due to bad code or files and
no user can cause the issue without futzing with the source files.

However, phpgw could certainly use better error handling.  php
recently (in relation to the age of phpgw) added the ability to have
generic error handling function, but it just might be too general to
be usefull for us and would destroy any good error handling that we
already have in place.

definatly something to look at post 1.0 and maybe for .18.

On Fri, 7 Jan 2005 09:33:49 -0000, Matt <address@hidden> wrote:
>    >must be a file somewhere that's got stray whitespace... not easy to
>    >find if it's not telling you were the headers were sent...
>    >
>    >just setup a test acocunt with email alerts enabled, included that
>    >user in an event, no errors. deleted event, no errors.
>    >
> It seems to me if a little ol' whitespace can up set the system imagine what
> say 100 non technical users will do.
> Might I suggest a little additional fault "coping" and some nasty
> generalisations to compensate for bad data.
> Its not easy to figure out what a default value should be but junkdata beats
> errors for most non technical users.
> On the same idea (I am unable to do this in PHP yet) I have found that a
> general error API works wonders.  For example:
> On error call errorthang(error.message, etc)
> All errors would (in theory) become transparent with some resulting in
> userfriendly apologies. All errors would be logged and would therefore
> provide an excellent digest of "live systems behavior".
> With a little thought any number of fault-correction sub-systems could be
> implemented.
> (It could also reduce the number of similar new user questions/bug-reports.)
> What do you all think?

reply via email to

[Prev in Thread] Current Thread [Next in Thread]