Frontend Key Groups

Hello @Claudio Acosta If you don’t know the exact Polyglot key, open Studio and go for example to Pages → Persons → View Profile. Open the block you need to edit and translate only the frontend part, just like you mentioned.

Another example: Navigation → Items → System → Site → Edit Item.

There you clearly see what is displayed in Studio and what is displayed on the frontend, so you only translate the “Link name displayed in site menus.

I hope I understand you correctly :)

Hi @PavelS

Yes, I understand. I did it that way once on another site, but it took a lot of time, and then as I used it, I realized that many messages were left untranslated, especially notifications and error messages.

That's why I'm looking for a faster and more effective way to do it.

Thank you very much.

Hello @Claudio Acosta I know what you're talking about, everyone has been through it, the Language String Editor was a good helper for this, but it's been out of stock for a long time. I have it physically, but it needs to be modified for the new UNA version. Unfortunately, I don't have time for that right now, I'm finishing another project, but I'll definitely come back to it.

Hi @PavelS @LeonidS

Thanks as always for the replies.

What I'm trying to do is update the sys_localization_strings table.

I created a new language in sys_localization_language and completely cloned the English language into sys_localization_strings.

I already have a CSV file translated with AI, which I generated from a Google Sheets file where I copied the translated texts.

I created a temporary table with only two fields (Id, String) where I want to import the data from the CSV file, but I'm having trouble importing it. The problem seems to be related to how MySQL interprets quotation marks. That's what I'm struggling with now.

Regards.

@LeonidS is right, thanks, man. The best and simplest solution for you is to create your own language module. What you're doing is a recipe for disaster :)

Hi @LeonidS @PavelS

Yes, I had considered creating a module and had read the documentation, but honestly, it seemed like it would take more time and perhaps more of my own knowledge and involvement.

Therefore, I decided to create a second language, clone the English one, and then translate it.

In the end, I translated everything—all 8151 records—since it's very difficult to filter out those that correspond only to the frontend. I did it following the steps indicated by chatgpt: creating a new language in sys_localization_languages, cloning the English language in sys_localization_strings, generating a CSV file, translating, importing to a temporary table, checking, and finally updating the sys_localization_strings table for new language and clearing the cache.

It's working well, so far.

However, @PavelS 's comment has worried me, and I'd like to know what kind of problems I might encounter.

Thank you both very much.

Hello @Claudio Acosta Creating a language module isn't hard at all—I have 13 of them. I also struggled with how to handle it as quickly as possible, etc., and believe me, editing a language module is much faster, more organized, and you can be sure your translations will always stay in place, whereas if your database crashes, you'll lose everything. When you uninstall the module, the database gets cleaned up and no unwanted clutter remains; if you do it manually, you have to do everything manually again.

As for scaring you, I didn’t mean to, but I’ve had it happen where a mistake I made while manually entering keys threw my entire website off.

Which path you choose is, of course, up to you, and if this works for you, there’s no problem with it as long as you’re careful and make regular backups.

As for the frontend-backend language separation, you can handle it the way I have it shown in the screenshot.

Hi @PavelS

I understand everything you mentioned. I did look at the documentation and it seemed like it would take much longer than doing it another way, but you're right, it would be safer.

I'll add it to my schedule to do it properly as soon as I have some time, because right now I'm busy with pre-launch tasks and I'm handling not only these things but also the sales side, so I'm swamped.

I have a question: which steps should I follow? "Creating a copy of the English app" or "Creating a new language app"? I assume the latter, but I'm asking just to be sure, to make sure I understood correctly.

Thank you very much and best regards.