For CMS blocks, should there be a translation in `spy_glossary_translation` for all placeholders and

UKEP86J66

For CMS blocks, should there be a translation in spy_glossary_translation for all placeholders and all available locales? We have recently added some locales and I am debugging an error in pub sync. It looks like the fix is add these missing rows into the db, but that seems like something that will go wrong again when we add more locales in the future. Is there a better way?

UKS668UPP

Hey there

UKEP86J66

Howdy stranger 😉

Valerii Trots

@UKBTMFXMJ?

Stanislav Matveyev

yes, in spy_glossary_key you should see generated keys for CMS blocks e.g.:

generated.cms.cms-block.Title-and-description-block.title.idCmsBlock.7.uniqueId.1

generated.cms.cms-block.Title-and-description-block.description.idCmsBlock.7.uniqueId.1

and for these keys in spy_glossary_translation should be translation per each locale

Stanislav Matveyev

probably you can use \Spryker\Zed\CmsBlock\Business\CmsBlockFacade::saveGlossary() to add missing glossary keys per each block

UKEP86J66

Thanks for confirming 🙇
In my project there are thousands of CMS blocks so this time I've wrote some SQL to add the missing locales, but next time I'll look at the facade method.