@helperhaps wrote:

branch: test-passed

Recently, I installed a plugin. Discourse updated to 1.6beta4 from beta1 when i rebuild docker. And then, user can not get their emails.

Opened /admin/email/skipped in chrome, i got

[Sender] 553 Mail from must equal authorized user

and in the lib/email/sender.rb:119

if SiteSetting.reply_by_email_address.present? && SiteSetting.reply_by_email_address["+"]
  email_log.bounce_key = SecureRandom.hex

  # WARNING: RFC claims you can not set the Return Path header, this is 100% correct
  # however Rails has special handling for this header and ends up using this value
  # as the Envelope From address so stuff works as expected
  @message.header[:return_path] = SiteSetting.reply_by_email_address.sub("%{reply_key}", "verp-#{email_log.bounce_key}")
end

remove the code listed, email works just well. So what this line use for? what can i do with this?

Posts: 5

Participants: 2

Read full topic

@Tia wrote:

After commenting with a whisper to a staff member on our community, I got this email from the original poster:

Hidden reply?
Hey,
The forum say that my help post from yesterday has two replies (one from you)
Did you reply to this? I can't see what you posted!

The whisper also appears in the comment count along with the whisper's avatar.
Is there a way to disable this? This kinda goes against the whole purpose of whispering.

Posts: 3

Participants: 2

Read full topic

@lrossouw wrote:

At the risk of flogging a dead horse:

• Is there a way to repin unpinned topics for all users?
• I want to change the user settings for all users to not automatically unpin pinned topics?
• I will allow unpinning per user but want the defaults to be "conservative"?

We are a NPO and our donation drive is being automatically unpinned. We want to keep it front of mind to users.

I'm assuming I need to run some sql to do this.

Posts: 3

Participants: 2

Read full topic

@Fred_vom_Jupiter wrote:

If I uncheck the allow uncategorized topics the category is still shown in the overview, and it is still possible to post in uncategorized.

Any idea why?

Posts: 3

Participants: 3

Read full topic

@vjFaLk wrote:

Hi! We use Discourse over at https://discuss.erpnext.com

We're getting an issue since several days, updating won't fix it :

