@Vaping_Community wrote:

Ok, so I have my site setup with SSL and it works great, images are downloaded from sources to preserve HTTPS but the favicon.ico will not / can not download? And is breaking the https.

OneBoxFaviconBroken.png1366x768 103 KB

Posts: 2

Participants: 2

Read full topic

@fhe wrote:

I’ve recently converted a large forum to Discourse and now noticed something, I’d like to change. We have many posts where quotation marks are used to denote small snippets of code or parameters to specific functions. Those are then often copied by members of our support community to for use in the software.

Those where not always enclosed in code tags, but instead using double or simple quotation marks, e.g.,

Parameter: /e, /select, “%_path%”

The problem here is, that quotation marks entered as " are automagically rendered to their open/closed forms as you can see above. This, unfortunately, breaks all the examples that are formatted in this way (it’s invalid syntax in the software).

Is there a way to prevent the automatic rendering of open/closed quotes “” and use the vertical form " instead by default — without putting everything in code blocks?

Posts: 1

Participants: 1

Read full topic

@Curtis_Kephart wrote:

I’d like to follow-up on this discussion:

I work with a discourse forum. Although we don’t want to explicitly prevent people from posting an email address or phone number, we would like to explore flagging such instances before they are made visible.
Perhaps a plugin and/or via some configuration of the “Needs approval” or “Akismet” flagger?

Why not completely prevent it? I can think of many situations in which there are good reasons to post an email or phone number. Certainly in a user-profile where one would like to advertise their business or portfolio.
Why be wary? We’ve recently seen a case or two where people shared their personal email address when a private message would have been a much better path. There’s also a fear of people posting other people’s private contact info. A quick human review would sort these smoothly, I think.

I’ll pre-apologize if I’ve missed a feature, plugin or discussion about this topic already.

Posts: 1

Participants: 1

Read full topic

@thsiung wrote:

Hi,

It’s a very nice title function.

Posts: 7

Participants: 2

Read full topic

@yuri25 wrote:

./launcher rebuild app

FAILED

Pups::ExecError: su postgres -c ‘psql discourse -c “alter schema public owner to discourse ;”’ failed with return #<Process::Status: pid 77 exit 2>
Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn’
exec failed with the params "su postgres -c ‘psql $db_name -c “alter schema public owner to $db_user;”’"
7e61d541e7a6bddbca1a66f2ee60f168d2fbbd96f493de4d354a30a31a35d80a
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one

---

Help me please. I install on a powerful dedicated server. Intel® Core™ i7-4770 Quadcore Haswell
2 x 2048 GB HDD SATA-III 32 GB DDR3

Posts: 7

Participants: 3

Read full topic

@jordan1909 wrote:

In our installation we have a need to include CC’d users on a topic.

Our sales team frequently forwards emails to our inbox which includes the forwarder but does not include the CC’d users. Now it does appear that a staged user is created unless I am mistaken.

Looking at the receiver.rb src it appears this functionality is pretty much there but doesn’t appear to be inviting the staged users as I would expect.

1. User forwards email in with abc@defg.com in CC.
2. If abc@defg.com is a user --> Invite to topic
3. If abc@defg.com is not a user --> Create staged users --> Invite staged user to topic so abc gets all subsequent posts.

Is this not the intended functionality? Will I need to make a plugin for this? If a plugin is needed, is the raw email content accessible?

Posts: 1

Participants: 1

Read full topic

@AstonJ wrote:

One of my forums went down yesterday, first with a blank page then displaying 429’s. Sam thinks it may be possible that my proxy is not configured correctly - anyone know what the best way is to ascertain whether IP addresses are being handed over correctly to Discourse?

I’m pretty sure it is set up correctly (as I have option forwardfor set in HAProxy and users’ IP addresses correctly show up in the admin CP) but I’d like to check Discourse’s end just in case.

Posts: 1

Participants: 1

Read full topic

@jordan1909 wrote:

I know this had been discussed before but I needed to see if this was going to be implemented.

We have a need to have a category on a private message to determine if private messages are marked solved, etc within a specific category.

Posts: 6

Participants: 4

Read full topic

@timdiggins wrote:

Given:

