Revise error types (warning or notice) raised by system

1 view
Skip to first unread message

Alexander Obuhovich

unread,
Mar 9, 2010, 5:21:58 AM3/9/10
to In-Portal Bugs
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 of development stages

--
Best Regards,

http://www.in-portal.com
http://www.alex-time.com

Dmitry A.

unread,
Mar 9, 2010, 11:27:39 PM3/9/10
to In-Portal Bugs Team
This is a good idea.

Where do we start here. Can you create a plan of action so we can
discuss and convert to the task?

DA.

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

Alexander Obuhovich

unread,
Mar 10, 2010, 3:09:55 AM3/10/10
to in-port...@googlegroups.com
We need to list all tirgger_error function usage cases and process each one individually.


--
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.

Alexander Obuhovich

unread,
Mar 13, 2010, 6:11:37 AM3/13/10
to in-port...@googlegroups.com
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

Alexander Obuhovich

unread,
Mar 13, 2010, 6:45:31 AM3/13/10
to in-port...@googlegroups.com
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.
trigger_error_fixes_modules.patch
trigger_error_fixes_core.patch

Dmitry A.

unread,
Mar 13, 2010, 6:31:03 PM3/13/10
to In-Portal Bugs Team
Not bad at all and great work Alex!

I guess we can schedule this for 5.0.4

DA.

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.
>

> >>> in-portal-bug...@googlegroups.com<in-portal-bugs%2Bunsubscribe@go oglegroups.com>


> >>> .
> >>> For more options, visit this group at
> >>>http://groups.google.com/group/in-portal-bugs?hl=en.
>
> >> --
> >> Best Regards,
>
> >>http://www.in-portal.com
> >>http://www.alex-time.com
>
> > --
> > Best Regards,
>
> >http://www.in-portal.com
> >http://www.alex-time.com
>
> --
> Best Regards,
>
> http://www.in-portal.comhttp://www.alex-time.com
>

>  trigger_error_fixes_modules.patch
> 1KViewDownload
>
>  trigger_error_fixes_core.patch
> 14KViewDownload

Alexander Obuhovich

unread,
Mar 14, 2010, 7:31:23 AM3/14/10
to in-port...@googlegroups.com
Already done. I've just pushing all new bugs to 5.0.4 right away.

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.

Reply all
Reply to author
Forward
0 new messages