@lovechopra1 wrote:
Problem: Tags on topic pages are not visible to web spiders
Steps to replicate:
1 Visit any tagged topic page in normal browser mode2 Now turn off javascript or try to access it from any text browser, you will not find tags on this page
Posts: 1
Participants: 1
@lovechopra1 wrote:
I want to display top 5 recently updated topics as per the topic's category on each of the topic pages, which should also be visible to web spiders, please suggest how can I achieve this in discourse?
Posts: 1
Participants: 1
@christianeg wrote:
Hi, I´d like to use hyperlink topic titles so readers read the title, click on it and jump into that site (blog post, news, etc)
Can this be done with Discourse?
Many thanks...
Posts: 5
Participants: 4
@downey wrote:
Continuing the discussion from Official Private Warning Enhancements:
Any chance to get an additional class for Messages that are Official Warnings? Right now the only way to differentiate them is the color of the envelope icon next to the title/subject.
Having an additional class in the
<body>tag would allow a different background or other visual styling. Right now body has two classes,navbar-visible&archetype-private_message.
Posts: 1
Participants: 1
@BCHK wrote:
I run a medical related forum with mostly non-technical users. They get the polls formatted wong a majority of the time. Its a real pain because I usually don't see them within the 5 minute edit window - so they are not a good experience for any of the users, and it just turns the average user off the polls.
At a minimum the polls need to be editable by moderators and admins so that we can fix them so that they actually work. As it is right now - most of the poll attemps on my forums are unsuccessful.
Posts: 16
Participants: 6
@downey wrote:
I know it's possible to add people to a Message topic, but how does one remove a user?
Posts: 1
Participants: 1
@bedhed wrote:
I'm selecting several topics
and using the "Change the tags" option.
The autocomplete to find tags works, BUT there is no button to "Save the change"
I'm guessing it would look like this
Posts: 5
Participants: 4
@downey wrote:
Where is the date coming from in the Twitter onebox? Got some different locale sneaking in.
Posts: 1
Participants: 1
@jks wrote:
I'm following the
INSTALL-cloud.mdinstructions, using a 1GB DigitalOcean droplet. When I set the values inapp.ymlto the recommended settings and keep the default English locale, the installation works. When I changeLANGtofi_FI.UTF-8andDISCOURSE_DEFAULT_LOCALEtofithe installation fails. There are some errors from perl about the locale being missing, but while adding the relevant localegen command to the postgres template removes these errors, it doesn't help with the failure. There's an error message starting withERROR: relation "users" does not existbut I get that with the English locale too, so it's probably not the problem.The final lines of output are
== Seed from /var/www/discourse/db/fixtures/501_meta_category.rb #<ActiveModel::Errors:0x007f455624c280 @base=#<PostCreator:0x007f4555c229b8 @user=#<User id: -1, username: "system", created_at: "2015-06-01 19:48:29", updated_at: "2015-06-01 19:50:05", name: "system", seen_notification_id: 0, last_posted_at: "2015-06-01 19:48:31", email: "no_email", password_hash: "44f98c4209fddf46d4d21581233aa4c6a3decf96243365c3da...", salt: "a5af1f9c4f936f2a2a2dae501d78079d", active: true, username_lower: "system", auth_token: nil, last_seen_at: nil, admin: true, last_emailed_at: nil, email_digests: true, trust_level: 4, email_private_messages: false, email_direct: false, approved: true, approved_by_id: nil, approved_at: nil, digest_after_days: 7, previous_visit_at: nil, suspended_at: nil, suspended_till: nil, date_of_birth: nil, auto_track_topics_after_msecs: nil, views: 0, flag_level: 0, ip_address: nil, new_topic_duration_minutes: nil, external_links_in_new_tab: false, enable_quoting: true, moderator: true, blocked: false, dynamic_favicon: false, title: nil, uploaded_avatar_id: nil, email_always: false, mailing_list_mode: false, locale: nil, primary_group_id: nil, registration_ip_address: nil, last_redirected_to_top_at: nil, disable_jump_reply: false, edit_history_public: false, trust_level_locked: false>, @opts={:raw=>"Keskustelua tästä sivustosta, sen järjestämisestä, siitä miten se toimii ja miten sitä voisi parantaa.", :title=>"Alueesta Meta", :category=>"Meta", :archetype=>"regular"}, @spam=false, @topic=nil, @post=nil, @guardian=#<Guardian:0x007f4555c22940 @user=#<User id: -1, username: "system", created_at: "2015-06-01 19:48:29", updated_at: "2015-06-01 19:50:05", name: "system", seen_notification_id: 0, last_posted_at: "2015-06-01 19:48:31", email: "no_email", password_hash: "44f98c4209fddf46d4d21581233aa4c6a3decf96243365c3da...", salt: "a5af1f9c4f936f2a2a2dae501d78079d", active: true, username_lower: "system", auth_token: nil, last_seen_at: nil, admin: true, last_emailed_at: nil, email_digests: true, trust_level: 4, email_private_messages: false, email_direct: false, approved: true, approved_by_id: nil, approved_at: nil, digest_after_days: 7, previous_visit_at: nil, suspended_at: nil, suspended_till: nil, date_of_birth: nil, auto_track_topics_after_msecs: nil, views: 0, flag_level: 0, ip_address: nil, new_topic_duration_minutes: nil, external_links_in_new_tab: false, enable_quoting: true, moderator: true, blocked: false, dynamic_favicon: false, title: nil, uploaded_avatar_id: nil, email_always: false, mailing_list_mode: false, locale: nil, primary_group_id: nil, registration_ip_address: nil, last_redirected_to_top_at: nil, disable_jump_reply: false, edit_history_public: false, trust_level_locked: false>, @secure_category_ids=[2, 3, 4]>, @errors=#<ActiveModel::Errors:0x007f455624c280 ...>>, @messages={:base=>["Title ei kelpaa; yritä olla kuvailevampi"]}> I, [2015-06-01T19:50:06.062243 #36] INFO -- : Terminating async processes I, [2015-06-01T19:50:06.062569 #36] 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.3/bin/postmaster -D /etc/postgresql/9.3/main pid: 65 2015-06-01 19:50:06 UTC [65-2] LOG: received fast shutdown request 2015-06-01 19:50:06 UTC [65-3] LOG: aborting any active transactions 2015-06-01 19:50:06 UTC [72-2] LOG: autovacuum launcher shutting down 2015-06-01 19:50:06 UTC [69-1] LOG: shutting down I, [2015-06-01T19:50:06.067727 #36] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 188 188:signal-handler (1433188206) Received SIGTERM scheduling shutdown... 188:M 01 Jun 19:50:06.120 # User requested shutdown... 188:M 01 Jun 19:50:06.121 * Saving the final RDB snapshot before exiting. 188:M 01 Jun 19:50:06.129 * DB saved on disk 188:M 01 Jun 19:50:06.129 # Redis is now ready to exit, bye bye... 2015-06-01 19:50:06 UTC [69-2] LOG: database system is shut down FAILED -------------------- RuntimeError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 288 exit 1> Location of failure: /pups/lib/pups/exec_command.rb:105:in `spawn' exec failed with the params {"cd"=>"$home", "hook"=>"bundle_exec", "cmd"=>["su discourse -c 'bundle install --deployment --verbose --without test --without development'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'bundle exec rake assets:precompile'"]} 23b06ff362c1f4d1ac3827d894564f26ca0463832e3d5f789d7c0bdebc90923d FAILED TO BOOTSTRAPHow could I debug this further?
Posts: 6
Participants: 3
@Vocino wrote:
I may be doing something wrong. After switching back to S3 uploads, custom avatars are broken.
The image file uploads correctly and appears in the S3 bucket but the image tag is:
<img alt="" width="120" height="120" src="/user_avatar/[forum.hostname]/vocino/120/5155.png" class="avatar">This is on v1.3.0.beta10 +22.
Image uploads seem to be displaying correctly when uploading an image in a post.
Posts: 5
Participants: 2
@PEB wrote:
Greetings,
I've tried to solve my problem by reading previous topics, but that didn't work.
Because of some proxy config in docker (I guess), all the people in our local network are seen by our discourse as coming from 127.0.0.1. 127.0.0.0/8 is whitelisted in "watched IP", yet, we have a user who is unable to register, he gets the message I pasted in the topic.
There is no blacklist, at least one admin registered under 127.0.0.1, and everything was fine 'till now. I tried to remove the whitelist and to add it again, the error message changed, now it's "max registration for this address reached", or something like this.
Looking in our logs, we can't find anything explaining why the whitelist is not effective.
Do you have any idea?
Thanks!
Posts: 31
Participants: 8
@Root wrote:
I've got an install of Discourse that upon submitting a registration and ideally after confirming the account, I need to copy username and password into a MySQL database using SHA256, not PBKDF2. I was initially thinking of just changing the registration process to accommodate that, however the password would already be salted and encrypted by that point.
I'm not familiar with Ruby on Rails either, what's the best place to start looking at in the source to achieve this?
Posts: 7
Participants: 4
@alexandermendes wrote:
Hi,
I've set up an instance of Discourse and implemented SSO. Everything is working well, apart from the updating of user avatars via SSO. I'm pretty sure I'm passing the parameters correctly, here's the error message I'm getting:
url: Failed to download external avatar: http:/www.example.com/uploads/user_1/1432737947.21_avatar.png, user id 1From looking at discourse_single_sign_on.rb it looks like the download is failing for whatever reason. Could this be something to do with me being behind an nginx proxy? If it helps, my nginx config file is:
upstream community { server 127.0.0.1:8081 fail_timeout=0; } server { listen 80; server_name community.example.com; root /usr/share/nginx/html; index index.html index.htm; client_max_body_size 10M; location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $host; proxy_pass http://community; } }As I say, everything else seems to be working well, just that the download is failing. Any ideas would be very much appreciated! Thanks.
Posts: 3
Participants: 2
@vi0oss wrote:
I go to forum and see just a white page. Enabling JavaScript for this domain reveals a Discourse instance.
Better options are:
1. Fully allowing participating without JavaScript (except of nice features);
2. Showing just read-only basically formatted content (like for the search engines);
3. Showing "This is a Discourse forum. It requires javascript."-like message.
Posts: 6
Participants: 3
@User143 wrote:
I am integrated auth0 login with discourse. when the user logged in through the auth0,if the user is not registered in discourse it will come with registration popup.How can we login the new user to the discourse without asking registration popup and email verification?
Posts: 2
Participants: 2
@peternlewis wrote:
So I applied the latest update, and then noticed it wanted me to update docker as well, and followed the instructions at How do I update my Docker image to latest?, ie:
cd /var/discourse git pull ./launcher rebuild appBut now it says I'm not up to date, except when I click the Click here to upgrade, it says I am:
![]()
So I've gone astray somewhere - how to I fix this up? Thanks.
Posts: 1
Participants: 1
@strategeek wrote:
Hello. The question is pretty clear. Does anyone know how to do that?
When I click on "Latest", pinned topics have no excerpts - that's great.
But when I reload the main discourse page, pinned topics are with excerpts. How to remove them?
Posts: 1
Participants: 1
@countcb wrote:
Hello all,
I have a discourse forum up and running for 2 months now.
I installed it via Docker following the official Instructions. I have it running with nginx to proxy pass requests to discourse.Everything was working fine. Today my hosting company had to reboot my machine. And now I'm getting a 502 Bad Gateway error when trying to access my forum.
I found out, that the problem seems to be the following:
[emerg] 781#0: bind() to unix:/shared/nginx.http.sock failed (98: Address already in use)So the container cant bind to the socket it seems?
nginx gives following error as was to be expected
[error] 2298#0: *1 connect() to unix:/var/discourse/shared/standalone/nginx.http.sock failed (111: Connection refused) while connecting to upstream, client: xx.yy.zzz.aaa, server: forum.example.com, request: "GET / HTTP/1.1", upstream: "http ://unix:/var/discourse/shared/standalone/nginx.http.sock:/", host: "forum.example.com"My app.yml looks like this:
app.yml
## ## After making changes to this file, you MUST rebuild for any changes ## to take effect in your live Discourse instance: ## ## /var/discourse/launcher rebuild app ## ## Make sure to obey YAML syntax! You can use this site to help check: ## http ://www.yamllint.com/ ## this is the all-in-one, standalone Discourse Docker container template # You may add rate limiting by uncommenting the web.ratelimited template. # Out of the box it allows 12 reqs a second per ip, and 100 per minute per ip # This is configurable by amending the params in this file templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/sshd.template.yml" - "templates/web.ratelimited.template.yml" - "templates/web.socketed.template.yml" ## which TCP/IP ports should this container expose? expose: - "2222:22" # fwd host port 2222 to container port 22 (ssh) params: db_default_text_search_config: "pg_catalog.english" ## Set db_shared_buffers to a max of 25% of the total memory. ## ## On 1GB installs set to 128MB (to leave room for other processes) ## on a 4GB instance you may raise to 1GB #db_shared_buffers: "256MB" # ## Set higher on large instances it defaults to 10MB, for a 3GB install 40MB is a good default ## this improves sorting performance, but adds memory usage per-connection #db_work_mem: "40MB" # ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed env: LANG: en_US.UTF-8 # DISCOURSE_DEFAULT_LOCALE: en ## TODO: How many concurrent web requests are supported? ## With 2GB we recommend 3-4 workers, with 1GB only 2 #UNICORN_WORKERS: 3 ## TODO: List of comma delimited emails that will be made admin and developer ## on initial signup example 'user1@example.com,user2@example.com' DISCOURSE_DEVELOPER_EMAILS: 'mail@example.com' ## TODO: The domain name this Discourse instance will respond to DISCOURSE_HOSTNAME: 'forum.example.com' ## TODO: The mailserver this Discourse instance will use DISCOURSE_SMTP_ADDRESS: *** # (mandatory) DISCOURSE_SMTP_PORT: 587 # (optional) DISCOURSE_SMTP_USER_NAME: *** # (optional) DISCOURSE_SMTP_PASSWORD: *** # (optional) #DISCOURSE_SMTP_ENABLE_START_TLS: true # (optional, default true) ## The CDN address for this Discourse instance (configured to pull) #DISCOURSE_CDN_URL: //discourse-cdn.example.com ## These containers are stateless, all data is stored in /shared volumes: - volume: host: /var/discourse/shared/standalone guest: /shared - volume: host: /var/discourse/shared/standalone/log/var-log guest: /var/log ## The docker manager plugin allows you to one-click upgrade Discourse ## http ://discourse.example.com/admin/docker hooks: after_code: - exec: cd: $home/plugins cmd: - mkdir -p plugins - git clone https ://github.com/discourse/docker_manager.git - git clone https ://github.com/discourse/discourse-tagging.git - git clone https ://github.com/discourse/discourse-spoiler-alert.git ## Remember, this is YAML syntax - you can only have one block with a name run: - exec: echo "Beginning of custom commands" ## If you want to set the 'From' email address for your first registration, uncomment and change: #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'" ## After getting the first signup email, re-comment the line. It only needs to run once. ## If you want to configure password login for root, uncomment and change: ## Use only one of the following lines: #- exec: /usr/sbin/usermod -p 'PASSWORD_HASH' root #- exec: /usr/sbin/usermod -p "$(mkpasswd -m sha-256 'RAW_PASSWORD')" root ## If you want to authorized additional users, uncomment and change: #- exec: ssh-import-id username #- exec: ssh-import-id anotherusername - exec: echo "End of custom commands" - exec: awk -F\# '{print $1;}' ~/.ssh/authorized_keys | awk 'BEGIN { print "Authorized SSH keys for this container:"; } NF>=2 {print $NF;}'My nginx config looks like this:
nginx config
server { listen 80; # change this server_name forum.example.com; location / { proxy_pass http ://unix:/var/discourse/shared/standalone/nginx.http.sock:; proxy_set_header Host $http_host; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; access_log /var/log/nginx/discourse-access.log; error_log /var/log/nginx/discourse-error.log; } }I tried the following things:
- restart the app
- rebuild the app
- reboot the host
- stop app, stop nginx, start app, start nginx
All still result in the above error message.
When I attach to the app via docker attach the above error message gets printed repeatedly.As stated above, this worked already for the past 2 month.
I have no clue why the socket can not be bound anymore... I mean the old socket can not still be up and blocking because I rebooted the host maschine...
Any help would be appreciated.Cheers, Christopher
PS: I had to put spaces behind all http and https occurrences because otherwise it would not let me create the topic.
Posts: 2
Participants: 1
@boomzilla wrote:
We have a lot of custom emoji. We updated to Beta 11 this morning and those emoji show up in the emoji menu but no longer work with auto-complete directly in the editor.
Posts: 1
Participants: 1
@AlexAB wrote:
Please navigate to our thread for details: http://forums.sketchup.com/t/discourse-links-misbehaving/11705
We keep getting errors with attached files and photos...This has been happening with a number of linked skps in the last 24hrs...
they take me to a page stating...
The page you requested doesn't exist or is private.
is there some issue or is it uploading errors?
Posts: 8
Participants: 2
