Property Editor UI Configuration problem?
# package-development
p
Running into an issue that I don't quite understand. I am following the tutorial to add a property editor (https://docs.umbraco.com/umbraco-cms/tutorials/creating-a-property-editor) and I correctly see it in the document type selection, but when creating a new datatype of it, I get this error https://cdn.discordapp.com/attachments/882984798719729704/1329537756677800008/image.png?ex=678ab406&is=67896286&hm=32601f803b319f34e4fe4808f575fbb82996093890836aea20cd3db8bcd6aa8c&
n
Hi Patrick, Can i ask you to share your manifest? Cause when picking Property Editor UIs for Documents, then they need to have a
propertyEditorSchemaAlias
defined, and I think the one you have defined then might not be a valid choice? (What we in the front-end/client call Property Editor Schema, is the Property Editors on the server. which is why I think that is what it is complaining about. The server generally knows nothing about Property Editor UIs, and this is a error coming from the server. 🤗 )
p
I forgot to commit it 😅 I'll get back to you with that. But it does have a propertyEditorSchemaAlias defined (you see it under the name in the image). "SeoToolkit.FieldsEditor"
n
Sorry, I should have spotted that. Sounds good, then please make sure that is the alias of an actual Property Editor on the server 🙂
p
Is that part missing from the documentation then? I don't see anything related to server code, only frontend
Oooh, is it because I use a custom
propertyEditorSchemaAlias
instead of one defined by Umbraco? And I guess I should follow this part then: https://docs.umbraco.com/umbraco-cms/tutorials/creating-a-property-editor/adding-server-side-validation?
I got it working. Thank you @Niels Lyngsø !
2 Views