This is a bit scary, but when I click one of my document types "Article" it throws an error:
No node exists with id '1168'
However on checking the DB, Article has a nodeId of 1061. What's weird is that on hovering over the document type's name on the left tab, the status bar shows javascript:openNodeType(1061);
The backend clearly has the right mapping, but I have no idea why this is being used.I can't find 1168 in either cmsDocument nor the cmsContent table.
Okay, i spoke to one of the user's of our system, and apparently she had added a property with a custom data type in this doctype. She wanted to switch data types of the property and so she deleted the data type BEFORE switching the property's type.
That's what's causing the error. Oh shoot, anyway think this is a solid lead.
I still think this is a bug fix, as the right functionality would be perhaps to delete all properties of that data type or perhaps resetting them to a default value.
Error accessing a document type on the backend.
This is a bit scary, but when I click one of my document types "Article" it throws an error:
No node exists with id '1168'
However on checking the DB, Article has a nodeId of 1061. What's weird is that on hovering over the document type's name on the left tab, the status bar shows javascript:openNodeType(1061);
The backend clearly has the right mapping, but I have no idea why this is being used.I can't find 1168 in either cmsDocument nor the cmsContent table.
Does anyone have an idea of what's going on here?
Okay, i spoke to one of the user's of our system, and apparently she had added a property with a custom data type in this doctype. She wanted to switch data types of the property and so she deleted the data type BEFORE switching the property's type.
That's what's causing the error. Oh shoot, anyway think this is a solid lead.
I still think this is a bug fix, as the right functionality would be perhaps to delete all properties of that data type or perhaps resetting them to a default value.
is working on a reply...