Zach Alexander wrote:

I'm using Docker, and trying to run pg_resetxlog to fix a corrupted database. But it complains

pg_resetxlog: cannot be executed by "root"
You must run pg_resetxlog as the PostgreSQL superuser.

Posts: 2

Participants: 1

Read full topic

Jeff Atwood wrote:

One thing we're thinking about is how to determine natural breakpoints or "chapters" for long discussion topics -- and we can eventually display these breakpoints as navigation selections on the expanded topic progress bar.

Say you have a 500+ post topic that you want to explore. How do you do that?

threadwouldntdie.jpg382x576 47.2 KB

One way is to use our "summarize topic" function, which uses our internal topic hotness algorithm to produce the reader's digest condensed version of the topic -- by stripping out 80% of the posts.

The traditional answer here is pagination, but when have you ever seen a book with chapters like this?

• chapter 1: pages 1 - 50
• chapter 2: pages 51 - 100
• chapter 3: pages 101 - 150
• chapter 4: pages 151 - 200

Chapters in a book have titles, and tend to break on meaningful turning points or inflection points in the story.

So the question is, what exactly are those natural inflection points in a 500+ post topic?

We have some ideas.

Activity-based breakpoints

Conversations tend to ebb and wane. There will be 50 posts one day, then everyone goes to sleep for the night. They wake up the next day and continue the conversation. The natural breakpoints are at lulls in the conversation:

• Activity period 1: Monday - Wednesday
• Activity period 2: Thursday - Friday
• Activity period 3: Sunday
• Activity period 4: May 2015

Time-based breakpoints

But what if the conversation never pauses, never wanes? How can you have meaningful breakpoints when the participants are in so many timezones, and the conversation so intense, that it never lets up?

Maybe you could use arbitrary time based breakpoints:

• Time period 1: May 2014
• Time period 2: June 2014
• Time period 3: First week of June 2014

Hotness or Significance breakpoints

We could use our existing in-topic hotness algorithm to determine which posts in the topic had the most "heat" and display some kind of visual heatmap of the topic, a map of interesting areas in the conversation where something significant happened as measured by likes, replies, internal/external links, read time, bookmarks, and so forth on each individual post in the topic.

So those heatmap breakpoints would look like:

• Significant event 1: three days ago
• Significant event 2: yesterday
• Significant event 3: six hours ago

Posts: 8

Participants: 8

Read full topic

Justin Gordon wrote:

Did the Embedded size of youtube just change with the latest update?

It seems smaller now. Is this configurable?

Posts: 4

Participants: 3

Read full topic

probus wrote:

Continuing the discussion from Dynamically shown new/updated topics throw off counts:

Despite the recent changes, this still isn't working properly.

Kuvankaappaus 2014-6-12 kello 9.02.10.png1456x360 62.6 KB

Posts: 4

Participants: 3

Read full topic

Arpit Jalan wrote:

So you want to bulk invite users to your Discourse instance? Great, let's get started!

Prepare CSV File

For bulk inviting users you will need to prepare a CSV file (with .csv file extension) with valid email of users whom you want to invite. These points should be considered while preparing CSV file:

• Only one email per line allowed.
• Email should be in first column.
• Email should be valid.

Below is the screenshot of example csv file.

I intentionally entered invalid email on line number 6 and 7, to show error notifications.

Add Site Contact User

System notifications (automated private messages) are authored by site contact user. If you don't have site contact user set up, we recommend you to set one up by going to admin/site_settings and searching for "site contact", you will see site contact username setting, enter the username of user whom you want to be site contact user.

admin_site_contact.png1118x219 25.7 KB

Note that site contact user should be admin and he/she will not receive system notifications themselves, so make sure you don't set yourself as site contact user, doing so you will not receive process notifications.

Upload CSV File

Go to Invites page and upload the CSV file by clicking Bulk Invite from File button.

batch_invite.png1133x426 64.3 KB

If the file is uploaded successfully, you will see below confirmation message.

Check Bulk Invite Progress Notification

Once the CSV file is processed, you will receive private message notification with progress report.

process_pm.png878x567 62.6 KB

In the above screenshot the notification says 5 invites sent, this means that invitation email to 5 users has been sent. On invites pages, you will be able to see sent invites.

invitations.png848x341 39.3 KB

Also the notification says 2 invites failed, along with reason and line number.

Now, you will need to correct the errors, in this case replace invalid emails with valid emails and upload the file again with only those two emails. If everything goes well, you will receive success notification similar to as shown above.

Invites Sent

If everything goes well as described, users will receive email similar to as shown below.

Once clicking the confirmation link their account will be activated.

Congratulations! That's it, you've successfully sent out bulk invites.

Posts: 6

Participants: 4

Read full topic

Smith Airoli wrote:

Continuing the discussion from Discourse on subdirectory - doubling relative_url parameter:

Hi Demil,

I tried the steps you mentioned for setting up discourse in sub-directory, but still its not working.
Except /discourse all other requests are showing 404 response.
I did the changes to production.rb, discourse_location.js, discourse.js as you mentioned.

Kindly help.

Posts: 1

Participants: 1

Read full topic

Michael wrote:

Hello,

I wanted to use a different font on my discourse installation. So I created a new custom Stylesheet.
The compressed version of it is then saved by discourse at public/uploads/stylesheet-cache/4fd080a2-a231-4db4-afe6-17e7ed00db00.css. So far, so good. Its also reachable via and delivered by nginx (https(...)/uploads/stylesheet-cache/4fd080a2-a231-4db4-afe6-17e7ed00db00.css).

The problem is, that it is not included in the source of the Page. The only stylesheets loaded are:

<link href="/uploads/stylesheet-cache/desktop_8626410c85c198229047facb29c0bcxxxxxxxxx.css" media="screen" rel="stylesheet" />

<link href="/assets/admin-8f9c0e30a136aa1df0e32bxxxxxxx.css" media="screen" rel="stylesheet" />

The Custom CSS is enabled in (Checkbox is ticked).

When I use the preview-feature at the Custom Stylesheet page, the stylesheet does get loaded tho:

<link class="custom-css" rel="stylesheet" href="/uploads/stylesheet-cache/4fd080a2-a231-4db4-afe6-17e7ed00db00.css?767d16300f8dd6c104d1436e1dfba8ec" type="text/css" media="screen">

Any Idea why that happens?

Posts: 2

Participants: 2

Read full topic

liwei_swjtu wrote:

Hi all,I've set up my discourse install in June 2013 under the Baus's guide, and the last version I upgraded is 0.9.6.3.Since Discourse has published an official guide, the ways in these tow guide have a lot of difference, anything that I should notice? thanks a lot.

Posts: 2

Participants: 2

Read full topic

Gergely Fazekas wrote:

I think I figured out what the problem is on my installation - I adjusted the server's /etc/hosts file, so the smtp server resolves to the internal IP instead of the public one, however that goes to hell because the same setting isn't in the container's /etc/hosts file.

How can I echo the setting while bootstrapping? Because if I ssh into the container, obviously /etc/hosts is on a read-only filesystem.

Posts: 3

Participants: 2

Read full topic

Wes Osborn wrote:

Running version 0.9.9.7 via a Docker install and I'm attempting to clean-up our Discourse permissions before we roll out our Discourse install publicly. During the setup phase we had several users with Admin access to help facilitate the setup of the software. Now I'm trying to revoke that Admin access and it doesn't seem to be working.

Here are the steps I'm taking:

1. User logs out of Discourse
2. Another admin user, pulls up their profile in: /admin/users
3. Click on the Log Out button on the users profile page to make sure that they are forced out of all logged in sessions
4. Click the Revoke Admin button
5. Ask user to log back into Discourse
6. When the login they still have access to the admin menu
7. The other admin refreshes their profile page and the Admin flag has been changed back to true

I've checked /logs and I don't see anything helpful there.

One other point worthing mentioning is that we do use SSO to logon our users, but I've checked and I don't see any obvious way that would be impacting this scenario.

Posts: 4

Participants: 2

Read full topic

Admir Hodzic wrote:

