Where do we start here. Can you create a plan of action so we can
discuss and convert to the task?
On Mar 9, 4:21 am, Alexander Obuhovich <aik.b...@gmail.com> wrote:
> We are currently reporting around 100 custom error messages, that will help
> developers to take care of possible problems before they happen. We should
> set proper error message type for each of them using following logic:
> - notice - information stuff, should be fixed, but not top priority and
> doesn't affect system's stability
> - warning - possible cause for larger problem, must be fixed before
> project is shown to client
> - fatal - critical, application failure and must not exist at all at any
You received this message because you are subscribed to the Google Groups "In-Portal Bugs Team" group.
To post to this group, send email to in-port...@googlegroups.com.
To unsubscribe from this group, send email to in-portal-bug...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/in-portal-bugs?hl=en.
I guess we can schedule this for 5.0.4
On Mar 13, 5:45 am, Alexander Obuhovich <aik.b...@gmail.com> wrote:
> Here are patches to fix this. There where 18 incorrect error type usages out
> of 72 through out all project and it's modules. Not so bad as I've assumed.
> On Sat, Mar 13, 2010 at 1:11 PM, Alexander Obuhovich <aik.b...@gmail.com>wrote:
> > Here are explanation of each error type:
> > - notice - coding style errors, that normally doesn't cause problems,
> > but should fixed when possible
> > - warning - most likely predicts large scale error, when not attended
> > in time
> > - error - fatal error, that prevents further script execution
> > On Wed, Mar 10, 2010 at 10:09 AM, Alexander Obuhovich <aik.b...@gmail.com>wrote:
> >> We need to list all tirgger_error function usage cases and process each
> >> one individually.
> >>> .
> >>> For more options, visit this group at
> >> --
> >> Best Regards,
> > --
> > Best Regards,
> Best Regards,