81c7d6a462
When the tag is muted and topic contains that tag, we should not mark that message as NEW. There are 3 possible settings which site admin can set. remove_muted_tags_from_latest - always It means that if the topic got at least one muted tag, we should not mark that topic as NEW remove_muted_tags_from_latest - only muted Similar to above, however, if at least one tag is not muted, the topic is marked as NEW remove_muted_tags_from_latest - never Basically, mute tag setting is ignored and all topics are set as NEW |
||
|---|---|---|
| .. | ||
| admin | ||
| admin-login | ||
| discourse | ||
| discourse-common | ||
| docs | ||
| ember-addons | ||
| locales | ||
| pretty-text | ||
| select-kit | ||
| wizard | ||
| activate-account.js.no-module.es6 | ||
| admin.js.erb | ||
| application.js | ||
| auto-redirect.js.no-module.es6 | ||
| deprecated.js | ||
| discourse-loader.js | ||
| discourse-objects.js | ||
| discourse.js.es6 | ||
| embed-application.js.no-module.es6 | ||
| ember_include.js.erb | ||
| ember_jquery.js | ||
| ember-shim.js | ||
| env.js | ||
| google-tag-manager.js.no-module.es6 | ||
| google-universal-analytics.js.no-module.es6 | ||
| main_include_admin.js | ||
| markdown-it-bundle.js | ||
| onpopstate-handler.js.no-module.es6 | ||
| polyfills.js | ||
| preload-application-data.js.no-module.es6 | ||
| preload-store.js.es6 | ||
| pretty-text-bundle.js | ||
| print-page.js | ||
| service-worker.js.erb | ||
| set-prototype-polyfill.js | ||
| template_include.js.erb | ||
| vendor.js | ||
| wizard-application.js | ||
| wizard-start.js.no-module.es6 | ||
| wizard-vendor.js | ||