Persist locale preference when switching between records

✋ Feature Requests
1

Hi all!

Would it be possible to persist the last used locale in a record?
Right now it always switches back to the default, we have a project with a lot of locales, which makes the editing experience the following.

  1. search your model/record to edit
  2. opens in default locale
  3. editors tries to find the locale that he needs to edit
  4. switches to another record
  5. repeats step 2-3.

Ideally this would be:

  1. search your model/record to edit
  2. opens in default locale
  3. editors tries to find the locale that he needs to edit
  4. switches to another record that automatically keeps the locale the same. no need to start searching again.

Many thanks in advance.

3

Hmm, I wonder if this is an oversight. Let me check with the devs and get back to you :slight_smile:

2 Likes
4

Quick update on this: We have tested some code changes that could make this happen, but first we have to merge some related planned work (just to avoid potential code conflicts). We’ll take a look at this again soon!

5

Hi Roger,
Thanks for the update, looking forward to it!

Thanks!

6

@thomas.vanleynseele This has been deployed :slight_smile: Now, as long as you’re within the same model, we should remember your chosen locale between different records and the collections view.

7

Sorry, just a quick heads-up… this change caused some unintentional side effects (as bugs), and we may need to temporarily roll it back until it can be more thoroughly tested :frowning:

It’s currently still live, but may temporarily disappear in the next couple days, unless we can easily fix the bugs. If not, we might have to roll it back and do a better job of testing it before re-releasing it.

(Sorry, this was my fault… my PR failed to account for some use cases that this interferes with…! It’s a good idea, still, but we need to better identify and work out the kinks first.)

8

We’ve temporarily rolled back this feature because it was causing both some bugs and unintentional side effects with complaints. We’ll have to reconsider how to implement it in a way that doesn’t affect existing users who don’t want this behavior…

9

Thanks for the heads up. Didn’t realize there was a use case where you don’t want this.

Still interested to see this being implemented, if needed, behind the “Editor Preferences” area?

Thanks Roger!

10

I didn’t either, but it caused a complaint from a customer who works with a lot of locales. But that’s not the main reason (as you said, that could be behind a preference). It was more that it caused some unexpected bugs with locale changing & saving that we didn’t anticipate, and we had to emergency hotfix it and roll it back.

It just needs a bit more time to work out the kinks, but hopefully we can re-add that soon!