I am extending Discourse with custom sharing system. I found way to add my sharing through plugin. But I have trouble on my server side reading shared post or topic. Is there any route (endpoint) which can return exact data of some post. When I do sharing i get
http: //my-forum.com/ t / name_of_post / TOPIC_ID / POST_ID / ?u=user_whic_is_sharing

Form this uri I can find topic_id and post_id so my server can handle data correctly Which endpoint I should call to get data from this post.
Can someone point me how discourse read postdata itself when handling one boxing links of discourse forum ?

If I call shared url without U param and with added .json at end of shared uri I do get json data but seems that I get all posts inside one topic when I call this url .

When I call

http://forum.robot.ba/t/442/1.json

I get json data but I do get whole topic (looks like to me).

Does that mean that my server should manually search through

RootObject/PostStream/List<Post>/Post

to get shared post ?

Posts: 1

Participants: 1

Read full topic

Michael Downey wrote:

Lately (last couple days) when I go in to Docker Manager, find that there are updates for Discourse, and click the blue button ... after clicking the "start" button I don't see any text in the black output section.

The button changes to grey and says "Upgrading...". The status/completion bar stays completely grey and never fills.

If I let it run and come back later, it seems to be updated.

Any ideas?

Posts: 4

Participants: 3

Read full topic

Simon Sapin wrote:

Discourse sends notification emails in some cases when stuff happens, which is great, but the HTML version contains misleading links.

<p>To respond, reply to this email or visit <a href="http://mandrillapp.com/track/click.php?u=3022&id=b9389b72f7394&url=http%3A%2F%2Fdiscourse.specifiction.org%2Ft%2Finitial-set-your-own-initial-styles-for-css-properties%2F198%2F7&url_id=6f6177a5a377b97e">http://discourse.specifiction.org/t/initial-set-your-own-initial-styles-for-css-properties/198/7</a> in your browser.</p>

When rendered, it looks like a link to http://discourse.specifiction.org/ but it actually goes to an unrelated domain. To a path, of all things, called /track/click.php. This smells bad. Thunderbird (at least for me) shows a big red warning "This message may be a scam."

Why is this the case? Who has access to the collected data? How is it used? Can it be disabled?

Posts: 4

Participants: 4

Read full topic

Jessp01 wrote:

Hello,

I have an existing Drupal 5 MySQL db that has all passwords stored using MD5 hashing.
Since we now want to move to Discourse, I need a way to auth against this DB.
Basically, the flow I would like to reach is:

1. User attempts to login to Discourse
2. User is Redirected to a page where the user and passwd are checked against MySQL DB
3. Post successful auth stage, user is redirected back to Discourse passing the relevant user params

So, the part I am missing is how my redirect request should look like at phase 2? i.e: what URL should I redirect back to within discourse and what params do I need to pass?

Thanks a lot in advance,

Posts: 2

Participants: 2

Read full topic

Zach Alexander wrote:

Per my flurry of threads yesterday, my postgres database has gotten corrupted, possibly due to two containers running at the same time (or some other reason).

It's working enough at the moment, but I can't complete a backup, nor restore from the most recent successful backups.

I'm going to do what I can myself with the help of Google and Stack Overflow, but any help ya'll can give along the way will be greatly appreciated.

The proximate problem I'm having right now is when I try to backup, I get

ERROR:  missing chunk number 0 for toast value 108751 in pg_toast_63466

Full log:

[2014-06-12 11:47:18] 'zach' has started the backup!
[2014-06-12 11:47:18] Marking backup as running...
[2014-06-12 11:47:18] Making sure '/var/www/discourse/tmp/backups/default/2014-06-12-184718' exists...
[2014-06-12 11:47:18] Making sure '/var/www/discourse/public/backups/default' exists...
[2014-06-12 11:47:18] Writing metadata to '/var/www/discourse/tmp/backups/default/2014-06-12-184718/meta.json'...
[2014-06-12 11:47:19] Enabling readonly mode...
[2014-06-12 11:47:19] Pausing sidekiq...
[2014-06-12 11:47:19] Waiting for sidekiq to finish running jobs...
[2014-06-12 11:47:19] Dumping the public schema of the database...
...
[2014-06-12 11:47:24] pg_dump: processing data for table "posts"
[2014-06-12 11:47:24] pg_dump: dumping contents of table posts
[2014-06-12 11:47:24] pg_dump: Dumping the contents of table "posts" failed: PQgetResult() failed.
[2014-06-12 11:47:24] pg_dump: Error message from server: ERROR:  missing chunk number 0 for toast value 108751 in pg_toast_63466
[2014-06-12 11:47:24] pg_dump: The command was: COPY public.posts (id, user_id, topic_id, post_number, raw, cooked, created_at, updated_at, reply_to_post_number, reply_count, quote_count, deleted_at, off_topic_count, like_count, incoming_link_count, bookmark_count, avg_time, score, reads, post_type, vote_count, sort_order, last_editor_id, hidden, hidden_reason_id, notify_moderators_count, spam_count, illegal_count, inappropriate_count, last_version_at, user_deleted, reply_to_user_id, percent_rank, notify_user_count, like_score, deleted_by_id, edit_reason, word_count, version, cook_method, wiki, baked_at, baked_version) TO stdout;
[2014-06-12 11:47:24] EXCEPTION: pg_dump failed
[2014-06-12 11:47:24] /var/www/discourse/lib/export/exporter.rb:167:in `dump_public_schema'
/var/www/discourse/lib/export/exporter.rb:33:in `run'
/var/www/discourse/lib/backup_restore.rb:160:in `block in start!'
/var/www/discourse/lib/backup_restore.rb:157:in `fork'
/var/www/discourse/lib/backup_restore.rb:157:in `start!'
/var/www/discourse/lib/backup_restore.rb:14:in `backup!'
/var/www/discourse/app/controllers/admin/backups_controller.rb:26:in `create'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/abstract_controller/base.rb:189:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:149:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:149:in `block in halting_and_conditional'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:229:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:229:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:166:in `block in halting'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:86:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:86:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/instrumentation.rb:31:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/notifications.rb:159:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/notifications.rb:159:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/abstract_controller/base.rb:136:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.1.1/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.1/lib/mini_profiler/profiling_methods.rb:108:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal.rb:195:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_controller/metal.rb:231:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/routing/route_set.rb:80:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/routing/route_set.rb:80:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/routing/route_set.rb:48:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/routing/mapper.rb:45:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/journey/router.rb:71:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/journey/router.rb:59:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/journey/router.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/routing/route_set.rb:676:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.2/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.2.1/lib/omniauth/builder.rb:59:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/etag.rb:23:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/conditionalget.rb:35:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/head.rb:11:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:119:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/flash.rb:254:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-0.9.4/lib/message_bus/rack/middleware.rb:55:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.1.1/lib/active_record/connection_adapters/abstract/connection_pool.rb:621:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.1/lib/active_support/callbacks.rb:82:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/remote_ip.rb:76:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-0.0.10/lib/logster/middleware/reporter.rb:23:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/quiet_logger.rb:10:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.1.1/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/methodoverride.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/runtime.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/sendfile.rb:112:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.1/lib/mini_profiler/profiler.rb:300:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/engine.rb:514:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/application.rb:144:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.1/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:138:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:65:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:572:in `process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:666:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:521:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/lib/unicorn/http_server.rb:140:in `start'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.2/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `<main>'
[2014-06-12 11:47:24] Notifying 'zach' of the end of the backup...
[2014-06-12 11:47:25] Cleaning stuff up...
[2014-06-12 11:47:25] Removing tmp '/var/www/discourse/tmp/backups/default/2014-06-12-184718' directory...
[2014-06-12 11:47:25] Unpausing sidekiq...
[2014-06-12 11:47:25] Disabling readonly mode...
[2014-06-12 11:47:25] Marking backup as finished...
[2014-06-12 11:47:25] Finished!

Posts: 2

Participants: 1

Read full topic

Dryusdan wrote:

Hello
I have (my webhost have) discourse 0.9.9.3 with french lang patch.

When I would change the permission for a category of forum (quota for us), I have some problem:

PUT https://community.olympe.in/categories/8 403 (Forbidden) vendor-a9acd18c846383250eddbd64b7c25f99.js:4

