@lovechopra1 wrote:
Problem: Categories not shown to web spiders on parent category pages
Steps to replicate:
1 Please visit any parent category page lets say "Extensibility"
2 You an see category are there with each topics
3. Now disable javascript, you will see categories are not there along with each topics
Posts: 1
Participants: 1
@cyborg wrote:
Hello,
I have a problem with "set administrator/moderator" buttons that when I try to nominate a user for that i get:
ActiveRecord::RecordInvalid (Validation failed: Name has already been taken)Any idea why and how could I solve this? Many thanks
Posts: 6
Participants: 3
@watchmanmonitor wrote:
I just invited a few people and using the group typeahead worked as expected. (It properly limited the Groups in the popup to add more).
However, when adding groups to a user on the admin page, the character matching was too loose, letting
smatch a group calledboardIn the attached picture, I would not expect either "retail" or "board" to show after I'd typed an
sThis was on a self-hosted docker setup running
v1.4.0.beta1 +54.
Posts: 4
Participants: 2
@MuhYal wrote:
Hi, before sorry for my bad English. I search search and again search but not see any fix for this problem.
I use OVH 4 GB VPS and install on Discourse. Working great! But if i want to rebuild Discourse see this error;
Extra info: if i reset my VPS then Discourse working great. And again i want to rebuild Discourse see this error;System:
Ubuntu 14.04 LTS x64System load:
System information as of Thu Jun 11 16:57:58 EEST 2015 System load: 0.0 Memory usage: 2% Processes: 107 Usage of /: 11.0% of 47.17GB Swap usage: 0% Users logged in: 0 Graph this data and manage this system at: https://landscape.canonical.com/Problem:
FAILED -------------------- RuntimeError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process:: Status: pid 423 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 --deplo yment --verbose --without test --without development'", "su discourse -c 'bundle exec rake db:migrate'", "su discou rse -c 'bundle exec rake assets:precompile'"]} d3373830790a702d911b561b005d279c5d149d91046cec48e2b78c7cfd7ba2d1 FAILED TO BOOTSTRAPFull log:
https://gist.github.com/muhyal/5ece5ca19c6810cef60b
Docker version:
root@vps174448:/var/discourse# docker --version Docker version 1.6.2, build 7c8fca2App.yml file:
## ## 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" ## which TCP/IP ports should this container expose? expose: - "80:80" # fwd host port 80 to container port 80 (http) - "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: "1024MB" # ## 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: tr ## TODO: How many concurrent web requests are supported? ## With 2GB we recommend 3-4 workers, with 1GB only 2 UNICORN_WORKERS: 4 ## 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: 'hidden' ## TODO: The domain name this Discourse instance will respond to DISCOURSE_HOSTNAME: 'www.sitename.com' ## TODO: The mailserver this Discourse instance will use DISCOURSE_SMTP_ADDRESS: hidden DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_USER_NAME: hidden DISCOURSE_SMTP_PASSWORD: hidden DISCOURSE_SMTP_ENABLE_START_TLS: true DISCOURSE_SMTP_OPENSSL_VERIFY_MODE: none ## 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-spoiler-alert.git - git clone https://github.com/discourse/discourse-tagging.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;}'
Posts: 6
Participants: 2
@Breaker wrote:
I was wondering if anyone knows of a way to have discourse act as an IDP (identity Provider) using SAML or OAUTH2.
im thinking about setting up a network of sites and would like for the forums to be the central spot for logging in.
I did notice on the boards here that CAS is enabled by default. That might work however if I read correctly it is limited to same domain emails? is this correct?
Posts: 1
Participants: 1
@accalia wrote:
Spoilers and emoji do not work correctly together.
Examples:
Input:
[spoiler]:+1:[/spoiler]Output:
:+1:Expected Output:
(even the manually constructed expected result appears to have issues here. expected results are as one would expect, spoilered text on either side of an emoji)
Input:
[spoiler]prefix text :+1: Suffix text[/spoiler]Output:
prefix text :+1: Suffix textExpected Output:
prefix textSuffix text
Posts: 6
Participants: 2
@jesselperry wrote:
Very crucial, high urgency bug
Emoji do not display anymore in a user card's description. They do appear in the description fine on the full profile page, but not on user card.
They used to appear fine on user card, not sure when they stopped working. Now it just shows the [emoji] bracket code instead of the graphic.
Posts: 2
Participants: 2
@fefrei wrote:
I'm trying to run discourse in a subdirectory. I've set up nginx on the server that forwards requests to /discourse/ to a high, firewalled port, and am trying to set up discourse to run on this port.
I have minimally adapted the standalone template to my
app.yml, which works fine - but assumes to run in the root directory. After a bit of reading configuration files, I think the needed setting isDISCOURSE_RELATIVE_URL_ROOT: /discoursein theenvblock.When setting this entry, rebuilding, and pointing a browser to
http://localhost:61001/, I get aNot Found: /, as expected. However, onhttp://localhost:61001/discourse/, I do get a blank page. Looking at the dev tools, I see that the HTML and CSS were delivered, but all JavaScript files ended up with a404.When am I doing wrong? I'm running the current
masterversion, commit904f795e17.
Posts: 8
Participants: 3
@watchmanmonitor wrote:
Continuing the discussion from Why are email addresses hidden behind a "show" button in admin?:
Hi, tell me more about this?
Posts: 2
Participants: 2
@joshmings wrote:
Discourse is running fine and I'm now looking at importing our phpBB3 forum. I've read through the threads and wanted to get your thoughts on best practice for import and testing.
Prepping old forum
Should inactive users, old posts, old categories be removed? We definitely want all the users brought over, and the popular boards/post, but don't necessarily need all the boards/categories as they are. One thought is combining everything into an 'Archive' board (an Archive category on our new Discourse site) to keep things clean.Testing phpBB 3 import
Is there a method for testing the connection and import for a subset of the forum? My thoughts are putting a sample set into another db, unless there's a way to limit it through the importer.What are your suggestions?
Posts: 1
Participants: 1
@tenzan wrote:
Hi all,
I've just setup brand new Discourse.
Welcome message sent to new user is not showing images (broken image?).
What is it happening so?
(It seems I can't upload image as I'm new user here)
Thanks.
Posts: 17
Participants: 2
@tenzan wrote:
I found several search results for this questions, but none of them answered to my question.
In traditional forum software you delete/configure in the admin panel.
In Discourse, as I understood, creating is done on the page were you click on Categories from the Top page.
I can't figure out how to remove a category name, I don't see the remove button...Thanks.
Posts: 5
Participants: 4
@tenzan wrote:
Recommended environment:
- Dual core CPU recommended
- 1 GB RAM minimum (with swap)
- 64 bit Linux compatible with Docker
The above is for 1 domain, I assume.
What are the minimum specs requirements for multisite discourse?
If I want to host 2 domains, does it mean I will need at least2GB RAM?
How about hosting 3 domains?
Posts: 2
Participants: 1
@Matthieu wrote:
Error in our logs
Uncaught TypeError: Discourse.start is not a function Url: https://forum.poppy-project.org/t/alternative-to-solidworks/152 Line: 770 Column: 13 Window Location: https://forum.poppy-project.org/t/alter
Uncaught TypeError: Discourse.start is not a function
Url: https://forum.poppy-project.org/t/alternative-to-solidworks/152
Line: 770
Column: 13
Window Location: https://forum.poppy-project.org/t/alternative-to-solidworks/152It is not really annoying, just filling our logs
Posts: 3
Participants: 2
@evantill wrote:
I could not make my simple onebox plugin working on discourse
Notes:
* Same code is working using the onebox test server
* Regexp was testedMy onebox whitelist :
Posts: 1
Participants: 1
@PJH wrote:
Attempting to upgrade from sometime after 1.4.0B1 to 1.4.0B2 aborts:
[...] == Seed from /var/www/discourse/db/fixtures/999_topics.rb *** Bundling assets. This might take a while *** $ bundle exec rake assets:precompile Purging temp files rake aborted! Tilt::ES6ModuleTranspilerTemplate::JavaScriptError: Script Timed Out (in /var/www/discourse/app/assets/javascripts/admin/controllers/admin-user-badges.js.es6) /var/www/discourse/lib/es6_module_transpiler/tilt/es6_module_transpiler_template.rb:83:in `block in evaluate' /var/www/discourse/lib/es6_module_transpiler/tilt/es6_module_transpiler_template.rb:65:in `block in protect' /var/www/discourse/lib/es6_module_transpiler/tilt/es6_module_transpiler_template.rb:63:in `synchronize' /var/www/discourse/lib/es6_module_transpiler/tilt/es6_module_transpiler_template.rb:63:in `protect' /var/www/discourse/lib/es6_module_transpiler/tilt/es6_module_transpiler_template.rb:81:in `evaluate' [...]/admin/upgrade is showing:
discourse (c761bf4) New Version Available! Remote Version: Last Updated: 16 hours ago 0 new commitsFull log at http://pastebin.com/bExYFP1N
Posts: 7
Participants: 2
@fmarco76 wrote:
Hi all,
I have developed a small sso application with flask in order to allow the the authentication using SAML in conjunction with mod_shibboleth. If you interested this is the link:
https://github.com/fmarco76/DiscourseSSO
Cheers,
Marco
Posts: 1
Participants: 1
@alefattorini wrote:
Imho this is a great piece of software, I am a community-lover
and that's the community overview that I needed a long time.
Thanks for merging my suggestions about read time and day visits, how these features are discussed it's really interesting for me since it's a real community effort
My compliments to all Discourse Team!
Posts: 1
Participants: 1
@hauleth wrote:
I'm trying to add static pages integration to some Discourse apps. For now I've started writing plugin that will integrate
high_voltagegem into that instances. For now this is simple script that just add that gem and setup routes for it:# name: low_voltage # about: Static pages for Discourse # version: 0.1 # authors: Łukasz Niemier gem 'high_voltage', '2.3.0' after_initialize do Discourse::Application.routes.append do get '/pages/*id' => 'high_voltage/pages#show' end endI've also added
app/views/pages/test.htmlfile but whenever I want to display that page I get 404 error.Am I doing something wrong or this is impossible?
Posts: 1
Participants: 1
@ankh2054 wrote:
Hi all,
Im looking at implementing a solution in wordpress where discourse becomes the SSO provider.
I already have 1000+ users on discourse and want to allow users to have accounts on the wordpress site.Does anyone know whether this is possible today using exiting plugins?
thanks
Posts: 1
Participants: 1
Very crucial, high urgency bug 
and that's the community overview that I needed a long time.
