I have some folderish dexterity content where the default view was changed
e.g. /profiles/types/my_custom_type.xml contains
<property name="default_view">my_new_and_improved_view</property> <property name="view_methods"> <element value="my_new_and_improved_view" /> <element value="my_custom_view" /> <!-- obsolete --> <element value="view" /> </property>
Updating the default_view property to my new template and registering it zcml generally causes the new view to be used. Except in a few content objects where the default view was manually set to another value by users and then reversed back to "my_custom_view". In the affected content, I found a property "layout" in the ZMI with this value.
Lazily and naively, I hoped that setting
would fall back to the view set as a default_view. No such luck. After googling for "default_view_fallback" I am under the impression (please correct me if wrong) that https://github.com/plone/Products.CMFDynamicViewFTI/blob/master/Products/CMFDynamicViewFTI/fti.py#L193 is responsible for getting the default view for my content but because plone_utils exists, the default_view_fallback check is never reached.
Do I have any options other than writing an upgrade step which checks my content for and removes this creatively named "layout" property? Did I miss some documentation somewhere?