### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [3월 18, 2019, 9:51오후 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/1 "2019-03-18T21:51:09Z")
Discourse ships with a couple of categories and topics, but they usually are in English. No matter what language your forum is using. That is going to change.
Up until now configuring `DISCOURSE_DEFAULT_LOCALE` in `app.yml` was the only way to change that. And you had to do it before bootstrapping the container.
## Wizard
Changing the default language in the wizard will automatically translate all seeded categories and topics as long as you didn’t already edit them manually.
## Manual update
You can find a new “Replace Text…” button in the “Admin \> Customize \> Text Content” section (`/admin/customize/site_texts`). Clicking on it brings up a dialog where you can select the content you’d like to update.
The dialog shows you only the categories and topics it could find. Some might be missing if you manually deleted any of them or when your forum was created a long time ago, because we didn’t keep track of “Welcome topics” in the past.
Clicking “Replace” will update the selected content with the latest translations for the current `default locale`. It will create new revisions for updated posts, so you will be able to see the diff and revert changes in the post’s revision history.
## Rake task
The old rake task for updating some topics (FAQ, Terms of Service, Privacy Policy) has been replaced by a new one:
```plaintext
./launcher enter app
rake i18n:reseed[locale]
```
⚠ It updates all seeded categories and topics _without checking_ if you manually edited them or not. So be careful!
## Notes
There are currently no translations for the “Admin Quick Start Guide”, but I’m planning to make it translatable in the near future. Stay tuned.
And here’s the commit in case you are interested: [FEATURE: Locale support for seeded categories and topics (#7110) · discourse/discourse@3fd04df · GitHub](https://github.com/discourse/discourse/commit/3fd04df781f1cb736228e3212ef79ab2ee20326e)
---
### Author:  [@neemiasvf](https://meta.discourse.org/u/neemiasvf)
#### Post date: [3월 18, 2019, 10:01오후 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/2 "2019-03-18T22:01:56Z")
Are the translations for these assets also on Transifex? I look forward to making these changes, but if the translation is just as reliable as the rest of the site… oh boy…
I’ve been translating, reviewing and proofreading everything from scratch on Transifex for the last couple of weeks now, and if this is also there, it’d be perfect. 🙂
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [3월 18, 2019, 11:03오후 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/3 "2019-03-18T23:03:07Z")
No, assets aren’t localized. Transifex doesn’t support that. ☹ But the seeded topics use only [one image](https://github.com/discourse/discourse/blob/master/public/images/welcome/discourse-edit-post-animated.gif) with English text in it. I guess we can live with that for know.
---
### Author:  [@neemiasvf](https://meta.discourse.org/u/neemiasvf)
#### Post date: [3월 18, 2019, 11:34오후 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/4 "2019-03-18T23:34:29Z")
Well, then where are the translations? I can’t see to find them on Github…
Only found the one in English:
>
---
### Author:  [@awesomerobot](https://meta.discourse.org/u/awesomerobot)
#### Post date: [3월 19, 2019, 12:15오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/5 "2019-03-19T00:15:54Z")
> [@neemiasvf](#):
>
> Well, then where are the translations? I can’t see to find them on Github…
Oh by assets did you mean the text of the translations? I think @gerhard assumed you meant images.
Check the note in the original post:
> [@gerhard](#):
>
> ## Notes
>
> There are currently no translations for the “Admin Quick Start Guide”, but I’m planning to make it translatable in the near future. Stay tuned.
---
### Author:  [@neemiasvf](https://meta.discourse.org/u/neemiasvf)
#### Post date: [3월 19, 2019, 12:52오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/6 "2019-03-19T00:52:06Z")
Yes, by “assets” I mean the actual text. Sorry about that. 😕
I did a bit of research and found them on Transifex. Those specific docs will be huuuge to translate. God help me. 😛
As for the **actual assets** , yes, I guess we can live with that forever haha. There’s no need to localize them. Like, ever.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [3월 19, 2019, 2:00오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/7 "2019-03-19T02:00:33Z")
> [@gerhard](#):
>
> Reseed…
This text is somewhat confusing to me, @codinghorror can you think of something better?
Maybe `Reset Seeded Translations...`/ `Reset Translations...` ?
Interestingly if we go with `Reset Translations...` we can use the same dialog to reset overrides in bulk.
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [3월 19, 2019, 2:13오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/8 "2019-03-19T02:13:07Z")
I think there is a lot of value in a “reset all translations”, though I guess technically it would be “reset all text”?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [3월 19, 2019, 2:22오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/9 "2019-03-19T02:22:54Z")
We could possibly give up this button altogether and only trigger the UI when you switch “default locale” on the site.
So if you HAD to reseed you could flick to french, ignore … flick to english?
---
### Author:  [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [3월 19, 2019, 3:22오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/10 "2019-03-19T03:22:22Z")
I think “reset all customized text” is still a good idea.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [3월 19, 2019, 3:25오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/11 "2019-03-19T03:25:59Z")
Assuming that these documents will continue to evolve in places would ‘refresh’ be a better word? They aren’t necessarily going to revert, right?
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [3월 19, 2019, 3:43오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/12 "2019-03-19T03:43:59Z")
> [@Stephen](#):
>
> They aren’t necessarily going to revert, right?
I think they are going to revert, but need @gerhard to confirm, I think it takes whatever text is in the various topics and overwrites with what we have in core. It would remove all the changes you made to the TOS and so on.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [3월 19, 2019, 3:47오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/13 "2019-03-19T03:47:06Z")
I get what’s happening, but my point is that if I build a site in 2014 and customise the ToS, and in the five years which follow the model ToS in core updated, then that button isn’t reverting it to the original ToS I had, it’s replacing it with a model document which is five years newer.
It’s being replaced, maybe refreshed, but not reset.
---
### Author:  [@sam](https://meta.discourse.org/u/sam)
#### Post date: [3월 19, 2019, 3:48오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/14 "2019-03-19T03:48:03Z")
Yes it is … one thing we should confirm here is that the replacement is done as an edit, at least that way you have a chance of recovering the diff.
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [3월 19, 2019, 2:13오후 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/15 "2019-03-19T14:13:59Z")
> [@sam](#):
>
> We could possibly give up this button altogether and only trigger the UI when you switch “default locale” on the site.
I thought about doing that, but I didn’t want to add a special case in the site settings code just for `default_locale` and triggering the reseed manually without changing the locale can be useful in other situations as well. For example: Replacing topics with new text shipped in core like we did with the ToS a few months ago.
I did add a link to the site setting’s description:
And the wizard automatically reseeds everything when the language is changed.
> [@Stephen](#):
>
> It’s being replaced, maybe refreshed, but not reset.
I like “replace” and “refresh”… I knew “reseed” was too technical and probably isn’t even a real word, but I couldn’t think of something better. 😊
> [@sam](#):
>
> one thing we should confirm here is that the replacement is done as an edit, at least that way you have a chance of recovering the diff.
Yes, it’s creating a new revision.
---
### Author:  [@Usman\_Shahid](https://meta.discourse.org/u/Usman_Shahid)
#### Post date: [12월 21, 2021, 7:38오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/18 "2021-12-21T07:38:48Z")
> [@gerhard](#):
>
> ```plaintext
> ./launcher enter app
> rake i18n:reseed[locale]
>
> ```
@gerhard 이 rake 명령어를 사용하여 faq, tos, 그리고 개인정보처리방침 페이지를 재생성하고 있습니다. 하지만 해당 페이지에 접근하면 404 오류가 발생합니다. 다음과 같이 명령어를 실행해 보았습니다.
```plaintext
rake i18n:reseed[en]
```
그리고
```plaintext
rake i18n:reseed["en"]
```
제 기본 로케일은 영어(미국)입니다. 원래 페이지들은 이미 오래전에 삭제되었으므로 재생성이 필요합니다.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [12월 21, 2021, 11:05오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/19 "2021-12-21T11:05:02Z")
제 생각에는 해당 페이지를 수동으로 만드는 것이 좋겠습니다. 여기, [try.discourse.org](http://try.discourse.org), 새 사이트에서 복사하거나, 해당 페이지에 포함되어야 할 항목에 대한 가이드라인을 구글에서 검색해 볼 수 있습니다.
---
### Author:  [@gerhard](https://meta.discourse.org/u/gerhard)
#### Post date: [12월 21, 2021, 12:37오후 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/20 "2021-12-21T12:37:35Z")
이 내용으로 올바른 방향으로 안내할 수 있을 것입니다.
> [@How to regenerate FAQ and TOS pages?](https://meta.discourse.org/t/how-to-regenerate-faq-and-tos-pages/110625/2?u=gerhard):
>
> Interesting. How did you manage to delete those topics? You shouldn’t be allowed to delete them in the UI. First, let’s see if the topics are really gone. ./launcher enter app rails c Topic.with\_deleted.exists?(SiteSetting.guidelines\_topic\_id) Topic.with\_deleted.exists?(SiteSetting.tos\_topic\_id) If the topics are really gone, create two new topics in the Staff category and assign the topic ids in the rails console to the site settings. SiteSetting.guidelines\_topic\_id = 4711 # replace with t…
---
### Author:  [@JammyDodger](https://meta.discourse.org/u/JammyDodger)
#### Post date: [7월 25, 2022, 7:23오전 UTC](https://meta.discourse.org/t/update-seeded-categories-and-topics/111963/21 "2022-07-25T07:23:00Z")
게시물 2개가 기존 주제에 병합되었습니다: [Discourse 설정 - 소개 페이지](https://meta.discourse.org/t/discourse-setup-about-page/233832/4)