Bartosz Sekula
Jan 18, 2017
visibility 5621
star star star star star
(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

error Please login to comment.
Latest blogs
Architecting an Enterprise-Grade Development Pipeline in Optimizely SaaS CMS

Most enterprise teams show up to Optimizely SaaS CMS with a clear roadmap for their release pipeline: DEV → QA → Stage → Prod. Four logical...

Vipin Banka | Jul 12, 2026

Bynder DAM Connector for Optimizely SaaS CMS: Improved Metadata Property Synchronization

While working with the Bynder DAM Connector for Optimizely SaaS CMS , one of the key areas I explored was how Bynder asset metadata is synchronized...

Vipin Banka | Jul 11, 2026

Optimizely DXP: Every Supported Culture, One Searchable Page

Quick one for anyone building multi-language sites on Optimizely DXP. I put together a reference tool listing all 806 supported cultures. More...

Adnan Zameer | Jul 10, 2026 |

A day in the life of an Optimizely OMVP: London Meetup 2026

On 2nd July 2026 the Optimizely London Developer Meetup returned to The Lightwell, and the running theme across the evening was less about individu...

Graham Carr | Jul 10, 2026

Optimizely’s Summer ’26 Roadmap: The CMS Is Starting to Look Less Like a Publishing Tool and More Like Marketing Infrastructure

Optimizely’s Summer ’26 Product Roadmap event was not just a list of product updates. At least, that is not the part I found most interesting. The...

Augusto Davalos | Jul 9, 2026

Optimizely Content JS SDK v2.1.0 — What's New and Why It Matters

  v2.1.0 of the Optimizely Content JS SDK and CLI landed on July 7, 2026. This is a substantial release bringing a wave of capabilities for...

Vipin Banka | Jul 8, 2026