Quantcast
Channel: Discourse Meta - Latest topics
Viewing all 60309 articles
Browse latest View live

Discourse is upto date, still asking for upgrade


I'm paying to fix the discourse-gate-plugin

0
0

@nixie wrote:

Here is link to the discourse-gate-plugin:

It broke once I updated Discourse last week.

It was an awesome plugin which was giving me 50+ new users daily.

I’ve reported there that the plugin is broken, looks like the OP is no more interested in developing it.

I’m ready to pay anyone who can fix this plugin.
Please contact me with your rate.

Posts: 1

Participants: 1

Read full topic

Data export failed

0
0

@Ivan_Rapekas wrote:

Hi, I tried to export data from admin dashboard and got export failed. Tried on two instances, 1.9.0.beta11, both work from folder /discuss (not from root /). How can I fix it?

Steps to reproduce:

  1. Go to admin/reports/topics or admin/reports/likes etc. It doesn’t matter, if there is a data for the period or not.
  2. Click Export
  3. Get a system topic with a result ‘Data export failed’

Log message:

Started GET "/discuss/admin/reports/topics?_=1507277465731" for 127.0.0.1 at 2017-10-06 08:11:29 +0000
Processing by Admin::ReportsController#show as JSON
  Parameters: {"_"=>"1507277465731", "type"=>"topics"}
Completed 200 OK in 18ms (Views: 0.2ms | ActiveRecord: 7.4ms)
Started POST "/discuss/export_csv/export_entity.json" for 127.0.0.1 at 2017-10-06 08:11:31 +0000
Processing by ExportCsvController#export_entity as JSON
  Parameters: {"entity"=>"report", "args"=>{"name"=>"topics", "start_date"=>"2017-09-06", "end_date"=>"2017-10-06", "group_id"=>""}}
Completed 200 OK in 14ms (Views: 0.2ms | ActiveRecord: 3.1ms)
Job exception: undefined method `data' for nil:NilClass

214

Posts: 4

Participants: 2

Read full topic

Where are images and attachments stored?

0
0

@Raphael_Haase_NL wrote:

I am running a newly setup Discourse.
Where do images and file attachments end up? In the same file system as Discourse somewhere?

Can images and attachments be offloaded to Azure Blob Storage?

Posts: 3

Participants: 3

Read full topic

"exclude rel nofollow domains" not respected inside of onebox

0
0

@abrambailey wrote:

Steps to recreate this bug:

  1. admin -> settings -> required -> add new whitelist domain

  2. ensure domain is whitelisted for oneboxing or whitelisting disabled for onebox

  3. Paste link to URL from whitelisted domain.

  4. Right click and inspect link created by onebox. rel=‘nofollow noopener’ will be present.

Posts: 1

Participants: 1

Read full topic

Feature Request: Custom Fields for Group

Drupal 7 Migration Questions

0
0

@j127 wrote:

Has anyone imported Drupal 7 passwords into Discourse? This is one area where I’m stuck on my migration.

I found this plugin and this info, but am not sure how to modify it for Drupal 7.

If I don’t migrate the passwords (leaving the password_hash and salt fields as nil), will users still be able to request new passwords? I’m a little worried about that in either case, because there are 20,000 users, and they will start getting summary emails from Discourse, which might send a lot of people to the site at once. If there is a bug with passwords or resetting them, things might get chaotic.

Temporary email address were saved during the last test import – something like tmpemail111@example.com. I don’t know why the first part of that email address was used for the name field and why the email field is blank. The email address does appear on the site itself for this user.

Is enough data included here in this sample user to have the new site run correctly in production?

=> [#<User:0x0000000723ab23
  id: 197,
  username: "SomeUser",
  created_at: Sat, 30 Apr 2012 13:17:11 UTC +00:00,
  updated_at: Mon, 01 Oct 2017 10:19:37 UTC +00:00,
  name: "Tmpemail111",
  seen_notification_id: 0,
  last_posted_at: nil,
  email: nil,
  password_hash: nil,
  salt: nil,
  active: true,
  username_lower: "someuser",
  last_seen_at: Sat, 30 Apr 2012 13:17:11 UTC +00:00,
  admin: false,
  last_emailed_at: Mon, 02 Oct 2017 23:19:33 UTC +00:00,
  trust_level: 1,
  approved: false,
  approved_by_id: nil,
  approved_at: nil,
  previous_visit_at: nil,
  suspended_at: nil,
  suspended_till: nil,
  date_of_birth: nil,
  views: 0,
  flag_level: 0,
  ip_address: nil,
  moderator: false,
  blocked: false,
  title: nil,
  uploaded_avatar_id: nil,
  locale: nil,
  suspended_at: nil,
  suspended_till: nil,
  date_of_birth: nil,
  views: 0,
  flag_level: 0,
  ip_address: nil,
  moderator: false,
  blocked: false,
  title: nil,
  uploaded_avatar_id: nil,
  locale: nil,
  primary_group_id: nil,
  registration_ip_address: nil,
  trust_level_locked: false,
  staged: false,
  first_seen_at: nil>]

Posts: 6

Participants: 2

Read full topic

No redirection when tags are renamed?

0
0

@arunsathiya wrote:

My Discourse does not seem to redirect tag page when it’s renamed. Not available on Discourse?

Posts: 1

Participants: 1

Read full topic


Add collapse button to user profile

How to create a Sub-Category

0
0

@BrickWood wrote:

Can anyone show me how to create a sub-category? Lot’s of topics about sub-subcategories and tags… but I just want to create a simple subcategory under a topic.

THX!!!

Posts: 6

Participants: 4

Read full topic

Solution for privateemail configurations

0
0

@Mohamed_farahat wrote:

several users tried to configure Discourse with privateemail without luck including me. you can read more about this problem here “Can’t get admin email to send working with using namecheap email server”. but after a month of investigations, i finally found the solution.

the main problem was the “from” field
discourse by default use noreply@yourdomain.com for notification emails but privateemail SMTP server needs the mail address of the mailbox you have.

there is no why to solve this issue while installation @codinghorror so after installation you have to re-open containers/app.yml file and make the following adjustments.

SMTP Configurations

  DISCOURSE_SMTP_ADDRESS: mail.privateemail.com
  DISCOURSE_SMTP_PORT: 587
  DISCOURSE_SMTP_USER_NAME: mailBox@yourdomain.com
  DISCOURSE_SMTP_PASSWORD: "****************"
  #DISCOURSE_SMTP_ENABLE_START_TLS: true          # (optional, default true)

1- use port 587
2- use your mailbox address instead of mailBox@yourdomain.com
3- uncomment DISCOURSE_SMTP_ENABLE_START_TLS and set it to true

Notification E-Mails Configurations

At the end of the file you would find

## Any custom commands to run after building
run:
  - exec: echo "Beginning of custom commands"
  ## If you want to set the 'From' email address for your first registration, uncomment and change:
  ## After getting the first signup email, re-comment the line. It only needs to run once.
  #- exec: rails r "SiteSetting.notification_email='mailBox@yourdomain.com'"
  - exec: echo "End of custom commands"

1- uncomment - exec: rails r "SiteSetting.notification_email='mailBox@yourdomain.com'"
2- use your mailbox address instead of mailBox@yourdomain.com

now ./launcher rebuild app and have fun :wink:

Posts: 1

Participants: 1

Read full topic

Confirmation Email Not Sent To User

0
0

@David_Kwan wrote:

Hi, a user tried to sign up on my site and did not receive the confirmation email so I had to activate her account from my admin panel. While her email shows up under her user, she is still not receiving email notifications. Does anyone have any tips for troubleshooting this so she receives email notifications again?

Posts: 9

Participants: 6

Read full topic

Sharing shared volumes

0
0

@Rob_Spencer wrote:

Hey guys,

On the topic of High Availability…

I have two containers:
web1
data

I want to create a third: web2.

Can I point to the same shared volumes for both web containers?

volumes:
  - volume:
      host: /var/discourse/shared/web
      guest: /shared
  - volume:
      host: /var/discourse/shared/web/log/var-log
      guest: /var/log

Posts: 1

Participants: 1

Read full topic

Users are not able to create Tags

0
0

@Dexter1 wrote:

Hello.

i activated Tags for users in topic but the users are not able to create tags only they can select the ones the admins created, what i can do in this case.??

Thanks.

Posts: 3

Participants: 2

Read full topic

Notifications not received for private messages I'm invited to

0
0

@ChrisBeach wrote:

I was recently invited to a PM conversation involving a moderator and member of my site.

This turned into quite an important conversation because the member was discussing paying for advertising on my forum (and had just paid, and wanted to know if I’d received the payment).

Unfortunately I never saw her most recent PM message. Discourse never alerted me to it in any way. I only found it when I saw an unexpected payment in my bank account from that member! Eventually I browsed to my messages page, and there was the message.

IMO when I’m invited into a PM chain, I should be notified of new messages in that chain.

Posts: 5

Participants: 3

Read full topic


Discourse deployment using github or bitbucket?

0
0

@eldy wrote:

I think I’ve installed discourse wrongly. I simply do git clone into my server.

If I want to modify the handlebar template like insert an ad, how do I do it now? I go into my server and cd to var/discourse, I can barely find anything, I couldn’t the template files.

What am I suppose to do should be clone a copy of discourse first into my local and git clone a copy of my local copy to my server, correct?

Posts: 7

Participants: 3

Read full topic

Importing from Vanilla, need assistance for Likes

0
0

@igot2b wrote:

Hello Discourse Community!

I’ve been playing around with migrating from Vanilla. I imported via the Vanilla import script and everything went fine so far.

Now I’m stuck and ask for your input.

I’ve been using the “Kudos” plugin in Vanilla to provide users the ability to like posts. Now I want to migrate these likes to discourse too. I found the following useful information:

I was already able to convert the data from MySQL and make it compatible with the “post_actions” table in PostgreSQL, matching the post IDs and user IDs to the new IDs and so on.

My problem:

  • I inserted one line into the post_actions table in the discourse database
  • The like would not show up when viewing the corresponding post in discourse
  • I then liked the post within discourse and the (now) two likes showed up
    • When checking the coresponding user I importet the like for, no likes where shown in the user profile
    • I don’t want to manually like every post so likes show up when viewing the post

My Questions:

  • Is there a recommended way to import likes from another source?
  • Is there a way to tell discourse to go through the post_actions table and do all the necessary actions?
    • Update posts
    • Update users
    • Update history or whatever else may be needed

Thanks if you followed so far and thank you in advance for your comment. If any furher information is needed please go ahead and ask straight away!

Posts: 3

Participants: 2

Read full topic

Discourse crashed after phpBB import

0
0

@danielK wrote:

Hey there,

I’m hosting a Discourse for a small community, which is running now for about half a year. However, before moving to DC we used a phpBB. In order to keep everything running, I decided to import the old php-board into a new and freshly installed DC, which worked totally fine so far.

After a few weeks, we decided to import another phpBB-board of a second community, since we want to have all at one place. Before doing so, I asked at the phpBB-Importer thread if it’s possible to import a second board to a running DC ( Importing from phpBB3 ). Unfortnuately, I forgot to run the SQL statements as mentioned in this thread. So I was running the import, which went well so far but after completion, hardly no new posts etc. appear. Only the user list became longer. The most critical thing by now is that no one is able to login anymore, except of a few, which were already logged in or never logged out. Luckily this is also me.

Then, I tried to import a backup and restore the old DC which failed. Anyone having an idea on what to do next? I would like to restore to the point before importing with the backup.

Posts: 2

Participants: 2

Read full topic

Installation of Discourse

0
0

@TravisM wrote:

I have a shared hosting package with midphase and would like to install discourse on it. However, I am extremely confused by the installation instructions. I can install most things but this has me stumped. I am fine after the setup wizard (playing on a localhost) But need someone to help me with the initial installation. I would prefer this done ASAP. I have no idea on the cost for this so I am open to quotes…

Posts: 5

Participants: 3

Read full topic

I'm logged into my discourse website, everything is working fine. Goto it logged out and its a blank white page

0
0

@Jeremiah_Schultz wrote:

Anyone have any idea WTF might be up with this? :disappointed_relieved::disappointed_relieved::open_mouth: My site has been completely inaccessible for who knows how long, but it is working perfectly fine for me logged in…

Any help will be very greatly appreciated.

Plugins:

discourse-adplugin 1.0.2 Y
Canned Replies 1.1 Y
discourse-details 0.4 Y
guest-gate 0.2.1 Y
discourse-narrative-bot 0.0.1 Y
discourse-nginx-performance-report 0.1 Y
discourse-presence 1.0 Y
discourse-whos-online 1.0 Y
docker_manager 0.1 Y
lazyYT 1.0.1 Y
poll 0.9 Y

Error logs:

Message

Uncaught Error: Could not find module preload-store imported from discourse/models/topic
Url: https://lazulu.net/assets/ember_jquery-a8dcbd325e04410f036f2a791d66d8316c48c5387acdd914de99a5dd6afb3cd3.js
Line: 19
Column: 10572
Window Location: NRA Gun of the Week: Smith & Wesson Performance Center Ported M&P9 Shield - Survivalism/Firearms - Lazulu.net
Backtrace

Error: Could not find module preload-store imported from discourse/models/topic
at o (https://lazulu.net/assets/ember_jquery-a8dcbd325e04410f036f2a791d66d8316c48c5387acdd914de99a5dd6afb3cd3.js:19:10578)
at i (https://lazulu.net/assets/ember_jquery-a8dcbd325e04410f036f2a791d66d8316c48c5387acdd914de99a5dd6afb3cd3.js:19:10417)
at n.state (https://lazulu.net/assets/ember_jquery-a8dcbd325e04410f036f2a791d66d8316c48c5387acdd914de99a5dd6afb3cd3.js:19:12063)
at e (https://lazulu.net/assets/ember_jquery-a8dcbd325e04410f036f2a791d66d8316c48c5387acdd914de99a5dd6afb3cd3.js:19:9876)
at require (https://lazulu.net/assets/ember_jquery-a8dcbd325e04410f036f2a791d66d8316c48c5387acdd914de99a5dd6afb3cd3.js:19:12048)
at https://lazulu.net/assets/application-ef45095b90e56ebe62969e7ebf180d223239fb5e1c6089857677ad97f1786acc.js:3:15739
Env

hostname lazulu-net-app
process_id 14579
application_version b2127600fb3213950bbdeedbcd9b99117623107f
HTTP_HOST lazulu.net
REQUEST_URI /logs/report_js_error
REQUEST_METHOD POST
HTTP_USER_AGENT Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_3 like Mac OS X) AppleWebKit/603.3.8 (KHTML, like Gecko) Version/10.0 Mobile/14G60 Safari/602.1
HTTP_ACCEPT /
HTTP_REFERER NRA Gun of the Week: Smith & Wesson Performance Center Ported M&P9 Shield - Survivalism/Firearms - Lazulu.net
HTTP_X_FORWARDED_FOR 173.252.84.56
HTTP_X_REAL_IP 173.252.84.56
params
message Uncaught Error: Could not find module preload-store imported from discourse/models/topic Url: htt
url https://lazulu.net/assets/ember_jquery-a8dcbd325e04410f036f2a791d66d8316c48c5387acdd914de99a5dd6afb3c
line 19
column 10572
window_location NRA Gun of the Week: Smith & Wesson Performance Center Ported M&P9 Shield - Survivalism/Firearms - Lazulu.net
stacktrace Error: Could not find module preload-store imported from discourse/models/topic at o (https:/

Message

Attempted to concat a non UTF-8 string in SafeBuffer - a certain op… - internal encoding UTF-8, external encoding UTF-8 attempted to append encoding ASCII-8BIT
Backtrace

/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/logger.rb:93:in add_with_opts' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/logger.rb:50:inadd’
/usr/local/lib/ruby/2.3.0/logger.rb:498:in warn' /var/www/discourse/lib/freedom_patches/safe_buffer.rb:36:inrescue in concat’
/var/www/discourse/lib/freedom_patches/safe_buffer.rb:8:in concat' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/buffers.rb:12:in<<’
/var/www/discourse/app/views/exceptions/not_found.html.erb:36:in _app_views_exceptions_not_found_html_erb__387294119657539499_69993632573200' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/template.rb:145:inblock in render’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications.rb:166:in instrument' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/template.rb:333:ininstrument’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/template.rb:143:in render' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/mini_profiler/profiling_methods.rb:76:inblock in profile_method’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/renderer/template_renderer.rb:54:in block (2 levels) in render_template' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/renderer/abstract_renderer.rb:39:inblock in instrument’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications.rb:164:in block in instrument' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications/instrumenter.rb:20:ininstrument’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications.rb:164:in instrument' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/renderer/abstract_renderer.rb:39:ininstrument’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/renderer/template_renderer.rb:53:in block in render_template' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/renderer/template_renderer.rb:61:inrender_with_layout’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/renderer/template_renderer.rb:52:in render_template' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/renderer/template_renderer.rb:14:inrender’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/renderer/renderer.rb:46:in render_template' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/renderer/renderer.rb:27:inrender’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/rendering.rb:100:in _render_template' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/streaming.rb:217:in_render_template’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/rendering.rb:83:in render_to_body' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rendering.rb:32:inrender_to_body’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/renderers.rb:37:in render_to_body' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/abstract_controller/rendering.rb:43:inrender_to_string’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rendering.rb:21:in render_to_string' /var/www/discourse/app/controllers/application_controller.rb:593:inbuild_not_found_page’
/var/www/discourse/app/controllers/application_controller.rb:165:in rescue_discourse_actions' /var/www/discourse/app/controllers/application_controller.rb:140:inblock in class:ApplicationController
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/rescuable.rb:112:in instance_exec' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/rescuable.rb:112:inblock in handler_for_rescue’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/rescuable.rb:80:in rescue_with_handler' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rescue.rb:15:inrescue_with_handler’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rescue.rb:32:in rescue in process_action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rescue.rb:29:inprocess_action’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/instrumentation.rb:32:in block in process_action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications.rb:164:inblock in instrument’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications/instrumenter.rb:20:in instrument' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/notifications.rb:164:ininstrument’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/instrumentation.rb:30:in process_action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/params_wrapper.rb:250:inprocess_action’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/railties/controller_runtime.rb:18:in process_action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/abstract_controller/base.rb:137:inprocess’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.9/lib/action_view/rendering.rb:30:in process' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/mini_profiler/profiling_methods.rb:76:inblock in profile_method’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal.rb:196:in dispatch' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal/rack_delegation.rb:13:indispatch’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_controller/metal.rb:237:in block in action' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/routing/route_set.rb:74:indispatch’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/routing/route_set.rb:43:in serve' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/journey/router.rb:43:inblock in serve’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/journey/router.rb:30:in each' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/journey/router.rb:30:inserve’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/routing/route_set.rb:817:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:189:in call!' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/strategy.rb:167:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.6.1/lib/omniauth/builder.rb:63:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/conditionalget.rb:25:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/head.rb:13:in call' /var/www/discourse/lib/middleware/anonymous_cache.rb:147:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/params_parser.rb:27:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/flash.rb:260:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:225:in context' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/session/abstract/id.rb:220:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/cookies.rb:560:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/query_cache.rb:36:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.9/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/callbacks.rb:29:inblock in call’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:88:in __run_callbacks__' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:778:in_run_call_callbacks’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.9/lib/active_support/callbacks.rb:81:in run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/callbacks.rb:27:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/remote_ip.rb:78:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/debug_exceptions.rb:17:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/show_exceptions.rb:30:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.7/lib/logster/middleware/reporter.rb:31:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/rack/logger.rb:38:in call_app' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/rack/logger.rb:22:incall’
/var/www/discourse/config/initializers/100-quiet_logger.rb:17:in call_with_quiet_assets' /var/www/discourse/config/initializers/100-silence_logger.rb:29:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.9/lib/action_dispatch/middleware/request_id.rb:21:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/methodoverride.rb:22:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/runtime.rb:18:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/sendfile.rb:113:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.5/lib/mini_profiler/profiler.rb:171:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.5/lib/message_bus/rack/middleware.rb:63:incall’
/var/www/discourse/lib/middleware/request_tracker.rb:73:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/engine.rb:518:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/application.rb:165:in call' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/railtie.rb:194:inpublic_send’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.9/lib/rails/railtie.rb:194:in method_missing' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:66:inblock in call’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:in each' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.8/lib/rack/urlmap.rb:50:incall’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:606:in process_client' /var/www/discourse/lib/scheduler/defer.rb:85:inprocess_client’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:702:in worker_loop' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:549:inspawn_missing_workers’
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/lib/unicorn/http_server.rb:142:in start' /var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.3.0/bin/unicorn:126:in<top (required)>’
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in load' /var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:22:in'
Env

hostname lazulu-net-app
process_id 331
application_version 87b4246c14eccb77a67839c727c336b224fb584b
HTTP_HOST lazulu.net
REQUEST_URI /t/a-certain-op%E2%80%A6
REQUEST_METHOD GET
HTTP_USER_AGENT Mozilla/5.0 (compatible; MJ12bot/v1.4.7; http://mj12bot.com/)
HTTP_ACCEPT text/html,text/plain,text/xml,text/*,application/xml,application/xhtml+xml,application/rss+xml,application/atom+xml,application/rdf+xml,application/php,application/x-php,application/x-httpd-php
HTTP_X_FORWARDED_FOR 88.198.19.164
HTTP_X_REAL_IP 88.198.19.164

Message

Uncaught TypeError: injectionJavaScriptObject_.captureReady is not a function
Url:
Line: 1
Column: 276
Window Location: USA Today Poll: ‘Americans Say Trump Is Wrong on NFL Protests’ Fans Say Player Protests Are ‘Appropriate’ - Conservative - Lazulu.net
Backtrace

TypeError: injectionJavaScriptObject_.captureReady is not a function
at javaReady_ (:1:276)
at HTMLDocument.contentReady_ (:1:327)
Env

hostname lazulu-net-app
process_id 331
application_version 87b4246c14eccb77a67839c727c336b224fb584b
HTTP_HOST lazulu.net
REQUEST_URI /logs/report_js_error
REQUEST_METHOD POST
HTTP_USER_AGENT Mozilla/5.0 (Linux; Android 7.0; SM-G935T Build/NRD90M; wv) AppleWebKit/537.36 (KHTML, like Gecko) Version/4.0 Chrome/61.0.3163.98 Mobile Safari/537.36 ACHEETAHI/1
HTTP_ACCEPT /
HTTP_REFERER USA Today Poll: ‘Americans Say Trump Is Wrong on NFL Protests’ Fans Say Player Protests Are ‘Appropriate’ - Conservative - Lazulu.net
HTTP_X_FORWARDED_FOR 74.132.252.144
HTTP_X_REAL_IP 74.132.252.144
params
message Uncaught TypeError: injectionJavaScriptObject_.captureReady is not a function Url: Line: 1 Colum
url
line 1
column 276
window_location https://lazulu.net/t/usa-today-poll-americans-say-trump-is-wrong-on-nfl-protests-fans-say-player-prot
stacktrace TypeError: injectionJavaScriptObject_.captureReady is not a function at javaReady_ (<anon

Message

Uncaught TypeError: Discourse.start is not a function
Url: Report: Russian Hackers Stole U.S. Cyber Secrets from NSA - Conservative - Lazulu.net
Line: 227
Column: 15
Window Location: Report: Russian Hackers Stole U.S. Cyber Secrets from NSA - Conservative - Lazulu.net
Backtrace

TypeError: Discourse.start is not a function
at https://lazulu.net/t/report-russian-hackers-stole-u-s-cyber-secrets-from-nsa/3290:227:15
at https://lazulu.net/t/report-russian-hackers-stole-u-s-cyber-secrets-from-nsa/3290:231:5
Env

hostname lazulu-net-app
process_id 14672
application_version b2127600fb3213950bbdeedbcd9b99117623107f
HTTP_HOST lazulu.net
REQUEST_URI /logs/report_js_error
REQUEST_METHOD POST
HTTP_USER_AGENT Mozilla/5.0 (iPhone; CPU iPhone OS 10_3_3 like Mac OS X) AppleWebKit/603.3.8 (KHTML, like Gecko) Version/10.0 Mobile/14G60 Safari/602.1
HTTP_ACCEPT /
HTTP_REFERER Report: Russian Hackers Stole U.S. Cyber Secrets from NSA - Conservative - Lazulu.net
HTTP_X_FORWARDED_FOR 173.252.92.119
HTTP_X_REAL_IP 173.252.92.119
params
message Uncaught TypeError: Discourse.start is not a function Url: https://lazulu.net/t/report-russian-hacker
url Report: Russian Hackers Stole U.S. Cyber Secrets from NSA - Conservative - Lazulu.net
line 227
column 15
window_location Report: Russian Hackers Stole U.S. Cyber Secrets from NSA - Conservative - Lazulu.net
stacktrace TypeError: Discourse.start is not a function at https://lazulu.net/t/report-russian-hackers-stole

Posts: 3

Participants: 2

Read full topic

Viewing all 60309 articles
Browse latest View live




Latest Images