@sicher wrote:

I’m running a local Discourse on a High Sierra machine, from master. All rspec tests pass ok and everything runs okay for a while. But after a few restarts the server just starts stalling. I’m getting some response in the logs (see below), but after some final sql query there’s nothing.

I’ve looked for stale processes, restarted and flushed redis but nothing helps short of wiping the whole thing and rebuilding it, which is very tedious.

I’ve tried to find anything on the forum about this issue, but to no avail. If anyone got a pointer as to what’s going on, I would be very grateful.

Puma starting in single mode...
* Version 3.9.1 (ruby 2.3.4-p301), codename: Private Caller
* Min threads: 0, max threads: 16
* Environment: development
* Listening on tcp://0.0.0.0:3000
Use Ctrl-C to stop
I, [2018-01-12T11:23:44.612920 #75343]  INFO -- : Started GET "/" for 127.0.0.1 at 2018-01-12 11:23:44 +0100
I, [2018-01-12T11:23:44.613970 #75343]  INFO -- : Started GET "/stylesheets/admin_787065b7345c06bae0a6b9a059aa7e02eda55089.css?__ws=localhost" for 127.0.0.1 at 2018-01-12 11:23:44 +0100
I, [2018-01-12T11:23:44.614363 #75343]  INFO -- : Started GET "/stylesheets/desktop_theme_2_79351136cf8688063df0d9c90150114b2b9bfbcf.css?__ws=localhost" for 127.0.0.1 at 2018-01-12 11:23:44 +0100
I, [2018-01-12T11:23:44.614668 #75343]  INFO -- : Started GET "/stylesheets/admin_787065b7345c06bae0a6b9a059aa7e02eda55089.css.map" for 127.0.0.1 at 2018-01-12 11:23:44 +0100
D, [2018-01-12T11:23:44.811108 #75343] DEBUG -- :    (83.4ms)  SELECT "schema_migrations"."version" FROM "schema_migrations" ORDER BY "schema_migrations"."version" ASC
I, [2018-01-12T11:23:44.980174 #75343]  INFO -- : Processing by ListController#latest as HTML
D, [2018-01-12T11:23:45.068186 #75343] DEBUG -- :    (22.5ms)  SELECT "schema_migrations"."version" FROM "schema_migrations" ORDER BY "schema_migrations"."version" ASC
D, [2018-01-12T11:23:45.068723 #75343] DEBUG -- :    (25.4ms)  SELECT "schema_migrations"."version" FROM "schema_migrations" ORDER BY "schema_migrations"."version" ASC
D, [2018-01-12T11:23:45.073171 #75343] DEBUG -- :    (3.5ms)  SELECT "schema_migrations"."version" FROM "schema_migrations" ORDER BY "schema_migrations"."version" ASC
I, [2018-01-12T11:23:45.105083 #75343]  INFO -- : Processing by StylesheetsController#show as CSS
I, [2018-01-12T11:23:45.106911 #75343]  INFO -- : Processing by StylesheetsController#show_source_map as */*
I, [2018-01-12T11:23:45.107335 #75343]  INFO -- : Processing by StylesheetsController#show as CSS
I, [2018-01-12T11:23:45.111310 #75343]  INFO -- :   Parameters: {"__ws"=>"localhost", "name"=>"admin_787065b7345c06bae0a6b9a059aa7e02eda55089"}
D, [2018-01-12T11:23:45.112606 #75343] DEBUG -- :    (1.9ms)  SELECT "groups"."id", "groups"."name" FROM "groups" ORDER BY "groups"."name" ASC
I, [2018-01-12T11:23:45.112676 #75343]  INFO -- :   Parameters: {"name"=>"admin_787065b7345c06bae0a6b9a059aa7e02eda55089"}
I, [2018-01-12T11:23:45.113830 #75343]  INFO -- :   Parameters: {"__ws"=>"localhost", "name"=>"desktop_theme_2_79351136cf8688063df0d9c90150114b2b9bfbcf"}
D, [2018-01-12T11:23:45.142633 #75343] DEBUG -- :   Theme Load (2.8ms)  SELECT  "themes".* FROM "themes" WHERE "themes"."color_scheme_id" IS NULL LIMIT 1
D, [2018-01-12T11:23:45.143359 #75343] DEBUG -- :   Theme Load (4.2ms)  SELECT  "themes".* FROM "themes" WHERE "themes"."color_scheme_id" IS NULL LIMIT 1
D, [2018-01-12T11:23:45.146208 #75343] DEBUG -- :   Category Load (3.7ms)  SELECT categories.*, t.slug topic_slug FROM "categories" LEFT JOIN topics t on t.id = categories.topic_id WHERE (NOT categories.read_restricted) ORDER BY "categories"."position" ASC
D, [2018-01-12T11:23:45.153093 #75343] DEBUG -- :   Theme Load (0.9ms)  SELECT  "themes".* FROM "themes" WHERE "themes"."id" = 2 LIMIT 1
D, [2018-01-12T11:23:45.201659 #75343] DEBUG -- :   Theme Load (2.0ms)  SELECT  "themes".* FROM "themes" WHERE "themes"."key" = '63ed90c3-fe83-4400-88c9-19a9ac24874c' LIMIT 1

Posts: 1

Participants: 1

Read full topic

@nixie wrote:

Sorry, I’m again with a really weird bug.

Issue

Joined date says “the user joined 1 day ago” - which is correct.
But, “days visited” says “the user has visited 3 days” - which is wrong
Reason - When the site itself is just 1-2 days old, and when the user itself is just 1-2 days old, how can “days visited” be more than 1-2 days?

Screenshot

image.png605x622 51 KB

Instance

Dev instance

Created on

I created this droplet at DigitalOcean 2 days ago.

How was the user created

It was the first user that got created by the wizard.
username of the user = admin

Posts: 1

Participants: 1

Read full topic

@erseco wrote:

Hi, I just deployed a multi-site discourse and now I want to programmatically migrate all my discourse sites (almost 20) to the new server.

Is possible to specify the site/database when calling ./launcher enter app or discourse restore filename.tar.gz?

Thank you in advance!

Posts: 1

Participants: 1

Read full topic

@dmitry_fedyuk wrote:

As I see, the current implementation does not use any software design patterns for extendability:

Posts: 1

Participants: 1

Read full topic

@gerald wrote:

Hi,

I Have a couple of issues with the Discourse-Wordpress integration (First, comments don’t appear on wordpress. Second, posts fail to auto-publish to Discourse).
I would like to hire a developer to help me with these issues (and more) but it is very hard to find a wordpress developer that also knows Ruby on rails (which as I understand is the what Discourse is using).
The question is, given that I can’t find a programmer for both Wordpress and Discourse - what is the most important skill? Wordpress or Ruby?

Posts: 2

Participants: 2

Read full topic

@Seth_Godin wrote:

[THANKS ALL, we’re set for now. Great to know how fabulous this community is.]

Hi Discoursians…

I’m looking for someone who can build a tool for us. The goal is to increase engagement among some members of the community on our private paid Discourse board.

Like most communities, it follows a power law curve, with a few totally immersed, some dipping in and out, and many lurking.

Here’s the simple spec of what we have in mind:

In the Discourse API you can find when a user was last seen last_seen_at and when they last posted last_posted_at.

CASE 1:

We can set a variable for length and a variable for text content on an ad-hoc basis via a simple dashboard or entry point. For example, if a person hasn’t posted in X days, the tool sends them a pm that says, “TEXT VARIABLE.”

We could do this for either the last_seen_at or last_posted_at variable, at our discretion.

We’d want to trigger this manually across our community, not have it be a consistent trigger. But it would be cool if we could also have it always working, and have multiple variables (5 days for the first notice, 20 days for the second, etc.)

And a final bonus feature would be a way to, instead of sending PMs, export the registered email address of each person. We’d then use that list in Ontraport or similar.

Thanks for considering…

Posts: 4

Participants: 3

Read full topic

@Juliendf wrote:

Hi guys,

I configured my Discourse set up to be able to use OAuth authentication from Google.
I want to keep it private so no sign up authorise. The user would only be allowed to sign up via invitation.
The goal would be to allow users to use google account or local account.

It works pretty well except that when I send an invite to a Google email, the user signs up and enter a password for the account. Then he is able to log in user Oauth or the password.

I would like to disable the use of a password for this type of account on only keeps it for local users.

Is that possible?

I hope it makes sense, thanks all!

Posts: 12

Participants: 3

Read full topic

@aarska wrote:

Dear all,
I have a problem… first of all, I am no expert, so please, bear with me.

I tried to upgrade discourse from the UI, then if I went to upgrade the plugins I got this:

<html><head></head><body>
<h2>You are running an old version of the Discourse image.</h2>
<p>
Upgrades via the web UI are disabled until you run the latest image.
</p>
<p>
To do so log in to your server using SSH and run:
</p>

<pre>
cd /var/discourse
git pull
./launcher rebuild app
</pre>
<p>
<a href='https://meta.discourse.org/t/how-do-i-update-my-docker-image-to-latest/23325'>More info on our support site</a>
</p>
</body>
</html>

The website was still working fine by then.

Then I went to a remote shell, and followed this guide: How do I manually update Discourse and Docker image to latest?

What happened was the following error.

Untitled.jpg1824x1024 355 KB

now the website isn’t working anymore. just not reachable.
Any idea about what I should do? I am at a bit of a loss, and seem to find no relevant guide or thread, in here. I just really need to get this to work without losing any data or options…

Posts: 3

Participants: 2

Read full topic

@lkramer wrote:

Hi all. We host with DiscourseHosting.com and I can see that they have our sites at 1.8.11 at the moment. A user of ours just asked where the “Back Button” has gone. To be honest, I never really noticed the back button before. I see in the Discourse 1.8.* release notes that there’s a few references to the back button coming and going. Has this button just been yanked altogether because it’s too buggy?

Posts: 5

Participants: 4

Read full topic

@matthieu_lamarque wrote:

Hello,
I have a question about private group :
It is possible to create a private group via a user other than admin ?

My user must be able to manage a private groupe (create/edit, add users, etc…).
I have to add some trust levels ?

Thanks for your help

Posts: 2

Participants: 2

Read full topic

@kevinrobinson wrote:

This is split out from the master accessibility thread: Accessibility audit and shepherd for making improvements

The issue here is that in certain tutorial popups, users aren’t able to get out of it with using a keyboard alone. Note that the initial report is from March 2017.

Report:

In the Banner, and in the Reply field (the pop-up that comes up to remind you of discussion etiquette), you cannot dismiss the banner nor make the warning go away without the use of a mouse. This must change as it is what we call a keyboard trap. There should be a way to give the dismiss X keyboard focus and actionability. This can be worked around by setting an option to disable this feature on an instance, but ideally the default setup upstream would included keyboard accessibility as well.

This may have changed since the original audit was done. It’s visually different than what I remember myself too, FWIW. Here’s an example of what I see opening this topic now:

Screen Shot 2018-01-12 at 10.58.58 AM.png1361x396 57.2 KB

For me on Chrome Desktop this works as expected, and there’s no issue on that popup.

Looking back in code to confirm that this was fixed, I found what I think is the code adding the “ESC” but blaming makes it look like this hasn’t been changed in the last six months: discourse/app/assets/javascripts/discourse/controllers/composer.js.es6 at a0b2b3c8a76adf1ef52f0c31424017b44d232221 · discourse/discourse · GitHub

I’ve pinged folks on my end to help confirm that this is fully accessible, and so unless I hear back differently from there or other folks can chime in here I think we can consider this one resolved.

Posts: 2

Participants: 1

Read full topic

@plosprawrs wrote:

For example in the body I am given markdown/HTML/etc capability. Does anyone know a way to bring attention to the topic title? ( IE color, bold, styling etc. )

Kind Regards

Posts: 3

Participants: 2

Read full topic

@kevinrobinson wrote:

This is split out from the master accessibility thread: Accessibility audit and shepherd for making improvements

Mary and Rich think this is more important. If there are inner and outer tables, they’d all need semantic labels and all need to be linked.

This appears to have changed since Rich’s audit on 3/30/17. If I remember right, the issue was that the “latest posts” column, a table was used for the layout of each post. On 1/10/18, running Array.prototype.slice.call(document.querySelectorAll(“table”))[0] on Categories - Discourse Meta looks good.

I tried looking back at git history for code related to the topics list to see where this might have changed in the last six months but couldn’t find it. If @sam or other folks can help confirm that there were nested tables previously or find this in GitHub that would be awesome and make sense of this too.

I’ve pinged back Rich to verify that the accessibility here is good now. If @tapper82 or other folks looking at screen reader tests can confirm this looks good we could close it too.

Posts: 5

Participants: 2

Read full topic

@kevinrobinson wrote:

This is split out from the master accessibility thread: Accessibility audit and shepherd for making improvements. Previously directly related issues: Accessibility: Improve contrast of text styling in default UI and Contrast and accessibility and Improving color and contrast on topic progress widget.

The overall accessibility question here is: do foreground and background text have sufficient contrast? This is of course dependent on theming, but the idea for this issue is that out-of-the-box defaults should be accessible.

The Tanaguru Contrast Finder Tool can help with conversations about contrast and accessibility.

The specific examples that came out of an accessibility audit we did were:

1. The text that appears for post excerpts
2. The reply field area text

Both have a color combination of #919191/#ffffff, which has a contrast ratio of 3.15, which is not sufficient. At this size, you will need a ratio of at least 4.5. Consider using the following foreground/background combination: #767676/#ffffff / has a ratio of 4.54

In our instance, we just updated the styling for this directly, but it’d be good to update the default so it meets this accessibility threshold as well.

1. The text that appears for post excerpts
Here’s what this change would look like for post excerpts on meta.discourse.org on Desktop (#919191 -> #767676):

before:

Screen Shot 2018-01-12 at 11.42.29 AM.png1155x845 141 KB

after:

Screen Shot 2018-01-12 at 11.42.45 AM.png1196x848 142 KB

2. The reply field area text
(edit: oops, this got cut out of my initial post)
Here’s what this part of the UI looks like, with the image from the original report in March 2017:

image.png1513x285 16.8 KB

Looking at this part of the UI now, it appears that this is implemented with a placeholder attribute on <textarea /> and that the current color on Mac Chrome Desktop is #626262 (with great contrast ratio of 6.0)!

Screen Shot 2018-01-12 at 11.47.13 AM.png1151x294 13.8 KB

At the same time I’m looking at this, I notice that several other bits of text have the same #919191 color though, including “kevinrobinson” at the top, “saved” and “hide preview” on the bottom strip, and the “uploading” message when uploading an image (not shown here):

Screen Shot 2018-01-12 at 11.49.39 AM.png1154x400 75.2 KB

These appear to be defined with the $primary-medium variable in SASS. There were some recent changes here in initial pass at color simplification by awesomerobot · Pull Request #4975 · discourse/discourse · GitHub in July 2017 that might be relevant, and we could revisit those colors to audit them across the UI in the default themes exhaustively. The short-term change here could be just to tweak that variable to #626262.

Posts: 9

Participants: 4

Read full topic

@supermathie wrote:

Before:

image.png1135x152 8.95 KB

Reproduction:

$ api_key=340496f95ab2f28cc45f575cbfcc28edd10db076beb1139da14b3fa80bb23dd2
$ curl -XPOST -H 'Content-Type: application/json' "http://discoursedev:3000/admin/backups.json?api_key=$api_key&api_username=michael" -d '{ "with_uploads": true }'
{"success":"OK"}
$ curl "http://discoursedev:3000/admin/backups.json?api_key=$api_key&api_username=michael"
(HTML error page as I'm in development mode)
$ curl "http://discoursedev:3000/admin/backups.json?api_key=$api_key&api_username=system"
[{"filename":"discourse-2018-01-12-112341-v20180111092141.sql.gz","size":3216556,"link":"//discourse/admin/backups/discourse-2018-01-12-112341-v20180111092141.sql.gz"}]

After:

image.png986x144 8.83 KB

Posts: 1

Participants: 1

Read full topic

@Vocino wrote:

I’d like to replace it with something else (an external api’s online status) but I can’t seem to figure out how to reference it.

I found some other how-to articles that referenced this:

<script type='text/x-handlebars' data-template-name='/connectors/poster-avatar-bottom/external-site-link'>
  {{#if externalSiteLink}}
    <span class="external-site-link">{{{externalSiteLink.link}}}</span>
  {{/if}}
</script>

Which seems like the type of thing I’m looking for. I just need the correct placement.

Posts: 3

Participants: 2

Read full topic

@jomaxro wrote:

Noticed this today in my notifications, it’s bugging me. Certain notifications wrap the topic title differently than others. In the image below, the accepted answer notification and the “invited to a private message” notification indent extra lines of text while the others do not.

image.png317x539 19.1 KB

Posts: 2

Participants: 2

Read full topic

@lkramer wrote:

Hello. So in searching some other threads here, it seems like the expected behavior is this:

1. Someone is reading a thread in Discourse and decided to login so they click the Login button
2. They pop over to WordPress where they login
3. They are redirected back to the Discourse thread that they were reading

That sounds great! In our case, this isn’t working I think because we use the MemberMouse plugin which forces people to a certain “welcome” URL after logging in. BUT, I can bypass that with a filter MemberMouse provides.

The only problem, is that the URL of the Discourse topic the person was reading doesn’t seem to be passed to WordPress.

E.g. Let’s say I’m in this topic in Discourse:
https://forums.gemsociety.org/t/any-brazil-company-which-sold-rough-faceting-amethyst-citerine-and-amertine/1246

And I click the Login button in Discourse

I get sent to this URL:
https://www.gemsociety.org/login/?redirect_to=%2Flogin%3Fsso%3Dbm9uY2U9Y2IwZGE0NmRlMGM0YTlhOGM1OTc4OGU0NGRjOGU3MDkmcmV0dXJu%250BX3Nzb191cmw9aHR0cCUzQSUyRiUyRmZvcnVtcy5nZW1zb2NpZXR5Lm9yZyUy%250BRnNlc3Npb24lMkZzc29fbG9naW4%253D%250B%26sig%3D419ba4dfda93d068c81470cf32e4aec633217047728a9bca514bbae3891cffde

Nowhere in that big string do I find the URL the person was reading in Discourse (/any-brazil-company…/).

So, I’m a little confused here. Any thoughts? Thanks!

Posts: 4

Participants: 2

Read full topic

@pfaffman wrote:

tl;dr: it looks like there are about 10GB of data reported by rake db:stats, but postgres_data is taking up 18GB. Does it seem likely that there are 8GB of indexes taking up the rest of the space, or is there some kind of cleanup that needs to be done?

Longer version of the same question

The postgres data directory is 18GB. A dump of the database is about 5GB.

var/discourse# du -hs shared/data/postgres_data/
18G     shared/data/postgres_data/

Here’s what rake db:stats reveals. I truncated the rows reported in kB (about 10GB).

table_name	row_estimate	size
post_timings	49643076	3011 MB
posts	2289502	990 MB
user_actions	5506773	915 MB
post_search_data	2136003	875 MB
email_logs	2934363	717 MB
topic_views	3498593	507 MB
topic_users	3714046	448 MB
post_stats	1894296	319 MB
notifications	1178136	296 MB
post_replies	1077331	127 MB
topics	146814	107 MB
post_actions	456903	63 MB
draft_sequences	671770	54 MB
post_revisions	74596	51 MB
user_profile_views	465818	49 MB
topic_search_data	124471	46 MB
topic_links	160437	33 MB
scheduler_stats	168878	29 MB
uploads	82100	22 MB
post_custom_fields	35255	22 MB
top_topics	106478	21 MB
unsubscribe_keys	109936	19 MB
optimized_images	67107	18 MB
user_histories	77643	13 MB
topic_link_clicks	124501	12 MB

Posts: 3

Participants: 2

Read full topic

@Ralphy wrote:

Hello,

I have my own self hosted install of discourse. I had been customising the site and accidentally changed these titles to green:

59C974E1-A152-4271-AECA-54847F6D6C70.jpeg640x572 64.6 KB

Is there any way to revert back to the original standard black colour? As I can’t find it in the customisation menu.

Thanks guys

Posts: 2

Participants: 2

Read full topic