-
Notifications
You must be signed in to change notification settings - Fork 63
Confusing property editors #97
Comments
hi @kows LeBlender does not include any editors. It creates a "tree" that is displayed under the "developer"-section in umbraco, and allows editing of the editors that are either in the config/grid.editors.config.js or individual package.manifest-files found in plugins. It also allows for creating editors (stored in config/grid.editors.config.js) by picking one or more datatypes. If you feel the editors created with LeBlender should be prefixed, you are free to do that in the UI. I'm not really sure what to answer here. Please let me know if I'm mistaking anything here. |
hi @soreng, |
Still, I'm not really sure what you are suggesting. The editors in the screenshots are from the starterkit - not LeBlender. You could also use icons with other colors if you need to distinguish LeBlender-created editors. |
One final comment, but we might come to an understanding on Slack then first. EDIT: I am certain they show up there because of the package.manifest, because if I remove that section from the manifest, they disappear from the dropdown. |
@soreng LeBlender define these property editors in package.manifest, which show up in datatype dropdown in Umbraco. Sometimes I have seen developers creating datatype instances of the
It seems is has been fixed in latest version, although I didn't find this version stable, when I tried out this version on existings projects and it only exists a NuGet package. But I am not sure it these defined property editors in latest version show up i the datatype dropdown? |
Hi there,
would it be possible to give some kind of indication that the editors included in this package are part of LeBlender?
It is quite confusing they show up in Umbraco's "Create datatype" dropdown list (where they never should be selected afaik) with no clear link to LeBlender.
This for rte, image, macro, embed and textstring.
LeBlender Editor even loads some stuff in there and gives weird behavior.
Preferably name or alias mentions LeBlender.
The text was updated successfully, but these errors were encountered: