@rob1 wrote:
Hi there,
Can anyone explain to me as I am not good on tech things of placing code in the right place. I want to put a countdown timer at the top of our community It's been requested by some of our members. The community is very new but we are building up quite nicely now
Also any help with regards to how exactly do step by step to give a custom color for the usernames of Moderators and Admins. We are all set after that
Thanks again
Rob
Posts: 10
Participants: 4
@Yuun wrote:
Issue:
At for example meta.discourse.org/my/summary, the "Most Liked By" column containers the correct numbers of likes and the correct users, but does not match them up correctly.
This is a little easier to see when you're the admin for the site and can check against a data explorer query, though. I can't easily verify it's happened on meta, have seen the issue most clearly on my site.
Repro:
Nothing special required, just visit a user summary page and check the numbers against some other source. For example using the data explorer plugin, or using the user directory in some circumstances (one of the "most liked by" for my page on my site, for example, is shown giving me more likes than he has given total on the user directory).
Posts: 12
Participants: 6
@Shrike wrote:
Hi!
I can't upgrade my Discourse installed via Docker. It just can't see updates.
It's installed in out lab which where there's restricted Internet - only whitelist addresses are allowed. But Discourse was installed successfully. Should I add some additional addresses to whitelist to allow upgrading?But issue with whitelist is my guess. Here'e the full story:
In /admin page I can see :
v1.5.0.beta11 +178
A check for updates has not been performed lately. Ensure sidekiq is running.
I go to /sidekiq and do see a lot of recurring jobs.In /logs I can see this eror
Job exception: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed:
with backtrace
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient/request.rb:445:inrescue in transmit'transmit'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient/request.rb:350:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient/request.rb:176:inexecute'execute'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient/request.rb:41:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient/abstract_response.rb:111:infollow_redirection'return!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient/abstract_response.rb:67:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient/request.rb:495:inprocess_result'block in transmit'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient/request.rb:421:in
/usr/local/lib/ruby/2.0.0/net/http.rb:852:instart'transmit'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient/request.rb:413:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient/request.rb:176:inexecute'execute'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient/request.rb:41:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rest-client-1.8.0/lib/restclient.rb:65:inget'singular_action'
/var/www/discourse/lib/discourse_hub.rb:36:in
/var/www/discourse/lib/discourse_hub.rb:20:inget'discourse_version_check'
/var/www/discourse/lib/discourse_hub.rb:13:in
/var/www/discourse/app/jobs/scheduled/version_check.rb:13:inexecute'block (2 levels) in perform'
/var/www/discourse/app/jobs/base.rb:154:in
Posts: 1
Participants: 1
@jesus2099 wrote:
I had been using a PunBB MusicBrainz forum for many years and when the Discourse MetaBrainz forum replaced it, I was very sceptical.
It looked overly modern to my taste. Too much white colour all over the place.But I was surprised that for a modern forum, it worked very very well in my good old Opera 12 and in a matter of a couple of days I was completely convinced and I find it very handy to use!
And I have always loved Markdown syntax but none of the forums I was on was using it before Discourse. It is a pleasure to use.
Most of all, it works so very well in a multitude of platforms for such a complex layout.
It must be very hard to maintain, or what?
Posts: 1
Participants: 1
@Yuun wrote:
If this doesn't make the cut for big enough issue, feel free to close with extreme prejudice.
Dropdowns, e.g. while editing category permissions:
And on admin/badges are rather difficult to read. I'm currently using:
body input, body select { color: #000; }But since CSS customizations are stripped out of admin I tend to get the light grey on white a fair amount, and it might be good to have fixed in general.
Posts: 2
Participants: 2
@erlend_sh wrote:
I think the Likes count should always be on the right side of the heart. This would keep it more consistent, and it would also put some much needed space between the Likes count and the date numbers:
I was confused for a long time, thinking the Likes count had disappeared along with the dark theme, because my brain was dismissing everything in the date section as "date stuff; not important".
Posts: 3
Participants: 2
@kuon wrote:
I'm setting up a forum for a gaming community on EvE online. And I'd like to give the players the possibility to not provide their email.
So, what I'd like to do, it to tell them to use playername@ouralliance.com as registration email. I use a modified version of https://github.com/discourse/discourse-oauth2-basic to automatically validate account that register with emails ending in ourallianace.com. As I use EvE online oauth as source of truth for account and disabled all other registration and login method, I know that each account is a valid EvE player.
But now, I'd like to tell discourse to not send any email to the domain ouralliance.com but I'd like to keep global emails enabled for people who wanna put their real email in.
What would be the best way to achieve that?
Posts: 1
Participants: 1
@wasimkham wrote:
I'm having a problem running the import script to import Kunena to Discourse. I'm running in a development environment in a vagrant VM. I don't know Ruby so I don't really understand what's going on but I've pasted the error below.
There's tons of pages of stack trace which I won't bore you with for now but here is the first section. If anyone has any insights I would really appreciate it.
So it imports the users successfully, I'm pretty sure it puts some categories in the DB but I think it fails after that.
[vagrant@precise32:/vagrant (master)]$ bundle exec ruby script/import_scripts/kunena3.rb You are running an old version of bundler, please upgrade bundler ASAP, if you are using Discourse docker, rebuild your container. loading existing groups... loading existing users... loading existing categories... loading existing posts... loading existing topics... fetching Joomla users data from mysql fetching Kunena user data from mysql creating users 12 / 12 (100.0%) ) creating topics and posts /var/lib/gems/2.2.0/gems/rack-mini-profiler-0.9.9.2/lib/patches/db/mysql2.rb:6: [BUG] Segmentation fault at 0x4d4f524a ruby 2.2.2p95 (2015-04-13 revision 50295) [i386-linux-gnu] -- Control frame information ----------------------------------------------- c:0012 p:---- s:0051 e:000050 CFUNC :each c:0011 p:0020 s:0048 e:000047 METHOD /var/lib/gems/2.2.0/gems/rack-mini-profiler-0.9.9.2/lib/patches/db/mysql2.rb:6 c:0010 p:0054 s:0040 E:00078c METHOD /vagrant/script/import_scripts/base.rb:420 c:0009 p:0071 s:0031 E:000324 BLOCK script/import_scripts/kunena3.rb:114 c:0008 p:0008 s:0027 e:000026 BLOCK /vagrant/script/import_scripts/base.rb:702 [FINISH] c:0007 p:---- s:0025 e:000024 CFUNC :loop c:0006 p:0012 s:0022 e:000021 METHOD /vagrant/script/import_scripts/base.rb:701 c:0005 p:0041 s:0017 E:001754 METHOD script/import_scripts/kunena3.rb:92 c:0004 p:0049 s:0012 E:0015c8 METHOD script/import_scripts/kunena3.rb:48 c:0003 p:0029 s:0008 E:0016f8 METHOD /vagrant/script/import_scripts/base.rb:45 c:0002 p:0076 s:0004 E:00062c EVAL script/import_scripts/kunena3.rb:143 [FINISH] c:0001 p:0000 s:0002 E:001afc TOP [FINISH] -- Ruby level backtrace information ---------------------------------------- script/import_scripts/kunena3.rb:143:in `<main>' /vagrant/script/import_scripts/base.rb:45:in `perform' script/import_scripts/kunena3.rb:48:in `execute' script/import_scripts/kunena3.rb:92:in `import_posts' /vagrant/script/import_scripts/base.rb:701:in `batches' /vagrant/script/import_scripts/base.rb:701:in `loop' /vagrant/script/import_scripts/base.rb:702:in `block in batches' script/import_scripts/kunena3.rb:114:in `block in import_posts' /vagrant/script/import_scripts/base.rb:420:in `create_posts' /var/lib/gems/2.2.0/gems/rack-mini-profiler-0.9.9.2/lib/patches/db/mysql2.rb:6:in `each' /var/lib/gems/2.2.0/gems/rack-mini-profiler-0.9.9.2/lib/patches/db/mysql2.rb:6:in `each' -- Machine register context ------------------------------------------------ GS: 0x00000033 FS: 0x00000000 ES: 0x0000007b DS: 0x0000007b EDI: 0x11210110 ESI: 0x11210110 EBP: 0xbf9f91a8 ESP: 0xbf9f9130 EBX: 0xb6c55540 EDX: 0x4d4f5246 ECX: 0x20292a28 EAX: 0x11210110 TRA: 0x0000000e ERR: 0x00000004 EIP: 0xb69db69b CS: 0x00000073 EFL: 0x00010202 UES: 0xbf9f9130 SS: 0x0000007b -- C level backtrace information ------------------------------------------- /usr/lib/i386-linux-gnu/libruby-2.2.so.2.2 [0xb76d931c] /usr/lib/i386-linux-gnu/libruby-2.2.so.2.2 [0xb76d9593] /usr/lib/i386-linux-gnu/libruby-2.2.so.2.2 [0xb75a2b39] /usr/lib/i386-linux-gnu/libruby-2.2.so.2.2 [0xb7662fac] [0xb77bd40c] /usr/lib/i386-linux-gnu/libmysqlclient.so.18(mysql_fetch_row+0x2b) [0xb69db69b] /var/lib/gems/2.2.0/extensions/x86-linux/2.2.0/mysql2-0.4.3/mysql2/mysql2.so(nogvl_fetch_row+0x1b) [0xb6cd248b] result.c:160
Posts: 1
Participants: 1
@Jared_Needell wrote:
I get an error in the admin panel ever since I restarted discourse.
Anyone able to help with this?
Posts: 3
Participants: 2
@Sebastian1 wrote:
Is there a way to remove the users column without touching code?
Posts: 2
Participants: 2
@Drew_Warwick wrote:
On the Discourse summary page, there's a section for Most Liked By:
It'd be neat if there were a section for Most Liked Users that showed the top six users that have received the most likes from the owner of the profile -- essentially the flip side of Most Liked By. Being able to see, at a glance, which users make posts that the profile owner likes the most would be interesting.
Posts: 2
Participants: 2
@Drew_Warwick wrote:
The profile summary has a section for Top Links:
It's not possible to find out where the profile owner has mentioned those links though using this interface. This section of the profile summary would be more useful if we could find the context these links were mentioned in.
Posts: 1
Participants: 1
@Roxelle wrote:
Goodmorning everyone ^^
Where I can find a guide to uninstall a plugin?
Posts: 4
Participants: 3
@thangngoc89 wrote:
I'm testing Discourse comment system for my blog and I noticed that there is a missing translation key on the page
Key:
[en.admin.embedding.embed_classname_whitelist]Route:
/admin/customize/embeddingDiscourse Version: Vagrant, master branch (I just cloned it)
Posts: 1
Participants: 1
@TechnoBear wrote:
Continuing the discussion from Make private group pages visible to only group members:
Steps to reproduce:
Create a group and uncheck "Group is visible to all users"
Add non-admin members to the group.
Each member will see the group as a link on their own profile (but not on others), but using the link will give an "access denied" error.
Either the link should not be visible to the member, or the member should have access to the group page.
Posts: 1
Participants: 1
@Roxelle wrote:
When you enable the badge system, you can view only those personal and not the default?
If you can, how?
Posts: 5
Participants: 3
@stav_sitnikov wrote:
hi is it possible to add an option for the "User Fields" that the input is Tags ?
Thanks .
Posts: 4
Participants: 3
@jamesarobbo wrote:
Just to be certain, I've added a custom initializer file to the initializers folder, will this be picked up when the app starts?
Cheers
Posts: 4
Participants: 2
@thangngoc89 wrote:
I'm testing Discourse Embed comment system for my static blog using React locally but I can't get it to work. I'm sure that I read the instruction like 10 times. So I'm thinking that localhost should be the blocker here.
Set up :
- A fake domain
cpp.devin/etc/hoststo for routing to localhost. Let's say it'scpp.dev- Discourse : Using vagrant with latest commit from Github.
Discourse port inside vagrant: 3000
- Host port for Discourse: 4000. I can access Discourse via
http://cpp.dev:4000- My website is running at
http://cpp.dev:3000- I added both
cpp.dev:3000andcpp.devto hosts list in Admin > Customize > Embedding section- Website embed code:
DiscourseEmbed = { discourseUrl: "http://cpp.dev:4000/", discourseEmbedUrl: window.location, }Looking good, now let's run it. It shows up an iframe with
loading discussionforever.
- In terminal, I see this message:
I, [2016-04-18T07:24:10.751058 #25645] INFO -- : Processing by EmbedController#comments as HTML I, [2016-04-18T07:24:10.784677 #25645] INFO -- : Parameters: {"embed_url"=>"http://cpp.dev:3000/dnh-cpp/cpp-co-ban/0-gioi-thieu-tong-quan/0-0-gioi-thieu-ve-khoa-hoc/"} D, [2016-04-18T07:24:10.807149 #25645] DEBUG -- : User Load (5.1ms) SELECT "users".* FROM "users" WHERE "users"."auth_token" = '951c06ee26073030dc3cf264e80804fa' LIMIT 1 [["auth_token", "951c06ee26073030dc3cf264e80804fa"]] D, [2016-04-18T07:24:10.866750 #25645] DEBUG -- : (3.6ms) SELECT "topic_embeds"."topic_id" FROM "topic_embeds" WHERE (lower(embed_url) = 'http://cpp.dev:3000/dnh-cpp/cpp-co-ban/0-gioi-thieu-tong-quan/0-0-gioi-thieu-ve-khoa-hoc') I, [2016-04-18T07:24:10.917468 #25645] INFO -- : Rendered embed/loading.html.erb within layouts/embed (0.9ms) I, [2016-04-18T07:24:10.987482 #25645] INFO -- : Completed 200 OK in 186ms (Views: 61.0ms | ActiveRecord: 8.7ms)
- In browser console, I see this
Failed to execute 'postMessage' on 'DOMWindow': The target origin provided ('http://cpp.dev:4000') does not match the recipient window's origin ('http://cpp.dev:3000').
No new topic was created.
Some suspicious log as `/logs/
Started GET "/dnh-cpp/cpp-co-ban/0-gioi-thieu-tong-quan/0-0-gioi-thieu-ve-khoa-hoc/" for 127.0.0.1 at 2016-04-18 07:29:25 -0400 6:29 pm Permalink Exists (1.1ms) SELECT 1 AS one FROM "permalinks" WHERE "permalinks"."url" = 'dnh-cpp/cpp-co-ban/0-gioi-thieu-tong-quan/0-0-gioi-thieu-ve-khoa-hoc' LIMIT 1 [["url", "dnh-cpp/cpp-co-ban/0 6:29 pm ActionController::RoutingError (No route matches [GET] "/dnh-cpp/cpp-co-ban/0-gioi-thieu-tong-quan/0-0-gioi-thieu-ve-khoa-hoc") /var/lib/gems/2.2.0/gems/actionpack-4.2.6/lib/action_dispatch/middlewareWhere is the wrong part in my setup ? Any help would be appriciated.
Posts: 8
Participants: 2
