plone/plone.dexterity — pull request #20 by datakurre (2014-08-01 03:50:25+00:00)
Title: Fix to not destroy AT references within a moved/renamed Dexterity container

I can guess that nobody wants AT related code in Dexterity, but where should this go and what would the most proper way to enable this only when Archetypes are present.

The issue is that when Dexterity container or its children contains any AT content with AT references in it, any move or rename operation will cause AT ReferenceEngine to remove those references.

I must not be the only one having this issue, because plone.app.contenttypes does not have a migration for AT Topics (and may not have for some time, because any migration could be destructive [for subtopics and custom criteria]). So, after p.a.contettypes migration, all AT Topics with path criteria will broke themselves sooner or later.