Can I as an admin enforce the option as well? Because tags are part of the forum experience and without it some users would miss out on extra context about topics. I really like the Horizon theme now with enriched topic details
The part about “Excerpts”, which can be enabled with: Enable with bin/rails r ‘SiteSetting.always_include_topic_excerpts = true’ that doesn’t seem to work for me.
/var/www/discourse# bin/rails r ‘SiteSetting.always_include_topic_excerpts = true’
fatal: detected dubious ownership in repository at '/var/www/discourse'
To add an exception for this directory, call:
git config --global --add safe.directory /var/www/discourse
/var/www/discourse/config/initializers/000-pg_connection_patch.rb:21:in `rescue in new_client': We could not find your database: discourse. Available database configurations can be found in config/database.yml. (ActiveRecord::NoDatabaseError)
To resolve this error:
- Did you not create the database, or did you delete it? To create the database, run:
bin/rails db:create
- Has the database name changed? Verify that config/database.yml contains the correct database name.
I don’t want to mess too much with this. I guess I’ll just leave it as is. But still leaving the error here in case my setup is broken or something in Discourse can be fixed.
Yes, that is the case right now. If you choose the high context options in the theme settings, all users will see this on Horizon. Or do you mean for later? Hmm, having an admin override a user setting wasn’t on the planning and it’s a bit unusual. I suppose we would leave it up to the user if they decide tags are important to them or not. But I think an admin will be able to set the default option probably.
@zogstrip Can you help with the command issue please?
Tags are really an important part of the way my forum works. If users disable it they might not understand the downgrade and don’t understand why others see a different layout. I would prefer that themes are set by admins. Or at least give admins the freedom to grant users this freedom, just like with theme selection. A consistent UI is I think important.
Yes this is how all our user preferences that are set by admins work. Admins can set a default and individual users can override.
If individual sites really really want to stop users setting individual preferences for whatever reason, adding custom CSS to hide the field for them should be enough.
