mirror of
https://github.com/discourse/discourse.git
synced 2024-11-26 19:23:43 +08:00
edec941a87
This commit introduces a few changes as a result of customer issues with finding why a topic was relisted. In one case, if a user edited the OP of a topic that was unlisted and hidden because of too many flags, the topic would get relisted by directly changing topic.visible, instead of going via TopicStatusUpdater. To improve tracking we: * Introduce a visibility_reason_id to topic which functions in a similar way to hidden_reason_id on post, this column is set from the various places we change topic visibility * Fix Post#unhide! which was directly modifying topic.visible, instead we use TopicStatusUpdater which sets visibility_reason_id and also makes a small action post * Show the reason topic visibility changed when hovering the unlisted icon in topic status on topic titles |
||
---|---|---|
.. | ||
add_topic_to_quotes.rake | ||
admin.rake | ||
annotate.rake | ||
api.rake | ||
assets.rake | ||
auto_annotate_models.rake | ||
autospec.rake | ||
avatars.rake | ||
backfill.thor | ||
categories.rake | ||
cdn.rake | ||
compatibility.rake | ||
db.rake | ||
destroy.rake | ||
dev.rake | ||
docker.rake | ||
documentation.rake | ||
emails.rake | ||
emoji.rake | ||
export.rake | ||
groups.rake | ||
hashtags.rake | ||
i18n.rake | ||
images.rake | ||
import.rake | ||
incoming_emails.rake | ||
integration.rake | ||
javascript.rake | ||
log.rake | ||
maxminddb.rake | ||
plugin.rake | ||
populate.rake | ||
populate.thor | ||
posts.rake | ||
profile.rake | ||
qunit.rake | ||
redis.rake | ||
release_note.rake | ||
revisions.rake | ||
rspec.rake | ||
s3.rake | ||
scheduler.rake | ||
search.rake | ||
site_settings.rake | ||
site.rake | ||
smoke_test.rake | ||
svg_icons.rake | ||
svg_sprites.rake | ||
tags.rake | ||
themes.rake | ||
topics.rake | ||
turbo.rake | ||
typepad.thor | ||
uploads.rake | ||
users.rake | ||
version_bump.rake |