If you have a piece of pdf content hosted* on a non-ssl site and
the ssl version of the site gives a ssl error (e.g. err_ssl_unrecognized_name_alert), and
you copy your link into a onebox-enabled site (e.g. discourse, I think, but I was using thredded: see thredded/thredded#682, I’ve also validated that this occurs in the current master of onebox with rake server).

I would expect it to either retrieve the pdf correctly and onebox it, or
attempt to retrieve it by https and fail and then just present a non-oneboxed link, or
(worst case) just show a onebox failure

but instead:

it throws an error (to be caught or not by the webapp using onebox).

---

So I think the conversion of http -> https is by design always_https in onebox/pdf_onebox.rb at 6b5b53b26e7bb36b9e3e6cedce5db9172692c851 · discourse/onebox · GitHub – to prevent mixed content errors.

traceback: traceback for oneboxing failure of https error · GitHub

However then I think onebox ought to deal with the https failure.
Not 100% sure how to proceed (I guess it’s possible to create a test case, it’s just a bit complicated).

Posts: 1

Participants: 1

Read full topic

@McBlu wrote:

G’day,

I have a secret group which is invite only. Here is what I have for security permissions:

If I add a person to this secret category, in order for them to be able to create/reply/see, do I need to add "everyone " as authorized as depicted below? From my tests, I believe adding “everyone” makes the category public.

Thanks in advance.

Posts: 2

Participants: 2

Read full topic

@jerdog wrote:

I just noticed this the other day, how that when I perform a backup (or a restore), instead of showing a live log of what’s happening it just shows the following:

Everything completes fine, but I don’t know what’s happening.

Edit: I actually have to reload the page in order for the live logs to appear - and they still don’t update. I have to reload to know if it’s done.

Posts: 1

Participants: 1

Read full topic

@andy.czerwonka wrote:

Message (2 copies reported)

NoMethodError (undefined method `category_id' for nil:NilClass) 
/var/www/discourse/app/models/topic_tag.rb:16:in `block in <class:TopicTag>'

Backtrace

/var/www/discourse/app/models/topic_tag.rb:16:in block in <class:TopicTag>' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:413:ininstance_exec’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:413:in block in make_lambda' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:235:inblock in halting_and_conditional’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:511:in block in invoke_after' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:511:ineach’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:511:in invoke_after' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:132:inrun_callbacks’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:827:in _run_destroy_callbacks' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/callbacks.rb:321:indestroy’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:303:in block in destroy' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:384:inblock in with_transaction_returning_status’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:233:in transaction' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:210:intransaction’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:381:in with_transaction_returning_status' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:303:indestroy’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/persistence.rb:211:in destroy!' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/associations/has_many_association.rb:105:ineach’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/associations/has_many_association.rb:105:in delete_records' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/associations/collection_association.rb:394:inremove_records’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/associations/collection_association.rb:387:in block in delete_or_destroy' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/associations/collection_association.rb:129:inblock in transaction’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:233:in transaction' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:210:intransaction’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/associations/collection_association.rb:128:in transaction' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/associations/collection_association.rb:387:indelete_or_destroy’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/associations/collection_association.rb:196:in destroy' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/associations/collection_association.rb:169:indestroy_all’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/associations/has_many_association.rb:26:in handle_dependency' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/associations/builder/association.rb:140:inblock in add_destroy_callbacks’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:413:in instance_exec' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:413:inblock in make_lambda’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:197:in block (2 levels) in halting' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:601:inblock (2 levels) in default_terminator’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:600:in catch' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:600:inblock in default_terminator’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:198:in block in halting' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:507:inblock in invoke_before’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:507:in each' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:507:ininvoke_before’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:130:in run_callbacks' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:827:in_run_destroy_callbacks’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/callbacks.rb:321:in destroy' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:303:inblock in destroy’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:384:in block in with_transaction_returning_status' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:233:intransaction’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:210:in transaction' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:381:inwith_transaction_returning_status’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:303:in destroy' /var/www/discourse/app/controllers/tags_controller.rb:123:inblock in destroy’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:235:in block in transaction' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/transaction.rb:194:inblock in within_new_transaction’ /usr/local/lib/ruby/2.4.0/monitor.rb:214:in mon_synchronize' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/transaction.rb:191:inwithin_new_transaction’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/connection_adapters/abstract/database_statements.rb:235:in transaction' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/transactions.rb:210:intransaction’ /var/www/discourse/app/controllers/tags_controller.rb:122:in destroy' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/basic_implicit_render.rb:4:insend_action’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:186:in process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/rendering.rb:30:inprocess_action’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:20:in block in process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:131:inrun_callbacks’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/callbacks.rb:19:in process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/rescue.rb:20:inprocess_action’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:32:in block in process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:inblock in instrument’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications/instrumenter.rb:21:in instrument' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/notifications.rb:166:ininstrument’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/instrumentation.rb:30:in process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal/params_wrapper.rb:252:inprocess_action’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activerecord-5.1.4/lib/active_record/railties/controller_runtime.rb:22:in process_action' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/abstract_controller/base.rb:124:inprocess’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionview-5.1.4/lib/action_view/rendering.rb:30:in process' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/mini_profiler/profiling_methods.rb:102:inblock in profile_method’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:189:in dispatch' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_controller/metal.rb:253:indispatch’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:49:in dispatch' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:31:inserve’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:50:in block in serve' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:ineach’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/journey/router.rb:33:in serve' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/routing/route_set.rb:834:incall’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-protection-2.0.0/lib/rack/protection/frame_options.rb:31:in call' /var/www/discourse/lib/middleware/omniauth_bypass_middleware.rb:24:incall’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/conditional_get.rb:38:in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/head.rb:12:incall’ /var/www/discourse/lib/middleware/anonymous_cache.rb:149:in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:232:incontext’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/session/abstract/id.rb:226:in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/cookies.rb:613:incall’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:26:in block in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/activesupport-5.1.4/lib/active_support/callbacks.rb:97:inrun_callbacks’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/callbacks.rb:24:in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/debug_exceptions.rb:59:incall’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/show_exceptions.rb:31:in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/logster-1.2.9/lib/logster/middleware/reporter.rb:31:incall’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:36:in call_app' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/rack/logger.rb:26:incall’ /var/www/discourse/config/initializers/100-quiet_logger.rb:16:in call' /var/www/discourse/config/initializers/100-silence_logger.rb:29:incall’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/remote_ip.rb:79:in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/request_id.rb:25:incall’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/method_override.rb:22:in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/actionpack-5.1.4/lib/action_dispatch/middleware/executor.rb:12:incall’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/sendfile.rb:111:in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-mini-profiler-0.10.7/lib/mini_profiler/profiler.rb:282:incall’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/message_bus-2.1.2/lib/message_bus/rack/middleware.rb:63:in call' /var/www/discourse/lib/middleware/request_tracker.rb:158:incall’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/engine.rb:522:in call' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:inpublic_send’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/railties-5.1.4/lib/rails/railtie.rb:185:in method_missing' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:68:inblock in call’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:53:in each' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/rack-2.0.3/lib/rack/urlmap.rb:53:incall’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:606:in process_client' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:701:inworker_loop’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:549:in spawn_missing_workers' /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/lib/unicorn/http_server.rb:142:instart’ /var/www/discourse/vendor/bundle/ruby/2.4.0/gems/unicorn-5.4.0/bin/unicorn:126:in <top (required)>' /var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:23:inload’ /var/www/discourse/vendor/bundle/ruby/2.4.0/bin/unicorn:23:in `<main>’

Env

hostname	CGYSVRDISCOURSE01-app
process_id	[17783, 17635]
application_version	9bb7c3dcf0db32861413f981fac9431ca5f1f15e
HTTP_HOST	discourse.3esi-enersight.com
REQUEST_URI	[/tags/jgsd, /tags/idea]
REQUEST_METHOD	DELETE
HTTP_USER_AGENT	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36
HTTP_ACCEPT	application/json, text/javascript, /; q=0.01
HTTP_X_FORWARDED_FOR	10.0.10.165
HTTP_X_REAL_IP	10.0.10.165
username	andy.czerwonka

Posts: 2

Participants: 1

Read full topic

@Timothy_Vail wrote:

Hello, I am trying to install wordpress and discourse on the same Amazon EC2 AWS server. I have discourse all set up already, but no wordpress yet. I tried to follow this guide

and

up to step 8

Now I am getting the APache2 Ubuntu page when I load my site, but nothing under /phpmyadmin

Where do I go from here?

I have discourse.conf in my nginx/sites-enabled/ and have this in it

upstream forum {
server 127.0.0.1:8080 fail_timeout=0;
}

upstream php {
    server unix:/tmp/php-cgi.socket;
    server 127.0.0.1:9000;
}

server {
    server_name mydomain.net *.mydomain.net 46.101.xxx.xxx;
    root /var/www/html;
    ## This should be in your http block and if it is, it's not needed here. <-- it's not there, so I'm leaving it here
    index index.php index.html index.htm;

    location / {
            #try_files $uri $uri/ /index.php?$args;
             try_files $uri $uri/ /index.php?q=$uri&$args; 
    }

    error_page 404 /404.html;

    error_page 500 502 503 504 /50x.html;
    location = /50x.html {
            root /usr/share/nginx/html;
    }

    location ~ \.php$ {
            #NOTE: You should have "cgi.fix_pathinfo = 0;" in php.ini <-- I did that
            include fastcgi.conf; # <-- this is crucial
            fastcgi_intercept_errors on;
            try_files $uri =404;
            fastcgi_split_path_info ^(.+\.php)(/.+)$;
            fastcgi_pass unix:/var/run/php/php7.0-fpm.sock;
            #fastcgi_pass php;
            fastcgi_index index.php;
            include fastcgi_params;
    }

    # This is for saving resources by caching static content longer
    location ~* \.(js|css|png|jpg|jpeg|gif|ico)$ {
            expires max;
            log_not_found off;
    }

    location = /favicon.ico {
            log_not_found off;
            access_log off;
    }
	
   location = /robots.txt {
            allow all;
            log_not_found off;
            access_log off;
    }
}

Posts: 3

Participants: 2

Read full topic

@Heather_Dudley wrote:

Is there an easy way to bulk edit categories from the admin panel? We’re working on a test site, and of course, I set up differing badge colors for all the categories. I’d like to change them all to roughly the same theme (it won’t be finalized, but this is at the request of beta testers, and I like pretty themes, so.)

Is there an easy way to do this, or do I have to go through and edit each category individually?

Posts: 3

Participants: 2

Read full topic

@Geoffrey_Challen wrote:

I’ve had a Discourse instance running happily for over a month, until just about an hour ago. Now I’m getting:

• frequent “The requested URL or resource could not be found.” when loading any page.
• periodic “you don’t have access to that category” errors
• random logouts
• random “You don’t have access to that topic errors”

Any clues how to debug or fix this? At least for me my forum is pretty unusable, and I suspect that this is also affecting other users…

Just confirmed that this is also affecting my other admin user.

Posts: 3

Participants: 1

Read full topic

@McBlu wrote:

G’day,

I am about to test creating accounts in our forum via twitter, facebook, and google.

I am going to test using the platforms to create an account via my own personal facebook, google, and twitter accounts. It occurred to me that even though I am the same person (obviously ) the accounts wouldn’t be linked. I guess people would pick the platform they want to sign in via and stick with that. But I can also imagine the scenario, where a person forgets their sign in on one platform, let’s say Facebook, and decides to just use another of their platforms, let’s say Twitter.

Is there an option for linking an account to different platform sign ins?

FYI, I am not necessarily thinking this is a good function to have, just wanting to understand how it works.

Posts: 3

Participants: 3

Read full topic

@gklages wrote:

Forums_Subject_Too_Long_in_Outlook.png3312x848 335 KB

As shown in my screenshot, I watch forums to read in Outlook, which works great except some forum posters put their entire message in the Subject Title (not entirely viewable) with only a few words in the Message Area.

When a Subject Title is longer than 30 characters, can the entire Subject Title be copied into the Message Area before it is posted and emailed to those watching the forum?

Or can we persuade users to use the Message Area by limiting the Subject Title to only 20 characters?

And/or can we have their Subject Title copied into their Message Area and move the cursor to the Message Area to allow them to keep typing (where it would be easier for others to read)?

Posts: 2

Participants: 2

Read full topic

@McBlu wrote:

G’day,

I have been thinking about the difference between forums and chat rooms and this article was helpful for explaining how they differ.

I might not be able to install the chat room plugin just yet due to budget constraints, which got me thinking why not just use a topic in a private category as a chat room where no particular topic is adhered to, moderating is less (tl 3 only in chat room), and content is not archived or preserved. I imagine deleting and restarting topic everynow and then if necessary.

Has anyone taken this approach and how has that worked out?
Is a chat room topic too taxing on the forum host in terms of retaining records of that chat room thread by default. Does it mess with search results? Anything else I am not thinking of?

Posts: 3

Participants: 3

Read full topic

@mschekotov wrote:

Hi there, folks.

I am currently migrating some forum to Discourse.
I have zero experience with RoR development, so I have few questions about Discourse and its infrastructure.

First of all, I’m planning to use the Discourse forum as-is, without custom plugins or source code modifications.
I, however, would like to write database migrations from time to time to simplify data transition from the staging instance of a forum to the production one.
I want to put these migrations in a git repository to fetch and apply them when rebuilding the app.

I would like to know the “true” way of achieving that.
Any help is highly appreciated, and links for further reading are welcome too.

Posts: 8

Participants: 3

Read full topic

@burningman wrote:

One of my forum goes offline. I checked on sever but everything is working fine on server side.
Another forum is working fine but one goes offline.

Is anyone here facing this issue.

It will be great if anyone here will share how and when forum comes back online.

Thanks

Posts: 23

Participants: 3

Read full topic