U4-7738 - Validate content type aliases - ensure unique across all three content type types

Created by Shannon Deminick 14 Jan 2016, 12:48:05 Updated by Shannon Deminick 20 Jan 2016, 17:09:07

Relates to: U4-7739

Relates to: U4-7737

We cannot let duplicate aliases exist between doc types, media types and member types. One reason is because it probably causes a few issues already with caching since many things are cached by content type alias. Second, this won't be supported for Models Builder correctly because we cannot have overlapping class names.

Marking as breaking change so people are aware

Comments

Shannon Deminick 20 Jan 2016, 15:11:44

To test:

  • Create a new document type and try to save it with the same alias as another
  • Create a new document type and try to save it with the same alias as another media type
  • Create a new document type and try to save it with the same alias as another member type
  • Update a document type and try to change the locked alias to the same as another
  • Update a document type and try to change the locked alias to the same as another media type
  • Update a document type and try to change the locked alias to the same as another member type
  • Create a new document type and try to save it with a unique alias - it should work
  • Update a document type and try to change the locked alias to something unique - it should work


Shannon Deminick 20 Jan 2016, 15:11:48

PR: https://github.com/umbraco/Umbraco-CMS/pull/1038


Priority: Task - Pri 1

Type: Bug

State: Fixed

Assignee:

Difficulty: Normal

Category:

Backwards Compatible: False

Fix Submitted:

Affected versions:

Due in version: 7.4.0

Sprint: Sprint 7

Story Points:

Cycle: