@tobiaseigen wrote:
Interesting - I just got my first akismet caught spam post. I then deleted the spam post and the spammer, celebrated this awesoem feature. But then I went back to my topic list. The topic the spam post was on is now at the top of the list! This seems like a bug to me since I don't see any reason to give this ancient topic that nobody else has thought to reply to zombie status.
Posts: 2
Participants: 2
@CamilleRoux wrote:
Hi,
How can I hide the click counter on a link in a post?
Thanks
Posts: 8
Participants: 4
@jesselperry wrote:
Just updated to beta 9, now my Discourse is completely white. I did the below and still have the same thing. Don't have CDN.
cd /var/discourse git pull ./launcher rebuild appAny ideas?
Posts: 27
Participants: 7
@steve_pd wrote:
So it turns out that Blizzard offer the option to authenticate via OAuth and I was wondering whether there's an existing route to add an additional OAuth 2.0 provider.
Has anyone had any success in adding another provider?
Posts: 1
Participants: 1
@Craig_Kahle wrote:
Is there a way to tell a message that is has been visited by the api_username from the API? I am mimicking the web GET request like so:
http://localhost:8100/v1/t/42439/1.json?track_visit=true&api_key=639786275e484433ff1e0c7fe71000499d82400f9018594fb609e&api_username=testUserHeaders are:
var req = { headers: { 'Accept':'application/json, text/javascript, */*', 'Content-Type' : 'application/json', 'Discourse-Track-View' : true } };Getting a 200 and JSON just fine, but the visit to the message is not being tracked. Any insight would be a huge help. Thanks!
Posts: 1
Participants: 1
@optimus wrote:
Hi there! I have been testing Discourse internally with my team for some months now, and now we're ready to have external users try it out. (They are outside of our network/domain). Earlier today, I had our network administrator open up port 80 in our firewall to allow people outside to get the Discourse forum (discourse.mydomain.org) but I get a "page cannot be displayed" error when I went outside and tried to get to the forum. So the site in not accessible from the outside for some reason :(. Can someone give me tips on which changes (if any) need to be made to make the Discourse site reachable from outside my network/domain? Do I need to change something about the Docker container settings or open some other ports in the firewall?BTW- I just tested and the Discourse is reachable from the internal network.
TIA,
Chris
Posts: 1
Participants: 1
@uwe_keim wrote:
Just upgraded this:
Which results in a non-changing progress for now about 15 minutes like this:
The logs under "/logs" contains no information.
Question:
Anything I should do (beside waiting) as the next steps?
Posts: 10
Participants: 3
@thisgeekza wrote:
For the past several versions now, I've been unable to use the Docker Manager to do an upgrade. The versions tab is blank. The other tabs do what they're supposed to. Rebuilding the container(s) works fine.
If I open the console and refresh the page, the server is returning a 500 error. If I expand the error, this is what shows (not sure if it helps with anything):
(Anonymized)
GET http://example.org/admin/docker/repos 500 (Internal Server Error) it.ajaxTransport.send @ /docker-manager-vendor:3 it.extend.ajax @ /docker-manager-vendor:3 (anonymous function) @ /docker-manager-vendor:18 y @ /docker-manager-vendor:15 h @ /docker-manager-vendor:16 o @ /docker-manager-vendor:18 r @ /docker-manager-vendor:18 n @ /docker-manager-vendor:18 o.reopenClass.findAll @ /docker-manager-app:1 y @ /docker-manager-vendor:15 h @ /docker-manager-vendor:16 o.reopenClass.findAll @ /docker-manager-app:1 s.default.r.Route.extend.model @ /docker-manager-app:1 y @ /docker-manager-vendor:9 n @ /docker-manager-vendor:9 z.extend.deserialize @ /docker-manager-vendor:10 f @ /docker-manager-vendor:15 r.runSharedModelHook @ /docker-manager-vendor:15 o.getModel @ /docker-manager-vendor:15 n @ /docker-manager-vendor:15 g @ /docker-manager-vendor:15 b @ /docker-manager-vendor:15 m @ /docker-manager-vendor:15 (anonymous function) @ /docker-manager-vendor:11 r.invoke @ /docker-manager-vendor:5 r.flush @ /docker-manager-vendor:5 i.end @ /docker-manager-vendor:5 i.run @ /docker-manager-vendor:5 y @ /docker-manager-vendor:9 l @ /docker-manager-vendor:9 (anonymous function) @ /docker-manager-vendor:6 it.Callbacks.c @ /docker-manager-vendor:2 it.Callbacks.h.fireWith @ /docker-manager-vendor:2 it.extend.ready @ /docker-manager-vendor:2 a @ /docker-manager-vendor:1This is not a major issue, but it would be nice to be able to upgrade from within the site from time to time. Any ideas as to what is broken with my setup?
Thanks.
Posts: 1
Participants: 1
@sam wrote:
I am noticing double request for topic json being initiated from "topic" and "fromParams".
The repro is quite simple:
- Navigate to a topic from topic list
- Click back
- Click on topic again and you get 2 json requests to topic just to load it.
![]()
@eviltrout can you have a look at this
Posts: 3
Participants: 3
@Howen wrote:
With version 1.3.0 beta9 :
It's not possible to save header and top sections.Remark : there is always a little icon which says "start tag seen without seeing a doctype first ..."
Posts: 6
Participants: 5
@mugli wrote:
Hi,
I'm still on a non-docker discourse. I was trying to upgrade to v1.3.0.beta9 from v1.3.0.beta3 (following this guide: https://github.com/discourse/discourse/blob/master/docs/INSTALL-ubuntu.md) and facing this error while migrating (
RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production bundle exec rake db:migrate --trace)Here's the output:
** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Invoke db:load_config (first_time) ** Execute db:load_config ** Invoke set_locale (first_time) ** Execute set_locale ** Execute db:migrate == 20150325190959 CreateQueuedPosts: migrating ================================ -- create_table(:queued_posts, {:force=>true}) rake aborted! StandardError: An error has occurred, this and all later migrations canceled: PG::UndefinedObject: ERROR: type "json" does not exist LINE 1: ...ger NOT NULL, "raw" text NOT NULL, "post_options" json NOT N... ^ : CREATE TABLE "queued_posts" ("id" serial primary key, "queue" character varying(255) NOT NULL, "state" integer NOT NULL, "user_id" integer NOT NULL, "raw" text NOT NULL, "post_options" json NOT NULL, "topic_id" integer, "approved_by_id" integer, "approved_at" timestamp, "rejected_by_id" integer, "rejected_at" timestamp, "created_at" timestamp, "updated_at" timestamp) /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/postgresql/database_statements.rb:128:in `async_exec' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/postgresql/database_statements.rb:128:in `block in execute' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract_adapter.rb:378:in `block in log' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications/instrumenter.rb:20:in `instrument' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract_adapter.rb:372:in `log' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/postgresql/database_statements.rb:127:in `execute' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/schema_statements.rb:205:in `create_table' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:656:in `block in method_missing' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:628:in `block in say_with_time' /home/doctocat/.rvm/rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/benchmark.rb:281:in `measure' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:628:in `say_with_time' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:648:in `method_missing' /var/www/discourse/db/migrate/20150325190959_create_queued_posts.rb:3:in `change' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:602:in `exec_migration' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:586:in `block (2 levels) in migrate' /home/doctocat/.rvm/rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/benchmark.rb:281:in `measure' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:585:in `block in migrate' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in `with_connection' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:584:in `migrate' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:759:in `migrate' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:998:in `block in execute_migration_in_transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:1044:in `block in ddl_transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `block in transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `within_new_transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/transactions.rb:208:in `transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:1044:in `ddl_transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:997:in `execute_migration_in_transaction' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:959:in `block in migrate' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:955:in `each' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:955:in `migrate' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:814:in `up' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/migration.rb:792:in `migrate' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:240:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:240:in `block in execute' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:235:in `each' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:235:in `execute' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain' /home/haoahaoa/.rvm/rubies/ruby-2.0.0-p353/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:172:in `invoke_with_call_chain' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/task.rb:165:in `invoke' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:150:in `invoke_task' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:106:in `block (2 levels) in top_level' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:106:in `each' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:106:in `block in top_level' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:115:in `run_with_threads' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:100:in `top_level' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:78:in `block in run' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:176:in `standard_exception_handling' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/lib/rake/application.rb:75:in `run' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.4.2/bin/rake:33:in `<top (required)>' /var/www/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `load' /var/www/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `<main>' Tasks: TOP => db:migrateCan anyone help on what I should do next?
Posts: 7
Participants: 2
@ashish2 wrote:
Link "sign up" and "create an account" buttons to different URL so that it can't open the Discourse sign up form
Posts: 2
Participants: 2
@Max_von_der_Marwitz wrote:
Have anyone managed to do this?
I have been working on it for a while now and have not found a good solution so far.
Posts: 3
Participants: 3
@brucellino wrote:
Hi all,
I'm trying to find out how to configure the upload of various kinds of files ( something which we will need ), and I followed the docs in docker/docker to https://github.com/discourse/discourse/blob/master/admin/site_settings/category/files However, this gives a 404 at the time of writing. Can anyone
- please confirm that we can indeed configure discourse to enable and disable specific kinds of files
- help me to find the correct documentation.
I would have opened an issue, but it seems that issues have been disabled on the repo.
Thanks !
Bruce
Posts: 3
Participants: 2
@Qasem_h wrote:
I want move a post to another topic but not work in persian language , I tested it in en lang it work
Posts: 5
Participants: 3
@masda70 wrote:
Setup: Unicorn behind Nginx installation with SSL. Latest Discourse (master). .zip uploads are allowed.
Operation: download an uploaded .zip file.Attempting GET request from authenticated user in Chrome at https://example.com/uploads/default/2842/e77595f6cc30a53c.zip
Result: Failed to load resource: net::ERR_INVALID_RESPONSE. Grey page.
Production log.
Started GET "/uploads/default/2842/e77595f6cc30a53c.zip" for 109.0.230.82 at 2015-05-13 12:04:21 +0200 Processing by UploadsController#show as HTML Parameters: {"site"=>"default", "id"=>"2842", "sha"=>"e77595f6cc30a53c", "extension"=>"zip"} Sent file /home/discourse/www/discourse/releases/20150513094508/public/uploads/default/2842/e77595f6cc30a53c.zip (0.1ms) Completed 200 OK in 57ms (ActiveRecord: 17.4ms) Started GET "/home/discourse/www/discourse/releases/20150513094508/public/uploads/default/2842/e77595f6cc30a53c.zip" for 109.0.230.82$ ActionController::RoutingError (No route matches [GET] "/home/discourse/www/discourse/releases/20150513094508/public/uploads/default/$ config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets' config/initializers/silence_logger.rb:26:in `call' lib/middleware/request_tracker.rb:70:in `call' lib/scheduler/defer.rb:85:in `process_client' lib/middleware/unicorn_oobgc.rb:80:in `process_client' Processing by ExceptionsController#not_found as HTML Rendered exceptions/not_found.html.erb within layouts/no_ember (13.8ms) Rendered layouts/_head.html.erb (0.1ms) Rendered common/_special_font_face.html.erb (0.4ms) Rendered common/_discourse_stylesheet.html.erb (0.3ms) Rendered application/_header.html.erb (0.1ms) Rendered text template (0.0ms) Completed 404 Not Found in 23ms (Views: 1.6ms | ActiveRecord: 5.2ms)I do not yet understand what is triggering the second request, and why the operation fails even though the first request returns a HTTP 200.
Posts: 2
Participants: 2
@lisajill wrote:
Well good morning!
We moderate our forums heavily. I'd like to keep up on moderating tags. Right now that is very difficult as there does not appear to be any sort of historical log of who tagged what.
Would it be feasible to add a log of new tags in the last day or week so that moderators/admins can go through and clean up?
I know tag moderation is one of the big gotchas with tagging. A feature like this would allow a team of moderators to keep the tagging clean and more relevant.
Thank you!
Posts: 1
Participants: 1
@Qasem_h wrote:
For see this bug :
1 : select one RTL language (fa_IR)
2:Click inNew Topicbutton in index page
3: write a emoji shortcode like:blush:
You will see something like this
Posts: 1
Participants: 1
@raul_pareja wrote:
Hi,
I have the next error when trying to "Download My Posts", I recently upgrade to the latest version v1.3.0.beta9
Job exception: undefined method `category' for nil:NilClass a min ago ! Job exception: Wrapped NoMethodError: undefined method `category' for nil:NilClass a min agoThe thing is some users are able to do it but not all of them, those who can not leave the above traces in the log
Is there any setting or config I am missing?
Thanks in advance
Posts: 2
Participants: 2
@RaceProUK wrote:
https://ρ.example.com
https://rρ.example.comIn preview:
Cooked:
Looks like when a Unicode character immediately follows the
//, the URL isn't turned into a navigable link.
Posts: 1
Participants: 1
