I’m not complaining or want this to be changed. I just want to post this, so that if it is actually the case, then it might be useful.
It seems like when there are new or unread posts/threads, there is displayed a different sentence at the bottom of the thread page. In those situations, it is displayed similar to this:
So this can be useful if your Notification settings are set up in a certain way (all new posts tracked). However, with most Notification settings, you still have to go between the Unread and New pages to read them all—and most importantly, from this, you can’t access new untracked posts in all categories.
If all the unread posts and new threads have been read, this is displayed:
Of which it is possible to go to the Latest page to see all new untracked posts.
Therefore…
When there are new threads or unread tracked posts, the sentence doesn’t work well for untracked posts.
It works okay if new posts aren’t automatically tracked, but you can’t disable notifications for new threads, so the first issue comes back in this case.
If all new posts are tracked, then you are left with always being forced to use the Unread and New pages, since you can only access the Latest page when everything has been read.
Again, I’m not complaining or asking to change this. I’m only pointing it out. Feel free to use this as you see fit.
Solution: Always have the ‘or view latest topics’ part.
Some users tend to keep Discourse opened for weeks/months. Unfortunately, users get a “network error” when they are trying to browse the forum with an expired session.
I can easily reproduce this behavior by setting the session expiry time to 1 hour, wait 1 hour and try to open my profile or a topic… Eventually i would get this network error issue.
From my perspective, we should redirect the users to the login/sso page when their session is expired. Is there anyway to achieve that?
What will happen if I enable badge on a site that is 7 months old?
Will it start to count things “starting from today” or will it give badges to folks for the efforts they have done in the past? If the latter is true, then the users will be getting lots of badges in one go - correct?
For diagnosis i referred to the link mentioned below :
This my snap shot of app.yml
TODO: The SMTP mail server used to validate new accounts and send notifications
DISCOURSE_SMTP_ADDRESS: md-in-63.webhostbox.net
DISCOURSE_SMTP_PORT: 587
DISCOURSE_SMTP_USER_NAME: xyz@email.com
DISCOURSE_SMTP_PASSWORD: "–"
DISCOURSE_SMTP_ENABLE_START_TLS: true # (optional, default true)
DISCOURSE_SMTP_AUTHENTICATION: "login"
DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none
I have added last 2 lines i.e. DISCOURSE_SMTP_AUTHENTICATION and DISCOURSE_SMTP_OPENSSL_VERIFY_MODE later and rebuild the app by the command ./launcher rebuild app
Then I did the telnet as guided
I did the tail of the logs but could not find any issues regarding the mail
currently there exist read, reply, and create topic access in each category,
I just wanted to know if this makes sense:
having a new access where a group of people (e.g. everyone) have access to only topic titles (see topic title), and others (e.g.TL0-4) have see access to the whole discussion.
use-case: when the category is completely hidden, nobody may ever know what is inside and they won’t get engaged enough to become a member or to grow. but when you see the titles it may engage you more to have the ability to discuss.
Hi! First let me thank you for this great piece of software!
I’ve just added a Discourse forum to our site. Many of our users value privacy and anonymity.
I’ve implemented my own SSO provider for Discourse, so the existing user accounts of our site are carried over to Discourse. This is working fine. Since we don’t require the user’s email addresses to be validated, I’ve set the require_activation flag (there’s just no way I let someone use a non-validated email address in Discourse).
Some of our users don’t want their mails to be validated. I want to give them the option to use Discourse anonymously. But I cannot figure out a way to do that:
Even if the user is actively logs out of Discourse (or never logged in), the site automatically tries to log him back in as soon as he clicks on a “Reply”-Button. In our case, that leads to our own logon dialog. So noone can post without an account. To use Discourse’s own anonymous posting feature, you still have to have a valid account and validated email address.
There doesn’t seem to be a way in the SSO process to tell Discourse “this user wants to be anonymous”. Or is there? I’d need something to tell Discourse to allow the current user to post anonymously without having a valid email address.
I’d appreciate if you could help me with this! Thanks.
The staff category is seen to all the staff members (which includes the moderators)
I don’t want the moderators to see the stuffs that I have inside the staff category (like the FAQ page, TOS page etc.)
So, I thought of changing the “Staff” category permission and this is what I can see there
So, it is not letting me change the permissions. Rather it says that I should be deleting the category and then create a new one if I want to change the permissions.
Will this work
Create a new category named “staff2” with right permissions (just the admin should have access to it)
Move all the topics from staff to staff2 (just those 7 default topics, nothing else)
Delete the staff category.
Rename “staff2” category to “staff”
My question:
The “About Us” page has links to the pages like TOS, FAQ etc. Since I moved those topics from the old staff category to the new staff category - will the links be broken? If so how to fix it?
I just realized we disable invites altogether when a topic is closed. This shouldn’t apply to admins, since we may want to continue a conversation by whispers or get a 2nd opinion on a tentatively closed topic.
I am following this installation guide to install Discourse on localhost. Everything was working as written in that guide but then as I types this command,
bundle exec rake db:migrate
I got a message that “rake aborted”. The complete message is below, please tell how to fix this?
rake aborted!
ln: failed to create symbolic link '/vagrant/public/plugins/discourse-narrative-bot': Protocol error
/vagrant/lib/discourse.rb:27:in `execute_command'
/vagrant/lib/plugin/instance.rb:449:in `activate!'
/vagrant/lib/discourse.rb:146:in `block in activate_plugins!'
/vagrant/lib/discourse.rb:143:in `each'
/vagrant/lib/discourse.rb:143:in `activate_plugins!'
/vagrant/config/application.rb:178:in `<class:Application>'
/vagrant/config/application.rb:26:in `<module:Discourse>'
/vagrant/config/application.rb:25:in `<top (required)>'
/vagrant/rakefile:5:in `require'
/vagrant/rakefile:5:in `<top (required)>'
/home/vagrant/.rvm/gems/ruby-2.3.1/gems/rake-12.1.0/exe/rake:27:in `<top (required)>'
/home/vagrant/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `eval'
/home/vagrant/.rvm/gems/ruby-2.3.1/bin/ruby_executable_hooks:15:in `<main>'
(See full trace by running task with --trace)
vagrant@discourse:/vagrant$
I also looked at this post but still couldn’t figure out the problem.
In meta, the category description is hidden and that gives it “more room” in the category box and it looks good.
But in my site, category description as well is shown which takes up “a lot of room” in the category box.
Is there a way to hide it?
How is it done in meta?
I have a premium group in my forum which I want to provide access to exclusive content in wordpress.
Is there any way to restrict certain wordpress pages or content based on Discourse user roles or groups?
Using wordpress as SSO host is not an option unfortunately
I saw that some emails on our Discourse community were suppressed because “User was seen recently”.
I couldn’t find it in the settings nor searching on the meta forum for an answer: what is recently defined as and is there an opportunity to change it somewhere in the settings?
I upgraded to 1.9.0 beta14 to fix an image orientation issue today, but I now notice that when I look at the list of NEW users, those who have NEVER had an email are now listed as “Last Emailed: < 1m”
It helps me to identify those who have not been emailed where there is a gap, so I can send a welcome message, so it is not as friendly to show “< 1m”, (plus it is inaccurate since they have not been emailed, so the database value isn’t Zero, but Null)
In editor when I was trying doing Discobot tutorial then I tried to make a hyperlink. But as I tried to make the link, there came this problem.
As I click on the link icon in editor the pop-up comes up. But then as I pressed the field for putting link, the “Paste” option got hidden on the left and there was literally no way to paste the link.
The category setting Suppress this category from the homepage. hides categories from the homepage of the site. If a site has Categories as the homepage in site settings, and a user sets their own homepage via user preferences, visiting /categories shows all categories, including those that are suppressed.
I’m working with Google Tag Manager and there is something I don’t understand on your implementation:
When I load the first page, I have two events sent:
a « Page View » event;
a « VirtualPageView » event.
Then, on all page changes:
a « VirtualPageView » event.
Why are you sending two events on the first page load?
I tried to override your page-tracking.es6.js in the initializers folder by creating a plugin which includes the same file in assets/javascripts/initializers/ but this doesn’t work and your file is executed, not mine. Maybe I’m not doing things good to override one of initializers file. What should I do?
I don’t know what can I do to do that so if someone can help me… thanks
