@dmitry_fedyuk wrote:
Provide the «New Category» dialog with an ability to suppress an auto-creation of the category topic.
See also: Provide the «New Category» dialog with an ability to choose an existing topic as the category topic.
Posts: 3
Participants: 3
@mcg wrote:
Apologies if the search engine has failed me here, but I don't see a way to cause welcome messages to be sent already closed; that is, to prevent replies. I see lots of posts about how to send the messages from a system user, to hide notifications, etc., but I'd simply prefer it be impossible to reply to such messages.
My forum is a software support forum, and I don't want to create the expectation that replies to the welcome PM are a means to obtain that support. (The text of the message itself asks users not to attempt that, but...)
Any thoughts? Thanks in advance.
Posts: 3
Participants: 3
@dmitry_fedyuk wrote:
Provide the «New Category» dialog with an ability to choose an existing topic as the category topic.
See also: Provide the «New Category» dialog with an ability to suppress an auto-creation of the category topic.
Posts: 2
Participants: 2
@anthony-o wrote:
I would want to change the style of the number of replies of a solved topic (I'm using discourse-solved plugin) on the welcome page, where the latest topics are listed (actually, I wanted to change this color in every list of topics when one is solved).
In a first try to do this, I used the following custom CSS:
td.num.posts a { border-width: 1px; border-style: solid; border-color: #acb21b; width: 100%; display: block; color: #acb21b; }But this would color every replies counter in the topic list.
As I've noticed that if a topic is solved, there is atd.main-link > span.link-top-line > div.topic-statuses > span.topic-status > i.fa-check-square-owhich exists, but I can't use it to include it in my CSS selector as it's a cousin of thetdwhich style I want to change and CSS cousin selector doesn't exist...Can someone tells me what is the good way to do this?
Posts: 1
Participants: 1
@ChrisBeach wrote:
I've noticed people occasionally posting the text "Uploading..." because they unwittingly saved their topic before uploads had completed. Just accidentally did it myself on a slow connection, in fact.
I think it might be handy to have a warning dialog ("Uploads in progress. Post anyway? Y/N") to make the user aware?
Posts: 3
Participants: 2
@designbygio wrote:
I install my local version of discourse which seems to work pretty fine.
I have an admin user and i created other 2 test users, which i can see the profile and i can see when i search for them in the search bar.
Anyway if i go to/usersi gotNo results were foundAny suggestion how can i check why is this happening?
I run discourse without Vm, with normal instalation following this guide
Posts: 3
Participants: 2
@Gina_Patterson wrote:
Hi there -
I have run through everything in the troubleshooting guide and still cannot get that registration email to send.In Sparkpost mail, it shows that an email was blocked last night when I tried to register, but nothing today (I have tried twice to register). The reason it shows is:
550 5.7.1 Unconfigured Sending DomainI changed the custom commands at the end of app.yml to this:
## If you want to set the 'From' email address for your first registration, uncomment and change:
## After getting the first signup email, re-comment the line. It only needs to run once.
- exec: rails r "SiteSetting.notification_email='noreply@bite-nutrition.com'"When I look at the production log, I see this:
Sent mail to gina@bite-nutrition.com (509.7ms) Error connecting to Redis on localhost:6379 (Errno::ECONNREFUSED) subscribe failed, reconnecting in 1 second. Call stack ["/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/r edis/client.rb:345:in `rescue in establish_connection'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:331:in `establish_connection'", "/var/www/discours e/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:101:in `block in connect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:293:in `with_re connect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:100:in `connect'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/clien t.rb:364:in `ensure_connected'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:221:in `block in process'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/g ems/redis-3.3.1/lib/redis/client.rb:306:in `logging'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:220:in `process'", "/var/www/discourse/vendor/bundle /ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:134:in `block in call_loop'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:280:in `with_socket_timeout' ", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/client.rb:133:in `call_loop'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/subscribe.r b:43:in `subscription'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis/subscribe.rb:12:in `subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3 .1/lib/redis.rb:2760:in `_subscription'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:2138:in `block in subscribe'", "/var/www/discourse/vendor/bundle/ruby/2. 3.0/gems/redis-3.3.1/lib/redis.rb:58:in `block in synchronize'", "/usr/local/lib/ruby/2.3.0/monitor.rb:214:in `mon_synchronize'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3 .1/lib/redis.rb:58:in `synchronize'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/redis-3.3.1/lib/redis.rb:2137:in `subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/mess age_bus-2.0.2/lib/message_bus/backends/redis.rb:304:in `global_subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus.rb:513:in `global_subscribe_t hread'", "/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.2/lib/message_bus.rb:461:in `block in new_subscriber_thread'"]Sparkpost mail shows sending domain is "ready to send".
DNS is configured
Haaaaalp! I'm soooo close!
Posts: 5
Participants: 2
@burke wrote:
Continuing the discussion from What does selecting "Primary Group" for a user do?:
From what I can tell, when members are in multiple groups one of the groups can be named as their primary group, but this can only be set by an administrator via the admin user screen.
Would it be reasonable to let the user decide for herself – i.e., add a this setting to the user's preference page? Or possibly as a feature on the new & improved Groups page (when viewing a non-primary group for whom your a member, you see a "make this my primary group" button)?
Posts: 2
Participants: 2
@joebuhlig wrote:
There are a lot of features I'm still working on but I want to go ahead and open this up for discussion. I've been working heavily on a plugin that allows you to take one-item or recurring payments in exchange for access to a group. Effectively, that allows you to put categories behind a paywall and opens up a lot of possibilities that allow the monetization of your forum.
The core of this plugin is free. However, both support and a handful of premium features are restricted to those who have an active license key. That license key is granted to those who have an active subscription on the Discourse League site.
The trouble with this is that we're working with an awesome open source project and I don't want to inhibit or take away from the culture that's been built in any way. So to help promote Discourse and encourage contributors, I'm making a free lifetime license key available to anyone who contributes a successful PR to Discourse core or any of the Discourse League plugins.
At this point, I still have a decent amount of work to do but hope to tie off the little details in the next week or two. At that point, I'll open this up as a full release and allow the purchase of license keys.
Posts: 1
Participants: 1
@joebuhlig wrote:
As part of the Discourse League project, I needed a way to generate and validate license keys. Thus, another plugin was required. But I wanted it to be possible for others to integrate license keys into their plugins as well. So here we go:
https://github.com/discourse-league/dl-license-keys
I put together a full how to on the League site, but the gist of it is that you need to create a new product that is tied to a group of users. Any time someone is added to the group a license key is generated for them. If they are removed from the group, their key is disabled.
From your plugin, you make an HTTP request using the ID of the product and the license key of the user to get the status of the key. It's up to you what you want to do with the response but I recommend saving the status to a hidden site setting. If you want to go even further, you can create a sidekiq job that re-validates on a daily basis. That will allow you to revoke access from your site.
Posts: 1
Participants: 1
@wm00 wrote:
I just want to know if I can use the script for a Spanish site.
Posts: 2
Participants: 2
@JagWaugh wrote:
Joe's Plugin got me thinking about monetization.
Our forum has always been "beerware", on the old site we did have a vanity badge for people who contributed and a couple of features that were limited to paid members, but we won't be moving away from the beerware model. So far the model has worked for us, and I'm sure that we aren't the only discourse site in a similar situation.
We don't want to put the site (or large parts of it) behind a paywall, but it would be nice if we had a way to prod non paying users to contribute, and offer something more than an ego badge.
So, what could we do to gently stimulate users, other than running a PBS "Bug em till they buy a coffee cup" campaign?
One way would be if we could throttle user activity, or trigger a "Hey there" based on if that user was in the group "Paid Members".
If "max emails per day per user" were group based that would be a possibility.
Restricting PMs to only Mods and admins would be another.
A "Hey there..." popup every X posts would be another.As far as I can tell there isn't really all that much infrastructure in place for sites which are somewhere between completely open, and putting parts of the site behind a paywall.
(A PayPal contribution facility with badge assignment would be magic!)
Posts: 2
Participants: 2
@PXJ wrote:
Although I know my way around WordPress and in the long distant past set up a BuddyPress (yeah, I know! :)) for writers, I hadn't come across Discourse until looking recently for a forum solution for Inspired Everywhere forum.
With the help of the wonderful Jay Pfaffman, everything is now set and I'm truly impressed at how slick everything is, and the degree to which stuff is pre-set and configured for folk like me.
Thank you, and congrats! Keep it going!!
Posts: 1
Participants: 1
@erlend_sh wrote:
Continuing the discussion from Is there a way to make the password requirements more simple?:
Prior art:
Posts: 1
Participants: 1
@LeoDavidson wrote:
I'm using the
user-profile-primaryplugin outlet to add some things to the user pages.In the .hbs template, I want some things to be conditional on whether the displayed user is the logged on user or someone else. This is done via a computed
viewingSelfproperty in the internal templates, but it's not available directly from the user model.From Important changes to Plugin Outlets for Ember 2.10 I can see that the child template no longer automatically inherits everything the parent template could use, and since viewingSelf is a computed property it looks like it is one of the missing things.
I also see in there that I can make a connector, and add whatever I need, so I'm trying something like this, just trying to get it so {{newTestThing}} will print the two usernames first:
export default { setupComponent(args, component) { const modelUser = args.model.get("username"); const activeUser = ???; component.set('newTestThing', modelUser + " --?-- " + activeUser); } }I can't work out what should go into ??? though.
currentUser,application, etc. don't seem to exist onthisor on any of the objects contained inargs(at least from trying various combinations, then setting a breakpoint and looking around in Chrome's js debugger).I'm probably missing something simple, but can't see the wood for the trees at the moment. Any help much appreciated!
(I'm not tied to this method of doing things, either. If there's an easier way to say
{{#if viewingSelf}}inside theuser-profile-primaryoutlet then that's my real goal.)
Posts: 3
Participants: 2
@sdd wrote:
BUG:
Enable CDN,
all emoji url will use https:// my cdn not have SSL, so unable to display emoji.
Posts: 3
Participants: 3
@peternlewis wrote:
Now that my category names are different to the category slugs, and have spaces in them, it would be nice to be able to do something like #"Questions & Suggestions" and have it work instead of just changing it to #general.
Posts: 2
Participants: 2
@imrehg wrote:
Discourse has really great preview cards for links in general, dropping in a link on a new line (onebox previews).
Recently I've found, though, that Github repository links no longer have any previews (I think they had before), while linking to a specific file on Github has. For example posting
https://github.com/resin-io-playground/awesome-resin-io:https://github.com/resin-io-playground/awesome-resin-io
^^ this has no preview (at the time of posting)
But posting a link to a file in the repo, e.g.
https://github.com/resin-io-playground/awesome-resin-io/blob/master/readme.md:^^ this has proper preview
I know it worked before, because in our Discourse the first link works, looking like this screenshot:
I suspect it has to do with Github's recent style changes (as that happened less than a week ago, and the working screenshot is from 14 days ago).
I also think that besides broken repo links, organization links also regressed, but don't have a previous working example at hand to double-check.
Any thoughts?
Posts: 5
Participants: 4
@barreeeiroo wrote:
Hello
I'm getting the error
ERR_TOO_MANY_REDIRECTSafter installing Discourse on my machine. I tried to delete and reinstall completly from 0, but the error stills appearing. Apache is working fine (I've just installed to test if it was an error of my machine), so IDK what is going wrongServer details:
- Hosting: ArubaCloud VPS
- OS: CentOS 7.2
- SSL: With Let's EncryptAnyone can help?
Posts: 5
Participants: 3
