@elliem wrote:
I have a fresh Discourse installed on DigitalOcean (followed ssh instructions)
After creating 5 users, and visiting /users page it always "No results were found."
What could be wrong? This happens for both logged in and logged out users. Also settings box is ticked to show users list.
Posts: 4
Participants: 3
@capitanroy wrote:
I just set up a new discourse instance for our forum at foro.makersofmurcia.org.
I've been having a lot of issues this time, but the main one left now is email deliverability:
The activation emails sometimes go out, sometimes they leave late, sometimes they don't all together.
The invite emails (nothing serious, about 20 addresses put in one by one) don't seem to go out either.
But when I test email deliverability at admin -> email -> adjustments, it flies through and get delivered in a few seconds.Any idea what this can be caused by?
Posts: 1
Participants: 1
@Callahan wrote:
Howdy, I have a question regarding permissions. We had a staff rank on our old forums that had all the abilities of trust level 4 + banning (without seeing ips) which worked perfectly for us for privacy reasons. However, moving over to discourse we can't seem to find a rank that does that. Trust level 4 can't ban and moderator can see IPs, so like am I missing something? or is that all there is in terms of permissions?
Posts: 2
Participants: 2
@bangarang wrote:
I want to use Prosody as my xmpp-server in conjunction with Discourse. Users should be able to login to Prosody with their Discourse login within their desired xmpp-client, which will primarily be Conversations. For web-based clients like Converse.js or Candychat i could implement the discourse SSO feature. But for non-web apps, like Conversations or Gajim, are their any other solutions out there, especially when Discourse and Prosody runnning on the same server?
The only solution i found so far, is to write a Prosody authentication module in Lua that simulates a browser request, which was suggested here:
Is there something similar in Lua out there which i could use to start with or other approaches to solve this request?
Posts: 1
Participants: 1
@JimmyX wrote:
Where plugins use engines are these created in the regular rails way using something like
rails plugin new myplugin --mountablein the discourse root directory?I have git cloned "discourse-links-category" to see what other people do. Within that plugin I don't find config/routes.rb. Instead it seems to do the same job with code in plugin.rb.
Do I simply add this engine code into plugin.rb (adjusted for what I want) ?
I use develop using vagrant.
Posts: 1
Participants: 1
@meglio wrote:
The search by Email Type is confusing when used in non-English.
While search is done with using English keywords (
digest,mailing_listetc), these words make no sense for one who does not understand English. So, as proposed in a placeholder text, they might type translated keywords instead, but it won't work (e.g.дайджест).Proposal
- Use a dropdown box with translated versions of the possible terms/keywords
- Display translated terms in the column cells, not the original English keywords themselves
- Still run Search with using English keywords, so that it always works no matter in which language the UX is.
Posts: 1
Participants: 1
@helperhaps wrote:
How does this line work? I can not find where the method defined or how the function defined.
I mean if i want to add a top-menu, how does it works?
Posts: 2
Participants: 2
@ewanyork wrote:
Hello,
We'd like to put links to telephone numbers in Discourse posts, using the href="tel:xxxx-xxxx-xxx" protocol. I've tried doing so using raw HTML anchor links and with Markdown, but Discourse always removes the href attribute totally and leaves us just with a plain anchor link without a target.
Is there any way I can achieve this? I can't find a setting to change, so am wondering if it's possible to escape the string in some way to prevent Discourse parsing and removing this? Since Discourse works so nicely on mobile, it seems a shame to completely prohibit tel: links.
Thanks in advance.
Posts: 5
Participants: 3
@tgxworld wrote:
I started to notice in the post preview that mentions are being parsed over and over again. We used to have a cache for it such that mentions that have already been found will be ignored.
Posts: 5
Participants: 4
@PaulMw wrote:
Hi, I've setup an rss feed to auto-post for embedded comments on our website, but although a category has been selected for it to post into, it's posting without a category.
I can't see any reason for it not to post into the right place, so I'm thinking this may be a bug?
Posts: 1
Participants: 1
@Nicholas_Tolstoshev wrote:
I'm using Survey Gizmo for our survey platform, and I'm looking to pass back the userid and/or the email address from Discourse to Survey Gizmo, so that I can correlate data across our userbase. Survey Gizmo can take a variable at the end of the URL using the format ?variable=foo - has anyone gotten a plugin or code working to do such a pass back?
Posts: 1
Participants: 1
@mntbighker wrote:
We are wondering if we can limit logins only to the gitlab omniauth plugin for everyone but the Admin. Or to a group we define.
On version v1.7.0.beta6 +13
Posts: 1
Participants: 1
@pfaffman wrote:
To reproduce:
[filename.png)](https://example.com/stupid(66)filename.png)Of course, a better solution might be to include just the raw image link on a line by itself. I may just need to deal with image links more elegantly. . .
Posts: 5
Participants: 2
@HAWK wrote:
Has anyone customised their About page?
I have a client that wants to add a lot of additional information into the top of their about page (essentially into the Site Description area at the top of their equivalent of this page)
How much flexibility is there? I can't seem to find that section to edit in /admin/customize/site_texts
Posts: 4
Participants: 2
@meglio wrote:
My server tells me:
New release '16.04.1 LTS' available.
Run 'do-release-upgrade' to upgrade to it.Should it be safe to:
- Turn off the server.
- Make a droplet backup while offline (DigitalOcean).
- Run
do-release-upgradeAny things to pay attention to?
Posts: 5
Participants: 4
@CT075 wrote:
A user recently reported to me that they were unable to receive a password reset email. Via impersonation, I have verified this from both a testing account and the user's actual account. Furthermore, it seems that creating a new account also doesn't send out an email. I'm not entirely sure how to go about debugging this, especially as the test email goes through completely fine. The on-site logs don't show any bounces or failures, but the emails are verifiably not being received.
We're using the recommended install on Digital Ocean, but I don't know what configuration details would be relevant. I can give any details that might be necessary. Thanks!
Posts: 6
Participants: 4
@ewanly wrote:
I wanted to do backup to my Discourse site, but I've got the following backup log;
[2016-10-31 22:53:43] 'Sam' has started the backup! [2016-10-31 22:53:43] Marking backup as running... [2016-10-31 22:53:43] Making sure '/var/www/discourse/tmp/backups/default/2016-10-31-225343' exists... [2016-10-31 22:53:43] Making sure '/var/www/discourse/public/backups/default' exists... [2016-10-31 22:53:43] Enabling readonly mode... [2016-10-31 22:53:43] Pausing sidekiq... [2016-10-31 22:53:43] Waiting for sidekiq to finish running jobs... [2016-10-31 22:53:43] Backup process was cancelled! [2016-10-31 22:53:43] Notifying 'Sam' of the end of the backup...After that, I wasn't able to access the site anymore. So I tried to make rebuild, rebuild started but after of 3-4 lines of output its stuck for long.
So I did powered off/on my droplet and did a rebuild successfully. But again when I'm trying to backup I'm getting the same error log.
This time I was able to stop the process by clicking cancel. The site is running without any other noticeable error. But no backup. (My disk have over 32GB space)
Any body facing this? What could be the solution please?
Posts: 2
Participants: 2
@lightweight wrote:
I'm hoping someone here will have the necessary insight/Discourse debugging fu to help me work out why my SSO efforts are failing...
The story so far: I have a Discourse instance (v1.7.0.beta6), running in a Docker container on Ubuntu Linux 14.04, serving via an HTTPS-configured nginx reverse proxy. I described the configuration previously. The HTTPS is provided by Let's Encrypt certs. It has been running without issue for months now, using
templates/web.template.ymlandtemplates/web.ratelimited.template.yml- so between the nginx reverse proxy on the VM and the Docker container, traffic is going by HTTP, not HTTPS. All external traffic is automatically redirected to external port 443.Now, I want to allow users to authenticate via an OAuth2 server provided by a multi-site WordPress instance I'm running on the same VM (not sure if this is relevant). It's got the WP OAuth Server (full version, not gratis one). I've set up the client for my Discourse instance, and have configured all the URLs in both the WP Server's config, i.e. the callback URL, and the various authorisation, token, and user URLs to be HTTPS. I also installed and rebuilt my Discourse instance with the
https://github.com/discourse/discourse-oauth2-basic.gitplugin.Initially the OAuth process was failing at the callback URL from Discourse, with an error related to "OpenURI::HTTPError (400 Bad Request) /usr/local/lib/ruby/2.3.0/open-uri.rb:359:in `open_http'" via the logs... it seems as though perhaps it's attempting to do the HTTPS via HTTP.
So I've now tweaked my nginx reverse proxy configuration to include
location @discourse2 { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto https; proxy_set_header Host $host; proxy_set_header X-Forwarded-Host $host:443; proxy_set_header X-Forwarded-Port 443; proxy_redirect off; add_header Front-End-Https on; proxy_pass https://discourse2;}
and this (discourse2 is the 2nd instance of Discourse running on this VM):upstream discourse2 { server 127.0.0.1:8443 fail_timeout=5; }and added the
templates/web.ssl.template.ymlto my app.yml, put copies of my Let's Encrypt certs into the shared/ssl/ dir, configured new ports in apps.yml file- "127.0.0.1:8443:443"and and ran./launcher rebuild app... The site, amazingly, works with this new configuration, and, with turning onforce_httpsin Discourse's security settings everything should be SSL end-to-end if I'm not mistaken...And yet, I still can't seem to get OAuth2 to work. I continue to get the open_http error, but am unable to work out what is going wrong. I note that the accompanying Request URI (from the logs) shows not just a single path, e.g.
/auth/oauth2_basic/callback?code=aw1tb7i0n8zekhrh3i9ldhnzzbhdwzak4arw5dzz&state=d514fc06d5e5a32e1b8cc9c327f88571ff3a2ba83e6836c0but a whole long list of them, presumably from prior test authorisation attempts, separated by commas. I include the one above, as it's expired and doesn't work in any case...This look familiar to anyone? Is there a way to get this to work without enabling SSL in the Docker containers? For the record, I've read up on the thread where people are encountering roughly similar problems with Google's OAuth2 service... but no major insights... Any thoughts gratefully accepted!
Posts: 1
Participants: 1
@leo.proctor wrote:
Hi,
I'm working on a plugin that deals with custom fields on Topic. I've added custom fields as recommended, by using TopicCustomField. I've also added custom text fields in form/composer via connector partials. Now I want to submit these text fields to update the topic custom fields. What is recommended way of doing it? Is there any guidelines/tutorial or any doc that i can follow? Or any help?
Thanks
Posts: 2
Participants: 2
