Dynamic Schema is not synced across ZEO clients

I wonder if this issue https://github.com/plone/plone.schemaeditor/issues/81 is a regression or is like that since ever.

I hardly can believe that nobody added a custom DX fields TTW in 12 years and didn't notice this.

Like https://stackoverflow.com/questions/23737057/how-to-make-dexterity-modifications-available-to-other-clients ?

2 Likes

6 years! :smiley: meanwhile I would consider it a feature.

I had this issue in 2015 in a Plone 4.3.x project where the customer could modify the content types themself. I don't think I investigated further, neither created an issue about it. I just added a cron to restart the instances every day to resolve this...

Cache keys should be written in the database. We should use a in memory (tempstorage?) zodb to handle this (a memcached like mechanism) like we had session storage in Zope.

Found something https://github.com/plone/plone.schemaeditor/issues/81#issuecomment-702625667

Fixing suggestions are welcomed.

Possible fix: https://github.com/plone/plone.dexterity/pull/137

1 Like

Sorry @yurj, but no, writing cache keys to db and generating write-on-reads is in general a bad idea - even in a (deprecated) temp storage.

I agree, random o time based names is a perfect solution.

Plone Foundation Code of Conduct