@zbor wrote:
I would like all topics to have category.
So if I chooseallow uncategorized topicsthen general will disapear but also I can't create category named General.How to make General category to all uncategorized topics?
Posts: 9
Participants: 2
@Lutz wrote:
On our side, trust level 3 depends on a high number of Likes. TL3 should not be easy to reach. Our user base is rather small.
The setting "tl3 requires likes received" is set to 500. Obviously, another hidden requirement is implicitly generated: "Likes Received: unique users" is set to 25% of "tl3 requires likes received".
This hidden requirement should either be disabled or freely configurable.
Example with "tl3 requires likes received" to 500 (Likes Received: unique users = 125 = 25% of 500):
Example with "tl3 requires likes received" to 100 (Likes Received: unique users = 25 = 25% of 100):
Edit: I also don't understand "Like Recived: unique days". Could be another hidden requirement.
Posts: 1
Participants: 1
@fbjerggaard wrote:
After importing data from Vanilla all my topics are blank. If I press the reply-counter (which is correct numbered) I can scroll through the posts, but the main content section is blank.
I get a bunch of these Javascript errors when opening a topic:
Uncaught TypeError: Cannot read property 'split' of null
I'm running Discourse commit a6ebe49 (newest upgrade available at the time of writing this)
Please let me know if you need any other information.
Posts: 5
Participants: 3
@veer wrote:
About 1 million topics, 20 GB of database, i am using discourse now. The RAM IS 4GB and 2 CPU's but the site got error 502 after crawling 30-40 pages, using a crawler. Site start giving error 502 after 30-40 page requests. What to do ?
Posts: 10
Participants: 4
@ChrisBeach wrote:
Seems a shame to truncate tweets when they're guaranteed to be less than 160 chars? Could the Twitter Onebox be made to allow more text?
Posts: 1
Participants: 1
@needhelp wrote:
Hi All,
A few questions if I may:
1) Post date: does anyone know why the date when a topic is created is different when viewed by different users? is the date determined by the user's local computer clock or determined by my forum's server?
I created a topic on Dec 31, 2016 but one of my site's users said the topic was shown as created on Jan 1, 2017 on his screen.
2) Date Range: is there a way to specify a date range so that I can see all topics that fall within this rage? I could only find show topics BEFORE a certain date and AFTER a certain date, but I couldn't find a specifc "start and end" range.
3) view ALL users - how can admin view all registered users? I can only see the option to view Active or New or Staff etc, but what if admin wants to view ALL users registered in the forum?
4) Hide the vertical scroll slider - can someone show me the CSS code or any other ways to hide the vertical scroll slider in desktop view? I only want the code to hide the vertical scroll slider in desktop view only and leave the mobile view unaffected.
Any suggestions would be appreciated,
Many thanks in advance.
Posts: 3
Participants: 2
@kmicic wrote:
Faced with this problem, I installed a free certificate from StartSSL for this instruction:
https://leland.me/https-discourse/After
./launch rebuild app
I get this error:
I, [2017-02-18T01:57:06.007241 #13] INFO -- : Purging temp files Bundling assets Compressing Javascript and Generating Source Maps I, [2017-02-18T01:57:06.023512 #13] INFO -- : File > /usr/local/bin/discourse chmod: +x I, [2017-02-18T01:57:06.029642 #13] INFO -- : File > /usr/local/bin/rails chmod: +x I, [2017-02-18T01:57:06.036734 #13] INFO -- : File > /usr/local/bin/rake chmod: +x I, [2017-02-18T01:57:06.043627 #13] INFO -- : File > /etc/update-motd.d/10-web chmod: +x I, [2017-02-18T01:57:06.048132 #13] INFO -- : File > /etc/logrotate.d/rails chmod: I, [2017-02-18T01:57:06.051864 #13] INFO -- : File > /etc/logrotate.d/nginx chmod: I, [2017-02-18T01:57:06.058561 #13] INFO -- : File > /etc/runit/1.d/00-ensure-links chmod: +x I, [2017-02-18T01:57:06.064783 #13] INFO -- : File > /root/.bash_profile chmod: 644 I, [2017-02-18T01:57:06.069187 #13] INFO -- : Replacing (?-mix:server.+{) with limit_req_zone $binary_remote_addr zone=flood:10m rate=$reqs_per_secondr/s; limit_req_zone $binary_remote_addr zone=bot:10m rate=$reqs_per_minuter/m; limit_req_status 429; server { in /etc/nginx/conf.d/discourse.conf I, [2017-02-18T01:57:06.070917 #13] INFO -- : Replacing (?-mix:location @discourse {) with location @discourse { limit_req zone=flood burst=$burst_per_second nodelay; limit_req zone=bot burst=$burst_per_minute nodelay; in /etc/nginx/conf.d/discourse.conf I, [2017-02-18T01:57:06.074786 #13] INFO -- : Terminating async processes I, [2017-02-18T01:57:06.075885 #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-02-18T01:57:06.076845 #13] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 155 2017-02-18 01:57:06 UTC [42-2] LOG: received fast shutdown request 2017-02-18 01:57:06 UTC [42-3] LOG: aborting any active transactions 2017-02-18 01:57:06 UTC [49-2] LOG: autovacuum launcher shutting down 155:signal-handler (1487383026) Received SIGTERM scheduling shutdown... 2017-02-18 01:57:06 UTC [46-1] LOG: shutting down 2017-02-18 01:57:06 UTC [46-2] LOG: database system is shut down 155:M 18 Feb 01:57:06.174 # User requested shutdown... 155:M 18 Feb 01:57:06.175 * Saving the final RDB snapshot before exiting. 155:M 18 Feb 01:57:06.213 * DB saved on disk 155:M 18 Feb 01:57:06.213 # Redis is now ready to exit, bye bye... /pups/lib/pups/config.rb:106:in `block (2 levels) in run_commands': Invalid run command cmd (SyntaxError) from /pups/lib/pups/config.rb:100:in `each' from /pups/lib/pups/config.rb:100:in `block in run_commands' from /pups/lib/pups/config.rb:99:in `each' from /pups/lib/pups/config.rb:99:in `run_commands' from /pups/lib/pups/config.rb:78:in `run' from /pups/lib/pups/cli.rb:31:in `run' from /pups/bin/pups:8:in `<main>' 77b9e445854ec87e7f697f10f0bc21372342b4e2a6b3cb2769179b3a4c6e160f ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than oneWhat am I doing wrong?
Posts: 2
Participants: 2
@Nick_Putman wrote:
I am the administrator of a discourse forum and I am no longer able to delete posts. I have updated to the latest version of discourse and still I have the issue.
I am not sure what I can do to troubleshoot this and would be grateful for some advice.
Thanks,
Nick
Posts: 3
Participants: 2
@ChrisBeach wrote:
Uh oh - oneboxing seems to be partially broken!
Londonist used to onebox - not anymore:
Yet other sites e.g. BBC, do still work.
Posts: 6
Participants: 2
@needhelp wrote:
Hello, can someone tell me how do I sort by Topic Creation Date on a category by category basis?
I see this thread is closed already
It says to use latest?order=created but can this be used on a category by category basis so that I am only viewing the topics in a particular category by topic creation date?
I assume I append latest?order=created to the URL but it doesn't work. It only works for viewing ALL topics.
Any advice would be appreciated.
Thanks
Posts: 2
Participants: 2
@veer wrote:
i created a buckup 5 minutes ago then tried to restrore this backup, i got the following error.
Validating metadata...
[2017-02-18 21:22:10] Current version: 20161216101352
[2017-02-18 21:22:10] Restored version: 20170215151505
[2017-02-18 21:22:10] EXCEPTION: You're trying to restore a more recent version of the schema. You should migrate first!
Discourse version is latest and updated, no change time of creating backup and importing backup.
what to do.
as backup failed i can not even rebuild the app.
rebuild get failed on DB migration.FAILED -------------------- Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake dbigrate' failed with return #<Process::Status: pid 3206 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"=>["suiscourse -c 'bundle install --deployment --verbose --without test --without delopment'", "su discourse -c 'bundle exec rake db:migrate'", "su discourse -c 'ndle exec rake assets:precompile'"]} 350f2874a5e5ab414a5317fe5c857436dd59de3545a269477d23d00ad9eb2808 ** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messagesthere may be more than oneRestroing from an older backup with matching version gives this error
[2017-02-18 22:29:02] Enabling readonly mode... [2017-02-18 22:29:02] Pausing sidekiq... [2017-02-18 22:29:02] Waiting for sidekiq to finish running jobs... [2017-02-18 22:29:02] Switching schemas... try reloading the site in 5 minutes, if successful, then reboot and restore is complete. [2017-02-18 22:29:02] Migrating the database... [2017-02-18 22:29:05] EXCEPTION: PG::UndefinedTable: ERROR: relation "user_auth_tokens" does not exist LINE 5: WHERE a.attrelid = '"user_auth_tokens"'::regc... ^ : SELECT a.attname, format_type(a.atttypid, a.atttypmod), pg_get_expr(d.adbin, d.adrelid), a.attnotnull, a.atttypid, a.atttypmod FROM pg_attribute a LEFT JOIN pg_attrdef d ON a.attrelid = d.adrelid AND a.attnum = d.adnum WHERE a.attrelid = '"user_auth_tokens"'::regclass AND a.attnum > 0 AND NOT a.attisdropped ORDER BY a.attnum [2017-02-18 22:29:05] /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/seed-fu-2.3.5/lib/seed-fu/runner.rb:46:in `eval' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/patches/db/pg.rb:90:in `async_exec' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/postgresql_adapter.rb:592:in `block in exec_no_cache' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract_adapter.rb:484:in `block in log' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/abstract_adapter.rb:478:in `log' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/postgresql_adapter.rb:592:in `exec_no_cache' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/postgresql_adapter.rb:584:in `execute_and_clear' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/postgresql/database_statements.rb:160:in `exec_query' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/postgresql_adapter.rb:733:in `column_definitions' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/postgresql/schema_statements.rb:197:in `columns' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/connection_adapters/schema_cache.rb:43:in `columns' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/attributes.rb:93:in `columns' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/attributes.rb:98:in `columns_hash' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/relation/query_methods.rb:969:in `block in create_binds' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/relation/query_methods.rb:967:in `each' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/relation/query_methods.rb:967:in `partition' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/relation/query_methods.rb:967:in `create_binds' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7.1/lib/active_record/relation/query_methods.rb:954:in `build_where'do not know what to do now.
Bump!
Posts: 1
Participants: 1
@sessionstart wrote:
Hi, after I added another site on the app, I failed to be kept in logging for both sites.
Anyone has the same problem?
Posts: 6
Participants: 4
@cpradio wrote:
Repro Steps:
- Subfolder Install
- Visit Tags page
- Click on any Tag
- Click on the tag name again in the Breadcrumb/Title
Expected:
You stay on the same pageActual:
You are redirected to theexample.com/tags/tagname(note the lack of subfolder)
Posts: 1
Participants: 1
@rubydoob wrote:
Say I have a custom rails app on a domain like www.example.com and my discourse install at forums.example.com
When users create accounts on my custom application and login, what options do I have to auto-create a discourse account and also log them into discourse?
Posts: 2
Participants: 2
@m1raz wrote:
Hello, when i run discourse_setup, it says Port 80 is used. Maybe there is something hosting installed by default, so I want to clear port 80 successfull instalation.
Port 80 appears to already be in use. If you are trying to run Discourse simultaneously with another web server like Apache or nginx, you will need to bind to a different port See https://meta.discourse.org/t/17247What I must to do to clear this Port from anything what is using it. If it would help - I'm trying to install Discourse here 185.145.253.103 (index.html appears, so something is using port 80. I'm not sure what)
Posts: 5
Participants: 3
@ky_metro wrote:
I'm getting complaints just lately that topic list links aren't working for users on IE11. They click the link but it does nothing, or loads a white page. The URL changes, but the page stays the same, or it goes blank. Opening in new tab works fine, or refreshing the page once the URL has changed.
I've confirmed this is happening on my site, but not on Meta. I'm on the latest beta. I've temporarily disabled all custom CSS styles and Babble chat plugin. I don't know what else I can do, except to steer users to a different browser. As far as I know Discourse still supports IE11, right?
Not sure if it's related, but in IE11 clicking the logo for "home" appears to cause a full page refresh. This happens on Meta as well.
Anybody care to have a look, it's here: http://forum.driveonwood.com.
Posts: 7
Participants: 4
@vvanpo wrote:
On desktop, when resizing the window down below 757px wide on a topic, #topic-closing-info forces the page to stay at least 757px wide. I've found changing
width: 757pxtomax-width: 757pxfixes the issue.
Posts: 2
Participants: 2
@Nick_Putman wrote:
Usually discourse defaults to avatars with the first letter of the username, but I am now occasionally seeing blank avatars, both for new and pre-existing users. I can download a png for these avatars, but they are just blank pngs.
How can I go about troubleshooting this?
Thanks,
Nick
Posts: 3
Participants: 3
@regnatarajan wrote:
Hello. I'm yet another newbie thinking of moving a forum over to Discourse.
What I want to know is this: If I install Discourse on a cloud server of my own somewhere, will my local install communicate with the Discourse servers for any purposes at all? In other words, if the Discourse company died, would my forum still work? Obviously I'm hoping it doesn't die but I'd like to know if I'll have time to migrate if it does.
Thanks in advance!
Posts: 5
Participants: 4
@m1raz wrote:
Configuration file at containers/app.yml updated successfully! Device "docker0" does not exist. Cannot connect to the docker daemon - verify it is running and you have accessAfter installing SMTP appers this. What I can do?
Posts: 11
Participants: 4
