@Alexander_Wright wrote:
Using the
[details=Summary]This text will be hidden[/details]in a private message results in the Summary drop down appearing correctly, but the hidden text appearing immediately below, and not hidden as it would be in a topic post.It does, however, work in the markup editor when you are writing the message.
Posts: 6
Participants: 2
@tgxworld wrote:
Continuing the discussion from Discourse Narrative Bot:
The quote reply button doesn't show up.
Posts: 6
Participants: 5
@gauthier wrote:
Hello,
I have an old page indexed by google: mydomain.com/search.php
When i click on it, i get a blank page.It's seems this page, search.php doesn't work on any discourse instance. Why?
Why
https://meta.discourse.org/search.php = ko
https://meta.discourse.org/search.xyz = ko
https://meta.discourse.org/sqd.xyz = okIs it a bug with the search feature?
It's not really a problem, but it's strange.Thanks
Posts: 6
Participants: 5
@Lee_Ars wrote:
After migrating Discourse to a new phy host and restoring the site from backup, I'm still getting the same error message in the staff category with the performance report option enabled—
Report is only available in latest image, please run: cd /var/discourse ./launcher rebuild appI went back and tried to re-do some of the troubleshooting @sam suggested in this eariler thread, but there doesn't appear to be a
/var/www/discourse/script/nginx_analyze.rbanymore, so I'm not sure exactly where to start.I can trigger
Jobs::DailyPerformanceReportfrom the sidekiq scheduler and it runs without errors, though it completes in 3ms and creates no topics. Triggering the report from the rails console also results in no output:# rails c [1] pry(main)> Jobs:: DailyPerformanceReport.new.execute(nil) => nilNo errors are logged in logster for either.
@downey or anyone else on the team, do you have any suggestions? Happy to do whatever it takes to get this resolved. Can also try to arrange a time to grant login access to the web host if you'd like to poke further.
Posts: 4
Participants: 3
@estyshoshana wrote:
My company is running a Discourse instance for our customers. We want to add a link to our main application that will bring users to a page where they can log in to our Discourse, with the email address they use in our system pre-filled. If they do not have an account, we want to bring them to a page where they can register for our Discourse, with the email address and possibly other information pre-filled.
I've searched in the Meta and looked at the API docs, and I do not see a straightforward way to do this. (Also, apologies; I am not sure what the best category for this question is.)
Is this possible and can this be done reasonably, or will it ultimately be a better use of our time to just implement Single Sign On? We don't yet have email validation set up in our application, but we are currently developing it.
Posts: 5
Participants: 3
@hallaathrad wrote:
Currently, if you're trying to start a message, there's a popup telling you the post needs to be at least 10 characters long (which also asks whether you have tried the <3 button... for whatever reason?).
Proceed to type said 10 characters, then press send.
You'll get a nice alert telling you "Body is too short (minimum is 20 characters)"10 ≠ 20. Is this project open source? I'd like to contribute.
Posts: 5
Participants: 3
@Jeff_Vienneau wrote:
Has anyone seen this issue before where some images are broken after a site upgrade?
Went from 1.6.5 to 1.6.7.
During the upgrade I got a log entry:
Sidekiq heartbeat test failed, restartingI manually did a
./launcher rebuild appafterwards but still had image issues.Any suggestions?
Posts: 3
Participants: 2
@merpdotcom wrote:
If it is not one thing is another. Hopefully someone can help me isolate what is wrong.
I tried repeatedly to get discourse to work on an OpenSuse 13.2 server at the colo, but no joy, and it appears it is not well supported on that platform.I have repeatedly completely uninstalled/removed docker, discourse, /var/discourse, removed images, containers, etc. I am perfectly willing to start fresh again if needed.
And that server, though it had a block of many IPs, I kept fighting over the ports, and setting up nginx while battling with all the other webservers running (Apache, Plone, etc.). So I tried setting up on my own laptop, but again OpenSuse 13.2 seemed to have a lot of issues with the setup.
So I setup an old laptop, completely fresh server install, with nothing else on it, with Ubuntu 16.04 LTS server, hoping the closer match to the instructions would solve things, however this is an at-home NAT network, so using proper DNS seemed to be tripping me up. I had setup portforwarding, and dns (I control my own dns servers at various colos). So i tried just configuring the host to only use the IP address. I'm a newb to docker and discourse, and I'm missing something somewhere.
It seems to be running, but I just can't for the life of me seem to figure out what piece I am missing so that it is accessible.
I tried several different instructions from several locations. Here is one (of several I tried) I have been following the directions step-by-step here still to now avail.:
https://www.digitalocean.com/community/tutorial/how-to-install-discourse-on-ubuntu-14-04But after everything is setup, I just get access denied on the server, even when doing lynx 172.17.0.1 or lynx 192.168.2.16 (the docker/discourse/app ip and the laptop/server ip respectively), and when trying to hist 192.168.2.16 from another computer on the same home network.
I'm not seeing where I can get some good logging information turned up so I can better debug, so I am hoping folks will be kind enough to walk me through troubleshooting this?
cat /proc/sys/net/ipv4/ip_forward 1 ifconfig docker0 Link encap:Ethernet HWaddr 02:42:20:24:0f:bc inet addr:172.17.0.1 Bcast:0.0.0.0 Mask:255.255.0.0 inet6 addr: fe80::42:20ff:fe24:fbc/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:339781 errors:0 dropped:0 overruns:0 frame:0 TX packets:339488 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:22368991 (22.3 MB) TX bytes:114341055 (114.3 MB) enp5s0 Link encap:Ethernet HWaddr 00:16:36:e1:e0:70 inet addr:192.168.2.16 Bcast:192.168.2.255 Mask:255.255.255.0 inet6 addr: 2601:602:c000:bdfc:216:36ff:fee1:e070/64 Scope:Global inet6 addr: fe80::216:36ff:fee1:e070/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:384670 errors:0 dropped:427 overruns:0 frame:0 TX packets:339498 errors:4 dropped:0 overruns:0 carrier:4 collisions:434 txqueuelen:1000 RX bytes:123207216 (123.2 MB) TX bytes:29004392 (29.0 MB) Interrupt:18 Memory:da000000-da020000 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:96 errors:0 dropped:0 overruns:0 frame:0 TX packets:96 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:7184 (7.1 KB) TX bytes:7184 (7.1 KB) veth107b9cb Link encap:Ethernet HWaddr 2a:2c:34:62:48:c9 inet6 addr: fe80::282c:34ff:fe62:48c9/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:360 errors:0 dropped:0 overruns:0 frame:0 TX packets:360 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:28542 (28.5 KB) TX bytes:120453 (120.4 KB) ping 172.17.0.1 PING 172.17.0.1 (172.17.0.1) 56(84) bytes of data. 64 bytes from 172.17.0.1: icmp_seq=1 ttl=64 time=0.081 ms lynx 172.17.0.1 Looking up '172.17.0.1' first Looking up 172.17.0.1 first Looking up 172.17.0.1 Making HTTP connection to 172.17.0.1 Alert!: Unable to connect to remote host. lynx: Can't access startfile http://172.17.0.1/ lynx 192.168.2.16 Looking up '192.168.2.16' first Looking up 192.168.2.16 first Looking up 192.168.2.16 Making HTTP connection to 192.168.2.16 Alert!: Unable to connect to remote host. lynx: Can't access startfile http://192.168.2.16/ netstat -na | grep LIST tcp 0 0 0.0.0.0:4422 0.0.0.0:* LISTEN tcp6 0 0 :::4422 :::* LISTEN tcp6 0 0 :::80 :::* LISTEN tcp6 0 0 :::443 :::* LISTEN iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination DOCKER-ISOLATION all -- anywhere anywhere DOCKER all -- anywhere anywhere ACCEPT all -- anywhere anywhere ctstate RELATED,ESTABLISHED ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain DOCKER (1 references) target prot opt source destination ACCEPT tcp -- anywhere 172.17.0.2 tcp dpt:https ACCEPT tcp -- anywhere 172.17.0.2 tcp dpt:http Chain DOCKER-ISOLATION (1 references) target prot opt source destination RETURN all -- anywhere anywhere ps -ef | grep discourse d2dadmin 14687 14608 0 15:35 ? 00:00:04 sidekiq 4.2.4 discourse [0 of 5 busy] message+ 14953 14591 0 15:35 ? 00:00:00 postgres: 9.5/main: discourse discourse [local] idle message+ 15065 14591 0 15:35 ? 00:00:00 postgres: 9.5/main: discourse discourse [local] idle message+ 15146 14591 0 15:35 ? 00:00:00 postgres: 9.5/main: discourse discourse [local] idle message+ 15171 14591 0 15:35 ? 00:00:00 postgres: 9.5/main: discourse discourse [local] idle message+ 16879 14591 0 15:49 ? 00:00:00 postgres: 9.5/main: discourse discourse [local] idle ps -ef | grep docker root 13013 1 0 15:33 ? 00:00:02 /usr/bin/dockerd -H fd:// root 13021 13013 0 15:33 ? 00:00:00 docker-containerd -l unix:///var/run/docker/libcontainerd/docker-containerd.sock --shim docker-containerd-shim --metrics-interval=0 --start-timeout 2m --state-dir /var/run/docker/libcontainerd/containerd --runtime docker-runc root 14509 13013 0 15:34 ? 00:00:00 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 443 -container-ip 172.17.0.2 -container-port 443 root 14518 13013 0 15:34 ? 00:00:00 /usr/bin/docker-proxy -proto tcp -host-ip 0.0.0.0 -host-port 80 -container-ip 172.17.0.2 -container-port 80 root 14524 13021 0 15:34 ? 00:00:00 docker-containerd-shim 5620389761ce36103721914d23d0d12a4b229c6c2acca30bff2695a7e6a7be2d /var/run/docker/libcontainerd/5620389761ce36103721914d23d0d12a4b229c6c2acca30bff2695a7e6a7be2d docker-runc lynx 172.17.0.2 Looking up '172.17.0.2' first Looking up 172.17.0.2 first Looking up 172.17.0.2 Making HTTP connection to 172.17.0.2 Alert!: Unable to connect to remote host. lynx: Can't access startfile http://172.17.0.2/ cat app.yml ## this is the all-in-one, standalone Discourse Docker container template ## ## After making changes to this file, you MUST rebuild ## /var/discourse/launcher rebuild app ## ## BE *VERY* CAREFUL WHEN EDITING! ## YAML FILES ARE SUPER SUPER SENSITIVE TO MISTAKES IN WHITESPACE OR ALIGNMENT! ## visit http://www.yamllint.com/ to validate this file as needed templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/web.ratelimited.template.yml" ## Uncomment these two lines if you wish to add Lets Encrypt (https) - "templates/web.ssl.template.yml" - "templates/web.letsencrypt.ssl.template.yml" ## which TCP/IP ports should this container expose? ## If you want Discourse to share a port with another webserver like Apache or nginx, ## see https://meta.discourse.org/t/17247 for details expose: - "80:80" # http - "443:443" # https params: db_default_text_search_config: "pg_catalog.english" ## Set db_shared_buffers to a max of 25% of the total memory. ## will be set automatically by bootstrap based on detected RAM, or you can override db_shared_buffers: "256MB" ## can improve sorting performance, but adds memory usage per-connection #db_work_mem: "40MB" ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed env: LANG: en_US.UTF-8 # DISCOURSE_DEFAULT_LOCALE: en ## How many concurrent web requests are supported? Depends on memory and CPU cores. ## will be set automatically by bootstrap based on detected CPUs, or you can override UNICORN_WORKERS: 4 ## TODO: The domain name this Discourse instance will respond to DISCOURSE_HOSTNAME: 192.168.2.16 ## Uncomment if you want the container to be started with the same ## hostname (-h option) as specified above (default "$hostname-$config") #DOCKER_USE_HOSTNAME: true ## TODO: List of comma delimited emails that will be made admin and developer ## on initial signup example 'user1@example.com,user2@example.com' DISCOURSE_DEVELOPER_EMAILS: 'remmedout@gmail.com' ## TODO: The SMTP mail server used to validate new accounts and send notifications DISCOURSE_SMTP_ADDRESS: smtp.gmail.com DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_USER_NAME: remmedout@gmail.com DISCOURSE_SMTP_PASSWORD: "remmedout" #DISCOURSE_SMTP_ENABLE_START_TLS: true # (optional, default true) ## If you added the Lets Encrypt template, uncomment below to get a free SSL certificate LETSENCRYPT_ACCOUNT_EMAIL: remmedout@gmail.com ## The CDN address for this Discourse instance (configured to pull) ## see https://meta.discourse.org/t/14857 for details #DISCOURSE_CDN_URL: //discourse-cdn.example.com ## The Docker container is stateless; all data is stored in /shared volumes: - volume: host: /var/discourse/shared/standalone guest: /shared - volume: host: /var/discourse/shared/standalone/log/var-log guest: /var/log ## Plugins go here ## see https://meta.discourse.org/t/19157 for details hooks: after_code: - exec: cd: $home/plugins cmd: - git clone https://github.com/discourse/docker_manager.git ## Any custom commands to run after building run: - exec: echo "Beginning of custom commands" ## If you want to set the 'From' email address for your first registration, uncomment and change: ## After getting the first signup email, re-comment the line. It only needs to run once. #- exec: rails r "SiteSetting.notification_email='info@unconfigured.discourse.org'" - exec: echo "End of custom commands"Please let me know what else I can do/provide to troubleshoot the problem.
Thanks!
Posts: 7
Participants: 2
@LilTrashPanda wrote:
As you can see, my "Max likes per day" are set to 2400. However, any time I log in and "Like" a post, I'm alerted that I only have a few left (and that's definitely not the case).
This is causing some confusion amongst my users, who don't comprehend the purpose of "limited Likes" and want the freedom to Like posts as they please -- which I agree with.
Is this specific alert something I can hide using CSS until a real fix is implemented?
Thanks!
Posts: 3
Participants: 2
@tgxworld wrote:
Continuing the discussion from The Official Discourse Slack Plugin:
Incoming Webhook
Go to the Incoming Webhooks configuration page for your Slack instance. Pick a channel, and click the big green "Add incoming webhook Integration" button. (You only need to do this once, even if you have multiple Discourse instances.)
Scroll down to Integration Settings and copy the "Webhook URL".
Go to your Discourse settings page, found at
<your-discourse-url>/admin/site_settings/category/plugins. In the slack outbound webhook url field, paste the webhook URL you copied from Slack.Select the Enable checkbox, and save all the changed settings. That's it! You're done!
Slash Commands (Optional)
By default, every new post on your Discourse will now create a Slack message in the channel you specified in step one. To change your notification defaults, go to
/admin/plugins/slackon your Discourse.
Go to
https://<your-team>.slack.com/apps/new/A0F82E8CA-slash-commandsto create a new outgoing command.Enter the name of the command (eg
/discourse) and click "Add Slash Command Integration":In the "URL" field, enter the URL that the slash command will post to:
<your-discourse-url>/slack/commandCopy your API token from the "Token" field:
Go to your Discourse settings page, found at
<your-discourse-url>/admin/site_settings/category/plugins. In the left-hand menu, scroll down and click "Plugins".In the "slack incoming webhook token" field, paste your API token:
In Slack, go to the channel you want to post notifications to, and enter the slash command you set up in step 2.
The bot will show you the options for subscribing to notifications:
Posts: 1
Participants: 1
@peternlewis wrote:
Syntax highlighting in code blocks seems to have stopped working on my site.
Using a code block with a specified language (eg "bash") like this:
echo "test"I get nice formatting here, and I have previously, but now (probably with the 1.6.6 or 1.6.7 updates), the highlighting stopped working.
Is there some new setting I need to enable? My settings look like this:
It doesn't seem to matter what language, bash, perl, applescript all do no highlighting.
Any ideas what's wrong?
Posts: 6
Participants: 3
@lsanarg wrote:
Someone knows if is possible to integrate with liquid template system? http://shopify.github.io/liquid/. Thanks in advance.
Posts: 2
Participants: 2
@adam_beers wrote:
I pulled down the DiscourseMobile from github. According to the github page, you run npm init and then react-native run-android. That didn't work, but it did indicate that npm install is needed first. I did that and it downloaded a bunch of stuff. Then, I tried importing into Android Studio and installed on my device, but it failed with an error about BundledBatch. I click on "RELOAD" on the bottom and get another error about development server.
How do I get it to work from a build?
Attached screenshots of the errors.
Posts: 5
Participants: 3
@Rana_Muhammad_Ahsan wrote:
I have implemented discourse using standard docker method, and for implementing SSL I'm following this post:https://meta.discourse.org/t/allowing-ssl-https-for-your-discourse-docker-setup/13847
I'm performing all the mentioned steps like:
-> Putting certificate and key in the right folder
-> Changing app.yml, and exposing 443 port for sslAfter doing all the changes, when I rebuild my app my SSL is not working, and my site just don't load. My SSL test result at SSL labs is also failing. Can you please help me figure out what I'm doing wrong ?
Posts: 7
Participants: 3
@junaid_pk14 wrote:
Hello,
Background:
We are using Vbulletin since 2004 and on mobile side we are using Tapatalk app. Tapatalk(tapatalk.com) also provides a app for global audience and plus for registered users, it allow to create private app with your brand and this is working well for long time.We started Discourse migration few months earlier and now it is in final stages and we need mobile apps. We have seen Discourse apps both on Apple store & Android play store? Do you provide re-brand feature or can we do our-self since Discourse has open-sourced the applications?
Can we re-brand Discourse mobile app(Android / iOS) apps and upload with our brand name on Apple & Google store with some label 'Powered by Discourse'?
Regards,
Junaid
Posts: 6
Participants: 4
@irshad_discource wrote:
I have configured my private discourse hosted in my root domain say www.mycompany.in/discuss to use only google authentication for logging in and account creation. And I have google authentication already for my root domain www.mycompany.in. Is there a way I can configure discouse to use the parent application google account ? Just to avoid multiple google account login ?
Posts: 1
Participants: 1
@Trash wrote:
It seems that we have postgresql 9.3 instead 9.5.
Removing postgresql-contrib-9.5 (9.5.5-1.pgdg16.04+1) ... update-alternatives: warning: forcing reinstallation of alternative /usr/share/postgresql/9.5/man/man1/postmaster.1.gz because link group postmaster.1.gz is broken update-alternatives: error: error creating symbolic link '/usr/share/man/man1/postmaster.1.gz.dpkg-tmp': No such file or directory dpkg: error processing package postgresql-contrib-9.5 (--remove): subprocess installed pre-removal script returned error exit status 2 dpkg: postgresql-9.5: dependency problems, but removing anyway as you requested: postgresql-contrib-9.5 depends on postgresql-9.5 (= 9.5.5-1.pgdg16.04+1). Removing postgresql-9.5 (9.5.5-1.pgdg16.04+1) ... invoke-rc.d: could not determine current runlevel invoke-rc.d: policy-rc.d denied execution of stop. Removing postgresql-client-9.5 (9.5.5-1.pgdg16.04+1) ... Processing triggers for postgresql-common (177.pgdg16.04+1) ... Building PostgreSQL dictionaries from installed myspell/hunspell packages... Removing obsolete dictionary files: Errors were encountered while processing: postgresql-contrib-9.5 FAILED -------------------- Pups::ExecError: apt-get remove -y postgresql-9.5 postgresql-client-9.5 postgresql-contrib-9.5 failed with return #<Process::Status: pid 16 exit 100> Location of failure: /pups/lib/pups/exec_command.rb:108:in `spawn' exec failed with the params "apt-get remove -y postgresql-9.5 postgresql-client-9.5 postgresql-contrib-9.5" 6608265d4e514f4433369a755976e57faee4fc16d73eb82241baed926f4dd310 FAILED TO BOOTSTRAP please scroll up and look for earlier error messages, there may be more than oneI read other topics with this error:
andSo, just to be sure, I need to build a new container with postgresql 9.5 and, after, a new fresh installation of Discourse importing my last backup?
Is this the correct way or I have something else to do before (or after)?Thanks
Posts: 1
Participants: 1
@Sebastian1 wrote:
Is there a way to change users email in the admin part without touching the code?
Posts: 2
Participants: 2
@Aman_Jagga wrote:
I have a custom Intro page for the discourse forum to tell new visitors about it benefits.I have designed a page through a plugin and is available at location like www.example/home.
I want to make this location(www.example/home) as the default landing location so that when a user hits the Url it lands directly to this location(www.example/home) but at the same time if the root location is accessed from the website itself (ex - clicking on logo that takes you to home location)the same intro page should not be shown
Any suggestions what could the best possible way to do this?
Posts: 1
Participants: 1
@pakl wrote:
If I, as the owner of my forum, want to post a topic with a cryptic title, it would be nice if discourse would let me do that without having me go and change a global setting first.
A "Yes" button, or a "I know what I'm doing" button would be nice here.
Posts: 4
Participants: 2
By default, every new post on your Discourse will now create a Slack message in the channel you specified in step one. To change your notification defaults, go to 
