Commit 2e16e170 authored by Arnaud Fontaine's avatar Arnaud Fontaine

Portal Type as Classes, ZODB Property Sheets: Ensure that they are reset on

other ZEO clients even if ZODB Components are not.

Steps to reproduce:

  1/ On zope1, view and edit a person to make sure class is fully loaded.
  2/ On zope2 add an interaction in person_interaction_workflow and add a script raising an exception.
  3/ Edit a person on zope2. The exception is raised, confirming that the interaction is called.

  When editing a person on zope1, the exception is not raised.
parent a270c222
...@@ -358,7 +358,10 @@ class ERP5Site(FolderMixIn, CMFSite, CacheCookieMixin): ...@@ -358,7 +358,10 @@ class ERP5Site(FolderMixIn, CMFSite, CacheCookieMixin):
# This should only happen before erp5_core is installed # This should only happen before erp5_core is installed
synchronizeDynamicModules(self) synchronizeDynamicModules(self)
else: else:
component_tool.reset() if not component_tool.reset():
# Portal Types may have been reset even if Components haven't
# (change of Interaction Workflow...)
synchronizeDynamicModules(self)
return self return self
......
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