NoMethodError (undefined method `trust_level' for nil:NilClass)
/var/www/discourse/app/serializers/queued_post_serializer.rb:33:in `include_can_delete_user?'

Traceback:

/var/www/discourse/app/serializers/queued_post_serializer.rb:33:in `include_can_delete_user?'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:374:in `include?'
(eval):14:in `_fast_attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:467:in `rescue in attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:455:in `attributes'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:479:in `_serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/serializer.rb:361:in `serializable_hash'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:89:in `block in _serializable_array'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:79:in `map'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:79:in `_serializable_array'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:73:in `serializable_array'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/active_model_serializers-0.8.3/lib/active_model/array_serializer.rb:49:in `as_json'
/var/www/discourse/app/controllers/application_controller.rb:258:in `serialize_data'
/var/www/discourse/app/controllers/application_controller.rb:269:in `render_serialized'
/var/www/discourse/app/controllers/queued_posts_controller.rb:12:in `index'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/implicit_render.rb:4:in `send_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:198:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rendering.rb:10:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:20:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:117:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:505:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:778:in `_run_process_action_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/callbacks.rb:19:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rescue.rb:29:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/instrumentation.rb:32:in `block in process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `block in instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/notifications.rb:164:in `instrument'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/instrumentation.rb:30:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/params_wrapper.rb:250:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/railties/controller_runtime.rb:18:in `process_action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/abstract_controller/base.rb:137:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionview-4.2.6/lib/action_view/rendering.rb:30:in `process'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.9.2/lib/mini_profiler/profiling_methods.rb:76:in `block in profile_method'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb:196:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal/rack_delegation.rb:13:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_controller/metal.rb:237:in `block in action'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:74:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:74:in `dispatch'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:43:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/mapper.rb:49:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:43:in `block in serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:30:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/journey/router.rb:30:in `serve'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/routing/route_set.rb:817:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-protection-1.5.3/lib/rack/protection/frame_options.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:186:in `call!'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/strategy.rb:164:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/omniauth-1.3.1/lib/omniauth/builder.rb:63:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/conditionalget.rb:25:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/head.rb:13:in `call'
/var/www/discourse/lib/middleware/anonymous_cache.rb:129:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/params_parser.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/flash.rb:260:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:225:in `context'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/session/abstract/id.rb:220:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/cookies.rb:560:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/query_cache.rb:36:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activerecord-4.2.6/lib/active_record/connection_adapters/abstract/connection_pool.rb:653:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/callbacks.rb:29:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:88:in `__run_callbacks__'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:778:in `_run_call_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/activesupport-4.2.6/lib/active_support/callbacks.rb:81:in `run_callbacks'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/callbacks.rb:27:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/remote_ip.rb:78:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/debug_exceptions.rb:17:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/show_exceptions.rb:30:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/logster-1.2.3/lib/logster/middleware/reporter.rb:31:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/rack/logger.rb:38:in `call_app'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/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.0.0/gems/actionpack-4.2.6/lib/action_dispatch/middleware/request_id.rb:21:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/methodoverride.rb:22:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/runtime.rb:18:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/sendfile.rb:113:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-mini-profiler-0.9.9.2/lib/mini_profiler/profiler.rb:167:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/message_bus-2.0.0.beta.8/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.0.0/gems/railties-4.2.6/lib/rails/engine.rb:518:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/application.rb:165:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:in `public_send'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/railties-4.2.6/lib/rails/railtie.rb:194:in `method_missing'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:66:in `block in call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `each'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/rack-1.6.4/lib/rack/urlmap.rb:50:in `call'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:562:in `process_client'
/var/www/discourse/lib/scheduler/defer.rb:85:in `process_client'
/var/www/discourse/lib/middleware/unicorn_oobgc.rb:95:in `process_client'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:658:in `worker_loop'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:508:in `spawn_missing_workers'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:519:in `maintain_worker_count'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/lib/unicorn/http_server.rb:283:in `join'
/var/www/discourse/vendor/bundle/ruby/2.0.0/gems/unicorn-5.0.1/bin/unicorn:126:in `<top (required)>'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:22:in `load'
/var/www/discourse/vendor/bundle/ruby/2.0.0/bin/unicorn:22:in `<main>'

I'm not well versed with Ruby on Rails / Ruby, but it seems the user object is is not being passed / is null?

Posts: 2

Participants: 2

Read full topic

@thorbenegberts wrote:

Our instance is hosted by Discourse (forum.plentymarkets.com).

I just wanted to test a plugin locally with the vagrant image. Is there any way to see on which version our productive instance is currently running?

On my local instance the version is displayed on the dashboard:

Bildschirmfoto 2016-05-17 um 14.35.42.png1314x356 33.3 KB

On my online instance however it's replaced by the "Account Management" panel:

Bildschirmfoto 2016-05-17 um 14.36.16.png1332x550 51 KB

Any idea where I can find it?

Kind regards,
Thorben

Posts: 3

Participants: 2

Read full topic

@CamilleRoux wrote:

When you quote a message with a mention, Discourse display 2 links (one empty and a correct one):

<blockquote><p>Je vous partage une réponse intéressante que <a class="mention" href="/users/swallez"></a><a class="mention" href="/users/swallez">@swallez</a> m'a faite sur Twitter :</p></blockquote>

Here is the quote link : https://forum.pragmaticentrepreneurs.com/t/choisir-son-moyen-de-paiement-passer-par-une-banque-et-si-oui-laquelle/6360/4?u=camilleroux

Posts: 1

Participants: 1

Read full topic

@Nick_Putman wrote:

Discourse was running fine a new server (Digital Ocean one click install) and now it is not. I am getting the '502 Bad Gateway - nginx' error message. I have not made any changes to the configurations - it just stopped working last night. This is the message I've had from the developer who has been helping with this:

Discourse is running on Docket along with the nginx. We configured discourse to listen to port 8080. Both discourse and nginx was working perfectly. But due to some unknown issue discourse is not working any more. In the server docket service is running but not found the discourse. Tried to relaunch the app.yml but its not found in its directory also ./launcher is not recognized by server.

Could someone help to troubleshoot this issue?

Posts: 15

Participants: 3

Read full topic

@CCSAwebdev wrote:

I have a discourse site that is only used for one month twice each year, therefore once that one month is over we save an image of the slice and shut everything down. Every time we boot up it attempts to send out a mass blast of digest emails to all the previous users, even though they're well past the "hasn't been seen in 20 days" setting to disable digest mail.

Thankfully during the switch from Mandrill to Mailgun on this last bootup because of a DNS problem it didn't send out the digests, but now I'm stuck with thousands of unsent digests piling up in the log. I've fixed the DNS issue and have all emails disabled until I can get things cleaned up.

Is there any way to delete these messages that are sitting in the outbound queue? I certainly don't need to spam thousands of people with digests that are from topics 6 months ago. I DO need to use digests for the new users.

Posts: 3

Participants: 2

Read full topic

@tim.smith wrote:

Does anyone know what the minimum S3 actions are for s3 uploads to work? The Setting up file and image uploads to S3 guide says to use "s3:*", but the infsec voice in my head tells me never to blindly allow all. Does anyone have a paired down list of permissions that Discourse requires?

Posts: 1

Participants: 1

Read full topic

@joebuhlig wrote:

Part of what I love about the new widget structure is being able to reuse code in multiple places. But I've run into an issue when attempting to do this for the voting plugin.

I use widgets heavily on the page for an individual topic. It makes the build process much smoother. But I want to take the base parent widget I've built for the topic page and place it on the topic list. That would allow the user to interact with the topic from the list itself. This is easily the most common request I get for this plugin.

However, since the topic list is built using raw handlebars templates, you can't mount a widget there.

I can get this done by reopening the topic list component and rebuilding the entire UI but that seems a bit extreme for something seemingly simple. I'm hoping someone has an idea for how to reuse a widget on a topic list. Thoughts?

Posts: 1

Participants: 1

Read full topic

@jmamazo wrote:

Hello guys
we are running our website on www.example.com and our forum on forum.example.com
now we want our forum to run on www.example.com/forum

so I moved the forum.example.com to forum.example.com/forum using https://meta.discourse.org/t/subfolder-support-with-docker/30507. This seems to work fine (I can access it via www.example.com/forum/) , but all our content still is forum.example.com so I renamed it to www.example.com following https://meta.discourse.org/t/change-the-domain-name-or-rename-my-discourse/16098. But now when I go forum.example.com it redirects me to www.example.com and when I go to www.example.com/forum/ still sends me back to www.example.com

Any ideas about how to do this properly?

Thanks

Posts: 1

Participants: 1

Read full topic

@DeanMarkTaylor wrote:

Before typing:

Pasted image332x583 28.6 KB

After you have typed something:

Note that both background and text are white.

Posts: 2

Participants: 2

Read full topic

@lrossouw wrote:

I have a large number of suspect users I want to delete. They were migrated from our previous vbb forum and they have been sitting on our forum as suspect users for some time. Many of these have profile link spam.

My criteria are to delete any user meeting the following criteria:

• users that were last seen say more than 3 years ago
• users that have no posts
• users that have not read any posts
• (maybe users that have a web profile url)

I am able to select these using sql, but now want to bulk delete them.

How do I go about this?

Posts: 2

Participants: 2

Read full topic

@tobiaseigen wrote:

Google analytics helps us to understand active user stats, but that overlooks the many email-only participants we have. An extremely handy data explorer query, methinks, would generate a chronological list of the following, with a filter by category preferably to ignore private categories:

• date
• username
• # topics started
• # topics replied
• # topics liked
• # messages started
• # messages replied
• # messages liked

Posts: 1

Participants: 1

Read full topic

@balthatrix wrote:

I'm noticing a couple api calls I can't make without a csrf token:

Wanting to initialize a new user here:
client.sync_sso (new_user_info)
-and-
Wanting to change an existing username here:
client.put("/users/#{old_un}/preferences/username", {new_username: new_un, username: old_un})

Both of these are rejected by my discourse server noting lack of csrf token.
Is there a workaround for this or is this just an inherently wrong approach?

Posts: 4

Participants: 2

Read full topic

@boblikesoup wrote:

Hey guys first time posting excited about these forums and the community. Ran into my first bug and couldn't find anything about it while searching.

I made a custom color scheme for my forum and this random pink color is showing up for a lot of the text and some icons even though it's not default nor did I designate it anywhere. #be5e79

Thanks!

Posts: 8

Participants: 3

Read full topic

@HAWK wrote:

Continuing the discussion from How to add header menu links:

I have recently updated my header links to work for the header now that it has been migrated to Virtual DOM and everything is working ok, unless you're on an iPhone 6.

My experience with media queries is very limited. Can anyone that knows their way around them give me a clue as to why it's not working for that specific device?

Here is the relevant code:

.mobile-view .hidden-for-mobile {
    display: none;
}
.add-header-links {
    margin-left: 0 !important;
}

@media screen and (max-width: 940px) {
    .nav-link-container li:nth-child(1) {
        display: none;
    }
}
@media screen and (max-width: 830px) {
    .nav-link-container li:nth-child(2) {
        display: none;
    }
}
@media screen and (max-width: 743px) {
    .nav-link-container li:nth-child(3) {
        display: none;
    }
}
@media screen and (max-width: 667px) {
    .nav-link-container li:nth-child(4) {
        display: none;
    }
}
@media screen and (max-width: 650px) {
    .nav-link-container li:nth-child(5) {
        display: none;
    }
}
@media screen and (max-width: 525px) {
    .nav-link-container li:nth-child(6) {
        display: none;
    }
}

This is what it looks like on an iPhone6 at the moment.

Posts: 7

Participants: 3

Read full topic

@charleswalter wrote:

I'm at a hotel in Costa Rica and many other guests must be using the wifi right now, because the Internet is awfully slow.

I thought it was interesting to see how Discourse behaved on a few instances. First, when tapping on the number of likes a post received, it appeared that there was no response. But indeed 5-6 seconds later popped the faces of who had liked my post.

Perhaps more importantly, I posted a reply, and saw that it posted, and then continued to navigate. But when I refreshed the topic, I noticed my post had not actually made it to the server.

Just wanted to share these experiences. I expect they can be simulated by applying throttling from Chrome developer tools. I don't expect this to be the norm, but if there are easy things that could be done to let user know to hold on, might be worth considering for future roadmap.

Posts: 1

Participants: 1

Read full topic

@saori wrote:

I'am creating my own dictionary using Discourse.

When I search almost of the words (watch, see, eat, play etc.) using Search mark within my website, these words can be shown successfully.
However,when I search pronominal (for example, you, me, they, he, she etc.), there's no search result (but these words exist). I don't know what's wrong.

If someone know how to fix it, please tell me.

Thank you!

Posts: 3

Participants: 3

Read full topic