The complexities of tracking email opens have been discussed before, and the general consensus has been it’s a bad idea to try. However, a number of our users have said that they’d find a per-user preference along the lines of “mark post as read when emailed” very useful, as it’s reasonable to assume that if they’ve been emailed it, then they’ve opened it.
As it turns out, this isn’t an original idea. @mcwumbly suggested the same thing over a year ago:
I think it’d be best default off, so as to not change users’ current expectations - but we could always add a preference to set the global default.
Would this be welcome in core, or does it belong in a plugin?
It seems that Discourse has started “automatically” converting “dumb” quotes into smart quotes in topic text (not just titles) (maybe in 1.9.5 or 1.9.6?).
My users have complained about this feature, but I don’t see any way to turn it off.
Is there a preference somewhere for it? I can’t see anything in my profile settings. In the site settings, I have the option:
Figure 1 is a test of my ruby script, it can send and receive mail
Figure 2 shows my Discourse app.yml email configuration, which is exactly the same as the test script configuration in Figure 1, but it doesn’t work. Why?
Hello, I’ve been using Discourse as our official forum for my game. And it’s been a great pleasure to use such a sophisticated platform as our forum.
And while using it in Korean, I encountered a tiny problem:
This bug occurs when I try to tag Korean words. As you can see in the picture above, when I try to add a Korean word as a tag, the cursor stays at the start of the textbox.
As for the version I am using, it’s v2.0.0.beta7 +14.
Please feel free to ask for further details if you need any.
I’ve noticed today that Transifex has an ‘proofread’ step added to the translate->review process.
Is this deliberate? Because currently for French, I do most of the reviewing of my own translations, so this won’t be adding more eye-balls, just more donkey work.
tl;dr below: Basically the with files compression vastly exceeds what’s practical to transfer onto the new hosting service so I’m curious if there’s even an option to transfer to S3.
I’ve been trying to do a migration via Backup (if there’s a better way to do it, please tell me) and run into an issue where I uploaded the backup file (22.3 gig) and then attempted to restore.
This has resulted in the system claiming there is no space on the 75 gig allocated and left me quite confused since most of this space seems to be need to make… another copy of the backup file before unzipping it?
What’s the best process for restoring this devoured space (Ubuntu 16.04) and are there any extra steps I should take with doing a restore for a backup file this size?
Alternatively, is there a way to migrate all the uploaded files to S3 when you’re using DiscourseHosting and then I’ll do a database transfer and rebake? (Unless that has problems I’m not aware of)
Edit: Okay, manually went in - killed and removed the docker container then rebuilt and now I seem to have the ~43 gig back… reattempting restoration… okay, found the core problem… compression was WAY more effective than anticipated.
Have an item waiting for approval in approval queue
Click on Delete User
Confirm to really delete and block email/IP
Come back with Server Error dialog
The item is actually successfully removed from the queue, but it still shows in the queue list (unless refreshed). Therefore, the error is most likely on the UI side that tries to remove the item from the list.
This issue was already reported a while ago but it seems no solution was found:
I noticed this for the badge “regular” (trust level 3). In Badges this is translated to the german badge “Stammgast”:
/admin/badges/3
So I also checked the value mentioned by @tgxworld /admin/customize/site_texts/badges.regular.name and it is set to “Stammgast”.
If I set the title in my profile it is also correct translated:
Then I save the setting and it is shown correctly:
But in my posts it is shown as “Regular”:
And when I load my settings again it also shows Regular:
So I’m migrating my Discourse instance to another server. According to Move your Discourse Instance to a Different Server, I created a backup and downloaded to my computer. Then I have a fresh installation on the new server. But when I try to restore, bad things happen:
[2018-04-27 11:32:32] 'vencent' has started the restore!
[2018-04-27 11:32:32] Marking restore as running...
[2018-04-27 11:32:32] Making sure /var/www/discourse/tmp/restores/default/2018-04-27-113232 exists...
[2018-04-27 11:32:32] Copying archive to tmp directory...
[2018-04-27 11:32:32] Unzipping archive, this may take a while...
[2018-04-27 11:32:33] No metadata file to extract.
[2018-04-27 11:32:33] Validating metadata...
[2018-04-27 11:32:33] Current version: 20180308071922
[2018-04-27 11:32:33] Restored version: 20171228122834
[2018-04-27 11:32:33] Extracting dump file...
[2018-04-27 11:32:33] Cannot restore into different schema, restoring in-place
[2018-04-27 11:32:33] Enabling readonly mode...
[2018-04-27 11:32:33] Pausing sidekiq...
[2018-04-27 11:32:33] Waiting for sidekiq to finish running jobs...
[2018-04-27 11:32:34] Restoring dump file... (can be quite long)
Then it gets stuck at the last line and never show anything new for like 20 minutes. But my site is so small that it wouldn’t take so long like this. Also, there is nothing new in /var/discourse/shared/standalone/log/var-log/postgres/current after a few minutes. I guess the restoring process seems broken… I tried again with no success. Is there any way to solve this problem?
FYI, the version of my old instance is 1.9.3 if I’m remembering clearly.
How to upload files to my sites root directory (https://example.com/file.txt), I’m trying to have loader.io config in the Root directory, i used ./launcher enter app and kept my file in public directory however after updating my instance it is gone.
I’d like to disable logging for my Discourse instance for several reasons:
#gdpr paranoia - I do not want to be collecting and storing anything that’s surplus to requirements - especially where IP addresses are concerned* - anonymous users have not given me permission to collect their IPs. I don’t want to risk breaking this draconian and poorly-defined new law
Performance - logging all request to disk is unnecessarily hammering my SSD, and probably incurs a small performance penalty when a page and all its assets are requested by the client
I don’t need the logs
What’s the easiest and most bullet-proof way of disabling:
nginx logging for my instance, please?
IP addresses in any other logs (e.g. rails logs) where anonymous users are concerned?
*yes, I know that the internal nginx instance may only see the 172.17.0.1 Docker interface IP. EU legislators are unlikely to understand or care about this technical detail. They’ll just see “IP address,” which is on their list of “personally identifying information”
This component includes a theme setting that allows you to add as many links as you want, determine their icons, and decide which devices they show up on!
Google advises using SendGrid, Mailgun, or Mailjet. However, since I didn’t see any Mailgun plugin for Discourse (two repo on GitHub indeed, but one hasn’t been updated since 2015, and the other even breaks the rebuild of Discourse), I formerly use SMTP to send emails via Mailgun, but this way has been blocked by Google. So my site’s email system is totally breaking down.
️ as well?
