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

Discourse Presence

0
0

@adrapereira wrote:

Repo: https://github.com/adrapereira/discourse-presence

Do you want to see who - apart from you - is using the "Reply" dialog box to write a reply to a particular topic? If so, then this plugin is for you! This is particularly useful to avoid those situations where a user replies to a topic and sees that another reply was submitted a few seconds earlier.

The inspiration for the plugin was this topic https://meta.discourse.org/t/see-who-all-are-writing-replies-to-a-topic/38884

When other users are using the Reply dialog box, their avatars are displayed to the right of the Reply and Cancel buttons.

When no users are currently replying but have a saved draft for the current topic, their avatars are also listed. To find out when the draft was last updated, you may hover over the avatars to see the date.

To Do

  • See who else is editing. I.e. when two or more admins are editing the same post, or (more likely) if two or more users are editing the same wiki topic.

Posts: 2

Participants: 2

Read full topic


Worked flawlessly first time, now getting 502 error

0
0

@Webtrend wrote:

First time I tried installing discourse using docker container on AWS, everything worked flawlessly. I managed to create an admin account using the console commands.

I just wanted to make sure that I can reproduce the results. So I stopped the container and deleted the images. I did not change any configuration in yml files. After bootstraping and launching, I am now getting Bad Gateway 502 error when I run the following command

curl 127.0.0.1:8080

The nginx error log shows following:

2016/08/09 23:52:37 [error] 42#42: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 172.17.0.1, server: _, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "127.0.0.1:8080"

I am wondering what does this error pertain to? What is running on port 3000?

Posts: 2

Participants: 2

Read full topic

Is Discourse open-source?

[PAID] Developer needed to install WordPress/Discourse combined platform with SSO

0
0

@platinum wrote:

Hello,

We are currently running Discourse by itself on a domain, where it has been used for forum discussions, since about six months ago.

Now: need to add Wordpress as a front end content server, with tight integration to our existing Discourse forums, with single-sign on for Wordpress and Discourse, the ability to keep a session active when the user moves between the two, etc. And, SSO using Facebook/Google credentials.

We prefer new user registrations for the wordpress/discourse integration to happen through Wordpress, unless you can suggest a better way.

Timeframe: ASAP

Budget: Flexible. You tell us.

Contact to discuss further so we can get you to work on our project and get you paid fast.

Posts: 1

Participants: 1

Read full topic

Zero search results searching private messages for specific keyword

0
0

@DeanMarkTaylor wrote:

As an admin attempting to search private messages for a discussion on "natwest"...

Using the search in:private natwest returns zero results.

Running the following query returns 9 results:

SELECT COUNT(*) FROM posts p
LEFT JOIN topics t on t.id = p.topic_id
WHERE t.archetype = 'private_message'
AND p.raw ILIKE '% natwest %'

Checking the actual posts they do contain text like "... its a natwest account ..." and "... I pick up the guarantee on the Natwest overdraft ..."

When using the search in:private car I see results as expected.

Is there a reason why I might not be seeing search results for the "natwest" keyword?

Currently running Discourse 1.7.0.beta1 - 823a699d41974affe42adbd562cc9fbfd5a56ef1.

Posts: 4

Participants: 3

Read full topic

Can we highlight a topic in the using an indicator like New Posts or by changing the color of the whole row?

0
0

@Gussie wrote:

I searched this category and the plugin and feature categories, but did not see a topic that addressed my question. I ran searches for "indicator" and "new post".

Is there a plugin that allows a topic to be distinguished in the list of latest topics if it was posted in a particular category being highlighted some way? The highlight could be an indicator like the "New" indicator. Or it could be a change of color for the whole row.

On my Discourse, I would like to distinguish topics made in one category (Classifieds) so that anytime someone posts a new topic there, they are highlighted in the Latest Topics list. Or the topic author could tick a checkbox so their topic could be highlighted in the list of latest topics.

I am new to Discourse, so maybe there is already a way to accomplish this. I would love to learn of a Discourse Way of accomplishing this.

Posts: 2

Participants: 2

Read full topic

Amazon SES and Avatar URL

0
0

@Terminator wrote:

Hi all,
After months I finally got around to setting up Discourse on my dedicated server with Docker. I was not familiar with docker before this but so far so good.

