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

Configuring nginx to work alongside Discourse

0
0

wrote:

I intend to host another website on the same machine as the one I host Discourse on. I have therefore tried to follow this guide: https://meta.discourse.org/t/advanced-setup-and-administration/15929. I can load dicourse by connecting to the ip address and port, but when I try to connect using the domain name, I only get the "Welcome to nginx" page. This is the file I have placed in /etc/nginx/sites-available

upstream discourse {
#fail_timeout is optional; I throw it in to see errors quickly
server 127.0.0.1:4001 fail_timeout=5;
}

# configure the virtual host
server {
# replace with your domain name
server_name [REMOVED (MY DOMAIN NAME)];

location / {
  proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
  proxy_set_header Host $http_host;
  proxy_redirect off;
  # pass to the upstream discourse server mentioned above
  proxy_pass http://discourse;
}

}

I have created a link to this file, that is placed in /etc/nginx/sites-enabled. I use CentOS 6.5, if that makes any difference.

Posts: 6

Participants: 3

Read full topic


Localised inline date/time

0
0

Leo McArdle wrote:

Timezones suck, especially when they make you miss meetings.

It would be incredibly useful to be able to add a date to a post, and have it automagically change into the timezone of the person reading it (if there's data to do so) or be able to click on it and have it show the time in various (or a user defined) timezone.

I'd love to propose a syntax to use, but I have no idea what makes the most sense. Obviously, it would include ISO 8601 formatted dates in some way.

Posts: 1

Participants: 1

Read full topic

QuotaExceededError - storage - exceeded the quota

0
0

Dean Taylor wrote:

From Error logs

Discourse 1.2.0.beta4 - https://github.com/discourse/discourse version 3cea85e09a5a86d7a965fb2ffd8b132659b79db0

Info

QuotaExceededError: DOM Exception 22: An attempt was made to add something to storage that exceeded the quota.
Url: http://example.com/assets/vendor-0dbc6e71b0ee5428574e3562afe91ef1.js
Line: 5
Column: 20205
Window Location: http://example.com/t/example/66158?utm_medium=email&utm_source=transactional&utm_campaign=club_email

Env

HTTP_HOST: example.com
REQUEST_URI: /logs/report_js_error
REQUEST_METHOD: POST
HTTP_USER_AGENT: Mozilla/5.0 (iPad; CPU OS 8_1_2 like Mac OS X) AppleWebKit/600.1.4 (KHTML, like Gecko) Version/8.0 Mobile/12B440 Safari/600.1.4
HTTP_ACCEPT: */*
HTTP_REFERER: http://example.com/t/example/66158?utm_medium=email&utm_source=transactional&utm_campaign=club_email
HTTP_X_FORWARDED_FOR: 86.174.1.2
HTTP_X_REAL_IP: 86.174.1.2

params:
  message: QuotaExceededError: DOM Exception 22: An attempt was made to add something to storage that exceeded t
  url: http://example.com/assets/vendor-0dbc6e71b0ee5428574e3562afe91ef1.js
  line: 5
  column: 20205
  window_location: http://example.com/t/example/66158?utm_medium=email&utm_source=transactional&

Posts: 3

Participants: 2

Read full topic

Nothing handled the action 'postChangedRoute'

0
0

Dean Taylor wrote:

Error from logs

Discourse 1.2.0.beta4 - https://github.com/discourse/discourse version 3cea85e09a5a86d7a965fb2ffd8b132659b79db0

Info

Nothing handled the action 'postChangedRoute'. If you did handle the action, this error can be caused by returning true from an action handler in a controller, causing the action to bubble.
Url:
Line:
Column:
Window Location: http://example.com/

Backtrace

Error: Nothing handled the action 'postChangedRoute'. If you did handle the action, this error can be caused by returning true from an action handler in a controller, causing the action to bubble.
    at new Error (<anonymous>)
    at Error.n (http://example.com/assets/vendor-0dbc6e71b0ee5428574e3562afe91ef1.js:8:7531)
    at Object.E [as triggerEvent] (http://example.com/assets/vendor-0dbc6e71b0ee5428574e3562afe91ef1.js:10:22558)
    at l (http://example.com/assets/vendor-0dbc6e71b0ee5428574e3562afe91ef1.js:15:22707)
    at Object.u.trigger (http://example.com/assets/vendor-0dbc6e71b0ee5428574e3562afe91ef1.js:15:14053)
    at V.extend.send (http://example.com/assets/vendor-0dbc6e71b0ee5428574e3562afe91ef1.js:10:25889)
    at o.create.send (http://example.com/assets/vendor-0dbc6e71b0ee5428574e3562afe91ef1.js:11:26441)
    at null._currentPostChanged (http://example.com/assets/application-30f67c93c3bfdd7e5c4e9d07fc512062.js:8:22230)
    at w (http://example.com/assets/vendor-0dbc6e71b0ee5428574e3562afe91ef1.js:9:15026)
    at f (http://example.com/assets/vendor-0dbc6e71b0ee5428574e3562afe91ef1.js:8:9996)

Env

HTTP_HOST: example.com
REQUEST_URI: /logs/report_js_error
REQUEST_METHOD: POST
HTTP_USER_AGENT: Mozilla/5.0 (Linux; Android 4.4.2; en-gb; SAMSUNG SM-G900F Build/KOT49H) AppleWebKit/537.36 (KHTML, like Gecko) Version/1.6 Chrome/28.0.1500.94 Mobile Safari/537.36
HTTP_ACCEPT: */*
HTTP_REFERER: http://example.com/
HTTP_X_FORWARDED_FOR: 82.45.1.2
HTTP_X_REAL_IP: 82.45.1.2

params:
  message: Nothing handled the action 'postChangedRoute'. If you did handle the action, this error can be caused
  url:
  line:
  column:
  window_location: http://example.com/
  stacktrace: Error: Nothing handled the action 'postChangedRoute'. If you did handle the action, this error can be

Posts: 1

Participants: 1

Read full topic

Automatically remove read-only mode message

0
0

Dean Taylor wrote:

When users see the read only message users are finding that after the admin as made the site read-write again users are having to refresh the page before the message disappears.

Could the message be made to update via the same polling method as notifications and other updates?

The read only message I am talking about is:
An administrator enabled read-only mode. You can continue to browse the site but interactions may not work.

Cheers,
Dean.

Posts: 4

Participants: 3

Read full topic

Store more than one IP address per user

0
0

Dean Taylor wrote:

Log more than just a single last used IP address for a user

My request would be for 3 or more IP Addresses

Generally I find that users are logging in simultaneously from multiple devices including:
- Home Desktop
- Home Tablet
- Mobile Phone
- Work Computer

A single IP is a bit pointless - whilst the two home connections may appear to be from the same IP address I usually find that the Mobile phone connects over 3G and work computer another IP.

This helps deal with systems administration, multiple accounts issues, debugging error reports found in logs and other usual items where IP address is used.

Posts: 3

Participants: 2

Read full topic

Loading times Admin User pages

0
0

Dean Taylor wrote:

Clicking though from users to a users /admin/users/{username} page takes too long...
... so long I consider this a bug.

Here is a screen capture of a click from the Admin Users list screen to a users admin page.
This is actually quite a fast example at ~32 seconds on a desktop browser (Chrome 39).

This makes clicking between profiles crazy painful.

I'm currently running:
Discourse 1.2.0.beta4 - https://github.com/discourse/discourse version 3cea85e09a5a86d7a965fb2ffd8b132659b79db0

Profiler Entries

It doesn't appear to be the queries that are actually slow - it appears to be the "Executing action: show".

Here are a few examples

#1

Executing action: show
T+534.5 ms
Reader
0.5 ms

Query

app/models/trust_level3_requirements.rb:218:in `flagged_post_ids'
app/models/trust_level3_requirements.rb:125:in `num_flagged_posts'
app/models/trust_level3_requirements.rb:36:in `requirements_met?'
app/serializers/trust_level3_requirements_serializer.rb:24:in `requirements_met'
lib/freedom_patches/ams_include_without_root.rb:55:in `include!'
app/controllers/application_controller.rb:207:in `serialize_data'
app/controllers/application_controller.rb:216:in `render_serialized'
app/controllers/admin/users_controller.rb:41:in `show'
lib/middleware/anonymous_cache.rb:119:in `call'
lib/middleware/unicorn_oobgc.rb:95:in `process_client'

SELECT "posts"."id" FROM "posts"  WHERE "posts"."user_id" = $1 AND (created_at > '2014-10-10 21:57:36.359430' AND (spam_count > 0 OR inappropriate_count > 0))

Result

Executing action: show — 1750.50 ms

#2

Executing action: show
T+2296.5 ms
Reader
0.5 ms

Query

app/models/trust_level3_requirements.rb:218:in `flagged_post_ids'
app/models/trust_level3_requirements.rb:138:in `num_flagged_by_users'
app/models/trust_level3_requirements.rb:37:in `requirements_met?'
app/serializers/trust_level3_requirements_serializer.rb:24:in `requirements_met'
lib/freedom_patches/ams_include_without_root.rb:55:in `include!'
app/controllers/application_controller.rb:207:in `serialize_data'
app/controllers/application_controller.rb:216:in `render_serialized'
app/controllers/admin/users_controller.rb:41:in `show'
lib/middleware/anonymous_cache.rb:119:in `call'
lib/middleware/unicorn_oobgc.rb:95:in `process_client'

SELECT "posts"."id" FROM "posts"  WHERE "posts"."user_id" = $1 AND (created_at > '2014-10-10 21:57:38.134558' AND (spam_count > 0 OR inappropriate_count > 0))

Result

Executing action: show — 1804.70 ms

#3

executing action: show
T+209.2 ms
Reader
0.8 ms

Query

app/models/trust_level3_requirements.rb:80:in `num_topics_replied_to'
app/models/trust_level3_requirements.rb:33:in `requirements_met?'
app/serializers/trust_level3_requirements_serializer.rb:24:in `requirements_met'
lib/freedom_patches/ams_include_without_root.rb:55:in `include!'
app/controllers/application_controller.rb:207:in `serialize_data'
app/controllers/application_controller.rb:216:in `render_serialized'
app/controllers/admin/users_controller.rb:41:in `show'
lib/middleware/anonymous_cache.rb:119:in `call'
lib/middleware/unicorn_oobgc.rb:95:in `process_client'

SELECT COUNT(distinct topic_id) FROM "posts"  WHERE ("posts"."deleted_at" IS NULL) AND "posts"."user_id" = $1 AND (created_at > '2014-10-10 21:57:36.041733' AND post_number > 1)
244.50 ms	

Result

Executing action: show — 244.50 ms

More

There are more too - but simply put they include:
1575.50 ms - SELECT "posts"."id" FROM "posts" WHERE "posts"."user_id" = $1 AND (created_at > '2014-10-10 21:57:40.053569' AND (spam_count > 0 OR inappropriate_count > 0))
2175.90 ms - SELECT "posts"."id" FROM "posts" WHERE "posts"."user_id" = $1 AND (created_at > '2014-10-10 21:57:41.625914' AND (spam_count > 0 OR inappropriate_count > 0))
1800.90 ms - SELECT "posts"."id" FROM "posts" WHERE "posts"."user_id" = $1 AND (created_at > '2014-10-10 21:57:43.889573' AND (spam_count > 0 OR inappropriate_count > 0))
1385.30 ms - SELECT "posts"."id" FROM "posts" WHERE "posts"."user_id" = $1 AND (created_at > '2014-10-10 21:57:45.688083' AND (spam_count > 0 OR inappropriate_count > 0))

Posts: 8

Participants: 3

Read full topic

Latest Update Problems - Frontend is Gone

0
0

Failcookie wrote:

I just updated my software to support the newest version, which Discourse says "discourse is at the newest version (4fd1fde)." When I go to the main site, nothing loads (http://community.completionistgamer.com/). I can see the admin panel and can navigate just fine in that area.'

Edit: I can still see a message "Version 1.2.0.beta4 1.2.0.beta5 ☺ Updates are available. Please upgrade! "

Posts: 6

Participants: 3

Read full topic


More info about wiki posts?

0
0

wrote:

Continuing the discussion from What is a wiki post?:

Hello, sorry but I would like to have more informations about wiki post. In sandbox discourse I can't create wiki posts, there is a setting to be chosen by the admin?
Or it is my fault?

I would like to know which are the features of the wiki posts... there are footnotes? Automatic table of contents...?

Where can I find more informations?
Thank you!

Posts: 2

Participants: 2

Read full topic

Disk space and backup failure notifications

0
0

Dean Taylor wrote:

It appears that one or more of the following are true:

  1. There are no backup failed notifications
  2. low disk space notifications
  3. failure notifications are not working

I have recently experienced a disk space issue where Discourse was left in a Read-only state.
Although backups had failed for a few days before this was the first time it was left read-only.

I had received no notifications of backup errors or disk space issues at all.

In addition I didn't get any notification again of the "download remote images" option being changed and it didn't appear in the staff actions log.


I have PM'ed @zogstrip to reopen this one, because it doesn't appear in any log I can't tell when this option changed.

I would expect to get some notification when errors with backups occur.

I would not expect the system to be left read-only, although this time around this was the only warning sign there was an issue.

Here is a log you might wish to review:

[STARTED]
'system' has started the backup!
Marking backup as running...
Making sure '/var/www/discourse/tmp/backups/default/2015-01-18-030000' exists...
Making sure '/var/www/discourse/public/backups/default' exists...
Writing metadata to '/var/www/discourse/tmp/backups/default/2015-01-18-030000/meta.json'...
Enabling readonly mode...
Pausing sidekiq...
Waiting for sidekiq to finish running jobs...
Dumping the public schema of the database...
pg_dump: reading schemas
pg_dump: reading user-defined tables
pg_dump: reading extensions
pg_dump: reading user-defined functions
pg_dump: reading user-defined types
pg_dump: reading procedural languages
pg_dump: reading user-defined aggregate functions
pg_dump: reading user-defined operators
pg_dump: reading user-defined operator classes
pg_dump: reading user-defined operator families
pg_dump: reading user-defined text search parsers
pg_dump: reading user-defined text search templates
pg_dump: reading user-defined text search dictionaries
pg_dump: reading user-defined text search configurations
pg_dump: reading user-defined foreign-data wrappers
pg_dump: reading user-defined foreign servers
pg_dump: reading default privileges
pg_dump: reading user-defined collations
pg_dump: reading user-defined conversions
pg_dump: reading type casts
pg_dump: reading table inheritance information
pg_dump: reading event triggers
pg_dump: finding extension members
pg_dump: finding inheritance relationships
pg_dump: reading column info for interesting tables
pg_dump: finding the columns and types of table "schema_migrations"
pg_dump: finding the columns and types of table "topics"
pg_dump: finding default expressions of table "topics"
pg_dump: finding check constraints for table "topics"
pg_dump: finding the columns and types of table "posts"
pg_dump: finding default expressions of table "posts"
pg_dump: finding the columns and types of table "users"
pg_dump: finding default expressions of table "users"
pg_dump: finding the columns and types of table "versions"
pg_dump: finding default expressions of table "versions"
pg_dump: finding the columns and types of table "topic_views"
pg_dump: finding the columns and types of table "uploads"
pg_dump: finding default expressions of table "uploads"
pg_dump: finding the columns and types of table "topic_users"
pg_dump: finding default expressions of table "topic_users"
pg_dump: finding the columns and types of table "topic_links"
pg_dump: finding default expressions of table "topic_links"
pg_dump: finding the columns and types of table "post_timings"
pg_dump: finding the columns and types of table "message_bus"
pg_dump: finding default expressions of table "message_bus"
pg_dump: finding the columns and types of table "notifications"
pg_dump: finding default expressions of table "notifications"
pg_dump: finding the columns and types of table "incoming_links"
pg_dump: finding default expressions of table "incoming_links"
pg_dump: finding the columns and types of table "post_replies"
pg_dump: finding the columns and types of table "categories"
pg_dump: finding default expressions of table "categories"
pg_dump: finding the columns and types of table "category_featured_topics"
pg_dump: finding default expressions of table "category_featured_topics"
pg_dump: finding the columns and types of table "site_settings"
pg_dump: finding default expressions of table "site_settings"
pg_dump: finding the columns and types of table "user_open_ids"
pg_dump: finding default expressions of table "user_open_ids"
pg_dump: finding the columns and types of table "user_actions"
pg_dump: finding default expressions of table "user_actions"
pg_dump: finding the columns and types of table "post_actions"
pg_dump: finding default expressions of table "post_actions"
pg_dump: finding the columns and types of table "post_action_types"
pg_dump: finding default expressions of table "post_action_types"
pg_dump: finding the columns and types of table "topic_link_clicks"
pg_dump: finding default expressions of table "topic_link_clicks"
pg_dump: finding the columns and types of table "category_featured_users"
pg_dump: finding default expressions of table "category_featured_users"
pg_dump: finding the columns and types of table "twitter_user_infos"
pg_dump: finding default expressions of table "twitter_user_infos"
pg_dump: finding the columns and types of table "email_logs"
pg_dump: finding default expressions of table "email_logs"
pg_dump: finding the columns and types of table "topic_allowed_users"
pg_dump: finding default expressions of table "topic_allowed_users"
pg_dump: finding the columns and types of table "facebook_user_infos"
pg_dump: finding default expressions of table "facebook_user_infos"
pg_dump: finding the columns and types of table "invites"
pg_dump: finding default expressions of table "invites"
pg_dump: finding the columns and types of table "topic_invites"
pg_dump: finding default expressions of table "topic_invites"
pg_dump: finding the columns and types of table "user_visits"
pg_dump: finding default expressions of table "user_visits"
pg_dump: finding the columns and types of table "email_tokens"
pg_dump: finding default expressions of table "email_tokens"
pg_dump: finding the columns and types of table "drafts"
pg_dump: finding default expressions of table "drafts"
pg_dump: finding the columns and types of table "site_customizations"
pg_dump: finding default expressions of table "site_customizations"
pg_dump: finding the columns and types of table "draft_sequences"
pg_dump: finding default expressions of table "draft_sequences"
pg_dump: finding the columns and types of table "post_search_data"
pg_dump: finding the columns and types of table "user_search_data"
pg_dump: finding the columns and types of table "category_search_data"
pg_dump: finding the columns and types of table "github_user_infos"
pg_dump: finding default expressions of table "github_user_infos"
pg_dump: finding the columns and types of table "site_texts"
pg_dump: finding the columns and types of table "user_histories"
pg_dump: finding default expressions of table "user_histories"
pg_dump: finding the columns and types of table "groups"
pg_dump: finding default expressions of table "groups"
pg_dump: finding the columns and types of table "group_users"
pg_dump: finding default expressions of table "group_users"
pg_dump: finding the columns and types of table "category_groups"
pg_dump: finding default expressions of table "category_groups"
pg_dump: finding the columns and types of table "topic_allowed_groups"
pg_dump: finding default expressions of table "topic_allowed_groups"
pg_dump: finding the columns and types of table "post_uploads"
pg_dump: finding default expressions of table "post_uploads"
pg_dump: finding the columns and types of table "optimized_images"
pg_dump: finding default expressions of table "optimized_images"
pg_dump: finding the columns and types of table "screened_emails"
pg_dump: finding default expressions of table "screened_emails"
pg_dump: finding the columns and types of table "screened_urls"
pg_dump: finding default expressions of table "screened_urls"
pg_dump: finding the columns and types of table "oauth2_user_infos"
pg_dump: finding default expressions of table "oauth2_user_infos"
pg_dump: finding the columns and types of table "plugin_store_rows"
pg_dump: finding default expressions of table "plugin_store_rows"
pg_dump: finding the columns and types of table "user_stats"
pg_dump: finding default expressions of table "user_stats"
pg_dump: finding the columns and types of table "post_details"
pg_dump: finding default expressions of table "post_details"
pg_dump: finding the columns and types of table "screened_ip_addresses"
pg_dump: finding default expressions of table "screened_ip_addresses"
pg_dump: finding the columns and types of table "api_keys"
pg_dump: finding default expressions of table "api_keys"
pg_dump: finding the columns and types of table "post_revisions"
pg_dump: finding default expressions of table "post_revisions"
pg_dump: finding the columns and types of table "topic_embeds"
pg_dump: finding default expressions of table "topic_embeds"
pg_dump: finding the columns and types of table "top_topics"
pg_dump: finding default expressions of table "top_topics"
pg_dump: finding the columns and types of table "category_users"
pg_dump: finding default expressions of table "category_users"
pg_dump: finding the columns and types of table "single_sign_on_records"
pg_dump: finding default expressions of table "single_sign_on_records"
pg_dump: finding the columns and types of table "badge_types"
pg_dump: finding default expressions of table "badge_types"
pg_dump: finding the columns and types of table "badges"
pg_dump: finding default expressions of table "badges"
pg_dump: finding the columns and types of table "user_badges"
pg_dump: finding default expressions of table "user_badges"
pg_dump: finding the columns and types of table "color_schemes"
pg_dump: finding default expressions of table "color_schemes"
pg_dump: finding the columns and types of table "color_scheme_colors"
pg_dump: finding default expressions of table "color_scheme_colors"
pg_dump: finding the columns and types of table "user_custom_fields"
pg_dump: finding default expressions of table "user_custom_fields"
pg_dump: finding the columns and types of table "category_custom_fields"
pg_dump: finding default expressions of table "category_custom_fields"
pg_dump: finding the columns and types of table "group_custom_fields"
pg_dump: finding default expressions of table "group_custom_fields"
pg_dump: finding the columns and types of table "post_custom_fields"
pg_dump: finding default expressions of table "post_custom_fields"
pg_dump: finding the columns and types of table "topic_custom_fields"
pg_dump: finding default expressions of table "topic_custom_fields"
pg_dump: finding the columns and types of table "invited_groups"
pg_dump: finding default expressions of table "invited_groups"
pg_dump: finding the columns and types of table "google_user_infos"
pg_dump: finding default expressions of table "google_user_infos"
pg_dump: finding the columns and types of table "user_avatars"
pg_dump: finding default expressions of table "user_avatars"
pg_dump: finding the columns and types of table "user_profiles"
pg_dump: finding default expressions of table "user_profiles"
pg_dump: finding the columns and types of table "quoted_posts"
pg_dump: finding default expressions of table "quoted_posts"
pg_dump: finding the columns and types of table "badge_groupings"
pg_dump: finding default expressions of table "badge_groupings"
pg_dump: finding the columns and types of table "incoming_referers"
pg_dump: finding default expressions of table "incoming_referers"
pg_dump: finding the columns and types of table "incoming_domains"
pg_dump: finding default expressions of table "incoming_domains"
pg_dump: finding the columns and types of table "topic_search_data"
pg_dump: finding the columns and types of table "badge_posts"
pg_dump: finding the columns and types of table "permalinks"
pg_dump: finding default expressions of table "permalinks"
pg_dump: finding the columns and types of table "warnings"
pg_dump: finding default expressions of table "warnings"
pg_dump: finding the columns and types of table "user_fields"
pg_dump: finding default expressions of table "user_fields"
pg_dump: finding the columns and types of table "user_exports"
pg_dump: finding default expressions of table "user_exports"
pg_dump: flagging inherited columns in subtables
pg_dump: reading indexes
pg_dump: reading indexes for table "schema_migrations"
pg_dump: reading indexes for table "topics"
pg_dump: reading indexes for table "posts"
pg_dump: reading indexes for table "users"
pg_dump: reading indexes for table "versions"
pg_dump: reading indexes for table "topic_views"
pg_dump: reading indexes for table "uploads"
pg_dump: reading indexes for table "topic_users"
pg_dump: reading indexes for table "topic_links"
pg_dump: reading indexes for table "post_timings"
pg_dump: reading indexes for table "message_bus"
pg_dump: reading indexes for table "notifications"
pg_dump: reading indexes for table "incoming_links"
pg_dump: reading indexes for table "post_replies"
pg_dump: reading indexes for table "categories"
pg_dump: reading indexes for table "category_featured_topics"
pg_dump: reading indexes for table "site_settings"
pg_dump: reading indexes for table "user_open_ids"
pg_dump: reading indexes for table "user_actions"
pg_dump: reading indexes for table "post_actions"
pg_dump: reading indexes for table "post_action_types"
pg_dump: reading indexes for table "topic_link_clicks"
pg_dump: reading indexes for table "category_featured_users"
pg_dump: reading indexes for table "twitter_user_infos"
pg_dump: reading indexes for table "email_logs"
pg_dump: reading indexes for table "topic_allowed_users"
pg_dump: reading indexes for table "facebook_user_infos"
pg_dump: reading indexes for table "invites"
pg_dump: reading indexes for table "topic_invites"
pg_dump: reading indexes for table "user_visits"
pg_dump: reading indexes for table "email_tokens"
pg_dump: reading indexes for table "drafts"
pg_dump: reading indexes for table "site_customizations"
pg_dump: reading indexes for table "draft_sequences"
pg_dump: reading indexes for table "post_search_data"
pg_dump: reading indexes for table "user_search_data"
pg_dump: reading indexes for table "category_search_data"
pg_dump: reading indexes for table "github_user_infos"
pg_dump: reading indexes for table "site_texts"
pg_dump: reading indexes for table "user_histories"
pg_dump: reading indexes for table "groups"
pg_dump: reading indexes for table "group_users"
pg_dump: reading indexes for table "category_groups"
pg_dump: reading indexes for table "topic_allowed_groups"
pg_dump: reading indexes for table "post_uploads"
pg_dump: reading indexes for table "optimized_images"
pg_dump: reading indexes for table "screened_emails"
pg_dump: reading indexes for table "screened_urls"
pg_dump: reading indexes for table "oauth2_user_infos"
...
pg_dump: executing SEQUENCE SET plugin_store_rows_id_seq
pg_dump: processing data for table "post_action_types"
pg_dump: dumping contents of table post_action_types
pg_dump: executing SEQUENCE SET post_action_types_id_seq
pg_dump: processing data for table "post_actions"
pg_dump: dumping contents of table post_actions
pg_dump: executing SEQUENCE SET post_actions_id_seq
pg_dump: processing data for table "post_custom_fields"
pg_dump: dumping contents of table post_custom_fields
pg_dump: executing SEQUENCE SET post_custom_fields_id_seq
pg_dump: processing data for table "post_details"
pg_dump: dumping contents of table post_details
pg_dump: executing SEQUENCE SET post_details_id_seq
pg_dump: processing data for table "post_replies"
pg_dump: dumping contents of table post_replies
pg_dump: processing data for table "post_revisions"
pg_dump: dumping contents of table post_revisions
pg_dump: executing SEQUENCE SET post_revisions_id_seq
pg_dump: processing data for table "post_search_data"
pg_dump: dumping contents of table post_search_data
pg_dump: processing data for table "post_timings"
pg_dump: dumping contents of table post_timings
pg_dump: processing data for table "post_uploads"
pg_dump: dumping contents of table post_uploads
pg_dump: executing SEQUENCE SET post_uploads_id_seq
pg_dump: processing data for table "posts"
pg_dump: dumping contents of table posts
pg_dump: [archiver] could not write to output file: No space left on device
EXCEPTION: pg_dump failed
/var/www/discourse/lib/backup_restore/backuper.rb:171:in `dump_public_schema'
/var/www/discourse/lib/backup_restore/backuper.rb:37:in `run'
/var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:13:in `backup!'
/var/www/discourse/app/jobs/scheduled/create_backup.rb:10:in `execute'
/var/www/discourse/app/jobs/base.rb:153:in `block (2 levels) in perform'
Notifying 'system' of the end of the backup...
Cleaning stuff up...
Removing tmp '/var/www/discourse/tmp/backups/default/2015-01-18-030000' directory...
Unpausing sidekiq...
Something went wrong while unpausing Sidekiq.
Disabling readonly mode...
--------------------------------------------
---------------- EXCEPTION -----------------
MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error.
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis/client.rb:110:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:416:in `block in del'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:37:in `block in synchronize'
/usr/local/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:37:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:415:in `del'
/var/www/discourse/lib/discourse_redis.rb:63:in `del'
/var/www/discourse/lib/discourse.rb:177:in `disable_readonly_mode'
/var/www/discourse/lib/backup_restore/backuper.rb:310:in `disable_readonly_mode'
/var/www/discourse/lib/backup_restore/backuper.rb:288:in `clean_up'
/var/www/discourse/lib/backup_restore/backuper.rb:61:in `run'
/var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:13:in `backup!'
/var/www/discourse/app/jobs/scheduled/create_backup.rb:10:in `execute'
/var/www/discourse/app/jobs/base.rb:153:in `block (2 levels) in perform'
--------------------------------------------
============================================
================ EXCEPTION =================
MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error.
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis/client.rb:110:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:416:in `block in del'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:37:in `block in synchronize'
/usr/local/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:37:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:415:in `del'
/var/www/discourse/lib/discourse_redis.rb:63:in `del'
/var/www/discourse/lib/backup_restore/backup_restore.rb:141:in `clear_shutdown_signal!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:170:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:13:in `backup!'
/var/www/discourse/app/jobs/scheduled/create_backup.rb:10:in `execute'
/var/www/discourse/app/jobs/base.rb:153:in `block (2 levels) in perform'
============================================
Sidekiq heartbeat test failed, restarting

The difference between the backup that apparently left the instance in read-only mode and that of the days previous appears to be just these extra lines in the latest log:

/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:13:in `backup!'
/var/www/discourse/app/jobs/scheduled/create_backup.rb:10:in `execute'
/var/www/discourse/app/jobs/base.rb:153:in `block (2 levels) in perform'
Notifying 'system' of the end of the backup...
Cleaning stuff up...
Removing tmp '/var/www/discourse/tmp/backups/default/2015-01-18-030000' directory...
Unpausing sidekiq...
Something went wrong while unpausing Sidekiq.
Disabling readonly mode...
--------------------------------------------
---------------- EXCEPTION -----------------
MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error.
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis/client.rb:110:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:416:in `block in del'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:37:in `block in synchronize'
/usr/local/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:37:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:415:in `del'
/var/www/discourse/lib/discourse_redis.rb:63:in `del'
/var/www/discourse/lib/discourse.rb:177:in `disable_readonly_mode'
/var/www/discourse/lib/backup_restore/backuper.rb:310:in `disable_readonly_mode'
/var/www/discourse/lib/backup_restore/backuper.rb:288:in `clean_up'
/var/www/discourse/lib/backup_restore/backuper.rb:61:in `run'
/var/www/discourse/lib/backup_restore/backup_restore.rb:161:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:13:in `backup!'
/var/www/discourse/app/jobs/scheduled/create_backup.rb:10:in `execute'
/var/www/discourse/app/jobs/base.rb:153:in `block (2 levels) in perform'
--------------------------------------------
============================================
================ EXCEPTION =================
MISCONF Redis is configured to save RDB snapshots, but is currently not able to persist on disk. Commands that may modify the data set are disabled. Please check Redis logs for details about the error.
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis/client.rb:110:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:416:in `block in del'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:37:in `block in synchronize'
/usr/local/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:37:in `synchronize'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.0/lib/redis.rb:415:in `del'
/var/www/discourse/lib/discourse_redis.rb:63:in `del'
/var/www/discourse/lib/backup_restore/backup_restore.rb:141:in `clear_shutdown_signal!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:170:in `block in start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `fork'
/var/www/discourse/lib/backup_restore/backup_restore.rb:158:in `start!'
/var/www/discourse/lib/backup_restore/backup_restore.rb:13:in `backup!'
/var/www/discourse/app/jobs/scheduled/create_backup.rb:10:in `execute'
/var/www/discourse/app/jobs/base.rb:153:in `block (2 levels) in perform'
============================================
Sidekiq heartbeat test failed, restarting

Posts: 1

Participants: 1

Read full topic

Discourse callback api

0
0

Dejan Milosevic wrote:

Do Discourse have callback api?

I need whenever someone create topic or post, to i can configure my api url where will discourse send request with data, user, title, date, etc.

I also need, if post contains specific hashtag, to append created link in post.

So, it is like this:

User postes with #recipe
Callback api sends request to other site to create link with that post and returns link url.
Discourse appends this url on post.

If this isnt implemented yet or ment to be implemented, can somebody help me or make me this for money.

Thank you very much.

offtopic: How that you have choose tags for this topic here and i am on latest discourse and dont have? Does i need to turn it on somewhere?

edit:

Where i can find list of javascript hooks?
I found easy way to create everything i want via javascript and without ruby at all in this plugin:

register_asset "javascripts/affiliate.js", :server_side

and every changes it need it has done in javascript side.

btw how can i disable this hashtag bold posting? I just need #hashtag without bolding.

i hope i am not violating any rules.

Posts: 6

Participants: 2

Read full topic

How To Configure SSo using SAML?

0
0

michael wrote:

Hi,

I'm newbe

l have a problem in configure SAML, we have to try configure
but fail. could you help how to configure SSO using SAML be success ,,,

Please Help Me....
thank's

Posts: 1

Participants: 1

Read full topic

Tags should be part of edit history

Is there a way to categorize user profiles?

0
0

Love Chopra wrote:

Hi,
I am using discourse for building educational community and I want to categorize my users based on following criteria:

  1. City
  2. Education Level
  3. Languages Known
  4. Expertise area

Also want to show public listing of users based on these above criteria, is there any way I can do this?

Posts: 1

Participants: 1

Read full topic

"Nice Post" threshold is too high for most sites, can we make it easier?

0
0

Kane York wrote:

The "Nice Post" threshold is too high for most sites, including Meta Discourse.

I think that @codinghorror has made at least four posts in the last week that would be worthy of being described as a "nice post", however he recieved a "Nice Post" badge for .. one.

Actually, let's look at the dates of the Nice Post awards:

  • Last Tuesday
  • Two weeks ago
  • Two weeks & two days ago
  • Four weeks and a day ago
  • Four weeks and three days
  • Six and a half weeks

That is a frequency more suitable for a "Silver" badge, not Bronze! Bronze badges should be easy, or at least attainable with a bit of effort.

I think that the current situation is untenable - it's denying many people and communities the 'gamification' incentives the system is clearly intended, but failing, to provide.

I think that the default like thresholds for the badges should be reduced. Here's my proposal, with numbers from this site as of last November:

  1. Welcome badge (1 like) stays where it is. Count: 17,000
  2. Nice Post (10 likes -> 5 likes) More reasonable & possible with small to medium sites. Count: 1300
  3. Good Post (25 likes -> 10 likes) This replaces the previous Nice Post levels. Count: 165
  4. Great Post (50 likes -> 25 likes) Replaces previous Good Post. Count: 12
  5. Legendary Post (N/A -> 50 likes) Replaces previous Great Post. Count: 1

(NB: The numbers for 25 and 50 likes have not changed in the interim.)

This proposal adds the previously missing level in the tiers between Welcome and 10 likes.

Even these aren't great ratios, though: compare to Stack Overflow, with approximately a division by 5 in each tier, rather than 10. But I think it'll do.

Posts: 3

Participants: 2

Read full topic


Disable email or provide Contact URL on About page

0
0

Arlair wrote:

Hi, I just set up Discourse yesterday and noticed it displays my email address on the About page. I don't want this for spam reasons. I would prefer to provide a URL for my existing WordPress contact page I am integrating with. Or at least be able to disable this section containing the email. I think this would it more flexible out of the box.

So for now though, I couldn't find a way to remove it from the About page via admin. Is this possible via some mechanism like changing a template?

Posts: 10

Participants: 4

Read full topic

Wordpress not pushing posts to Discourse

0
0

wrote:

My Wordpress installation is correctly publishing to Discourse, however it only works for one of the Discourse usernames, the original admin.

When I use any other Discourse username, the "Start the discussion" link at the bottom of the post is self-referencing.

I've replicated the issue with several posts, and the issue is the same - only the original admin account can publish posts to Discourse

Posts: 2

Participants: 1

Read full topic

Nested preformatted text in Numbered List

0
0

Nairolf wrote:

It's not possible to create a preformatted text nested in a numbered list.

Example:

  1. My first command

    $ echo hello

Posts: 8

Participants: 4

Read full topic

How do I configure "Show Full Post"

0
0

wrote:

I'd like to do the same thing they've implemented on the Boing Boing forum for blog posts ie

Show the url with a corresponding "Show Full Post" link as in the screenshot

Is this a custom implementation or is it standard Discourse?

Many thanks.

Posts: 4

Participants: 2

Read full topic

How to resubscribe to Mandrillapp Email Notifications?

0
0

Mohammad Mustafa Ahmedzai wrote:

Hi,

Thank you so much to the entire team of Discourse for bringing forward such a dynamic and multi-functional forum software. We love it and so do our readers at ask.mybloggertricks.com!

My question is that when a user who has clicked the unsubscribe link at the footer of email sent by Mandrillapp, and he is unsubscribed from future email notifications and see this on the browser:

You've been unsubscribed.
Your email address, xyz@xyz.com, has been removed from our mailing list. We're sorry to see you go, but we won't be sending any more email to your address.

How can he resubscribe to email notifications and receive regular email updates of the forum through Mandrillapp again?

Posts: 4

Participants: 3

Read full topic

Viewing all 60309 articles
Browse latest View live




Latest Images