@User143 wrote:
For example my wordpress url is site.wordpress.com and discourse url is discourse.site.com then how can we set my end point url for SSO?
Is it possible to enable the Auth0 SSO in discourse??
Posts: 3
Participants: 2
@User143 wrote:
For example my wordpress url is site.wordpress.com and discourse url is discourse.site.com then how can we set my end point url for SSO?
Is it possible to enable the Auth0 SSO in discourse??
Posts: 3
Participants: 2
@vulkanino wrote:
I'm trying to translate: "Poll must have different options."
Does "different" mean not-equal or does it mean various (more than one)?
Posts: 3
Participants: 2
@raul_pareja wrote:
Hi all,
I am getting this error when trying to update from v1.1.0.beta3 to v1.1.0.beta4, actually I got this when I do the db:migrate after getting the version v1.1.0.beta4 from git
git reset --hard v1.1.0.beta4
After that I stop the application and run bundle install --without test --deployment, but the next step fails
RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ENV=production bundle exec rake db:migrate --trace ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Invoke db:load_config (first_time) ** Execute db:load_config ** Execute db:migrate == 20140924192418 RenameContentType: migrating ================================ -- rename_column(:site_contents, :content_type, :text_type) -> 0.0044s -- rename_column(:site_contents, :content, :value) -> 0.0018s -- rename_table(:site_contents, :site_texts) rake aborted! StandardError: An error has occurred, this and all later migrations canceled: PG::Error: ERROR: relation "site_texts" already exists : ALTER TABLE "site_contents" RENAME TO "site_texts"/fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.2/lib/patches/sql_patches.rb:160:in `exec' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.2/lib/patches/sql_patches.rb:160:in `async_exec' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/connection_adapters/postgresql/database_statements.rb:128:in `block in execute' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract_adapter.rb:373:in `block in log' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.6/lib/active_support/notifications/instrumenter.rb:20:in `instrument' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract_adapter.rb:367:in `log' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/connection_adapters/postgresql/database_statements.rb:127:in `execute' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/connection_adapters/postgresql/schema_statements.rb:381:in `rename_table' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:649:in `block in method_missing' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:621:in `block in say_with_time' /home/kingadmin/.rvm/rubies/ruby-2.0.0-p576/lib/ruby/2.0.0/benchmark.rb:281:in `measure' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:621:in `say_with_time' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:641:in `method_missing' /fjord/discourse/db/migrate/20140924192418_rename_content_type.rb:5:in `change' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:595:in `exec_migration' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:579:in `block (2 levels) in migrate' /home/kingadmin/.rvm/rubies/ruby-2.0.0-p576/lib/ruby/2.0.0/benchmark.rb:281:in `measure' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:578:in `block in migrate' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:294:in `with_connection' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:577:in `migrate' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:752:in `migrate' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:991:in `block in execute_migration_in_transaction' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:1037:in `block in ddl_transaction' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `block in transaction' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract/database_statements.rb:209:in `within_new_transaction' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/connection_adapters/abstract/database_statements.rb:201:in `transaction' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/transactions.rb:208:in `transaction' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:1037:in `ddl_transaction' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:990:in `execute_migration_in_transaction' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:952:in `block in migrate' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:948:in `each' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:948:in `migrate' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:807:in `up' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/migration.rb:785:in `migrate' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.6/lib/active_record/railties/databases.rake:34:in `block (2 levels) in <top (required)>' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:240:in `call' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:240:in `block in execute' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:235:in `each' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:235:in `execute' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:179:in `block in invoke_with_call_chain' /home/kingadmin/.rvm/rubies/ruby-2.0.0-p576/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:172:in `invoke_with_call_chain' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/task.rb:165:in `invoke' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:150:in `invoke_task' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:106:in `block (2 levels) in top_level' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:106:in `each' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:106:in `block in top_level' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:115:in `run_with_threads' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:100:in `top_level' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:78:in `block in run' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:176:in `standard_exception_handling' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/lib/rake/application.rb:75:in `run' /fjord/discourse/vendor/bundle/ruby/2.0.0/gems/rake-10.3.2/bin/rake:33:in `<top (required)>' /fjord/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `load' /fjord/discourse/vendor/bundle/ruby/2.0.0/bin/rake:23:in `<main>' Tasks: TOP => db:migrate
Did I miss something important? the migration complains of the rename_table because the "site_texts" already exists, can I skip this somehow or how can I check the integrity of the database in order to try to upgrade to another newer version?
Many thanks in advance
Posts: 3
Participants: 2
@yamikuronue wrote:
I'm trying to find a thread called "You know you've been spending too much time on TDWTF when".
For some reason, when I enter "you've" as a search term, it screws up the results:
Am I doing something wrong here?
Posts: 4
Participants: 2
@Mischief wrote:
I'm noticing on my mandrill account that emails from my installation are being sent to anonymous users at a Discourse created address. Naturally these are bouncing.
I'm using v1.3.0.beta6 +185
Could we either have no email address allocated to anonymous users or have it set up so all emails out to them are suppressed.
Posts: 2
Participants: 2
@clay wrote:
Here's what I did:
- Select 1 post and use it to create a new topic.
- Select 9 more posts and try to move them to the topic created in step 1. Chronologically, they came before the post selected in 1.
- Encountered the following error. It manifested as the button on the "move posts" modal as stuck in the "Saving..." state:
The logs showed the following two errors:
Job exception: Couldn't find Post with 'id'=3606 [WHERE ("posts"."deleted_at" IS NULL)]
The full backtrace was:
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/relation/finder_methods.rb:320:in `raise_record_not_found_exception!' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/relation/finder_methods.rb:429:in `find_one' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/relation/finder_methods.rb:413:in `find_with_ids' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/relation/finder_methods.rb:68:in `find' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.9/lib/active_record/querying.rb:3:in `find' /var/www/discourse/app/jobs/regular/post_alert.rb:5:in `execute' /var/www/discourse/app/jobs/base.rb:153:in `block (2 levels) in perform'
And also this error:
Job exception: Wrapped ActiveRecord::RecordNotFound: Couldn't find Post with 'id'=3606 [WHERE ("posts"."deleted_at" IS NULL)]
With this backtrace:
/var/www/discourse/app/jobs/base.rb:178:in `perform' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/processor.rb:75:in `execute_job' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/processor.rb:52:in `block (2 levels) in process' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/chain.rb:127:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/chain.rb:127:in `block in invoke' /var/www/discourse/lib/sidekiq/pausable.rb:81:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/chain.rb:129:in `block in invoke' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/server/active_record.rb:6:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/chain.rb:129:in `block in invoke' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/server/retry_jobs.rb:74:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/chain.rb:129:in `block in invoke' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/server/logging.rb:11:in `block in call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/logging.rb:24:in `with_context' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/server/logging.rb:7:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/chain.rb:129:in `block in invoke' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/chain.rb:132:in `call' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/middleware/chain.rb:132:in `invoke' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/processor.rb:51:in `block in process' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/processor.rb:98:in `stats' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/sidekiq-3.3.2/lib/sidekiq/processor.rb:50:in `process' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in `public_send' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:26:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/calls.rb:122:in `dispatch' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:60:in `block in invoke' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/cell.rb:71:in `block in task' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/actor.rb:357:in `block in task' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/tasks.rb:57:in `block in initialize' /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/celluloid-0.16.0/lib/celluloid/tasks/task_fiber.rb:15:in `block in create'
Posts: 1
Participants: 1
@clay wrote:
- Find an existing topic and use the mod tools to select a post or two
- Click to move the posts to a new topic.
- Enter a topic title, but leave the category default selection alone.
- Move the posts.
The new topic will be created without a category. I've been able to reproduce this consistently. On my discourse instance, users are not allow to create posts without a category.
Posts: 3
Participants: 2
@Onyx wrote:
It seems to be isolated only to links to other Discourse instances though.
Repro steps, with "Open external links in new tab" enabled in options:
- Reply to a post containing a link to another Discourse instance (not a oneboxed post)
- Click the "Reply to" indicator.
- Click on the link
- external links to non-Discourse sites seem to work fine
- links to other Discourse instances open in same tab
- EXCEPTION: http://what.thedailywtf.com behaves correctly
Reproduced here in a PM chain.
Posts: 1
Participants: 1
@CamilleRoux wrote:
I love the Discourse Cheat Sheet from Sitepoint. Is it possible to add this kind of subject by default and add translation too ?
PS: The Explanation of Trust Levels is good too
Posts: 1
Participants: 1
@RaceProUK wrote:
I've seen it with H1s; not sure if it affects all header levels. Anyway, I'll use the next few posts to demonstrate the issue.
Edit: Here we go:
Does appear to be a specific H1 issue.
It affects reply chains going the other way too; can't show that here though, as the UI element needed to view the back-chain is hidden.
Posts: 7
Participants: 3
@AlexAB wrote:
I am trying to edit the profile questions that are shown in a users profile, see the red box for example. I looked through the backend and can't find that option anywhere! I am wondering if it was moved or removed or where I can find it to edit/update those questions?
Thanks,
Posts: 3
Participants: 1
@Mohammad wrote:
After the recent upgarde my poll list turned static. Neither is it showing poll results nor giving option to cast a vote. Kindly check into this problem and let me know how can I retrieve the old poll results.
Posts: 20
Participants: 4
@TechnoBear wrote:
Presumably others have noticed this, but I'll post it anyway:
(Here on meta.)
Posts: 5
Participants: 4
@dashohoxha wrote:
The only way that I have seen for embedding comments in a static site through Discourse is the one described in this blog: http://eviltrout.com/2014/01/22/embedding-discourse.html
However I find that approach a bit complicated, and having many assumptions/restrictions that don't fit many users. At least it does not work for me, it does not work the way that I want.A better approach in my opinion would be to build a plugin that works as described below.
On the page that embeds the comments we include code like this (not generated by the plugin):
<div id="discourse-comments"></div> <script type="text/javascript"> var discourseUrl = "http://discuss.btranslator.org/"; function showDiscourseTopic(topic) { var comments = document.getElementById('discourse-comments'); var iframe = document.getElementById('discourse-embed-frame'); if (iframe) { iframe.remove(); } iframe = document.createElement('iframe'); iframe.src = discourseUrl + '/t/' + topic + '/?embedded=true'; iframe.id = 'discourse-embed-frame'; iframe.width = '100%'; iframe.height = '500px'; iframe.frameBorder = '0'; iframe.scrolling = 'yes'; comments.appendChild(iframe); }; showDiscourseTopic('create-at-least-5-public-topics-and-30-public-posts-to-get-discussion-started'); </script>
One of the problems with the code above is that it does not set the height of the iFrame to match the height of the content. I think that iFrame Resizer can be used to fix it. This requires the script iframeResizer.contentWindow.min.js to be included in the page contained within the iFrame. This can be done by the plugin, but only when the GET parameter
?embedded=true
is passed to the url.Another problem is that it displays extra content, which are useful in a full page display but are useless in an embedded display. This can be fixed by adding extra CSS code, which are included by the plugin only when the GET parameter
?embedded=true
is defined, and which hides the parts of the page that are irrelevant for the embedded case. As an example see the difference between https://btranslator.org/vocabulary/ICT_sq and https://btranslator.org/vocabulary/ICT_sq?display=iframe . The second case is more suitable to be displayed inside an iFrame.An extra functionality that is important for seamless comment integration (at least for my case), is that if the current page has no comments, the corresponding discourse topic should not exist and should not be created. Maybe the plugin can detect automatically that the requested topic does not exist and should just display a Reply/Comment input box. When the first comment is submitted, the topic should be created automatically and the first comment appended to it. Or maybe this issue can be solved by the javascript that is embedded on the page, using the API.
I could have tried to build this plugin myself, but I am not familiar with RoR and with the Discourse details, so I need some help. From what I have seen around (in other discussions) at least the first 2 steps should not be very difficult. But maybe the last step is not too difficult either.
Posts: 3
Participants: 1
@amccormack wrote:
My discourse site has about a dozen users, and we use the site in bursts, and not with regular frequency. I made a post on April 29th, (the first in about 2 weeks), but no email digest was ever sent out to anyone. If I use the "Digest Preview" for that week, nothing is rendered.
I can confirm that my mail settings are correct, as other discourse mails work, but no digest emails appear in the sent logs (or the logs for my mail provider).
Here are some settings that I thought might be relevant:
- The site is Invite Only and Login Required and doesn't allow new registration
- digest min excerpt length = 100 (The post in question is more than 100 characters)
- Suppress digest email after days = 365 (The site is only a few months old)
- Disable digest emails = unchecked
Because I can't even get the Digest Preview to show the post, I don't believe this is related to a user's specific settings.
How can I determine what is stopping the Mail Digest from being sent?
Posts: 3
Participants: 2
@watchmanmonitor wrote:
Continuing the discussion from Should it be possible to flag a closed issue?:
So, I'm trying to re-open this topic:
because I still have that issue.
However, I've already flagged it once, and I'm getting a 500 error on meta.
I tried to flag the follow up:
and I think it worked once, but can't tell, and I get a 500 error when I try a second time.
So, I have a new bug, and I'd like topic 27636 re-opened for discussion, please.
Posts: 3
Participants: 2
@henick wrote:
Hi, I am embedding heat maps into my discourse instance and am planning on using the Google heat maps api v3 to do so. Does anybody know if there is an existing discourse plugin to utilize?
https://developers.google.com/maps/documentation/javascript/examples/layer-heatmap
Thanks,
Ray
Posts: 2
Participants: 2
@rubydoob wrote:
Say I am hosting discourse on my domain like:
discuss.example.com
And my main site, which is a separate Rails app on:
www.example.com
I want to have a login box which simply pushes the username/pwd to the discourse login process, so then when they go to discuss.example.com they are already logged in, and also when they are at www.discourse.com I can hook into discourse and grab the user's profile information etc.
Any recommendations on how to go about doing this?
Posts: 1
Participants: 1
@franklyn wrote:
App Version: 1.3.0.beta7
The language is set as Chinese.
Backtrack is as the following:
Anyone can help? Thanks./var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/config.rb:92:in
block in missing_interpolation_argument_handler'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/interpolate/ruby.rb:29:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/interpolate/ruby.rb:29:inblock in interpolate_hash'
gsub'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/interpolate/ruby.rb:21:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/interpolate/ruby.rb:21:ininterpolate_hash'
interpolate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/interpolate/ruby.rb:17:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/backend/base.rb:152:ininterpolate'
translate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/backend/base.rb:41:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/backend/fallbacks.rb:45:inblock (2 levels) in translate'
catch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/backend/fallbacks.rb:44:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/backend/fallbacks.rb:44:inblock in translate'
each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/backend/fallbacks.rb:42:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n/backend/fallbacks.rb:42:intranslate'
block in translate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n.rb:158:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n.rb:154:incatch'
translate'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/i18n-0.7.0/lib/i18n.rb:154:in
/var/www/discourse/lib/freedom_patches/translate_accelerator.rb:64:intranslate'
create_moderator_post_in_original_topic'
/var/www/discourse/app/models/post_mover.rb:128:in
/var/www/discourse/app/models/post_mover.rb:114:innotify_users_that_posts_have_moved'
move_posts_to'
/var/www/discourse/app/models/post_mover.rb:41:in
/var/www/discourse/app/models/post_mover.rb:26:inblock in to_new_topic'
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:201:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/database_statements.rb:209:inwithin_new_transaction'
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
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/transactions.rb:208:intransaction'
to_new_topic'
/var/www/discourse/app/models/post_mover.rb:25:in
/var/www/discourse/app/models/topic.rb:603:inmove_posts'
move_posts_to_destination'
/var/www/discourse/app/controllers/topics_controller.rb:501:in
/var/www/discourse/app/controllers/topics_controller.rb:337:inmove_posts'
send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/implicit_render.rb:4:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:189:inprocess_action'
process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rendering.rb:10:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:20:inblock in process_action'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:113:incall'
block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:552:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:502:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:86:inrun_callbacks'
process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/callbacks.rb:19:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rescue.rb:29:inprocess_action'
block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:32:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:inblock in instrument'
instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications/instrumenter.rb:20:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/notifications.rb:159:ininstrument'
process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/instrumentation.rb:30:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/params_wrapper.rb:250:inprocess_action'
process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/railties/controller_runtime.rb:18:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/abstract_controller/base.rb:136:inprocess'
process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.10/lib/action_view/rendering.rb:30:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.3/lib/mini_profiler/profiling_methods.rb:106:inblock in profile_method'
dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:196:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal/rack_delegation.rb:13:indispatch'
block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_controller/metal.rb:232:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:incall'
dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:82:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:50:incall'
block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:73:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:ineach'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/journey/router.rb:59:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/routing/route_set.rb:692:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:incall!'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:incall!'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:incall!'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:incall!'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:incall!'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:186:incall!'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/strategy.rb:164:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.2/lib/omniauth/builder.rb:59:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/conditionalget.rb:35:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/head.rb:11:incall'
call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:123:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/params_parser.rb:27:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/flash.rb:254:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.11/lib/message_bus/rack/middleware.rb:67:incall'
context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/cookies.rb:562:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/query_cache.rb:36:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.10/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:29:inblock in call'
run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.10/lib/active_support/callbacks.rb:82:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/callbacks.rb:27:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/remote_ip.rb:76:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/debug_exceptions.rb:17:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/show_exceptions.rb:30:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.8.1/lib/logster/middleware/reporter.rb:31:incall'
call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:38:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/rack/logger.rb:22:incall'
call_with_quiet_assets'
/var/www/discourse/config/initializers/quiet_logger.rb:10:in
/var/www/discourse/config/initializers/silence_logger.rb:26:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.10/lib/action_dispatch/middleware/request_id.rb:21:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.3/lib/mini_profiler/profiler.rb:276:in
/var/www/discourse/lib/middleware/request_tracker.rb:70:incall'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/engine.rb:514:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/application.rb:144:incall'
public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.10/lib/rails/railtie.rb:194:inmethod_missing'
call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:138:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:65:inblock in call'
each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:incall'
process_client'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:576:in
/var/www/discourse/lib/scheduler/defer.rb:85:inprocess_client'
process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:670:inworker_loop'
spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:525:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:140:instart'
'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/bin/unicorn:126:in
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:inload'
'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in
Posts: 2
Participants: 1
@Number9 wrote:
I'm developing a rails engine plugin for Discourse. Rails, no worries. But Discourse seems like a black box. Existing Discourse plugins' code has references to such things as Discourse.SiteSettings.image_gallery_thumbnail_height, or Discourse.addInitializer(...) which implies there's a library of hooks, functions, global vars, all the useful bits you need to implement a plugin, but I have failed to find a spec. Any help is much appreciated.
Posts: 1
Participants: 1