We have moved to GitHub Issues
Created by Daniel Chenery 15 Nov 2017, 11:05:17 Updated by Robert Copilau 26 Feb 2018, 11:41:05Tags: Unscheduled PR
Subtask of: U4-9609
Obsolete property editors are still available via the Document Type settings screen, regardless of the the
As this setting haven't worked (since forever?), it's worth considering the impact for upgrades as if any obsolete property editors is in use and the settings showDeprecatedPropertyEditors is false you'll get an exception.
One solution could be to change the implementation and only do the check for showDeprecatedPropertyEditors in the controller where editors are fetched (for the content type editor)
PR changed to only do the check on controller level
Obsolete property editors will not show if you either create or edit a document type - already in use obsolete property editors work just fine. Merging.
Backwards Compatible: True
Due in version:
Sprint: Sprint 79