Under Community Review

This is Under Community Review to solicit feedback and use cases. Does this happen just with Templates or are they particularly hard to catch with particular types of items?

Do you use the BluePrint viewer to check for such localizations? If not, how do you eventually discover the issue with a template or other item?

Provide visual feedback to indicate that an item is localised elsewhere.

One of the classic Tridion mistakes is to make half a dozen futile edits to a template, only to realise that lower in the blueprint a localised version is actually what has effect. The same thing presumably applies to content.

My first thought was that items in lists should show a different icon if they have a localised version, however there is already a lot of information packed into the various icons, so perhaps this would be too much for a "nice to have" feature. It strikes me that once you open the item popup, it's still not too late to warn you that your edits are likely to be overruled elsewhere.

This is mostly about catching mistakes. One can easily argue that good practice would be to prevent the child item being localised, but especially on a  development server, it's not always helpful to lock everything down, so a little hint from the GUI would be nice.

Dominic Cronin
Parents

  • No - I don't use the BluePrint viewer for this. I rarely do. I mean, apart from the fact that the blueprint visualisation was certainly an impressive bit of browser work, it's not that useful. I sometimes wish it would be a good way to navigate to elsewhere in the blueprint, but that usually ends in disappointment. With anything like a large blueprint, it's really hard to see the wood for the trees anyway.

    Usually the process of discovering an unintended localisation begins with seeing that you don't get the output you expected from your templates.

Comment

  • No - I don't use the BluePrint viewer for this. I rarely do. I mean, apart from the fact that the blueprint visualisation was certainly an impressive bit of browser work, it's not that useful. I sometimes wish it would be a good way to navigate to elsewhere in the blueprint, but that usually ends in disappointment. With anything like a large blueprint, it's really hard to see the wood for the trees anyway.

    Usually the process of discovering an unintended localisation begins with seeing that you don't get the output you expected from your templates.

Children
No Data