Issue 286 in dexterity: Dynamic schemas and multiple zeoclients

[dext...@googlecode.com]

Status: New
Owner: j...@lentin.co.uk
Labels: Type-Defect Priority-Medium

New issue 286 by j...@lentin.co.uk: Dynamic schemas and multiple zeoclients
http://code.google.com/p/dexterity/issues/detail?id=286

You can probably guess what the bug is from the subject :)

Fire up a ZEO server and a few clients with a 4.3 buildout[0].
* Pointing at :8081, make a type and add one field via. schema editor
* Open same editor page on :8082 (the first time this type has been used on
this client), all looks same
* Add another field using :8081.
* Refresh editor page on :8082, no sign of extra field.
* :8082/Plone/portal_types/camel/manage_propertiesForm, the XML for the
extra field is visible, but the generated schema code is still stale.

Is there already a mechanism that should be telling the other ZEO clients
to invalidate the generated schema? Have I not done something to get it to
work? Or is this an oversight, in which case what sane options are there to
fix it?

My first random stab is some kind of checksumming within
plone.dexterity.fti.lookupSchema() or thereabouts.

[0] https://github.com/regebro/Plone-Buildout-Example is what I used, FWIW


--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[dext...@googlecode.com]

Comment #1 on issue 286 by dgl...@gmail.com: Dynamic schemas and multiple
zeoclients
http://code.google.com/p/dexterity/issues/detail?id=286

This is supposed to be working in plone.dexerity >= 2.1.1.

Also, this tracker is supposed to be closed. Use github or dev.plone.org
instead.

[dext...@googlecode.com]

Comment #2 on issue 286 by dominik...@gmail.com: Dynamic schemas and
multiple zeoclients
http://code.google.com/p/dexterity/issues/detail?id=286

I still have this problem with plone.dexterity-2.1.3 and
plone.app.dexterity-2.0.8
I created a new entry at github
https://github.com/plone/plone.app.dexterity/issues/104

BTW there is also a 2 year old entry https://dev.plone.org/ticket/12363