Please note that I have searched for answers for a day before I post this. I need a fresh look so any help is much appreciated.

Amazon SES:
I manually created the admin following the guide in the git docs with rake. That is because despite having a whitelisted email and domain from SES, it doesnt seem to be able to connect and I get Net Connect timeout in the logs. I have a working setup outside of docker with same email and SES settings on another app.

What could be the possible causes and how do I troubleshoot this further?
For e.g. , Can someone guide me to a rails console method of calling the "email test" and inspect the variables set?

SSO avatar URL (lower priority):
I implemented SSO bridging my custom PHP site with Discourse within an hour and no problems whatsoever and users can sign in. The only problem is that avatar_url is not getting applied. I get the default ones. I am pretty sure it all the data gets passed i.e. 'avatar_url' and 'avatar_force_update' I have checked the production.log while doing a test SSO for new user and I can see the parameters are passed.
I am using the forced update as well set to true. I dont think it has any impact.

Posts: 1

Participants: 1

Read full topic

Links in generated email are incorrect

0
0

@jamesmarkcook wrote:

I'm running Discourse on a subdomain (forum.url.com). When users request a password reset, the link it generates is links.url.com, missing out the forum part.

I've checked my app.yml and my discourse hostname is forum.url.com

Any idea how I fix this?

Thanks

Posts: 6

Participants: 2

Read full topic


Expandable advanced search UI panel

0
0

@codinghorror wrote:

We've got some excellent advanced search options in Discourse at this point, but the UI for them is.. how shall I put this..

... uhhh... bad? Yes, I believe the word I am looking for is "bad".

Recently, I was pleasantly surprised to discover the advanced search in NodeBB is really quite good! In any full page search result there's this little expandable "Advanced Search" panel:

Clicking to expand the "Advanced Search" shows:

I am not proposing any change to the current advanced search options in Discourse at all, merely building UI similar to this around the advanced search options we already have.

My hope is that since this is mostly a UI task, and scoped to the full search results page, it could be taken on by someone in the community. A simple V1 that gets the basics of advanced search UI in, would be perfect. If anyone is interested, we'd be happy to sponsor it.

Posts: 1

Participants: 1

Read full topic

Discourse API - Login case SSO Provider to Consumer site

0
0

@junaid_pk14 wrote:

Hello,

We are working on integrating Main Rails app with Discourse forum. Our Main rails app is SSO provider and forum is SSO consumer. We want to implement the case of automatic login on SSO consumer site when user successfully login on main Rails site. I explored the code of Discourse API gem(https://github.com/discourse/discourse_api.git) and weservices code in the discourse app(admin/users_controller.rb). I think it can be implemented the above case easily as you implemented the log_out webservice code. All we need to return session cookie in webservice after successfully setting auth code to user and api consumer will create cookie on their end with relevant domain name depending type of url scheme(directory based or sub-domain) your Main rails app & forum app url have. Is Discourse team have any plan for its implementation? https://meta.discourse.org/c/extensibility/sso don't exist mentioned here https://meta.discourse.org/t/official-single-sign-on-for-discourse/13045).

I also opened a SSO related issue(https://meta.discourse.org/t/sso-login-logout-issues/48351) 2 days back in 'Support' category but didn't receive any feedback on it.

Thanks
Junaid

Posts: 1

Participants: 1

Read full topic

I made my own CDN

0
0

@Terminator wrote:

I made my own cdn.:smiling_imp: yes it sounds ironic. It is cheaper though. 1TB for 4$ approximately.

You can test it here with your site (non-ssl) http://serve.3ezy.com

Let me explain what is happening here.
You get a 2-3 VPS around the location you are interested in. If you like DO then use that but I don't.
Setup Nginx reverse proxy on each node as you would for your origin upstream.
Use Amazon Route 53 DNS to automatically serve closest VPS to end user. Use LBR.

Here is an example of nginx conf https://github.com/abshkd/dumbcdn/blob/master/nginx-cdn.conf

Flagged as spam: I can understand why, it was in response to another thread about CDN and the topic was split off into its own. I added some more info since then

Posts: 1

Participants: 1

Read full topic

SyntaxError in Turkish Translation

Fenced codeblocks with extra spaces at the end don't work?

0
0

@kuba-orlik wrote:

Why doesn't this code:


var www_server = Sealious.ChipManager.get_chip("channel", "www_server"); www_server.route({ method: "GET", path: "/users.csv", handler: function(context, request){ // .. logic goes here

preserve newlines? Did the syntax change or is there something I am missing?

Posts: 7

Participants: 4

Read full topic

Login page does not appear when anon user tries to download file

0
0

@petruschang wrote:

Hi,

I have a discourse site (docker install, updated to latest version) where people mainly use the discourse site via email (email in). Attachments are displayed as links.

The site is configured with login_required = true. If people are logged in they can download the file when clicking the link in the email.

But if people are not logged in they cannot download the file. Unfortunately, they are also not presented with some kind of login alert or login page.

I think, this issue was already mentioned and closed here:

Any help would be greatly appreciated.

Posts: 2

Participants: 2

Read full topic

İ am almost done to translate tr_Tr on Transifex


Sso login error

0
0

@qintengfei wrote:

Message

Verbose SSO log: Nonce has already expired

nonce: bm9uY2U9ZjhlZjFkM2ZlMjg4NjAyODc0ZDcwZTMwYWM1N2RkOTAmcmV0dXJu
X3Nzb191cmw9aHR0cCUzQSUyRiUyRmRpc2NvdXJzZS5mYW1pMnUuY29tJTJG
c2Vzc2lvbiUyRnNzb19sb2dpbg==

name: qintengfei
username: qintengfei
email: qintengfei@fami2u.com
avatar_url:
avatar_force_update:
require_activation: true
bio: asdfasdf
external_id: znRj97BuMYEkhiKpk
return_sso_url:
admin:
moderator:
suppress_welcome_message:

Backtrace

/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.5/lib/logster/logger.rb:76:in `add_with_opts'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.5/lib/logster/logger.rb:37:in `add'
/usr/local/lib/ruby/2.3.0/logger.rb:498:in `warn'
/var/www/discourse/app/controllers/session_controller.rb:77:in `sso_login'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionview-4.2.7/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/routing/route_set.rb:817:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:127:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activerecord-4.2.7/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/activesupport-4.2.7/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/logster-1.2.5/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7/lib/rails/rack/logger.rb:22:in `call'
/var/www/discourse/config/initializers/100-quiet_logger.rb:13:in `call_with_quiet_assets'
/var/www/discourse/config/initializers/100-silence_logger.rb:26:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/actionpack-4.2.7/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-mini-profiler-0.10.1/lib/mini_profiler/profiler.rb:171:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/message_bus-2.0.1/lib/message_bus/rack/middleware.rb:62:in `call'
/var/www/discourse/lib/middleware/request_tracker.rb:73:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/railties-4.2.7/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:562:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:658:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:508:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/lib/unicorn/http_server.rb:132:in `start'
/var/www/discourse/vendor/bundle/ruby/2.3.0/gems/unicorn-5.1.0/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:23:in `load'
/var/www/discourse/vendor/bundle/ruby/2.3.0/bin/unicorn:23:in `<main>'

Env

hostname	iZ25kveqji9Z-app
process_id	139
application_version	5e3932d40427af086244752e7c0b1171f86cb113
HTTP_HOST	discourse.fami2u.com
REQUEST_URI	/session/sso_login?sso=bmFtZT1xaW50ZW5nZmVpJmV4dGVybmFsX2lkPXpuUmo5N0J1TVlFa2hpS3BrJmVtYWlsPXFpbnRlbmdmZWklNDBmYW1pMnUuY29tJnJlcXVpcmVfYWN0aXZhdGlvbj10cnVlJnVzZXJuYW1lPXFpbnRlbmdmZWkmbm9uY2U9Ym05dVkyVTlaamhsWmpGa00yWmxNamc0TmpBeU9EYzBaRGN3WlRNd1lXTTFOMlJrT1RBbWNtVjBkWEp1JTBBWDNOemIxOTFjbXc5YUhSMGNDVXpRU1V5UmlVeVJtUnBjMk52ZFhKelpTNW1ZVzFwTW5VdVkyOXRKVEpHJTBBYzJWemMybHZiaVV5Um5OemIxOXNiMmRwYmclM0QlM0QlMEEmYmlvPWFzZGZhc2Rm&sig=1b722a07f9787dc4a3f0cda9d9d879f9d08ad074b1a2c74d6736c83c545dea28
REQUEST_METHOD	GET
HTTP_USER_AGENT	Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.116 Safari/537.36
HTTP_ACCEPT	text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
HTTP_REFERER	http://login.fami2u.com/sign-in?sig=52e60335d04525f5cb31f96f57e79a5765503a9dbd1dee74250070610b1625a0
HTTP_X_FORWARDED_FOR	111.206.166.29
HTTP_X_REAL_IP	111.206.166.29
params
sso	bmFtZT1xaW50ZW5nZmVpJmV4dGVybmFsX2lkPXpuUmo5N0J1TVlFa2hpS3BrJmVtYWlsPXFpbnRlbmdmZWklNDBmYW1pMnUuY29tJ
sig	1b722a07f9787dc4a3f0cda9d9d879f9d08ad074b1a2c74d6736c83c545dea28

Posts: 1

Participants: 1

Read full topic

Unsubscribe links do not unsubscribe

0
0

@moparisthebest wrote:

I imported a large forum into discourse (~650k users/3.5 million posts), this requires users to reset their passwords and not all have.

But I have been receiving numerous complaints that people get the digest email, click the unsubscribe link, check "Don't send me any mail from moparisthebest.com", click unsubscribe, see the "Unsubscribed! You have been unsubscribed. To change your email settings visit your user preferences." message, but still continue to get emails. I've even received a few angry emails asking me to unsubscribe them.

So, what can I do to make this work as quickly as possible, or maybe unsubscribe everyone in a quick automated fashion? And how do I unsubscribe individual users manually?

Posts: 2

Participants: 2

Read full topic

Stuck at "2 months later"

0
0

@jesselperry wrote:

I just noticed a weird thing where no matter how much of a gap there is between messages, it maxes out at "2 months later."

If it's less than 2 months, it shows the proper time. But in one instance the message was over a year later, but the notice between the messages just says "2 months later."

Any idea what's going on?

Posts: 5

Participants: 3

Read full topic

Messaging: Group inboxes and archives show even after all messages deleted

Data directory "/shared/postgres_data" has group or world access

0
0

@Dan_G wrote:

When I try to ./laucher bootstrap app discourse it fetches the docker image from the registry and quickly fails afer on

LOG:  skipping missing configuration file "/shared/postgres_data/postgresql.auto.conf"
2016-08-10 18:21:43 UTC [53-2] FATAL:  data directory "/shared/postgres_data" has group or world access
2016-08-10 18:21:43 UTC [53-3] DETAIL:  Permissions should be u=rwx (0700).

My volume configuration is as such:

## The Docker container is stateless; all data is stored in /shared
volumes:
  - volume:
      host: /data/discourse/shared/standalone
      guest: /shared
  - volume:
      host: /data/discourse/shared/standalone/log/var-log
      guest: /var/log

/data is a partition on a second disk (formatted as ext4) but that never proved to be an issue with docker for me before, I run my private docker registry the same way. /data/discourse doesn't exist prior to ./launcher bootstrap app, it is created by by the launcher so I presume it could give it the permissions it wants.

And here's my docker info:

docker info
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 1
Server Version: 1.12.0
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 8
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: overlay host bridge null
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Security Options:
Kernel Version: 3.16.0-4-amd64
Operating System: Debian GNU/Linux 8 (jessie)
OSType: linux
Architecture: x86_64
CPUs: 2
Total Memory: 3.865 GiB
Name: ICL2-LVCORPO-11
ID: TZE6:YZCD:3EFK:IKLN:5RVI:BGA4:M3GS:4CI2:P3TW:TFZY:J2IY:CDFT
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
WARNING: No memory limit support
WARNING: No swap limit support
WARNING: No kernel memory limit support
WARNING: No oom kill disable support
WARNING: No cpu cfs quota support
WARNING: No cpu cfs period support
Insecure Registries:
 127.0.0.0/8

Any clue?

Posts: 3

Participants: 2

Read full topic

Viewing all 60309 articles
Browse latest View live




Latest Images