The bug is at line 4 of vendor-a9acd18c846383250eddbd64b7c25f99.js

Additionaly, I see other bug in the same action:

SyntaxError: Unexpected token <
    at Object.parse (native)
    at Function.et.parseJSON (https://community.olympe.in/assets/vendor-a9acd18c846383250eddbd64b7c25f99.js:4:16421)
    at https://community.olympe.in/assets/application-626afd97cbe2bab68eb6949e7b508599.js:3:8204
    at m (https://community.olympe.in/assets/vendor-a9acd18c846383250eddbd64b7c25f99.js:6:28992)
    at d (https://community.olympe.in/assets/vendor-a9acd18c846383250eddbd64b7c25f99.js:6:28911)
    at w (https://community.olympe.in/assets/vendor-a9acd18c846383250eddbd64b7c25f99.js:6:29708)
    at https://community.olympe.in/assets/vendor-a9acd18c846383250eddbd64b7c25f99.js:8:4902
    at Object.r.flush (https://community.olympe.in/assets/vendor-a9acd18c846383250eddbd64b7c25f99.js:6:20315)
    at Object.n.end (https://community.olympe.in/assets/vendor-a9acd18c846383250eddbd64b7c25f99.js:6:16032)
    at https://community.olympe.in/assets/vendor-a9acd18c846383250eddbd64b7c25f99.js:6:14996 vendor-a9acd18c846383250eddbd64b7c25f99.js:5

I using chrome.

If you see, know and corrected this error, I heard you

Thank

Dryusdan

Sorry for my bad english, because I'm french ^^

Posts: 3

Participants: 2

Read full topic

Jonathan wrote:

I can never get it to work when following these instructions (or any for that matter).

At best, I can make it say this in response to trying to start the server with it.

RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ROOT=~/www/discourse RAILS_ENV=production NUM_WEBS=2 bluepill --no-privileged -c ~/.bluepill load ~/www/discourse/config/discourse.pill
Killing previous bluepilld[32421]

Does anyone know why it does this? Any clues as to how I can troubleshoot?

My last attempt has the following output:

user@host:~/www/discourse$ rvm wrapper $(rvm current) bootup bluepill
Regenerating ruby-2.1.1 wrappers.........
user@host:~/www/discourse$ rvm wrapper $(rvm current) bootup bundle
Regenerating ruby-2.1.1 wrappers.........
user@host:~/www/discourse$ RUBY_GC_MALLOC_LIMIT=90000000 RAILS_ROOT=~/www/discourse RAILS_ENV=production NUM_WEBS=2 bluepill --no-privileged -c ~/.bluepill load ~/www/discourse/config/discourse.pill
user@host:~/www/discourse$

Posts: 1

Participants: 1

Read full topic

James Hayward wrote:

Hello

I have been trying to set up reply by email on a new discourse install.

We were on 0.9.9.6 and I was able to enter the settings, and I left it for a few days, but it didn't seem to work. I've realised that I entered the pop3s username incorrectly!

I have now upgraded to 0.9.9.8 and I am not able to change it - I constantly get the error "There's no user with that username"

I have tried resetting all the email settings and starting again, but I now can't even enter the old, incorrect, username. I thought it might be related to the fact that the new username doesn't look like an email address, but that doesn't seem to be the case.

Thanks

James

Posts: 1

Participants: 1

Read full topic

NomNuggetNom wrote:

Saw a new update for the "Go to Bottom" and "Go to Top" buttons today:

When clicked, it does this:

But, why not change it back to this:

And register clicks in the middle (where it says 3 of 40) to bring up a number input dialog, and retain the buttons?

Posts: 2

Participants: 2

Read full topic

Kane York wrote:

Continuing the discussion from What definition of time is this forum using?:

I think that the user activity page deserves a redesign. Here's my mockup:

2014-06-12 17.31.10.jpg2448x3264 1.98 MB

Basically, put icons in the stream, shrink down like given and received, and only put excerpts on new topics and new posts.

This should help make it not a mess of excerpts.

Posts: 8

Participants: 7

Read full topic