I learned about Discourse when I signed up for the Hugo.io forum. Then I signed up for this one, and saw that my profile is not universal, and that I have to copy it from site to site. Other topics led me to this category, and I am just wondering what is the status. Does the hub concept exist today? I for one, think it's a great idea if it's technically possible.
I noticed that on the top page of meta, I see my custom uploaded avatar in the list next to a post I made. However when I click the topic, I see the avatar from my Gravatar, which was present when I first signed up.
I am using my current discourse instance on sub-domain. I don't want to use SSO for user login/signup as i want to use discourse inbuilt login/signup mechanism only.
What i want is as soon user click login/signup button on my main domain page user will redirect to sub.discourse.org/login page(which is on discourse sub-domain) and as soon user login/signup successfully done it will redirect to my main domain page which i specify.
Hi, Right now i'm having Domain (A) on which website is running and sub-domain (B) on which discourse instance is running, what i thinking of is there any way that as soon as user login or signup on sub-domain (B) it will send callback to Domain (A) from which i'll able to identify that user is authorized?
When granting a new badge to a user (admin/users/$user/badges), the badges aren't sorted in any apparent order.
I expected some sort of alphabetical sorting, but that doesn't appear to be the case. Neither are badges in the same group put together, which is another sorting candidate.
My idea here is too good to pass up. Had to open a new thread to get feedback.
Basically, it expands on @codinghorror's idea that the OP meta bar is a map of the conversation and thus helps the reader understand visually what to expect below.
Here's my ideas that relate to the concept of a "topic map":
1. Include images and videos below the topic's posted links. This could be a simple small-thumbnail gallery. The thumbs can be all one specific size and ratio (cropping). Videos can be included with this gallery but the thumbnail would be an image, not the actual video.
Clicking the thumbnail auto-jumps the browser to the reply it first appeared in. That allows a reader to get immediate context on why it was posted in the first place. If they want to see the bigger size or watch the video, they only need to click on it as usual in the reply, then follow the replies after it for future conversation and context.
2. Expand on the link map by offering links to the replies they first appeared in within the thread. This can be done with a simple text arrow such as ˅ which visually points down into the replies of the topic. This is in direct relation to the references section of any Wikipedia article. The very first thing shown is an up arrow ˄ which links to where it was mentioned and cited.
As per @codinghorror's suggestion, I started working on a "Features Highlight" page before the holidays kicked in. The final stretch has been put off for a while due to other commitments, but I finally got around to finishing it today.
Like the video, it's pretty rough and serves primarily as a proof-of-concept. I'd be happy to work as a gif-monkey (and possibly copywriter) together with @awesomerobot to make a polished page for v1.2.
My personal goal is to maintain a clearly communicated version timeline for every major Discourse release.
Is there a way to remove the upload option for images? We didn't want to "host" images on our forums. We'd rather the end users just put the image link in.
If this isn't an option, is there a way to hide the image upload button? (CSS?)
Hi, on my website recently everytime someonr tries to create a post/topic, it comes up with the 500 internal server error. does anyone know how to fix this, as it kind of ruins the point of my website. Thanks
Some of my users have expressed confusion at the blue + New Topic button, which is what you select to submit your new topic after you have written it. It is identical to the button you push to start the new topic in the first place, and they spent some time hunting around for the button to submit the form. The suggestion is to rename this to "post new topic" or some such. Same thing for replies.
To quote:
Just a small suggestion - I think it is confusing that the button to post a new topic (below the text box where you write the new topic) is labelled '+ New Topic' - could we change it to 'Post New Topic' perhaps?
It's just that it looks the same as the button you press to start working on a new topic - the first few times I posted a new topic I didn't realize that it was the post button and spent a while searching around before I realized. And then yesterday, [another colleague] did the same thing. Is there a way to change it easily so it says 'Post' or 'Post Topic' perhaps? If not, I'm sure we'll learn the habit, but I just worry that other new users will also find it confusing...
Discourse v1.2.0.beta4 Appears on Safari, Chrome, Firefox
The logged out view of http://forum.cocos2d-swift.org/ is displaying [en.undefined] instead of the appropriate strings for the Log In and Sign Up buttons. See screenshot below. This is not occurring with our other Discourse forums.
I'd be interested in a feature to disable the auto-update on the main page - the feature where the topic list page will periodically check for new activity and, if found, add an update count to the page title and a bar at the top of the topic list reading "x or new updated topics. Click to show". I suppose a checkbox in the settings, enabled by default, that could be disabled to stop the behavior.
I have some experience in Rails and JS development, and I'm willing to write it myself if the Discourse team would be open to a pull request.
Personally, I find it distracting to my usual forum workflow. I like to keep a forum main page open in a tab while I work, with a couple of topics that sound interesting open in other tabs, and periodically check on them. If the forum has any decent activity level, then the update counter is constantly updating and beckoning me to check/refresh it again. I'd like to be able to have it remain static until I explicitly refresh the page.
I'm working on improving a full text postgres search and decided to have a peek through Discourse's implementation, since our use cases are very similar.
Was wondering if any devs (or otherwise knowledgeable persons) might have some insight into the logic behind Discourse search (which, I have to admit, is much more logic-heavy than I was expecting it to be.)
Some specific questions:
Why the differentiation between a Post and its PostSearchData (ie, why is just putting the ts_vector column straight onto the Post a bad idea?)
What's the reasoning behind having separate SearchData classes for each searchable type (PostSearchData, CategorySearchData, etc.), instead of making it a polymorphic relationship? (ie a searchable has_one search_data) Would the resulting generic SearchData table be too massive to work with?
I see there's a need to occasionally reindex the search (using the rebuild_problem_posts method); why is that? Does the search data go off over time for some reason?
Any other specific things to be aware of while putting a search like this together?
I'm having an issue with a discount kitchen spammer. They keep changing the ip and email address however the content of the message is always the same. Is there some way to just instant ban them if they link to the spam website?