Cannot remove a culture in Resource strings

George Tselios asked on March 10, 2020 18:13

Dear Sirs,

We are developing a new portal using Kentico MVC v12.0.51. Initially our portal was setup to use two cultures: Greek (el-GR) and English (en-US). Also, we have entered several Resource strings in the Localization application both in Greek (el-GR) and English (en-US).

Currently we needed to change the English culture from en-US to en-GB. As far as the web site is concerned, we removed the initial culture (en-US) and added a the new one (en-GB). Since there was no content in English language, we did not face any problem.

On the other hand, in the Resource strings of the Localization application, we cannot remove the English (en-US) culture. We tried to set the en-GB culture as a UI Culture, but nothing changed. Also, when we select the en-GB culture in the drop-down of the upper right side of the Resource strings, we get the message: "The system does not contain a localization pack for the selected culture. You can download additional localization packs from http://devnet.kentico.com/download/localization-packs", but there is no language pack for the en-GB culture.

Now we must enter the Resource strings in three cultures (el-GR, en-GB and en-US) and moreover the en-US culture is the required one.

Please advise on how to resolve this issue. Is this a bug of Kentico Admin?

Thanks in advance,

George

Correct Answer

Juraj Ondrus answered on March 11, 2020 13:23

Copy the resx file and rename it as mentioned above, to contain the culture code and it should do the trick.

0 votesVote for this answer Unmark Correct answer

Recent Answers

Brenden Kehren answered on March 10, 2020 19:56

You need to make a few changes:

Settings > Content > Multilingual > Default content culture
Sites > your site > Cultures > Default content culture

This should get you past the problem you're having now.

0 votesVote for this answer Mark as a Correct answer

George Tselios answered on March 11, 2020 10:27

Dear Brenden,

I followed your suggestions, but still nothing is changed.

Currently all Resource strings that were initially inserted for the en-US culture still remain in the system and there is no way to remove them. Also the default culture is still en-US, which means the any new Resource string must be entered in en-US culture (at least).

Is there any other setting that I need to configure?

Regards,

George

0 votesVote for this answer Mark as a Correct answer

Juraj Ondrus answered on March 11, 2020 13:05

For the missing localization package - I believe that US and GB are very close languages so what you can do is to just copy and re-name the default cms.resx file to "custom.en-gb.resx". For the default UI culture, you may want to use the CMSDefaultUICulture web.config key:

< add key="CMSDefaultUICulture" value="en-gb"/>

and in this case, you do not need to rename the resx file - as described above or as described in the key description in docs. English will still be English so you can use the same CMS.resx file.

0 votesVote for this answer Mark as a Correct answer

Brenden Kehren answered on March 11, 2020 13:07

George are you talking about the front facing website culture or the Kentico UI culture?

0 votesVote for this answer Mark as a Correct answer

George Tselios answered on March 11, 2020 13:20

Hi Juraj and Brenden,

I followed Juraj's suggestion and added the appSetting in the web.config file of the Admin and the en-US version of the Resource strings was removed (or is not visible any more).

Now, we have the el-GR and the en-GB cultures for inserting Resource strings, which was what we needed.

On the other hand we still get the "The system does not contain a localization pack for the selected culture. You can download additional localization packs from http://devnet.kentico.com/download/localization-packs" message in the Resource strings area. Can we do something to remove this message because it will be frustrating for the authors?

@Brenden: We were talking about the web site cultures and resource strings. As it seems the default culture (in regards to Resource strings) is configured by the Admin application, even if you do not want to use it in the web site application.

Regards, George

0 votesVote for this answer Mark as a Correct answer