Sol wrote:
and it would be great if could also put the star icon next the topics in the normal topic list view on mobile
Posts: 7
Participants: 3
Sol wrote:
and it would be great if could also put the star icon next the topics in the normal topic list view on mobile
Posts: 7
Participants: 3
Caue Rego wrote:
I understand we should probably not use discourse for this, but what if I want a new kind of "community open" ticket system? Can you picture any deal breaker issues with this?
Also, is there maybe someone else who tried to do anything similar?
Without any extensibility, this is how I envision it might work right away, for our little business:
- We'd slowly and even personally warn users of how it works. They're already used with our different thinking methodology anyway.
- Anyone would be able to comment on other people's tickets.
- You're responsible for tracking (getting updates on) your own ticket if you want.
- Staff would need to manually give the topic link for each new ticket associated with the corresponding customer, at least for new users.
Maybe a few issues, but not so terrible given the concept:
- You can't have an automated list of your own tickets in the site (as already implied, unless you bookmark / star them yourself).
- No user sensitive information must be shared on the site (not like facebook is all that much safer, if you know what I mean).
I would guess it shouldn't be too hard to extend it to make it more private and thus "covering" those issues:
- Make new topics invisible per default in a specific category.
- Let users list invisible topics to which they're assigned or simply "have read".
- Pre-assign emails to topics, so new users can have their own invisible topics list.
It wouldn't be a "community ticket system" any longer, but it'd still be a great tool IMHO.
Instead, I'm really into the whole idea of opening the tickets and see what happens!
Man am I excited about this?
There must be a huge problem I'm over seeing here...
Posts: 1
Participants: 1
Andrew Kraut wrote:
I've created a few badges now, and some have really obscure history that I'd like to link to. Is there a way to do that within the badge description? (For example, mentioning "talking chickens" and "oboes" in the same post grants the "CPA badge". New 1040)
Posts: 2
Participants: 2
Marco wrote:
I have written a (very) long topic, with many emoji.
I have tried to post it also on try.discourse.com, but it gives me the following error:Unknown error saving post, try again. Error: 502 Proxy Error ( The specified network name is no longer available. )
The post contains all of the emojis in the form:
:bowtie:
:smile:
:laughing:
:blush:
:blush:
:relaxed:
:smirk:
:heart_eyes:
:kissing_heart:
:flushed:
:relieved:
:relieved:
:grin:
:wink:
[...]
Posts: 3
Participants: 2
Ionuț Staicu wrote:
I think i just found another bug, this time on the Polls plugin. Steps to reproduce:
- Create a normal topic with a list in it and publish it
- Edit the post
- Add to the title "Poll: ", in order to make that list a poll
- Server throws a 500 error
(also replicable on meta.discourse )
Posts: 2
Participants: 2
Clay Heaton wrote:
I'm running 1.1.0.beta3.
When a user responds to an email notification (reply by email feature) and includes an
@user
notification of somebody, that is not picked up and parsed by Discourse and@user
is not notified through the forum or email.For instance, I just had a user respond to a notification (in Outlook) and the following appeared in the body of the response, as posted to the thread:
<p class="MsoListParagraph" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-indent:-.25in;mso-list:l0 level1 lfo4">· I can imagine this could be a useful feature. @username1 @username2 what do you think? <p></p>
Neither
@username1
nor@username2
was notified of the emailed response.
Posts: 10
Participants: 3
Tpokorra wrote:
This is probably related to https://meta.discourse.org/t/read-only-mode-bugs/12708.
I tried to set in the settings, Backups, allow restore. But it did not allow to save it.
Because there is no error message, I first thought something was wrong with my nginx reverse proxy, showing 405 (Method Not Allowed) errors.
It took a while until I realised that I had set the read-only mode, and that was the reason why all POST and DELETE (user logout) requests failed.It would be good if there was an error message showing that currently changing the settings or logging out is not available due to read-only mode.
Posts: 4
Participants: 3
Molly Cushing wrote:
Hey there, I'm interested in using Discourse and I have a few questions.
Are there custom user roles? I know that it integrates with WordPress (which is absolutely stellar!). I'd love to be able to have custom user roles for staff members like: editor, writer, community manager, etc. Is that possible? I believe I've seen some people have "co-founder" next to their name so I believe it is, yeah?
Can you make the default display on the forum home be the categories display, rather than the latest?
Are badges customizeable? Or are they just the star with bronze, silver, and gold coloring?
Posts: 2
Participants: 2
Adam Capriola wrote:
- > This doesn't work.
This doesn't work.
- Some text. > On the next line, it's ok.
- Some text.
On the next line, it's ok.
- A list with a space between each point. - > The arrow quoting doesn't work. - [quote]But if I surround with [quote] tags it does.[/quote]
A list with a space between each point.
The arrow quoting doesn't work.
Posts: 2
Participants: 2
Thomas Smyth wrote:
Hi everyone.
On my forum, email delivery is generally working (the test email succeeds) but I'm not getting notifications for private messages OR new user signups (even though I'm a moderator). I checked my settings and I have email_disests, email_direct, email_private_messages, and email_always are set to true. Only mailing_list_mode is false:
I've checked the email log and there is nothing relevant under 'sent' or 'skipped'.
I've noticed missing emails on this (meta) forum also. For instance, cpradio mentioned me in a post 24 days ago but I got no notification even though my settings for this forum are the same.
Not sure if these are related but the former is much more important. Thanks!
Posts: 1
Participants: 1
nx2zdk wrote:
All of this setup is on the same host.
Note that: docker0 inet address is
172.17.42.1
and data container is running as:CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 8754aa7b07cf local_discourse/data:latest "/sbin/runit" About an hour ago Up About an hour 0.0.0.0:2221->22/tcp, 0.0.0.0:5432->5432/tcp, 0.0.0.0:6379->6379/tcp data
When I try runinning this command:
psql -h 172.17.42.1 -p 5432 -U discourse discourse -W
and enter password for the password prompt, I get into postgres console without any error.
On bootstrap process, I run:
./launcher bootstrap web_only
And It failed with this error:
I, [2014-09-30T17:56:56.373972 #38] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' rake aborted! PG::Error: could not connect to server: Connection refused Is the server running on host "172.17.42.1" and accepting TCP/IP connections on port 5432?
That looks like the app cannot connect to postgresql server on the data container (which is already bootstrapped and started and I was able to connect via
psql
)my web_only.yml looks like this (excepts the credential, domain name and email):
templates: - "templates/sshd.template.yml" - "templates/web.template.yml" expose: - "80:80" - "2222:22" params: ## Which Git revision should this container use? (default: tests-passed) #version: tests-passed env: LANG: en_US.UTF-8 ## TODO: How many concurrent web requests are supported? ## With 2GB we recommend 3-4 workers, with 1GB only 2 #UNICORN_WORKERS: 3 ## TODO: configure connectivity to the databases DISCOURSE_DB_SOCKET: '' DISCOURSE_DB_USER: discourse DISCOURSE_DB_PASSWORD: mypassword DISCOURSE_DB_HOST: 172.17.42.1 DISCOURSE_DB_NAME: discourse DISCOURSE_REDIS_HOST: 172.17.42.1 ## ## 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: 'MYEMAIL' ## ## TODO: The domain name this Discourse instance will respond to DISCOURSE_HOSTNAME: 'discuss.MYDOMAIN' ## ## TODO: The mailserver this Discourse instance will use DISCOURSE_SMTP_ADDRESS: smtp.mandrillapp.com # (mandatory) DISCOURSE_SMTP_PORT: 587 DISCOURSE_SMTP_USER_NAME: MYEMAIL DISCOURSE_SMTP_PASSWORD: APIKEY ## ## The CDN address for this Discourse instance (configured to pull) #DISCOURSE_CDN_URL: //discourse-cdn.example.com volumes: - volume: host: /var/discourse/shared/web-only guest: /shared - volume: host: /var/discourse/shared/web-only/log/var-log guest: /var/log ## The docker manager plugin allows you to one-click upgrade Discouse ## http://discourse.example.com/admin/docker hooks: after_code: - exec: cd: $home/plugins cmd: - mkdir -p plugins - git clone https://github.com/discourse/docker_manager.git ## Remember, this is YAML syntax - you can only have one block with a name run: - exec: echo "Beginning of custom commands" ## If you want to configure password login for root, uncomment and change: - exec: apt-get -y install whois # for mkpasswd ## Use only one of the following lines: #- exec: /usr/sbin/usermod -p 'PASSWORD_HASH' root - exec: /usr/sbin/usermod -p "$(mkpasswd -m sha-256 'MYPASSWORD')" root ## If you want to authorized additional users, uncomment and change: #- exec: ssh-import-id username #- exec: ssh-import-id anotherusername - exec: echo "End of custom commands" - exec: awk -F\# '{print $1;}' ~/.ssh/authorized_keys | awk 'BEGIN { print "Authorized SSH keys for this container:"; } NF>=2 {print $NF;}'
and data.yml
templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/sshd.template.yml" expose: - "5432:5432" - "6379:6379" - "2221:22" params: db_default_text_search_config: "pg_catalog.english" ## Set db_shared_buffers to 1/3 of the memory you wish to allocate to postgres ## on 1GB install set to 128MB on a 4GB instance you may raise to 1GB #db_shared_buffers: "256MB" env: # ensure locale exists in container, you may need to install it LANG: en_US.UTF-8 volumes: - volume: host: /var/discourse/shared/data guest: /shared - volume: host: /var/discourse/shared/data/log/var-log guest: /var/log # TODO: SOME_SECRET to a password for the discourse user hooks: after_postgres: - exec: stdin: | alter user discourse with password 'MYPASSWORD'; cmd: su - postgres -c 'psql discourse' raise_on_fail: false
Any idea what could cause this error or anything missing to config?
Posts: 5
Participants: 2
James Milligan wrote:
I note that this was in a recent commit, so it's more than likely that this has just not been finished, rather than a bug.
On latest pull from the repo, I added a user field via Customise, a standard text field with "Membership Number" in, and set it to "not editable" after signup.
Going to the signup page shows the usual form (username/password etc), but no box for a field. Trying to register fails, see screenshot below.
The field also doesn't show on a user's profile at all, although when set to be editable, is so via preferences.
Posts: 5
Participants: 3
Lars Christian wrote:
Hi,
New to the forum here, so hello everyone, pleased to meet you all!
I've just installed Discourse for a new project I'm working on, and I've managed to bridge the gap between by installing the WP-Discourse plugin. So far, so good. I do have a question about the settings for pulling notable replies though.
One condition is "minimum number of replies" - Does this mean direct replies to that specific post, or does it mean subsequent replies in the topic? It doesn't seem to specified anywhere.
Thanks in advance.
Posts: 1
Participants: 1
flexihack wrote:
I recently featured Discourse on one of my blog post about modern forum software. If you want to check it out, it's available on TinyWebDev site.
Please let me know if I need to fix anything or add anything related to Discourse. Greatly appreciate it.
Posts: 7
Participants: 7
Sam Saffron wrote:
markdown bug, you can't talk about code
`
test
`
``` [code]test[/code] ```
Posts: 1
Participants: 1
Pratik Vyas wrote:
I realy want to minimize attachment uploads. I read somewhere that the "max attachment size" value applies to profile pictures as well and so, have set it to 20.
However, I find users attaching pictures ~84K large.
Would it make sense if I plugged in some JS to remove the file input box in the attachment modal?
Posts: 2
Participants: 1
JJ wrote:
I already have my discourse site on DigitalOcean. (Paid to install. )
But I am trying to install on my country's VPS service. (DigitalOcean is pretty much slow in my country)So I just bought new VPS, and I believe hardware requirements for Discourse are OK.
But I am not sure about Software Requirements: Postgres 9.1+, Redis 2.6+, Ruby 1.9.3+.
(I have no idea about Docker because I am not a programmer. I knows only basics about HTML, PHP, JS...)The questions is... "Installing Discourse with Docker" means:
- I don't have to install Postgres, Redis, and Ruby things (Docker will cover all the software required.)
- I should install Postgres, Redis, and Ruby first, then install Discourse with Docker.
So newbie's question, help me please.
Posts: 5
Participants: 2
The long version of me wrote:
Running latest docker installation on digital ocean. I had to change mail setup in app.yml after the change I ran:
./launcher rebuild app
The error received:
(<unknown>): found a tab character that violate intendation while scanning a plain scalar at line 67 column 13 -e LANG=en_US.UTF-8 YAML syntax error. Please check your /var/docker/containers/*.yml config files.
The site went down and it was easily fixed with:
./launcher start app
but my app.yml was not updated with new mail configuration. I have manually changed/translated some strings in serveren.yml and I am assuming this was the main problem for this error.
Posts: 4
Participants: 2
DanaRelayr wrote:
Hello,
We're using the discourse forum and we have had constant complaints from users registering to our forum and not receiving their activation emails. We are forced to manually activate them from our Admin panel. What should we check? we do not host the forum ourselves.
Thanks
Posts: 4
Participants: 3
Nate Finch wrote:
I wrote a blog post about how to use Juju to deploy Discourse:
http://npf.io/2014/10/deploy-discourse-juju/
The nice thing is that the Juju charm install exactly follows the steps in the Digital Ocean install guide, so you're not setting up some frankenstein environment that the Discourse folks won't know what to do with. But at the same time, it takes a lot of the trial and error out of the process (figuring out how to script the install and exactly what needed to be installed when took me the better part of a week, albeit only 1-2 hours a day). Also, since it removes a lot of the manual steps of the install guide, it only takes about 8 minutes, and most of that is just waiting for discourse to come up.
Give it a try and feel free to leave comments here or on the blog post if you have any problems.
Posts: 1
Participants: 1