@tobiaseigen wrote:

I just came across an awesome African emoji set and would like to adopt it wholly to replace equivalent emoji from the apple emoji set I am using now (the discourse default). I am not entirely clear on how best to do this. Ideally I'd match the filenames with the 4 standard versions and upload that in a folder, equivalent to the 4 standard ones provided that all apparently also have matching filenames so you can switch between them and still have emoji work. The filenames for the African emoji set are completely different now though there will be matches for the standard versions, and this would be a fun contribution to make.

Suggestions?

Posts: 2

Participants: 2

Read full topic

@meglio wrote:

I'd like to experiment by making it clear to readers that this topic and that topic and that other topic wouldn't take long to read, so go ahead and read it now!

I know that at medium.com it encouraged me to read more, so I believe it could encourage some else.

In order to do so, I'd like to display the approximate reading time in the topics list.
Is this possible to achieve somehow?

Posts: 3

Participants: 3

Read full topic

@codinghorror wrote:

We are now bundling the discourse-details plugin with all Discourse installs, thanks to @zogstrip.

This means you can have hidden and expandable text in your posts for whatever use you want.

We leveraged the HTML 5.1 features <element> and <detail> which are natively supported in Chrome and Safari, and probably soon in other browsers -- we wrote shims so it works in all browsers.

https://developer.mozilla.org/en-US/docs/Web/HTML/Element/details

[ details=the summary]blablabal[/details]

will generate

<details>
<summary>the summary</summary>
blablabal
</details>

Live demo:

click or tap here to expand and collapse

Church-key yr irony Carles. Letterpress master cleanse trust fund asymmetrical, farm-to-table Wes Anderson chambray pickled brunch messenger bag synth kale chips cornhole bespoke actually. Meggings quinoa kitsch locavore sustainable, yr selvage cray shabby chic Brooklyn Neutra letterpress semiotics lumbersexual. IPhone mumblecore Thundercats selfies Marfa Williamsburg, ugh farm-to-table. Chambray vinyl chillwave, twee you probably haven't heard of them keytar forage cornhole post-ironic iPhone. Four loko single-origin coffee literally, fixie food truck 3 wolf moon listicle crucifix semiotics cardigan distillery polaroid. Artisan American Apparel VHS, biodiesel blog brunch Blue Bottle skateboard ugh.

yyZwINK.jpg540x960 55.5 KB

Raw denim 8-bit cold-pressed cred. Pop-up cred hoodie swag blog Truffaut flexitarian Bushwick put a bird on it.

• Tilde cray freegan semiotics, salvia PBR wayfarers Carles Kickstarter.
• Intelligentsia 90's cray hella, whatever lumbersexual Echo Park Pinterest McSweeney's kogi Vice listicle.
• Retro lomo pug, YOLO irony McSweeney's farm-to-table bitters single-origin coffee next level taxidermy keytar Wes Anderson.

Put a bird on it

Brooklyn cred, 8-bit semiotics roof party trust fund beard. Pork belly 90's tofu pug slow-carb.

Posts: 6

Participants: 4

Read full topic

@ggarron wrote:

Hi

I have a discourse instance up and running. I also have it embbeded in my jekyll blog for comments

I think i can use the same forum to power comments in my wordpress blog. I have created the api installed the plugin and configured in different ways none is fully working.

The post are being created, but comment not showing.

I have put 0 to all values but max comments to show where there is 10.
I have 2015 theme and tried with native comments enabled and disabled.

Is anything I am missing?

Thanks for your time and help.

Posts: 1

Participants: 1

Read full topic

@haydenjames wrote:

Facebook auth works but the popup also contains a red box which warns "You are using a display type of 'page' in a small browser window..."

How can this be fixed? Is this the solution: http://help.webtechapps.com/2013/09/20/facebook-display-type-popup/

Posts: 5

Participants: 3

Read full topic

@badevguru wrote:

The new tag plugin is great. Now that I am using it, I would like to combine it with search and bulk actions to manage the tags across many topics.

Use case: Up to now, many of the topics had key phrases in them to indicate that they were special. I'd like to go ahead and add a tag to all of the topics that have that key phrase. Ideally I would

1. use the search url to find the topics
2. use the topic selector to select all of the topics for a bulk action
3. use the bulk action - Add Tag to add a new tag to all selected topics

Posts: 9

Participants: 5

Read full topic

@stellarhopper wrote:

Hi,

I had an old 9.9.x install (docker based), and I tried to upgrade it to the latest today, and have been running into a series of problems.

1. First, I tried upgrading using the upgrade admin panel, and that didn't go too well - it seemed to freeze up, and I had to reboot.

2. Then I tried ./launcher rebuild app - and that failed quite early in the process - around "Pulling fs/metadata/dependent layers"

3. Next, since I had a backup from the admin cp, I decided to fully reinstall. So I deleted (renamed) /var/docker (the old install) away, and started afresh in /var/discourse. The install/bootstrap went fine this time. When trying to start it though, I got an error:

Found an existing container by its name, recovering cidfile, please rerun

On re-running:

cid found, ensuring container is started
Error response from daemon: Cannot start container 971e92863c77: Volume exists: 0d89465b1f9e0b67dbd782ace8714e463acafc5e2c3e0b872bbd0ef3d3e30e0c

I then tried ./launcher restart app and that seemed to work - except, the site kept giving me a 502 - bad gateway

./launcher logs app is filled with messages like:

ok: run: redis: (pid 33) 0s
ok: run: postgres: (pid 31) 0s
[33] 26 Feb 07:06:57.492 # Can't chdir to '/shared/redis_data': No such file or directory
[38] 26 Feb 07:06:57.983 # Can't chdir to '/shared/redis_data': No such file or directory
[40] 26 Feb 07:07:01.369 # Can't chdir to '/shared/redis_data': No such file or directory
Server listening on 0.0.0.0 port 22.
Server listening on :: port 22.
[41] 26 Feb 07:07:04.827 # Can't chdir to '/shared/redis_data': No such file or directory
[42] 26 Feb 07:07:09.017 # Can't chdir to '/shared/redis_data': No such file or directory
[43] 26 Feb 07:07:10.698 # Can't chdir to '/shared/redis_data': No such file or directory
[44] 26 Feb 07:07:11.534 # Can't chdir to '/shared/redis_data': No such file or directory
2015-02-26 07:07:13 UTC FATAL:  data directory "/shared/postgres_data" does not exist
[46] 26 Feb 07:07:13.705 # Can't chdir to '/shared/redis_data': No such file or directory
[51] 26 Feb 07:07:15.284 # Can't chdir to '/shared/redis_data': No such file or directory
2015-02-26 07:07:15 UTC FATAL:  data directory "/shared/postgres_data" does not exist

SSH'ing into the app, and looking at /shared/log/production.log :

Error connecting to Redis on localhost:6379 (Errno::ECONNREFUSED) subscribe failed, reconnecting in 1 second. Call stack ["/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:331:in `rescue in establish_connection'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:317:in `establish_connection'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:94:in `block in connect'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:279:in `with_reconnect'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:93:in `connect'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:262:in `with_socket_timeout'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:273:in `without_socket_timeout'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:125:in `call_loop'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/subscribe.rb:35:in `subscription'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/subscribe.rb:12:in `subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis.rb:2622:in `_subscription'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis.rb:2035:in `block in subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/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.1/lib/redis.rb:37:in `synchronize'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis.rb:2034:in `subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.6/lib/message_bus/reliable_pub_sub.rb:247:in `global_subscribe'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.6/lib/message_bus.rb:375:in `global_subscribe_thread'", "/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-1.0.6/lib/message_bus.rb:370:in `block in new_subscriber_thread'"]
...

And /shared/log/rails/unicorn.stderr.log :

I, [2015-02-26T07:08:20.009631 #59]  INFO -- : pid=/var/www/discourse/tmp/pids/unicorn.pid possibly stale, got EPERM signalling PID:50
I, [2015-02-26T07:08:20.036221 #59]  INFO -- : Refreshing Gem list
URGENT: could not connect to server: No such file or directory
	Is the server running locally and accepting
	connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.5432"?
 Failed to initialize site default
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:331:in `rescue in establish_connection': Error connecting to Redis on localhost:6379 (Errno::ECONNREFUSED) (Redis::CannotConnectError)
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:317:in `establish_connection'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:94:in `block in connect'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:279:in `with_reconnect'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:93:in `connect'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:350:in `ensure_connected'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:207:in `block in process'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:292:in `logging'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:206:in `process'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis/client.rb:112:in `call'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis.rb:789:in `block in get'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis.rb:37:in `block in synchronize'
	from /usr/local/lib/ruby/2.0.0/monitor.rb:211:in `mon_synchronize'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis.rb:37:in `synchronize'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/redis-3.2.1/lib/redis.rb:788:in `get'
	from /var/www/discourse/lib/discourse_redis.rb:57:in `block (2 levels) in <class:DiscourseRedis>'
	from /var/www/discourse/config/initializers/secret_token.rb:6:in `<top (required)>'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/dependencies.rb:241:in `load'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/dependencies.rb:241:in `block in load'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/dependencies.rb:232:in `load_dependency'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/dependencies.rb:241:in `load'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/engine.rb:648:in `block in load_config_initializer'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.1.8/lib/active_support/notifications.rb:161:in `instrument'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/engine.rb:647:in `load_config_initializer'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/engine.rb:612:in `block (2 levels) in <class:Engine>'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/engine.rb:611:in `each'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/engine.rb:611:in `block in <class:Engine>'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/initializable.rb:30:in `instance_exec'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/initializable.rb:30:in `run'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/initializable.rb:55:in `block in run_initializers'
	from /usr/local/lib/ruby/2.0.0/tsort.rb:150:in `block in tsort_each'
	from /usr/local/lib/ruby/2.0.0/tsort.rb:183:in `block (2 levels) in each_strongly_connected_component'
	from /usr/local/lib/ruby/2.0.0/tsort.rb:210:in `block (2 levels) in each_strongly_connected_component_from'
	from /usr/local/lib/ruby/2.0.0/tsort.rb:219:in `each_strongly_connected_component_from'
	from /usr/local/lib/ruby/2.0.0/tsort.rb:209:in `block in each_strongly_connected_component_from'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/initializable.rb:44:in `each'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/initializable.rb:44:in `tsort_each_child'
	from /usr/local/lib/ruby/2.0.0/tsort.rb:203:in `each_strongly_connected_component_from'
	from /usr/local/lib/ruby/2.0.0/tsort.rb:182:in `block in each_strongly_connected_component'
	from /usr/local/lib/ruby/2.0.0/tsort.rb:180:in `each'
	from /usr/local/lib/ruby/2.0.0/tsort.rb:180:in `each_strongly_connected_component'
	from /usr/local/lib/ruby/2.0.0/tsort.rb:148:in `tsort_each'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/initializable.rb:54:in `run_initializers'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/application.rb:300:in `initialize!'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/railtie.rb:194:in `public_send'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.1.8/lib/rails/railtie.rb:194:in `method_missing'
	from /var/www/discourse/config/environment.rb:5:in `<top (required)>'
	from config.ru:3:in `require'
	from config.ru:3:in `block in <main>'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `instance_eval'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.5.2/lib/rack/builder.rb:55:in `initialize'
	from config.ru:1:in `new'
	from config.ru:1:in `<main>'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn.rb:48:in `eval'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn.rb:48:in `block in builder'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:764:in `call'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:764:in `build_app!'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/lib/unicorn/http_server.rb:137:in `start'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-4.8.3/bin/unicorn:126:in `<top (required)>'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `load'
	from /var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:23:in `<main>'
 ...

Any pointers what might be wrong?

Thank you!

Edit: This is on Ubuntu 12.04. I had to get a newer docker than what the distro had - I now have:

$ docker -v
Docker version 1.5.0, build a8a31ef

Posts: 5

Participants: 2

Read full topic

@meglio wrote:

Not sure if this is really relevant, but still let me put this image here:

81.png1747x536 50.3 KB

Posts: 3

Participants: 3

Read full topic

@terrytong wrote:

How to configure Discourse to connect to postgresql by unix-domain socket?

Is there an official guide for Discourse configuration?

Posts: 1

Participants: 1

Read full topic

@terrytong wrote:

My website is hosted by nginx. How to configure Discourse so that nginx can redirect http request to mywebsite.com/bbs/ to Discourse?

Posts: 3

Participants: 3

Read full topic

@terrytong wrote:

In admin/upgrade, the "Upgrade to the Latest Version" button is grey and can't be pressed, any idea?

Should I upgrade discourse to the latest commit or the latest released version, e.g. 1.2? How to upgrade to a certain version?

How often should I upgrade docker_manager? Should I always keep it upgraded to the latest commit?

Posts: 6

Participants: 2

Read full topic

@boomzilla wrote:

One category of request we get is to move posts from one topic to another. This typically happens with a "Something Else" flag to the moderators.

However, we have several TL4s who can do this, but there's no easy way for users to include them in the request to move, meaning that it might take a lot longer before a moderator or admin to see the request and do the move. This seems like the sort of thing that would require its own option (and we definitely get them enough). Or possibly this could be an enhancement to the "Off Topic" flag.

Posts: 5

Participants: 3

Read full topic

@rodrigofarcas wrote:

Is there a fix for arrows being bigger in height than category names?

http://screencast.com/t/ZcySDu3NIa

Posts: 3

Participants: 3

Read full topic

@downey wrote:

Should I be worried? A few giant "Internal Server Error" messages in the black status screen as shown here. Everything seems to be OK from the outside user perspective, but....

$ bundle install --deployment --without test --without development
Fetching gem metadata from https://rubygems.org/..Retrying dependency api due to error (2/3): Bundler::HTTPError Net::HTTPInternalServerError:
Internal Server Error

.....
Fetching version metadata from https://rubygems.org/.Retrying dependency api due to error (2/3): Bundler::HTTPError Net::HTTPInternalServerError:
Internal Server Error

..
Fetching dependency metadata from https://rubygems.org/..
Using rake 10.4.2
(etc.)

Posts: 2

Participants: 2

Read full topic

@trandatnh wrote:

This is what I want

Posts: 3

Participants: 2

Read full topic

@FHTzoob wrote:

Usually upon searching a word in the search tab, if the word is in the page you're on it will be highlighted yellow, like this:

Pasted image817x155 24.5 KB

However today I was doing a lot of formatting and noticed that if the text is written inside

<details><summary><kbd><b>

Then it disappears when searched.

For example:

Pasted image1126x513 83.9 KB

Then when you search "staff":

Pasted image1119x473 122 KB

Posts: 8

Participants: 3

Read full topic

@Zarmakuizz wrote:

Hi everyone

I am currently a student in an internship, inside a startup, and I am on a task of implementing a badge system on our app. This is my first take on badges, so I am looking for inspirating examples.

I already looked at Discourse as an example for the design part (I used Discourse on another community), so I though about looking at Discourse again for the coding part. How it was implemented. That's when I read somewhere on the Design thread that the badge system would have needed 6-8 weeks to implement? While it seemed to my colleagues and me that it could be done in a shorter time. So I think we might be missing something.

I don't know how long it was in the end, however I am curious about the architecture behind. To make reading the code easier, I am looking for draft documents, blog posts, or anything about the development specification of the badges on Discourse, in case this resource exists?

Thank you for your attention ^^

Posts: 2

Participants: 2

Read full topic

@Pirat wrote:

what to do

NoMethodError (undefined method `admin?' for nil:NilClass)

Uncaught TypeError: Cannot read property 'mapRoutes' of undefined Url:
Uncaught SyntaxError: Unexpected token r Url:
Can't verify CSRF token authenticity
TypeError: e.popup is not a function Url
Uncaught TypeError: undefined is not a function Url:
TypeError: Discourse.Route is undefined Url:

Posts: 2

Participants: 2

Read full topic

@boushleyExtra wrote:

I've been using the discourse_docker setup for a while now and I'm wondering if a pull request that moves the rails logs would be acceptable.

It's a bit odd to me that the majority of logs end up in /var/log inside the container which in the samples is mounted out to a specific log location. However the rails and unicorn logs are symlinked to /shared/log/rails. This means that logs for the discourse instance end up in multiple locations on the host. It seems like it would be a fairly trivial change inside of the web.template.yml template to symlink /var/www/discourse/log to /var/log/rails instead of /shared/log/rails.

Is this separation of logs purposeful? Or would a pull request centralizing the logs be welcomed?

Posts: 4

Participants: 3

Read full topic

@rossbollinger wrote:

I'm a freelance animator and have never been an active forum user, but Discourse is changing that for me, and I am eagerly monitoring its development.

For an average internet user like myself coming primarily from a social media environment, visible Markdown or BBCode within the reply box feels disorienting. For most forum users, I imagine that this goes virtually unnoticed, but for the average person it could be overwhelming at first and potentially dissuading to new users.

I started wondering if maybe there was a way we could offer a simplified reply box as an optional setting, and I did a few mock-ups incorporating some of my favorite elements from the functionality of Basecamp as well as Gmail and Facebook.

The simplifed reply box would basically look like an email, and you would also have a slim option that would shrink to the width of the sidebar, so you could easily read responses while formulating your reply.

Here's the expanded version:

replybox-long.png1238x357 44.2 KB

And here's the slim version:

replybox-short.png1238x351 99.9 KB

The expanded version would be quite similar to the current reply box except that it would have the code-less functionality of an email. I removed a couple of the formatting icons such as horizontal rules in my design, but as to which functions would and would not be present in the simplified view, that could be the topic of an entirely different discussion. My main suggestion is just this notion of an optional, code-less reply box, and the possibility for a slim setting.

As I am new to the discussion, I apologize if I am suggesting something that has been already been proposed. Either way, I am very much on board with Discourse and excited to see it continue to unfold!

Posts: 10

Participants: 5

Read full topic