U4-5892 - Failed to find Content type / Wrong alias name

Created by Mirko Matytschak 26 Nov 2014, 17:12:56 Updated by Nicholas Westby 10 May 2016, 20:35:05

Umbraco 6.2.1

I get the following log message:

2014-11-26 17:14:28,633 [191] ERROR Umbraco.Core.UmbracoApplicationBase - [Thread 187] An unhandled exception occurred System.Exception: ContentTypeService failed to find a content type with alias "Infokasten-1-3".

The Name of the content type is "Infokasten 1/3", the alias is "Infokasten13". If I look at the umbraco.config, the elements of the according document type have the name <Infokasten-1-3 ...

As far as I know, the element name should be the document type alias, so it should read <Infokasten13 ... in the umbraco.config

The message appears in the same situation as reported here:

http://issues.umbraco.org/issue/U4-5888

but I don't think that there is a relationship between these two issues.

2 Attachments

Comments

Mirko Matytschak 11 Dec 2014, 11:27:35

Could please somebody have a look at this issue? It breaks our customer's site. I see the exception as shown on the attached picture. The exception occurs, if i try to get an existing document with Umbraco.TypedContent(int id). The document has a document type name "Infokasten 1/3" and an alias "Infokasten13". The umbraco.config file shows an element name of "Infokasten_1_3" which is exactly the name appearing in the exception. I'm sorry that I've posted this comment in the wrong issue report first...


Mirko Matytschak 11 Dec 2014, 14:04:03

Update: I renamed the content type to be the same as the alias (which is Infokasten13). Now a new phenomen starts to appear: If I click at the node in the content section I get a 404 error message instead of the content editor page. I can publish the node with the right mouse button, but can't change any properties, since the editor doesn't appear. The log doesn't show anything interesting.


Nicholas Westby 10 May 2016, 20:34:49

I was experiencing this issue too after an upgrade from Umbraco 6.1.6 to Umbraco 7.4.3. The problem seems to be related to the fact that hyphens/dashes are no longer allowed as document type aliases. On upgrade, the hyphens are removed in some places.

I was able to fix the issue by renaming the document type a couple times (e.g., from "subFolder" to "subFolder2" and back to "subFolder). In this example, my original document type had an alias of "sub-Folder").


Priority: Normal

Type: Bug

State: Submitted

Assignee:

Difficulty: Very Easy

Category:

Backwards Compatible: True

Fix Submitted:

Affected versions: 6.1.6, 7.4.3

Due in version:

Sprint:

Story Points:

Cycle: