@kudos wrote:
I just want to know out of curiosity that what is this in discourse, which is an amazing piece of undisputed software, https://www.screencast.com/t/VGKe0fFgBP1H
Scroll-bar or parallax or something else?
Posts: 3
Participants: 2
@kudos wrote:
I just want to know out of curiosity that what is this in discourse, which is an amazing piece of undisputed software, https://www.screencast.com/t/VGKe0fFgBP1H
Scroll-bar or parallax or something else?
Posts: 3
Participants: 2
@scottfsmith wrote:
I have been running my site fine with apache2 as the main server on my ubuntu linode. I set up a reverse proxy for Discourse. It stopped working today, it is dropping connections and needs many reloads to work. If I connect directly to the port (8000) it works fine so it must be something in the proxy.
This problem started when earlier today I decided to migrate my old images over from S3, I ran the migrate_to_s3 script and then did a rebake on all the posts. I had to reconfigure my Linode for more swap (2GB) because the rebake failed before I did that. Anyway, it was a pain (and not all images ended up migrating, I don't know why) but the site finally was all back to normal EXCEPT for the dropping of connections -- its almost unusable now.
I thought maybe the apache reverse proxy was the problem so I tried an nginx reverse proxy .. same thing. Then I tried the nginx direct socket connection and it still was dropping connections. I am pretty clueless as to what the cause could be, and unfortunately I did several actions and any one could have caused problems. Any ideas? I checked the apache and discourse error logs and there was nothing of interest.
Posts: 1
Participants: 1
@Arta_S wrote:
Hey guys,
I want a rough idea about digitalocean's droplets in term of monthly pageviews that they can handle.
I am currently looking at these 4 packages:
Can you please specify "How much monthly page views each of these 4 packages can handle" ?
Posts: 3
Participants: 2
@peternlewis wrote:
Yes, sigh, I know, again.
1.7 breaks the workaround we had for Mac Mail threading, namely always including "Re:" at the start of the subject
Setting for email subject
Re: [%{site_name}] %{optional_pm}%{topic_title}
Unfortunately, Discourse 1.7 sensibly does not include an "In-Reply-To" on the first post, and this results in the first post being threaded separately from the replies in Mac Mail.
I have a hack to put the "In-Reply-To" back:
@message.header['Message-ID'] = incoming_message_id || post_message_id - if post && post.post_number > 1 + if post @message.header['In-Reply-To'] = referenced_post_message_ids.first || topic_message_id + end + if post && post.post_number > 1 @message.header['References'] = [topic_message_id, referenced_post_message_ids].flatten.compact.uniq end
but this is obviously less than ideal. That said, I've got no ideas for any better solution, and the alternative (the initial post being threaded separately from replies) is very bad for those of us using Mailing List Mode since it appears as an unanswered question even though there are answers.
I'm hopeful someone else will have some better idea to restore Mac Mail threading, or a better workaround, or something…? Failing that, at least this documents the issue for anyone else with lots of Mac forum users.
Posts: 1
Participants: 1
@techAPJ wrote:
Want to migrate from GetSatisfaction to Discourse? Great! Let's get started.
What data can be imported?
- Users
- Topics & Replies
- Topic Permalinks
Prerequisites
Set up Discourse development environment on OS X, Ubuntu or Windows.
Install dependencies:
cd ~/discourse echo "gem 'reverse_markdown'" >> Gemfile bundle install
Clear existing data from your local Discourse instance:
cd ~/discourse rake db:drop db:create db:migrate
You will get a bunch of CSV files as export data, rename them all so
users.csv
is the users table export (it may come from getsatisfaction as Users-Table 1.csv)topics.csv
is the topics table exportreplies.csv
is the reply table exportPerform Import
Start import process:
cd ~/discourse bundle exec ruby script/import_scripts/getsatisfaction.rb /home/user/files/path
Replace
/home/user/files/path
with the path of CSV export files.Wait until the import is done. You can restart the process if it slows down to a crawl.
Start your Discourse instance:
bundle exec rails server
Take backup of the data and upload it on your production site by following this howto.
Congratulations! You have successfully migrated your site from GetSatisfaction to Discourse!
Posts: 1
Participants: 1
@rsoutar wrote:
Hi, I was running an update using
./launcher rebuild app
But it stuck at156:M 23 Jan 10:19:31.078 * 10 changes in 300 seconds. Saving... 156:M 23 Jan 10:19:31.081 * Background saving started by pid 3150 3150:C 23 Jan 10:19:31.655 * DB saved on disk 3150:C 23 Jan 10:19:31.657 * RDB: 26 MB of memory used by copy-on-write 156:M 23 Jan 10:19:31.714 * Background saving terminated with success 2017-01-23 11:23:52 UTC [3137-57] discourse@discourse WARNING: skipping "sql_languages" --- only table or database owner can vacuum it 2017-01-23 11:23:52 UTC [3137-58] discourse@discourse WARNING: skipping "sql_packages" --- only table or database owner can vacuum it 2017-01-23 11:23:52 UTC [3137-59] discourse@discourse WARNING: skipping "sql_parts" --- only table or database owner can vacuum it 2017-01-23 11:23:52 UTC [3137-60] discourse@discourse WARNING: skipping "sql_sizing" --- only table or database owner can vacuum it 2017-01-23 11:23:52 UTC [3137-61] discourse@discourse WARNING: skipping "sql_sizing_profiles" --- only table or database owner can vacuum it WARNING: skipping "sql_languages" --- only table or database owner can vacuum it WARNING: skipping "sql_packages" --- only table or database owner can vacuum it WARNING: skipping "sql_parts" --- only table or database owner can vacuum it WARNING: skipping "sql_sizing" --- only table or database owner can vacuum it WARNING: skipping "sql_sizing_profiles" --- only table or database owner can vacuum it
Using htop I saw that it running a VACUUM for an hour or so.
Any ideas? Thank you
Posts: 4
Participants: 3
@erlend_sh wrote:
Common operations and instructional material for Discourse administrators.
Posts: 1
Participants: 1
@erlend_sh wrote:
For documentation regarding tasks that require some sysadmin know-how, or instructional material for budding Discourse sysadmins.
Posts: 1
Participants: 1
@erlend_sh wrote:
For documentation regarding tasks that require some developer know-how, or instructional material for budding Discourse developers.
Posts: 1
Participants: 1
@erlend_sh wrote:
Continuing the discussion from Use category slug in menus instead of category name:
The slug for the System Administrators category is
sysadmins
. Here's what happens if I wanna move a topic there.So far so good:
Bummer:
Which is not consistent with our hashtag autocompletion, which does in fact appear to take the slug into account:
Posts: 1
Participants: 1
@mattdamod wrote:
I'm such a noob... I can't find where to edit the welcome banner. Once a user has clicked the small x it disappears and never comes back... where are those settings also?
Thanks
Posts: 3
Participants: 3
@erlend_sh wrote:
You might have noticed some changes in our #howto category.
Basically, here's what we've done:
(1) Added the following sub-categories:
- Sysadmins
- Developers
- Administrators
- faq (moved from top-level category)
I'll probably rename FAQ to "Users". Just gotta take a closer look at all the docs we've got there.
(2) Enabled
show subcategory list
Any other sub-categories you're missing here?
Posts: 4
Participants: 3
@hallaathrad wrote:
So as I was going to post a link to an article from google's blog like so:
our instance of Discourse is giving me the following message:
Any ideas what went wrong, and how to fix it?
Posts: 14
Participants: 7
@Fer_Nando wrote:
It´s posible, for future updates, change all letter avatars to an html element with css for improve load performance with minor request? Sorry for my english, i´m not native speaker.
This is a nice example:
https://codediode.io/lessons/198632-default-avatars-with-username-initials
Posts: 6
Participants: 5
@grxninesix wrote:
I am unable to enter a name on this box.
iPhone 6s+
iOS 10.2
Posts: 2
Participants: 2
@jomaxro wrote:
Continuing the discussion from Can't mark a post as wiki anymore:
In the past, there were two icons for wiki posts - a wiki edit icon (pencil and paper) and an edit log icon (pencil). Clicking the wiki edit icon opened the editor, clicking the edit log icon opened the edit log. Now, the edit log icon seems to have been removed entirely from wiki posts, and it clicking the wiki edit icon brings up the log, not the editor. Was this change intentional? I've already gotten 2 complaints from my site about this change.
Posts: 5
Participants: 2
@jomaxro wrote:
Continuing the discussion from Design choice behind /t, /c, and /users:
@Sam requested a specific topic...here it is.
There have been requests for
/u/
to work in a URL similar to how/c/
and/t/
work.
Posts: 2
Participants: 2
@dfpoon wrote:
Continuing the discussion from Linked replies showing up again so you have to read them twice - can this be addressed?:
Sorry for this noob question. I have searched this meta forum for quite a while but still couldn't figure out how could I trigger the "linked reply" view? Could anyone please tell me. Thanks.
Posts: 2
Participants: 2
@jgujgu wrote:
I've had a hard time using the admin utility tool to unpin and/or archive topics. I tried to do so on both dev
v1.8.0.beta1 +3
|Firefox 50.1.0
and productionv1.8.0.beta2 +63
|Firefox 50.1.0
&Chrome 55.0.2883.95
, resulting in slightly different errors. I have tried this both on newly created topics and topics generated at the creation of a category.I ran rspec with one inconsequential failure:
rspec ./spec/models/user_visit_spec.rb:36 # UserVisit#by_day collect closed interval visits
Acceptance tests would've been more telling, but, weirdly, when I went to /qunit, nothing loaded:
dev:
Unprocessable Entity unwrapErrorThrown@ember:30421:15 errorFor@ember:30403:14 onerrorDefault@ember:30393:17 EventTarget.trigger@ember:57841:9 Promise.prototype._onError/<@ember:58725:9 Queue.prototype.invoke@ember:339:7 Queue.prototype.flush@ember:407:9 DeferredActionQueues.prototype.flush@ember:531:9 Backburner.prototype.end@ember:601:7 Backburner.prototype.run@ember:724:11 run@ember:21520:12 performAjax/args.error@discourse/lib/ajax:87:11 jQuery.Callbacks/fire@jquery:3183:11 jQuery.Callbacks/self.fireWith@jquery:3313:7 done@jquery:8757:5 .send/callback/<@jquery:9121:9 ember Uncaught promise: Object { jqXHR: Object, textStatus: "error", errorThrown: "Unprocessable Entity" }
production w/Firefox:
No Reason Phrase o@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:10:25500 i@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:10:25357 r@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:10:25286 ye.trigger@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:19:30372 j.prototype._onError/<@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:20:324 a.prototype.invoke@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:3:26544 a.prototype.flush@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:3:27069 u.prototype.flush@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:3:27837 p.prototype.end@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:3:28182 p.prototype.run@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:3:29309 l@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:9:423 e/n.error@https://graphme.io/assets/application-21942e0b16b99fd916a9193250f85511ffed539932522c8923d0b334e3d20270.js:1:28767 oe.Callbacks/l@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:2:6505 oe.Callbacks/c.fireWith@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:2:7278 r@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:3:10235 .send/n/<@https://graphme.io/assets/ember_jquery-60dedd1dca1d8b8ce48b6d0087db3b96f3149b9b5af2d0c7c6357967d29031fb.js:3:16063
production w/Chrome:
Does anyone else have this problem? Perhaps I should come back after I get qunit in order.
Posts: 1
Participants: 1