Commit 745cb2bb authored by Julien Muchembled's avatar Julien Muchembled

Lower severity of log when portal type class is broken

Lower severity to WARNING because there are legitimate cases, like old objects
in the trash.
An ERROR log (catched by LogInterceptor) was making testBusinessTemplate fail.

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@39861 20353a03-c40f-0410-a6d1-a30d3c3de9de
parent 50a33d37
......@@ -5,7 +5,7 @@ from Products.ERP5Type.Globals import InitializeClass
from Products.ERP5Type.Base import Base as ERP5Base
from ExtensionClass import ExtensionClass, pmc_init_of
from ZODB.broken import Broken, PersistentBroken
from zLOG import LOG, ERROR, BLATHER
from zLOG import LOG, WARNING, BLATHER
from portal_type_class import generatePortalTypeClass
......@@ -122,7 +122,7 @@ class PortalTypeMetaClass(ExtensionClass):
try:
baseclasses, attributes = generatePortalTypeClass(portal_type)
except AttributeError:
LOG("ERP5Type.Dynamic", ERROR,
LOG("ERP5Type.Dynamic", WARNING,
"Could not access Portal Type Object for type %r"
% portal_type, error=sys.exc_info())
baseclasses = (ERP5BaseBroken, )
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment