Skip to content
This repository has been archived by the owner on Sep 29, 2020. It is now read-only.

Confusing property editors #97

Open
kows opened this issue Jul 9, 2018 · 5 comments
Open

Confusing property editors #97

kows opened this issue Jul 9, 2018 · 5 comments
Assignees
Labels

Comments

@kows
Copy link

kows commented Jul 9, 2018

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.

@soreng
Copy link
Contributor

soreng commented Jul 9, 2018

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.

@soreng soreng self-assigned this Jul 9, 2018
@soreng soreng added the question label Jul 9, 2018
@kows
Copy link
Author

kows commented Jul 9, 2018

hi @soreng,
I was not sure it was the intention but it seems like it wasn't by your reply.
I guess Umbraco also checks the package.manifest for the dropdown for creation of data types.

What I am talking about is the following:
macro
rte
textstring
image
leblendereditor

@soreng
Copy link
Contributor

soreng commented Jul 9, 2018

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.

@kows
Copy link
Author

kows commented Jul 10, 2018

One final comment, but we might come to an understanding on Slack then first.
The screenshots I took are from the "Developer" -> "Data Types" -> "Create" -> "New data type" screen.
On a fresh Umbraco installation, these do not appear in the dropdown.
They do after installing LeBlender.
I'm guessing this is caused by the property editors listed in package.manifest of LeBlender.
Perhaps this configuration can be moved to another section?
I'm rather new to plugin dev/setup of Umbraco.

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.

@bjarnef
Copy link
Contributor

bjarnef commented Jul 14, 2018

@soreng LeBlender define these property editors in package.manifest, which show up in datatype dropdown in Umbraco.

https://github.com/Lecoati/LeBlender/blob/1e4a1c1851e4d970ea6ad034b7345857b1a01981/Src/Lecoati.LeBlender.Ui/App_Plugins/LeBlender/package.manifest

Sometimes I have seen developers creating datatype instances of the rte instead of the core Umbraco.TinyMCEv3 which can cause some issues, where the rte defined in LeBlender store the value type as TEXT (not sure if it was stored as TEXTpreviously?)

{
"name": "Rich text editor",
"alias": "rte",
"isGridEditor": true,
"editor": {
"view": "rte",
"valueType": "TEXT"
}
},

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.
#61

But I am not sure it these defined property editors in latest version show up i the datatype dropdown?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

3 participants