Database saved strings besides block names and descriptions
Permalink
Hi,
I guess most of you know that the names and descriptions of blocks are saved in the database and not read from the mo file after installation - which means that you can translate the standard blocks only by already having a language file at the point of the conrete5 installation or changing the values in the database.
My question is: Is there any list of strings where this happens? Or can anybody confirm that this is only the case with the blocks?
The reason is that I plan to change the translation and I don't want to reinstall after each change to get an effect.
I guess most of you know that the names and descriptions of blocks are saved in the database and not read from the mo file after installation - which means that you can translate the standard blocks only by already having a language file at the point of the conrete5 installation or changing the values in the database.
My question is: Is there any list of strings where this happens? Or can anybody confirm that this is only the case with the blocks?
The reason is that I plan to change the translation and I don't want to reinstall after each change to get an effect.
Did you ever resolve this? I have the same question. Also, do you know where in the database the values are stored? I've looked and nothing looks obvious to me.
Hi,
no, I never found a solution to this issue. Since I'm not working with Concrete5 at the moment, I even can't answer you which table contains the names. But there was a pretty obvious table named block_type or something at that time ;-)
no, I never found a solution to this issue. Since I'm not working with Concrete5 at the moment, I even can't answer you which table contains the names. But there was a pretty obvious table named block_type or something at that time ;-)
1. This is NOT just issue with block names, it also applies e.g. to attribute type names, attribute names and single page names. Basically all the strings that come from the DB.
2. This issue has been previously discussed and there are some (I don't know exactly what) improvements to this in the recent 5.5.0 release
3. There are also still some pull requests in github related to this issue so it might be getting better
At least international developers have started to take closer look into this issue and the solution will be to wrap all those strings inside the t() function, although they come from the database. By doing the strings can be included into the translation templates and therefore they would be translated into each language.
So, shortly: it is still "work in progress" but this is a known issue that will be given a closer look in the near future. Also, they haven't even released the "official translation template" for 5.5.0 yet, so I'm not sure whether they will include those strings already in this version.
**However, I'd still love to hear something about this from the core team because I've only talked about this issue with international developers (outside US) who are not part of the core team.**
Antti / Mainio
2. This issue has been previously discussed and there are some (I don't know exactly what) improvements to this in the recent 5.5.0 release
3. There are also still some pull requests in github related to this issue so it might be getting better
At least international developers have started to take closer look into this issue and the solution will be to wrap all those strings inside the t() function, although they come from the database. By doing the strings can be included into the translation templates and therefore they would be translated into each language.
So, shortly: it is still "work in progress" but this is a known issue that will be given a closer look in the near future. Also, they haven't even released the "official translation template" for 5.5.0 yet, so I'm not sure whether they will include those strings already in this version.
**However, I'd still love to hear something about this from the core team because I've only talked about this issue with international developers (outside US) who are not part of the core team.**
Antti / Mainio
