Bartosz Sekula
Jan 18, 2017
  5477
(7 votes)

Persist "Show Content in Current Language Only" settings

Introduction

When working with multiple languages, it is possible to filter the gadgets to only show content in the currently selected language.
CMS UI 10.4.0 introduces a feature that will persist those settings so that the user does not have to manually set them after each page reload.
This feature is released as a response to user requests that we have received on different occasions, for example this feature request: Setting for default value on 'Show content in all languages' in the edit mode page tree.

Details

It is possible to set that setting in the navigation pane, Versions gadget and Blocks gadget as shown in the screenshot below:

Image Pages_Option_1092.png

The screenshot shows items that have already been translated to the current language, as well as items in the master language that have not been translated yet (marked with italic font).
After enabling Show Content in Current Language Only, the list would be filtered to only show the items that were explicitly created in the current language (in this case, it would be Swedish).

Image Pages_After_Turning_On_1092.png

The improvement here is that the selection persists across page reloads. So, the editor can now switch between the view mode and edit mode without the need to enable that setting again.
There is also an additional link that resets the list back to the default option. The link is added to the bottom of each gadget.

Image Additional_Reset_Link_1092.png

It works the same for the Blocks gadget and the Versions gadget.
The settings are not related to one another between the gadgets so the setting can be enabled, for example, in the navigation page and Blocks gadget but not in the Versions gadget:

Image Pages_And_Blocks_Turned_On_1092.png

Additionally, the setting is separate per gadget instance so you can add two instances of the Versions gadget and configure one of them to only show the current language while the other will continue to show all languages:

Image Two_Versions_Gadgets_1092.png

The settings are stored in the local browser storage.

Jan 18, 2017

Comments

Per Magne Skuseth
Per Magne Skuseth Jan 18, 2017 09:24 AM

Neat!

Aria Zanganeh
Aria Zanganeh Jan 20, 2017 01:07 PM

Good

Please login to comment.
Latest blogs
Before Upgrading to Optimizely CMS 13: A Developer Checklist

A practical checklist for reviewing a CMS 12 solution before moving to Optimizely CMS 13.

Wojciech Seweryn | May 26, 2026 |

From websites to agents. Five takeaways from the Optimizely Partner Close-Up in Stockholm

Last week was the annual partner close-up event in Stockholm, Sweden, fast becoming a favourite Optimizely event of the year. An opportunity to mee...

Mark Welland | May 26, 2026

Visibility — The Six Audits I Run on Every Optimizely Engagement

Long-running content management systems accumulate problems that never throw exceptions. The Editor Power Tools audit family is six lenses on what...

Allan Thraen | May 26, 2026 |

Understanding Optimizely Opal Cost

Opal pricing are transparent at large extent, It is based on a credit consumption model rather than fixed per-user licensing or tokens consumptions...

K Khan | May 25, 2026