Use "default" fallback for missing translation


getting this when trying to save a CMS block:
Could not find a translation for key CMS Block was updated successfully., locale de_DE

I really think there should be a fallback here, because it obviously knows what it should show the translation for, but refused to show it at all because of missing DE translation for that particular string.
Simply showing “CMS Block was updated successfully.” when there is no translation for it, is fine.

1 Like

Hi Jan,

Thank you for the feedback, but could you provide more details please?
Maybe some steps to reproduce?

Best regards,


Steps to reproduce:

  • Enter Zed in non default locale (DE_de is fine)
  • Open Content
  • then any CMS Block
  • try to save CMS block
  • get the error.

Are we doing something wrong?

Best regards,


Well, you have DE_de translations done, because I can see it all over your screenshot/gif.

Our UI is having english everywhere (although “de_DE” is set in stores.php) thanks to usual fallback that seem to “usually work”.

The only difference is that we have no imported translations for “de_DE” and it only fails on that flash message (so far).

Issue is visible only if you don’t have the translation (which you do, hence no issue on your setup)


Ok, now it’s clear what you meant from the beginning. Sorry about that.
I’ll reproduce this today or tomorrow.

Best regards,


I can confirm the error that the translations are missing for the success message when trying to create a product, a category or a attribute after I’ve run composer update "spryker/*"



Sorry for the late reply. I was able to reproduce.
I’ll update here when the status is changed.

Best regards,


@tvalerii what’s the ETA for releasing the fix for this? It’s a bit annoying to get the exception on every successful operation.
Can also confirm running data:import:glossary doesn’t solve the issue.


Hi Jan,

there is a migration guide to be prepared soon and the ticket itself AFAIK is going to be taken into development in next sprint.
Sorry for inconvenience.

Spryker Support Team


Hi @janmyszkier,

while the ticket about using “default” translation is not yet finished, maybe you could implement “back office translation” feature.
Here is some documentation about it:

Spryker Support Team