Hi Tor,

Yeah, the sort order is something we've been looking at, we don't have a universal solution, because for example in a grid a nested property can have its own way of storing things, and it's actually the displaying of all the nested sorted elements that are a bit of a pain.

Naming it's difficult because we are translating what can be a quite complicated structure into something linear that may well then be imported into another system (via an export). I am more inclined to say it's a developer choice as to how items within the grid are named, and we then do our best to represent that.

Ignoring deeply nested properties: again its something that has been asked for and we are looking at - the main thing holding us back is how this will be a major version change as it will change how certain properties are passed around as these elements are loosely coupled - so the value mappers (the things that do the extraction) don't actually know about the set settings and just extract values, so at the top level we can say don't extract this, but once we are nested (at the moment) nothing gets sent around - it will be a change to how we pass stuff around which will change value mappers which will have an impact on people who have custom ones.

Property workaround: The workaround is to use a datatype that doesn't have a value mapper for these values you don't want to map.

What this means in practice is having your own datatype that behaves like Umbraco.Textbox but are called something else (like My.TextString)

Properties using this datatype wouldn't have a value mapper they would be ignored at every level by Translation Manager - this is probably something we should just create and ship with translation manager, to be honest - would make this a bit easier.

and don't worry all feedback is welcome - there are so many different ways people have this setup we couldn't possibly work it all out, so anything you notice/want to change is always a help.

Hi

Just to follow up, we are looking at the naming/sorting stuff

looks like there are some quick wins, we can do which make nested / DTGE stuff look nicer. and well be in the right order.

Kevin

Thanks for the update!

I see how using a different datatype would solve the property hiding. I think it's feasible for us to take care of that (and if you're coming out with a built-in datatype ready for use, then we'll use it).

On the Grid Layout Value Mapper, would it be possible to add some extensibility to it, e.g. event handlers for generating fields names and another event handler for comparing them for sort rank?

Do you have any plans for new releases in the short term? What we do will probably be dependent on that.

-Tor

Hi

a quick "catch the easy stuff" release should be out tomorrow - which will fix sort orders of properties and the tab groups.

it probably won't have the ignore text datatype in it ( but might see what we can do on that one ).

There are events firing at a slightly higher level then field generation:

There is a TranslationNodeService.Created which is fired once a node has been created an example of how you might use that to do stuff to properties

{
  // in ApplicationStarted or similar register the event 
  TranslationNodeService.Created += TranslationNodeService_Created;
}

private void TranslationNodeService_Created(TranslationNodeEventArgs e)
{
  // e.Node.Groups contains the tab groups with the properties 
  // in it. here you could go in manipulate names, strip out properties ect.
}

for indivudial nodes all the events are :

TranslationNodeService.Created += TranslationNodeService_Created;
TranslationNodeService.Approved += TranslationNodeService_Approved;

TranslationNodeService.Creating += TranslationNodeService_Creating;
TranslationNodeService.Approving += TranslationNodeService_Approving;

the Creating / Approving are cancellable (so you can stop the process if you need to).

There are also a load of events the TranslationJobService fires, but they are more about jobs then properties, but if you need them they are there.

Just to add - code sample for using the Created event to manipulate property values in a translation node :

https://gist.github.com/KevinJump/9551e9adbaebba1910771f7b40936649

I'm on 7.14, Umbraco Cloud website version. VS 2017.

is working on a reply...