I am not new to Discourse. I migrated from phpBB to Discourse over on my other car interest site exiges.com.
I have been massively impressed with the steady churn of enhancements that the discourse team have been releasing so I took the plunge and moved my 750k posts , 20k members Xenforo forum across to Discourse.
Using a healthy dose of luck, judgement and AI I wrote an import script to get the data across. I have a self hosted system with AllHost.IO , 8cores and 8GB RAM and it took 37 hrs to migrate.
I came here not really to shout about my site(s) but more to say thanks to the devs. I was a die hard Xenforo fanboy but this platform in my opinion has made the admin side easy and the frequent updates are just brilliant.
The only thing that I can see that might help our users is the change in UI for quotes.
In Discourse we simply reply. The Discourse reply is a non quoted reply but I appreciate we can highlight and the tooltip pops up for quote.
In Xenforo you reply and the original post is quoted. I can appreciate both methods of execution here. It might take some time for our users to understand this.
I had a custom plugin that added an extra few tables and linked in to the main tables to provide a garage, but thats more of a custom development.
I am actively seeking to reduce the amount of third party extensions after being bitten by changes that have broken these addons that I become so reliant on.
Yeah good call. I remember falling into that trap with vB and having to walk away because it was so hacked together that it wasn’t sustainable. When one thing broke, it was like a house of cards.
I want to set the permission at the top level ( imported and Archived Board ) to read only and have the inheritance passed down to the child items.
I dont appear to be able to do that at present so I have to edit 9 children individually. Its not a deal breaker but it would be great to have a parent / child / inheritance option to inherit permissions.
I hear you—we’ve been back and forwards on this a few times and ultimately the decision comes down to safety. Discourse treats every category as its own independent thing, so a sub-category isn’t a permissions “child” of its parent; it’s really just nested for navigation and organisation. We did that because admins often want a sub-category to be deliberately different from the parent.
We settled on a safety net, making it impossible for a sub-category to be less restrictive than its parent to avoid a situation where someone is locked out of a category but is able to see private sub-categories inside it. This way you get full freedom to make child permissions stricter, but you can’t accidentally leak content through a more permissive one.
I appreciate where you are coming from here. I am seeing it from a different angle.
I want consistent permissions. I need to deny a series of categories a write / create permission. I could miss one and leave it open for replies ..
I think if we got the UI and logic right on this it could work. However , its not a deal breaker and I spent my break at work finding each category and removing two ticks …
