similarly to what's being done on ActivityTool, also call setSite in AlarmTool

before processing a timer


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@38627 20353a03-c40f-0410-a6d1-a30d3c3de9de

product/ERP5/Tool/AlarmTool.py

@@ -46,6 +46,7 @@ import re
 # minimal IP:Port regexp
 NODE_RE = re.compile('^\d+\.\d+\.\d+\.\d+:\d+$')
 
+from zope.site.hooks import setSite
 try:
   from Products.TimerService import getTimerService
 except ImportError:
@@ -210,6 +211,10 @@ class AlarmTool(BaseTool):
     if not acquired:
       return
     try:
+
+      portal = self.getPortalObject()
+      setSite(portal)
+
       # make sure our skin is set-up. On CMF 1.5 it's setup by acquisition,
       # but on 2.2 it's by traversal, and our site probably wasn't traversed
       # by the timerserver request, which goes into the Zope Control_Panel