@Osama wrote:
As you can see the “Expand” button is between the name and the avatar, whereas on desktop the button is aligned to the right after the name/username.
It seems this left floating in
mobile/user.scssis the culpritIf I float it to right in my chrome dev console I get this:
Which seems to fix this particular issue, but might break something else.
Posts: 1
Participants: 1
@erlend_sh wrote:
Continuing the discussion from Watching and tracking implementation for tags and categories:
@sam please tell me if I’ve gotten this right.
Here’s this topic that was created way back in May 2014:
https://meta.discourse.org/t/how-to-handle-multiple-account/15244?u=erlend_shI’m tracking the feature category, so as per our tracking updates in 2016, I should be seeing this topic pop up as unread now that it has been bumped up with new replies, but I don’t:
I just discovered it (along with several others) today.
Possibilities:
- I haven’t properly understood our tracking system and this is working as intended.
- It’s working as intended but does not apply here because the topic was created before the new tracking system.
- it’s not working as intended.
Posts: 3
Participants: 2
@erlend_sh wrote:
Continuing the discussion from Watching and tracking implementation for tags and categories:
There’s one piece of logic I don’t think we cover yet:
- “this is a topic” was created in 2015
- I join the forum in 2016. I track no categories, but I’m always on the lookout for
topics, i.e. topics that are completely new to me.
- “this is a topic” receives replies.
- the only way for me to spot this topic is to notice it as unopened in Latest.
In my opinion, the logic should be:
If a topic is completely unread and receives new replies, it should show up as
for me, so long as it also matches my
Consider topics new whenpreference.
Posts: 2
Participants: 2
@erlend_sh wrote:
Been meaning to request this feature for years.
I don’t need to watch any topic here on meta. As long as it’s tracked, I’ll see it.
Every single time I create a new topic, I change it from Watching to Tracking afterwards.
There ought to be a user preference for this:
When I post a new topic, set that topic to
- Watching
- Tracking
- Normal
Obviously the default should remain Watching.
p.s. @awesomerobot maybe we ought to have some more white space between those top preferences? They’re placed so tightly together my eyes always scan multiple times to confirm that I’m looking at the right coupling.
Posts: 1
Participants: 1
@meglio wrote:
People in our community sometimes think that the levels are not automatic, and there’s some bias in how levels are granted.
Is it a good idea to disclose the current settings for trust levels, so that users know what exactly they should do to reach some particular level?
Posts: 9
Participants: 8
@communitygal wrote:
A message was sent within the hour that contains language I need to update.
I have read through the automated emails but I don’t know how to update the messages from Discobot that have the wrong name for our community.
Where can I edit these words?
Thanks!
Posts: 2
Participants: 2
@Osama wrote:
Original idea here:
Screenshots
Installation
Follow the instructions in this #howto topic:
And here is the GitHub repository for the theme, and the JSON file:
discourse-tab-bar.dcstyle.json (6.1 KB)
Customization
See the readme file in the theme’s GitHub repository.
Ideas to improve this theme are very welcome
Posts: 9
Participants: 5
@StephaneFe wrote:
Is it already possible to show vote counters in the topic list or this is not existing (yet)?
If yes, is there a discouse page where I can see how it looks?
Thanks
Posts: 1
Participants: 1
@Tumi wrote:
hello i was read that i cant use normal gmail to set up working installation of discorse becouse google will be off this box ? Is it true ?
I was heard that g suite is working good for it? It is right?
Have you know any else possibilities to sending mailing to users without mailgun , elasticemail etc ??
Posts: 5
Participants: 2
@nickmorin wrote:
I just wanted to say thank you to everyone that makes Discourse possible and for all your help when I first joined your community seeking guidance. @codinghorror @sam @HAWK @pfaffman and many more!
I launched our private Beta Discourse community for cannabis professionals in December 2016. We started with zero members, as most communities do, then went live in March with our awesome founding members and team. It took a lot of research, development, conversations, failing, humility, learning, and improving, but we got to our one year mark last Friday (12/1). I wanted to share my story with you, since the Discourse team helped me when it was just an idea in my head.
Here is a quick infographic of what our community is about:
GrowersNetwork.pdf (7.5 MB) and our public website. Our Discourse instance is private.Some fun facts at our one year mark:
- We currently have 2,166 users
- Our membership base is global, consisting of members from Canada, USA, Israel, Colombia, Netherlands, and more
- We are one of the leading professional communities within the global cannabis community.
- And we have successfully monetized our membership base through monthly subscription rates ($100/month) and monthly advertising via custom banner advertising we coded.
- We currently have an amazing team of 9 employees. Our community manager is unfortunately leaving as of this month, as he accepted another job offer - we are currently seeking a replacement if you know anyone with cannabis community experience.
We are so happy that we chose Discourse over the plethora of other community options on the market. From the strong open source development support to the helpful admins that provide clarity on questions we get stumped on. Choosing the software to run our community was the most important decision we had to make before we launched. And if I went back in time, I would make the same decision: Discourse.
Thank you again for everyone that is involved in this amazing community of communities.
If you are ever available to talk further, I am always available for your calls at 520-278-5084 and your emails at nick@growersnetwork.org.
Sincerely,
Nick
Posts: 1
Participants: 1
@typeoneerror wrote:
I was hoping to use the Discourse API Ruby Gem and replace my SingleSignOn class with the one in there. It looks dated compared to discourse/single_sign_on.rb at master · discourse/discourse · GitHub, so I was going to submit a PR to get it up to speed, but I’m stuck on setting up a test environment as noticed in the gem repo:
2. Inside of your discourse directory, run: `bundle exec rake db:api_test_seed`When I do this I get…
~/Dev/discourse (master) $ bundle exec rake db:api_test_seed Loading test data for discourse_api rake aborted! ActiveModel::UnknownAttributeError: unknown attribute 'auth_token' for User. /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activemodel-5.1.4/lib/active_model/attribute_assignment.rb:48:in `_assign_attribute' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activemodel-5.1.4/lib/active_model/attribute_assignment.rb:40:in `block in _assign_attributes' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activemodel-5.1.4/lib/active_model/attribute_assignment.rb:39:in `each' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activemodel-5.1.4/lib/active_model/attribute_assignment.rb:39:in `_assign_attributes' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activerecord-5.1.4/lib/active_record/attribute_assignment.rb:26:in `_assign_attributes' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activemodel-5.1.4/lib/active_model/attribute_assignment.rb:33:in `assign_attributes' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activerecord-5.1.4/lib/active_record/core.rb:337:in `initialize' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activerecord-5.1.4/lib/active_record/inheritance.rb:66:in `new' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activerecord-5.1.4/lib/active_record/inheritance.rb:66:in `new' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activerecord-5.1.4/lib/active_record/persistence.rb:33:in `create' /Users/typeoneerror/Dev/discourse/db/api_test_seeds.rb:1:in `<main>' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/bootsnap-1.0.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `load' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/bootsnap-1.0.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:30:in `load' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:286:in `block in load' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:258:in `load_dependency' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:286:in `load' /Users/typeoneerror/Dev/discourse/lib/tasks/db.rake:46:in `block in <main>' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/gems/rake-12.1.0/exe/rake:27:in `<top (required)>' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/bin/ruby_executable_hooks:15:in `eval' /Users/typeoneerror/.rvm/gems/ruby-2.4.1@discourse/bin/ruby_executable_hooks:15:in `<main>' Tasks: TOP => db:api_test_seed (See full trace by running task with --trace)Probably an old rake task or something? What am I doing incorrectly? Do you recommend that we make our own SingleSignOn class as shown in Official Single-Sign-On for Discourse (sso) or the Ruby Gem?
Posts: 6
Participants: 2
@LlamaSenpai wrote:
Hello, I would like to know if there was a way to hide the beginning of the pined post that appears in the list of topics (screenshot : Imgur: The magic of the Internet), the bbcode is not very attractive …
Thanks
Posts: 4
Participants: 3
@ninermac wrote:
I have a large SMF install. It’s over half a million posts.
My goal is to port over to Discourse with a wordpress front end. The question is, what would that process look like. I’ve tested imports of smf to Discourse, but it seems in my eventual end state Wordpress would handle the accounts. After the import my accounts would all be in Discourse instead.
Any thoughts on high level move from SMF to Discourse with Wordpress?
Posts: 2
Participants: 2
@GuidoD wrote:
I do have the same Problem as Parisa. The installation is currently on v1.9.0.beta14 +18 and the system tells me to upgrade to 1.9.0.beta15 but UI upgrade is disabled
<h2>You are running an old version of the Discourse image.</h2> <p> Upgrades via the web UI are disabled until you run the latest image. </p>but doing the upgrade on the console does fail.
How can I solve this?FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 11137 exi t 1> Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --withou t test --without development'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]} 3fef1ff0c053dc5c0e9b7ba85f73b95bbdf875181f42cd625bfe9ede20d4315f ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than oneand further up I do see:
Building native extensions. This could take a while... 0: unicorn (5.3.1) from /var/www/discourse/vendor/bundle/ruby/2.3.0/specifications/unicorn-5.3.1.gemspec Using webmock 3.0.1 0: webmock (3.0.1) from /var/www/discourse/vendor/bundle/ruby/2.3.0/specifications/webmock-3.0.1.gemspec Bundle complete! 105 Gemfile dependencies, 181 gems now installed. Gems in the group development were not installed. Bundled gems are installed into `./vendor/bundle` I, [2017-12-09T04:35:40.446491 #16] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' rake aborted! ArgumentError: wrong number of arguments (given 1, expected 2) /var/www/discourse/plugins/discourse-layouts/lib/widget_helper.rb:4:in `add_widget'
Posts: 2
Participants: 2
@ZackFea wrote:
I did add a new plugin and got automatic the last version.
./launcher cleanup ./launcher rebuild append in this error:
LoadError: cannot load such file -- simple-rssHere is the full log:
I, [2017-12-09T10:07:24.953141 #13] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' rake aborted! LoadError: cannot load such file -- simple-rss /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:292:in `require' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:292:in `block in require' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:258:in `load_dependency' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:292:in `require' /var/www/discourse/plugins/discourse-autobot/app/jobs/regular/poll_website_feed.rb:5:in `<class:PollWebsiteFeed>' /var/www/discourse/plugins/discourse-autobot/app/jobs/regular/poll_website_feed.rb:4:in `<module:Jobs>' /var/www/discourse/plugins/discourse-autobot/app/jobs/regular/poll_website_feed.rb:3:in `<top (required)>' /var/www/discourse/plugins/discourse-autobot/app/jobs/base.rb:26:in `require_relative' /var/www/discourse/plugins/discourse-autobot/app/jobs/base.rb:26:in `<top (required)>' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:286:in `load' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:286:in `block in load' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:258:in `load_dependency' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:286:in `load' /var/www/discourse/plugins/discourse-autobot/plugin.rb:25:in `block (2 levels) in activate!' /var/www/discourse/plugins/discourse-autobot/plugin.rb:25:in `each' /var/www/discourse/plugins/discourse-autobot/plugin.rb:25:in `block in activate!' /var/www/discourse/lib/plugin/instance.rb:270:in `block in notify_after_initialize' /var/www/discourse/lib/plugin/instance.rb:268:in `each' /var/www/discourse/lib/plugin/instance.rb:268:in `notify_after_initialize' /var/www/discourse/config/application.rb:219:in `each' /var/www/discourse/config/application.rb:219:in `block in <class:Application>' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/lazy_load_hooks.rb:67:in `block in execute_hook' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/lazy_load_hooks.rb:60:in `with_execution_control' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/lazy_load_hooks.rb:65:in `execute_hook' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/lazy_load_hooks.rb:50:in `block in run_load_hooks' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/lazy_load_hooks.rb:49:in `each' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/lazy_load_hooks.rb:49:in `run_load_hooks' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/application/finisher.rb:73:in `block in <module:Finisher>' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/initializable.rb:30:in `instance_exec' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/initializable.rb:30:in `run' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/initializable.rb:59:in `block in run_initializers' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/initializable.rb:58:in `run_initializers' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/application.rb:353:in `initialize!' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in `public_send' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in `method_missing' /var/www/discourse/config/environment.rb:5:in `<top (required)>' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:292:in `require' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:292:in `block in require' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:258:in `load_dependency' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/dependencies.rb:292:in `require' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/application.rb:329:in `require_environment!' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/application.rb:445:in `block in run_tasks_blocks' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rake-12.1.0/exe/rake:27:in `<top (required)>' /usr/local/bin/bundle:23:in `load' /usr/local/bin/bundle:23:in `<main>' Tasks: TOP => db:migrate => environment (See full trace by running task with --trace) I, [2017-12-09T10:07:43.575814 #13] INFO -- : gem install yt-support -v 0.1.3 -i /var/www/discourse/plugins/discourse-autobot/gems/2.4.2 --no-document --ignore-dependencies Successfully installed yt-support-0.1.3 1 gem installed gem install yt -v 0.32.1 -i /var/www/discourse/plugins/discourse-autobot/gems/2.4.2 --no-document --ignore-dependencies Successfully installed yt-0.32.1 1 gem installed I, [2017-12-09T10:07:43.576606 #13] INFO -- : Terminating async processes I, [2017-12-09T10:07:43.576706 #13] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/9.5/bin/postmaster -D /etc/postgresql/9.5/main pid: 42 I, [2017-12-09T10:07:43.576862 #13] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 155 2017-12-09 10:07:43.577 UTC [42] LOG: received fast shutdown request 2017-12-09 10:07:43.577 UTC [42] LOG: aborting any active transactions 2017-12-09 10:07:43.579 UTC [49] LOG: autovacuum launcher shutting down 2017-12-09 10:07:43.581 UTC [46] LOG: shutting down 155:signal-handler (1512814063) Received SIGTERM scheduling shutdown... 2017-12-09 10:07:43.608 UTC [46] LOG: database system is shut down 155:M 09 Dec 10:07:43.609 # User requested shutdown... 155:M 09 Dec 10:07:43.610 * Saving the final RDB snapshot before exiting. 155:M 09 Dec 10:07:43.646 * DB saved on disk 155:M 09 Dec 10:07:43.646 # Redis is now ready to exit, bye bye... FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 395 exit 1> Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development --retry 3 --jobs 4'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]} a7f1896ead97d3d5a82d2229b56a75354c7972bc6a6cd889f83d4fc091f7ec62 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one
Posts: 4
Participants: 2
@MAR wrote:
Hello Discourse Community,
Hope this reaches you well. I am wondering if there is anyone running multiple discourse sites for various organizations? Are these all separate instances ? or can you maintain these on a server and upgrade simultaneously, provide single sign-on across multiple instances?
Posts: 3
Participants: 3
@pfaffman wrote:
Steps to reproduce:
- create admin account from wizard
- ignore (or don’t receive) activation email
- return to wizard, create admin account again
Behavior: Nothing happens.
Expected behavior: Get a “admin user already exists” error or re-send activation email
I thought I’d never figure out why this new admin couldn’t get the activation email and I was getting emails just fine. I finally created an admin user for myself, found the user on the admin/users page and re-sent the activation notice.
Posts: 5
Participants: 2
@hanks wrote:
Hi!
I have a Wordpress blog which I connected to a Discourse forum through WP Discourse. WP Posts and comments are synchronized with Discourse through Discourse API.
About the SSO, from what I understand, two choices are given :
- Discourse authentication goes through WP. Users can’t log into Discourse by other means than through WP.
- WP authentication goes through WP or Discourse, the choice is given to the user (there is a “login with Discourse” link under the WP login form).
Question 1: Regarding the solution 2), is there any way to force WP users to login/create accounts through Discourse? By having an embedded Discourse login form instead of Wordpress login form or something like that… So all the users are managed by Discourse, which I would prefer.
Question 2: I didn’t try it yet, but with the solution 1) is it possible to use a WP plugin to allow users to log in through Facebook or other social media when being on the WP login form, and if they do this way it also creates a Discourse account?
From what I imagine, it would be: Facebook login creates a WP account -> Creation of a WP account which logs to Discourse too.
Basically, if a user wants to log in on Discourse or WP, they are redirected in both cases to the WP login form, which gives a choice: WP login (which creates a Discourse account thanks to SSO), or Facebook login (which does the same through WP… Am I clear ?)
Question 3: Actually, with WP Discourse, a synchronized WP post displays the post comments, but no comment form. Instead, there is a " Continue the discussion" link which leads to Discourse.
Is there any fairly simple way to the following things?
- If the user is already logged in, show a text area which sends the content to Discourse through the API and redirects the user to the post discussion on Discourse
- If the user isn’t logged in, show a login form which redirects somewhere after having logged in (on the WP post page or the post discussion on Discourse)
I’m not particularly afraid of having to do some PHP code, but I don’t know much about WP methods and stuff that I should use doing so.
Posts: 4
Participants: 2
@Tumi wrote:
Hello.
1). How can in check or find site which are building with discourse ? Can i look at source code to “find it” ?
- As admin what can i do to hide information that im using a discourse ? a reason is for example security becouse i dont sure about docker supporters…
Posts: 3
Participants: 2
topics, i.e. topics that are completely new to me.
)
