github-mirror/discourse
2
0
Fork 0
mirror of https://github.com/discourse/discourse.git synced 2024-11-29 03:15:48 +08:00
Code Issues Actions 1 Packages Projects Releases Wiki Activity
c468110929
discourse/app/assets/javascripts/admin/addon/templates/site-text-index.hbs

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

76 lines
1.9 KiB
Handlebars
Raw Normal View History

FEATURE: Can override any translation via an admin interface
2015-11-24 05:45:05 +08:00
<div class="search-area">
<p>{{i18n "admin.site_text.description"}}</p>
UX: Remove confusing fallback locale warning (#18096)
2022-08-26 07:22:04 +08:00
<TextField
@value={{this.q}}
@placeholderKey="admin.site_text.search"
@class="no-blur site-text-search"
@autofocus="true"
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
@key-up={{this.search}}
UX: Remove confusing fallback locale warning (#18096)
2022-08-26 07:22:04 +08:00
/>
Support for "Only show overridden" in site text customization
2015-12-01 04:22:58 +08:00
FEATURE: Locale support for seeded categories and topics (#7110)
2019-03-19 04:09:13 +08:00
<div class="reseed">
UX: Remove confusing fallback locale warning (#18096)
2022-08-26 07:22:04 +08:00
<DButton
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
@action={{this.showReseedModal}}
UX: Remove confusing fallback locale warning (#18096)
2022-08-26 07:22:04 +08:00
@label="admin.reseed.action.label"
@title="admin.reseed.action.title"
@icon="sync"
DEV: Update DButton uses (#23333) 1. Use `this.` instead of `{{action}}` where applicable 2. Use `{{fn}}` instead of `@actionParam` where applicable 3. Use non-`@` versions of class/type/tabindex/aria-controls/aria-expanded 4. Remove `btn` class (it's added automatically to all DButtons) 5. Remove `type="button"` (it's the default) 6. Use `concat-class` helper
2023-08-31 17:49:35 +08:00
class="btn-default"
UX: Remove confusing fallback locale warning (#18096)
2022-08-26 07:22:04 +08:00
/>
FEATURE: Locale support for seeded categories and topics (#7110)
2019-03-19 04:09:13 +08:00
</div>
<p class="filter-options">
UX: Text customization for different languages. (#11729) Admins can now edit translations in different languages without having to change their locale. We display a warning when there's a fallback language set.
2021-01-19 01:53:45 +08:00
<div class="locale">
<label>{{i18n "admin.site_text.locale"}}</label>
UX: Remove confusing fallback locale warning (#18096)
2022-08-26 07:22:04 +08:00
<ComboBox
@valueProperty="value"
@content={{this.availableLocales}}
@value={{this.locale}}
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
@onChange={{this.updateLocale}}
UX: Remove confusing fallback locale warning (#18096)
2022-08-26 07:22:04 +08:00
@class="locale-search"
@options={{hash filterable=true}}
/>
UX: Text customization for different languages. (#11729) Admins can now edit translations in different languages without having to change their locale. We display a warning when there's a fallback language set.
2021-01-19 01:53:45 +08:00
</div>
DEV: Remove `d-checkbox` component Replaces the last occurrence of `d-checkbox` with a regular input element. Includes a minor refactor of admin site text search.
2019-02-21 22:54:54 +08:00
<label>
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
<input
FEATURE: Warn about outdated translation overrides in admin dashboard (#22384) This PR adds a feature to help admins stay up-to-date with their translations. We already have protections preventing admins from problems when they update their overrides. This change adds some protection in the other direction (where translations change in core due to an upgrade) by creating a notice for admins when defaults have changed. Terms: - In the case where Discourse core changes the default translation, the translation override is considered "outdated". - In the case above where interpolation keys were changed from the ones the override is using, it is considered "invalid". - If none of the above applies, the override is considered "up to date". How does it work? There are a few pieces that makes this work: - When an admin creates or updates a translation override, we store the original translation at the time of write. (This is used to detect changes later on.) - There is a background job that runs once every day and checks for outdated and invalid overrides, and marks them as such. - When there are any outdated or invalid overrides, a notice is shown in admin dashboard with a link to the text customization page. Known limitations The link from the dashboard links to the default locale text customization page. Given there might be invalid overrides in multiple languages, I'm not sure what we could do here. Consideration for future improvement.
2023-07-10 10:06:40 +08:00
id="toggle-overridden"
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
type="checkbox"
checked={{this.resolvedOverridden}}
{{on "click" this.toggleOverridden}}
UX: Remove confusing fallback locale warning (#18096)
2022-08-26 07:22:04 +08:00
/>
DEV: Remove `d-checkbox` component Replaces the last occurrence of `d-checkbox` with a regular input element. Includes a minor refactor of admin site text search.
2019-02-21 22:54:54 +08:00
{{i18n "admin.site_text.show_overriden"}}
</label>
FEATURE: Warn about outdated translation overrides in admin dashboard (#22384) This PR adds a feature to help admins stay up-to-date with their translations. We already have protections preventing admins from problems when they update their overrides. This change adds some protection in the other direction (where translations change in core due to an upgrade) by creating a notice for admins when defaults have changed. Terms: - In the case where Discourse core changes the default translation, the translation override is considered "outdated". - In the case above where interpolation keys were changed from the ones the override is using, it is considered "invalid". - If none of the above applies, the override is considered "up to date". How does it work? There are a few pieces that makes this work: - When an admin creates or updates a translation override, we store the original translation at the time of write. (This is used to detect changes later on.) - There is a background job that runs once every day and checks for outdated and invalid overrides, and marks them as such. - When there are any outdated or invalid overrides, a notice is shown in admin dashboard with a link to the text customization page. Known limitations The link from the dashboard links to the default locale text customization page. Given there might be invalid overrides in multiple languages, I'm not sure what we could do here. Consideration for future improvement.
2023-07-10 10:06:40 +08:00
<label>
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
<input
FEATURE: Warn about outdated translation overrides in admin dashboard (#22384) This PR adds a feature to help admins stay up-to-date with their translations. We already have protections preventing admins from problems when they update their overrides. This change adds some protection in the other direction (where translations change in core due to an upgrade) by creating a notice for admins when defaults have changed. Terms: - In the case where Discourse core changes the default translation, the translation override is considered "outdated". - In the case above where interpolation keys were changed from the ones the override is using, it is considered "invalid". - If none of the above applies, the override is considered "up to date". How does it work? There are a few pieces that makes this work: - When an admin creates or updates a translation override, we store the original translation at the time of write. (This is used to detect changes later on.) - There is a background job that runs once every day and checks for outdated and invalid overrides, and marks them as such. - When there are any outdated or invalid overrides, a notice is shown in admin dashboard with a link to the text customization page. Known limitations The link from the dashboard links to the default locale text customization page. Given there might be invalid overrides in multiple languages, I'm not sure what we could do here. Consideration for future improvement.
2023-07-10 10:06:40 +08:00
id="toggle-outdated"
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
type="checkbox"
checked={{this.resolvedOutdated}}
FEATURE: Warn about outdated translation overrides in admin dashboard (#22384) This PR adds a feature to help admins stay up-to-date with their translations. We already have protections preventing admins from problems when they update their overrides. This change adds some protection in the other direction (where translations change in core due to an upgrade) by creating a notice for admins when defaults have changed. Terms: - In the case where Discourse core changes the default translation, the translation override is considered "outdated". - In the case above where interpolation keys were changed from the ones the override is using, it is considered "invalid". - If none of the above applies, the override is considered "up to date". How does it work? There are a few pieces that makes this work: - When an admin creates or updates a translation override, we store the original translation at the time of write. (This is used to detect changes later on.) - There is a background job that runs once every day and checks for outdated and invalid overrides, and marks them as such. - When there are any outdated or invalid overrides, a notice is shown in admin dashboard with a link to the text customization page. Known limitations The link from the dashboard links to the default locale text customization page. Given there might be invalid overrides in multiple languages, I'm not sure what we could do here. Consideration for future improvement.
2023-07-10 10:06:40 +08:00
{{on "click" this.toggleOutdated}}
/>
{{i18n "admin.site_text.show_outdated"}}
</label>
FEATURE: Locale support for seeded categories and topics (#7110)
2019-03-19 04:09:13 +08:00
</p>
FEATURE: Can override any translation via an admin interface
2015-11-24 05:45:05 +08:00
</div>
No implicit this codemod (#17235) * Run no-implicit-this codemod for app templates * Run tagless-ember-components-codemod for plugins * Turn on no-implicit-this lint
2022-07-06 01:41:31 +08:00
<ConditionalLoadingSpinner @condition={{this.searching}}>
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
{{#if this.model.extras.recommended}}
FEATURE: Can override any translation via an admin interface
2015-11-24 05:45:05 +08:00
<p><b>{{i18n "admin.site_text.recommended"}}</b></p>
Support for "Only show overridden" in site text customization
2015-12-01 04:22:58 +08:00
{{/if}}
FEATURE: Can override any translation via an admin interface
2015-11-24 05:45:05 +08:00
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
{{#each this.model as |siteText|}}
UX: Remove confusing fallback locale warning (#18096)
2022-08-26 07:22:04 +08:00
<SiteTextSummary
@siteText={{siteText}}
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
@editAction={{this.edit}}
UX: Remove confusing fallback locale warning (#18096)
2022-08-26 07:22:04 +08:00
@term={{this.q}}
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
@searchRegex={{this.model.extras.regex}}
UX: Remove confusing fallback locale warning (#18096)
2022-08-26 07:22:04 +08:00
/>
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
{{else}}
{{i18n "admin.site_text.no_results"}}
FEATURE: Can override any translation via an admin interface
2015-11-24 05:45:05 +08:00
{{/each}}
FIX: Text content search warning if more than 50 results
2019-03-09 05:13:10 +08:00
DEV: Modernize admin-site-text route/controller (#23581) - Switch to `@tracked` and native getters - Remove queryParam defaults which are awkward to work with. Instead, add `resolvedBlah` getters - Add 'no results found' text - Use standard 'model' key instead of a custom `setupController` method - Remove use of `route-action` - Remove `{{action` helper Default queryParams in ember controllers are tricky to work with, especially when combined with the new router service. Instead, we can handle defaults ourselves
2023-09-14 18:27:09 +08:00
{{#if this.model.extras.has_more}}
FIX: Text content search warning if more than 50 results
2019-03-09 05:13:10 +08:00
<p class="warning">{{i18n "admin.site_text.more_than_50_results"}}</p>
{{/if}}
DEV: Run angle-brackets codemod (#17286) Co-authored-by: Peter Wagenet <peter.wagenet@gmail.com>
2022-06-30 18:30:50 +08:00
</ConditionalLoadingSpinner>
Reference in New Issue Copy Permalink