support for contentment datatypes

[ribsdigital]

hi matt,

we've hit an issue where a contentment datatype isn't loading when set as a field datatype...

the datatype we've been exprimenting with is a datalist reading from an enum and rendering as a radio button list:

there are no errors raised in the logs and/or the backoffice, the datatype just doesn't appear to load:

appreicate contentment is a 3rd party plugin so it may not be supported but we wanted to run it by you 👍

[mattbrailsford]

@ribsdigital I'll see if I can see why it doesn't work, but just a heads up, when reporting issues you need to report them on the konstrukt repo. You seem to keep raising them on the konstrukt-documentation repo which is intended for documentation issues. I've transferred this issue over to the correct repo, but just thought I'd mention it for future issues.

[mattbrailsford]

@ribsdigital ok, there should be a 1.0.3-beta0002 on the unstable feed shortly which resolves this. If you wanna give it a try and let me know if it works for you 👍

[ribsdigital]

hi @mattbrailsford appologies for posting on the wrong repo... i'll post any further issues here 👍

we've just tried out the beta version and although it fixes the issue with the contentment datatype, all datatypes that're based on content pickers are now failing!

editing an exisiting entity results in the picked content failing to load.

creating a new entity allows picking, but once a piece of content is selected the following console error occurs:

if we revert back to v1.0.2 everything the content pickers work as expected...

weird! does this happen on your side?

[mattbrailsford]

I think you might be suffering from this issue https://github.com/umbraco/Umbraco-CMS/issues/10951 (that unfortunately got closed) but it seems you have a mix of ID types being posted back to the content API which it doesn’t like.

I’ll have to take give it a try on my local install

[mattbrailsford]

@ribsdigital are you using the normal content picker? or do you have a custom picker implementation anywhere?

[ribsdigital]

hi @mattbrailsford it's the content picker that ships with the umbraco core...

we've tried this in a couple of projects now with the same outcome...

[mattbrailsford]

Do you have any other custom content picker implementations where in your solution? (within Konstrukt or not)

[ribsdigital]

hi @mattbrailsford no - this is running in a very skinny standalone install of umbraco that i'm using specifically for testing konstrukt. other than creating the home doctype and setting up the pocos as outined in the docos, it's not got anything else in it.

[mattbrailsford]

Hmm, then I can't think what is affecting this. It's not particularly Konstrukts issue, it's a problem in the content picker where in it's prevalue it can be told what type of id to store (int or udi) but the bug I link to is that for some reason any content picker that runs first dictates what id type must be used for ALL content pickers across the solution.

From the error you are showing, it does look like the content picker is mixing it's id types (you've got an int id and a udi id trying to be looked up, which is what is causing the error).

As I say though, unfortunately this isn't Konstrukts issue. It's the core one I linked to.

[mattbrailsford]

I did wonder if it was something in contentment which does indeed have a treepicker in it, but it's idType is set to "udi" which I believer is the default so should be ok. It really looks like somewhere there is a picker configured with an idType of "int" and it's messing with the rest of them.

[mattbrailsford]

I'm gonna close this issue as I'm pretty sure the remaining item is a core issue and the fix for the original bug is in place. This will actually be in the upcoming 1.1.0 release