Just was thinking that some communities might benefit from an acronym expander. i.e., Automatically create a link when a matched acronym or other term appears in a post that would give a hover tip or other such UI junk that would explain what the term means.
We probably wouldn't use this because we try hard to avoid jargon, but I've seen it elsewhere and found it useful. So maybe someone will be interested in picking this up and running with it.
After changing the min post length setting in admin...
... What is required for users to see this change take effect?
Background
At specific times we have "meetings" at these times in a few topics we find the minimum post length actually hinders conversation.
So when these meetings occur I want to reduce the minimum post length requirement to say 2... ...(it would be nice if I could do this per topic or category etc - but it's not available as an option)...
It seems changing this value doesn't take effect immediately.
Is a server rebuild / restart required?
Or just that all users need to close browsers and open again?
Create a topic and make the lead post a wiki post.
Optionally add some replies.
Lock the topic.
Expected Results:
It is no longer possible to edit the wiki post.
Actual Results:
It IS possible to edit the wiki post.
While it's still possible to remove the wiki option from the post in the locked topic, if I assumed that locking the topic would prevent edits to the wiki post, I figure maybe I'm not the only one. (But history has shown that's often wrong!)
On a new forum (50 topics atm), i see the similar topic box to be empty pretty often. I'm not sure what's the algorithm for displaying that, but i think it should be hidden if there are no results, no?
…on the console - filled with all the stuff I was waiting for! Is Discourse trying to do something funny with my data, does it have to be in a special format, rendered specifically?
I use SSO, and at sign-up on my main site, my users get a new account on Discourse. Since yesterday only 1 user have been created (which is wrong). I just checked my error log and it says a lot of stuff like this:
ActiveRecord::RecordInvalid: Validation failed: Signup is not allowed from this account. in users#sync_sso ActiveRecord::RecordInvalid (Validation failed: Signup is not allowed from this account.)
I didn't change anything. My users sign up on my own site, and I use an API call with my admin user (and his API-key) to sync them. I've been fine until last night, getting ~50 users per day.
Can I do anything?
EDIT: It's the call to /admin/users/sync_sso that fails, all of a sudden. Hasn't worked for 20 hours. However, when the user clicks "Login" he is redirected, authenticated then redirecetd back, the users is created and is then logged in. It's only the /admin/users/sync_sso-call that fails.
@sam How do you specify them as admins in your SSO payload? I'd like to do this and it seems like it's possible but I'm not clear on what to include in my payload to make it happen.
This idea fixes a small ux issue, but when you load a discourse forum with a cold cache, there is a small moment when you can see the image loading (depending upon your hosting setup, it can take longer or shorter amounts of time). It would be nice if Discourse preloaded both header images in the background, so by the time a user scrolls, they don't see the loading part.
You can see it on meta if you clear the cache, but your CDN loads so fast it isn't very noticable. On my hosted copy, it takes longer to load and is thus more noticeable.
Other images that are easy to see being used on the site should probably also be preloaded, but I'm not sure how you would find those. Most of them, I'd imagine, are probably used right away anyways.
So We have a category that has a scrolling background of an image. Our company logo is getting lost in the colors, and we want it to remain white as it is on the main page. The main header (not the tiny one that just says "so and sos discourse" Is adopting the background image. How can I keep the background image but ensure that it doesn't replace the white header background at the top of our page?
Imported a big forum 2.500.000 posts, many categories, etc.
When scrolling down in some categories and the system tries to load more topics, I am getting a 500 server error on console. Out of memory? any ideas appreciated.
I have a Discourse installation installed on DO via docker. What's best practice for moving the installation to a new droplet? I'd assume just create an image from the droplet, kill the droplet, spin up new droplet from the saved image. Or is there a better way to do it?
My use case is: I want to have backups of my droplet, which means i need a new droplet as they can only be toggled on with new droplets, and not on existing droplets AFAIK. Also, I want to make sure I don't lose any data acquired so far from the Discouse installation.