Richie

@Richie@meta.discourse.org

This is a remote user, information on this page may be incomplete. View at Source ↗

⁨Comment⁩ on ⁨Introducing nested replies⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

Image markvanlan:

I chose not to convert historical topics in a category when it is enabled, is that users are likely going to interact differently

Image markvanlan:

I worry that admins will enable it for historical topics and then suddenly the conversation is unreadable

Interesting…

Does this suggest it should be tested in our communities in isolation first, before we all pull the trigger and convert every existing topic? :thinking:

Image markvanlan:

The easiest change I can think of is when the category setting is toggled, we have a modal popup saying “do you want to apply this to existing topics?”

That’d work, providing it supported tens of thousands of topics.

But it’d need to be made very clear that there is no coming back from this :sweat_smile:

Will this feature be implemented here on meta first, or on https://try.discourse.org so we can test it outside of our production environments?
⁨Comment⁩ on ⁨Introducing nested replies⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:
Ok, not sure how viable the bulk-toggle might be for categories with tens of thousands of topics. Might rails bulk / batch conversion jobs be option? :thinking:

And is this reversible? Can a threaded topic be converted back to a flat topic?
⁨Comment⁩ on ⁨Introducing nested replies⁩ ⁨⁨4⁩ ⁨weeks⁩ ago⁩:

Image markvanlan:

When nesting is enabled for a category, pre-existing topics stay in flat mode. Each topic can individually toggled from the admin wrench, but there is currently no way to convert an existing category to nested mode.

Can existing topics be bulk-changed / updated via the Select Posts > Bulk Actions options?

Or are there any rails console options to bulk-update all existing topics?