@sdomino wrote:

DISCLAIMER:
Unsupported installs of Discourse are highly discouraged. If you feel like you must proceed please understand that the Discourse team cannot, and should not, provide support for this installation. If you have any questions please DO NOT direct them to the Discourse team. Instead, you can join us on Slack for help.

If you wish to continue, here is the guide that outlines how to install and run Discourse with Nanobox.

Posts: 5

Participants: 3

Read full topic

@reg.dan wrote:

And nothing shows up in the logs. What steps do I take to diagnose the issue? Thanks!

Posts: 6

Participants: 5

Read full topic

@gooddadmike wrote:

Y’all have that? I can link to the features page, but people are lazy, right?

Posts: 3

Participants: 3

Read full topic

@Candido_Cleyton wrote:

Hello Sirs,

I do not know if this area is suitable for such a question, I apologize if I am wrong, I speak little English.

But I wanted help from you if possible, I created a plugin and I can activate and deactivate it, but it does not do anything yet, I’m crawling because my focus is more JAVA, Ruby on Rails I do not understand anything, following, I would like this plugin to block Certain groups do download attachments, how can I do this in the plugin?

Posts: 1

Participants: 1

Read full topic

@tophee wrote:

If new users do the discobot tutorial, one of the most important things they learn is oneboxing. Unfortunately, few users actually embark on that journey and so I am often editing user posts to turn their links into oneboxes.

I’m assuming that I’m not alone with this and so I’m curious to hear how others are dealing with this. I have this idea of adding some hint to the editor modal for links, but won’t be able to test this before I’m back to my desktop computer next month. Adding an education message could be another option (it could show whenever a user who has never posted a onebox adds a uri to a post).

But maybe people have come up with less technical solutions?

Posts: 3

Participants: 3

Read full topic

@jomaxro wrote:

When allow uncategorized topics is disabled, I’d like to propose requiring the user to select a category before they are allowed to start writing the body of the post.

The use case for this is a site that makes significant use of topic templates. As users are not required to select a category, many go right to writing their post, and only select a category after they’ve written their post. As there is content in the composer, the topic template is not added, thus negating the usefulness of the template.

Posts: 2

Participants: 2

Read full topic

@Peter_Salzmann wrote:

Hi everyone,

When I perform a full backup and download the file is this good enough to do a full restore if I re-installed Discourse and did a re-import on a fresh discourse?

It’s upgrade time and as our community grows I feel uneasy about command line upgrades. If this goes down for any reason and doesn’t come back up I’m not informed well enough to tackle that straight on. I’d rather know that a full restore is possible therefore I’d make a big effort to backup the DB before any major upgrade is performed so I’m in a position to restore and continue business as usual in the event I had to re-install due to my instance not coming back.

Thanks in advance for any tips you can share to deal with this situation.

Posts: 3

Participants: 2

Read full topic

@alexweissman wrote:

I’ve set up a webhook with only the Topic Event and Post Event options checked - in other words, I only want to receive data when a topic is created/updated/replied-to.

Unfortunately, it seems that new user registration is triggering a “topic” event, so that I receive a message from discobot whenever someone signs up. The relevant headers are:

X-Discourse-Instance: http://forums.userfrosting.com
X-Discourse-Event-Id: 27
X-Discourse-Event-Type: topic
X-Discourse-Event: topic_created

and the payload starts with:

{
  "topic": {
    "id": 30,
    "title": "🤖 Greetings!",
    "fancy_title": ":robot: Greetings!",
    "posts_count": 1,
    "created_at": "2017-07-15T04:29:01.550Z",
    "views": 0,
    "reply_count": 0,
    "participant_count": 1,
    "like_count": 0,
    "last_posted_at": "2017-07-15T04:29:01.641Z",
    "visible": true,
    "closed": false,
    "archived": false,
    "has_summary": false,
    "archetype": "private_message",
    "slug": "greetings",
    "category_id": null,
    "word_count": 110,
    "deleted_at": null,
    "pending_posts_count": 0,
    "user_id": -2,
    "pm_with_non_human_user": true,
    "draft": null,
    "draft_key": "topic_30",
    "draft_sequence": 0,
    "unpinned": null,
    "pinned_globally": false,
    "pinned": false,
    "pinned_at": null,
    "pinned_until": null,
    "details": {
      "created_by": {
        "id": -2,
        "username": "discobot",
        "avatar_template": "/user_avatar/forums.userfrosting.com/discobot/{size}/1_1.png"
      },
   ...

It appears that discobot sends a PM to the new user upon registration. However, I find it counterintuitive for a PM to be considered a “topic” event.

Posts: 3

Participants: 2

Read full topic

@He-Man wrote:

I was going through discourse code, and comparing it with standard emberjs projects.

Discourse uses version 2.13 of emberjs.

The emberjs directory structure includes node_modules folder.

But the front end part of discourse project does not have any node_modules folder. So discourse does not use any module from npm?

Posts: 5

Participants: 4

Read full topic

@Ham wrote:

Hi. Im trying to rebuild my app and get the following error:’

root@discourse-2gb-nyc3-01:/var/discourse# ./launcher rebuild app
Ensuring launcher is up to date
Fetching origin
remote: Counting objects: 77, done.
remote: Compressing objects: 100% (8/8), done.
remote: Total 77 (delta 50), reused 56 (delta 49), pack-reused 20
Unpacking objects: 100% (77/77), done.
From https://github.com/discourse/discourse_docker
378d927..42504d3 master -> origin/master
+ f38ec69...583394d check-free-space -> origin/check-free-space (forced update)
* [new branch] fix-hsts -> origin/fix-hsts
* [new branch] revert-358-no-env-in-bootstrapped-image -> origin/revert-358-no-env-in-bootstrapped-image
Updating Launcher
Updating 378d927..42504d3
Fast-forward
image/auto_build.rb | 7 ++++---
image/base/Dockerfile | 9 +++++++--
image/base/install-imagemagick | 2 +-
image/base/install-pngquant | 7 ++-----
image/discourse_test/Dockerfile | 3 ++-
launcher | 16 ++++++++++++++++
samples/mail-receiver.yml | 2 +-
templates/web.letsencrypt.ssl.template.yml | 2 +-
templates/web.ssl.template.yml | 6 ++++++
9 files changed, 40 insertions(+), 14 deletions(-)
flag provided but not defined: --format
See '/usr/bin/docker info --help'.
You have less than 5GB of free space on the disk. You will need more space to continue

Would you like to attempt to recover space by cleaning docker images and containers in the system?(y/N)y
docker: 'system' is not a docker command.
See 'docker --help'.
If the cleanup was successful, you may try again now
root@discourse-2gb-nyc3-01:/var/discourse# ./launcher rebuild app
flag provided but not defined: --format
See '/usr/bin/docker info --help'.
You have less than 5GB of free space on the disk. You will need more space to continue

I contacted digital ocean who told me to run this command to see which are the large files on the account.
sudo find / -xdev -type f -size +100M

This gave me this output but I have no clue what anything is and digital ocean says they dont know either and to ask somewhere else.

root@discourse-2gb-nyc3-01:~# sudo find / -xdev -type f -size +100M
/var/lib/docker/aufs/diff/780a8273c9c35d1578ad2e9c37740643ffcc5f9a0a02ed13bd6ad3 6b1d30337e/var/www/discourse/.git/objects/pack/pack-786c3e3931ecb9c41964039462a2 ac21ab04f903.pack
/var/lib/docker/aufs/diff/62de8bb092bdbcfa1c2e276e651597f75b50e9be9fe840a49a8887 5f92d49a4e/var/www/discourse/.git/objects/pack/pack-ad1b9e467013bbde4c943b686ed0 f752aa11e241.pack
/var/lib/docker/aufs/diff/dcdadb45247a230b98d2cbf2f3919ba115c9c5be7dcbb2293b3197 94e9b898c6/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/906c19aa33de1990eae5c0ddcc8f184bffc18e2e26e3a81eb49c0e 37093d3fd0/var/www/discourse/.git/objects/pack/pack-1453eeeb2c0970e6769a7119d737 ec109d8f65cc.pack
/var/lib/docker/aufs/diff/4da38e43cac022d21a8193d829feaa5a46b41209aef340457376d3 03cf962a41/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/75408591168a8d1c7a0dd320dc6ef93ee292d139cba2a62bc5a66e e39de424cd/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/54bd77881e9857e50409c7f962f17f31207d2ced252739efb7ef17 44606850f0/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/fb7cfba393923d5768ec852510705c213877668d90cfa850dd697c d860ae4a32/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/57d799d4c06bbe4e44278bbf1b371037f4fe16047fc7e56c6f414e e0c177ece8/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/ad60b1035f646e9a125f0872ec6d96c7a57a3e104bd8eaa9201545 4c26553691/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/4482660ffadd10299985867a04e84fcdc019b8ef6e9b227f349e4e 000ed67841/var/www/discourse/.git/objects/pack/pack-1453eeeb2c0970e6769a7119d737 ec109d8f65cc.pack
/var/lib/docker/aufs/diff/a75cd7f5028f5c7bd862ed87430136d185fa4d289d902433e93bda beed6a7e54/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/d2c00d454df1d07656601d711d82471f5e5e55db10299d60dad6ba 751f468fab/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/ff74c46bd207d5715d1647c80ebf7233d4fbc8ea54d81b25d43eb8 d85de6de77/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/d2baf46996b2c0aa41294c6c6908c76e4edbecf438b1078976557d 18d18f2577/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/110963d247e29eb5a9ee8118490203d6eaea66cdee92e88b1f04ce 87d691bb16/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/6a2c56759c30fed3a6063c40520625894a2ebc2fe535eaadbe419d 966b091c14/var/www/discourse/.git/objects/pack/pack-ad1b9e467013bbde4c943b686ed0 f752aa11e241.pack
/var/lib/docker/aufs/diff/96307463bdcd7e7af65ae5ac730ba79888155fc41c6bf7d7029ab7 d53ca311c2/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/56ae0770f9955c51d01677c35f4a6f9e61f417dce2ba553b20f355 e63b2ee48b/var/www/discourse/.git/objects/pack/pack-1453eeeb2c0970e6769a7119d737 ec109d8f65cc.pack
/var/lib/docker/aufs/diff/150185fc8bdf50199dd159d9a3cee8c21fd14ef64878325f7ec486 f07ef89234/var/www/discourse/.git/objects/pack/pack-1453eeeb2c0970e6769a7119d737 ec109d8f65cc.pack
/var/lib/docker/aufs/diff/9c706298412117f289d50fac1f82afd7303e81c610bbbaeb64d921 080300d481/var/www/discourse/.git/objects/pack/pack-1453eeeb2c0970e6769a7119d737 ec109d8f65cc.pack
/var/lib/docker/aufs/diff/85f1f1d75570be4c2dca04507ad477a9784e26a7c26ecc0f506b48 5976565491/var/www/discourse/.git/objects/pack/pack-1453eeeb2c0970e6769a7119d737 ec109d8f65cc.pack
/var/lib/docker/aufs/diff/630f9ed1999332022afeceb41c3dc21d811bf6f09888fec5cedbe1 e652c817a6/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd0 12f1a8290078.pack
/var/lib/docker/aufs/diff/bd17a418c6c37e527b2f48469b0e274d2a633a78d388ced04f79e5d28b97a6f6/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd012f1a8290078.pack
/var/lib/docker/aufs/diff/190bad8da2f168ae9ca604f21374dbd9e182998635cce33e1464e065f1c561ce/var/www/discourse/.git/objects/pack/pack-1453eeeb2c0970e6769a7119d737ec109d8f65cc.pack
/var/lib/docker/aufs/diff/4257a4c8045a218a00b60a0d76398f28e122612f08289de805e08c8d903ff213/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd012f1a8290078.pack
/var/lib/docker/aufs/diff/3c2b2dffcfa267c0e6bcc5d7016b68efff7a5f0a017c51213a748d5b40d0feb8/var/www/discourse/.git/objects/pack/pack-1453eeeb2c0970e6769a7119d737ec109d8f65cc.pack
/var/lib/docker/aufs/diff/c6e55b7b8bd3b3cab54010998dd910ef6937fb5686d2f220ea7a7a3cd1c4891f/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd012f1a8290078.pack
/var/lib/docker/aufs/diff/6ea0c94616f38471a0f63b06612602578755a0c04e8f8dbb718d667cc3d86145/var/www/discourse/.git/objects/pack/pack-1453eeeb2c0970e6769a7119d737ec109d8f65cc.pack
/var/lib/docker/aufs/diff/e9ff26f9c95a36d651e2df7e4a164600fc3d0a04e8c4bfcc08c152ecb4750202/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd012f1a8290078.pack
/var/lib/docker/aufs/diff/89111fc5418ab72ed66b461df7eb94189ea40647965596c5fed731330148a969/var/www/discourse/.git/objects/pack/pack-786c3e3931ecb9c41964039462a2ac21ab04f903.pack
/var/lib/docker/aufs/diff/d378f4ccb08d23c4158ea6c47528012345d35f6836bf6e4c7c95a10aec829841/var/www/discourse/.git/objects/pack/pack-1453eeeb2c0970e6769a7119d737ec109d8f65cc.pack
/var/lib/docker/aufs/diff/dd08347f5848c56ddbc80d93755f7d8d204a667084a20e05ba3a3a0cec217529/var/www/discourse/.git/objects/pack/pack-786c3e3931ecb9c41964039462a2ac21ab04f903.pack
/var/lib/docker/aufs/diff/6abd1eebed66038a8ff39533384ac2516a4b1da10fa83bfdc020df76a72ef7ce/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd012f1a8290078.pack
/var/lib/docker/aufs/diff/3202dfb7802efe4dceeeb6b8e89c311fa4b5de718f3ee4c0bae937b9e1d4b2a6/var/www/discourse/.git/objects/pack/pack-d7a718badb9f114ee853b887fdd012f1a8290078.pack
/var/log/btmp
/var/log/btmp.1

I have the
2 GB / 40 GB Disk / NYC3 - Ubuntu Discourse on 14.04
plan on digitial ocean. My site is not the large from what I believe and Im not familiar with docker at all. Can anyone please tell me what the issues are and how to go about correcting this? Im on 1.9.0 beta 1 and getting the notice to upgrade but cant do anything. Thank you.

Posts: 5

Participants: 3

Read full topic

@fantasticfears wrote:

I am working on the feature to allow overriding site setting based on the default_locale. @sam have talked with me that site setting based on environment is misleading. So I’d like to draw some proposals here to see which one is the best to go.

For the record, taking an example of the possible format:

min_search_term_length:
  client: true
  default:
    development: 2
    default: 3
  hidden:
    production: false
    development: true

As an aside, the overrides setting format will be:

min_search_term_length:
  client: true
  default: 3
  locale_default:
    zh_CN: 1
  hidden: false

hidden property proposal

hidden only accepts a true value instead of dependending on env. I don’t think a good use to hide anything in the dev and test environment. There are only 4 cases under the development category.

Rails.env params in the site setting

Remove any Rails.env params in the site setting and put them in another yaml file.

Related site settings should be put on a file and loaded with site setting. Can be config/site_settings_{dev,env}.yml

• + The site setting file is clean.
• + The site settings are centralized in a place so that it’s easy to follow.
• - Another file

I’d prefer this for clarity.

Put them into an initializer

Same pros as above. It’s not that obvious if they are put in config/initializers/005-site_settings.rb.

Merge them with locale_default

Instead of sending them outside the site setting files, we can have a override params to put locale or env.

min_search_term_length:
  client: true
  default: 3
  default_overrides:
    development: 2
    zh_CN: 1

This style also looks good considering such overrides are not much.

Posts: 1

Participants: 1

Read full topic

@SithLord wrote:

Your main www landing page is displaying various responsive elements in a jumble. To exclude domain issues, i took this screen on a stand alone win2008 r2 server that has never been attached to a domain.

image.png1286x779 107 KB

Posts: 5

Participants: 5

Read full topic

@Bank_Live wrote:

Normal. I use plugin https://github.com/evil-shrike/discourse-whitelist-iframe.git
I insert
<iframe src="https://www.facebook.com/plugins/video.php?href=https%3A%2F%2Fwww.facebook.com%2Fseen.everything%2Fvideos%2F1221002978004237%2F&show_text=0&width=400" width="400" height="400" style="border:none;overflow:hidden" scrolling="no" frameborder="0" allowTransparency="true" allowFullScreen="true"></iframe>

s1.jpg1051x567 88 KB

VDO can work. After last update Version v1.9.0.beta4
plugin https://github.com/evil-shrike/discourse-whitelist-iframe.git error “https://eleceasy.com/assets/plugin-third-party…”

I try plugin other

https://github.com/hiveeyes/discourse-whitelist-iframe.git
https://github.com/looker/discourse-whitelist-iframe.git
https://github.com/evil-shrike/discourse-whitelist-iframe.git
https://github.com/VinkasHQ/discourse-facebook-onebox.git

s2.jpg1273x625 124 KB

not work.
How can i fix it. Thank you very much

Posts: 4

Participants: 3

Read full topic

@kglobal wrote:

Hello,

We need a Discourse platform setup with the following features:

1. Topics started/tags created by moderators/admin only

2. Plugin with custom post entry fields to include:

   • Title
   • Text field A
   • Text field B
   • Location (looks up longitude and latitude from location field - perhaps uses Google Maps API or GeoNames?)
   • Start time/date
   • End time/date and option for “present”
   • Priority level (1-5)
   • Tags
   • Poll
   • Image
   • Text field C

3. A system to export (via JSON) public thread info (above) related to specific tag and organized by priority level and/or votes. In other words, there would be a separate JSON for each series of tags. I think the Data Explorer plugin would possibly work. The proper query would have to be scripted. The exported data would happen every 15 minutes and stored locally on the server.

We need this done by the beginning of August. PM me your offer along with any work experience/portfolio. Please let me know if you have any questions. More information will be provided to interested parties.

Thank you for your time! Have a great day!

Chris

Posts: 1

Participants: 1

Read full topic

@Y2K wrote:

Is it possible to have multiple instances of Discourse but that users can log in to all of them with the same ID info?
Let’s say that I have a forum for multiple cities, city1.domain.com, city2.domain.com, city3.domain.com but that users only have to register once.
Thanks for the help in advance

Posts: 3

Participants: 3

Read full topic

@Pawan_Jindal wrote:

Hello,
I am new to Discourse and am in process of setting it up. I was trying to update the Privacy Policy but I don’t see the pencil icon on the post. are there any special steps to edit that? i was able to edit Terms of service

image.png1012x367 20.1 KB

Posts: 6

Participants: 3

Read full topic

@sjmscott wrote:

Continuing the discussion from Create a link that will bring a user to their own profile:

I spend most of my time as a Discourse Admin educating users. I have many users over the age of 55 who have used Yahoo Groups for 20 years. The transition has been hard for them. I have a section on my website called HelpDesk in which I have a series of videos and tutorials. There are some users who appreciate simple animated gifs that show them how to send a PM, but other users prefer links to help them find what they want to do.

If a user asks, “How do I see my sent messages?” Writing this is confusing and hard to follow for some users:

1. Click on the circle in the upper right hand corner. Click it.
2. Look for the mailbox icon. Click it.
3. Look for Sent “click it”

A video or animated gif can help them visualize all of this.

This is better:

How do I see my sent messages?

Just click here! Please see our FAQ for more help.

I’m working on building something for my FAQ pages that links them to some key activities. Hopefully, as they click around they will begin to start learning where things are located.

I have gathered some of the key links that will help users find things. It also helps me to make requests such as: Please update your profile picture by clicking here. If you want to learn more, please watch this video.

Here are some useful links:

• https://meta.discourse.org/my/preferences/account
• https://meta.discourse.org/my/preferences/profile
• https://meta.discourse.org/my/preferences/emails
• https://meta.discourse.org/my/preferences/categories
• https://meta.discourse.org/my/preferences/tags
• https://meta.discourse.org/my/badges
• https://meta.discourse.org/my/activity/
• https://meta.discourse.org/my/activity/bookmarks
• https://meta.discourse.org/my/notifications
• https://meta.discourse.org/my/messages
• https://meta.discourse.org/my/summary
• https://meta.discourse.org/my/messages/sent

I would be interested in hearing your success stories in educating users who struggle with technology.

Posts: 1

Participants: 1

Read full topic

@Steve_Pavlina wrote:

I had this potential bug come up twice so far.

A user registers for my forum (which is private and invite only), gets the activation email, activates their account, logs in, posts for a while, and then takes a break for a few weeks.

When they try to login again, they get an error message like this:

You can’t log in yet. We previously sent an activation email to you at youremail@domain.com. Please follow the instructions in that email to activate your account.

At this point they’re stuck. They can’t login. Reactivating via the previously sent activation email that they’ve already used doesn’t work. And if I go to their user page, it shows that their account is already approved. If I manually deactivate and reactivate it, that doesn’t let them login either.

This has happened to two different users on our forums so far. Once they’re frozen out, the problem occurs across different browsers and devices, so it doesn’t appear to be a caching issue. We also ruled out any sort of ad blocker. Seems like a potential bug to me.

Otherwise how do I restore these accounts to active status, so these members can login again? Both are still being prevented from logging in. I’d prefer not to make them new accounts since they’ve already set up profiles and posted under the old accounts.

This is with version v1.9.0.beta4 +52 from a few days ago. But it started happening a few weeks earlier.

Posts: 4

Participants: 2

Read full topic

@LockeCJ wrote:

Similar to

Posting a link to a getyarn.io clip appears to onbox in the preview, but the actual post causes the browser to download a .mp4 file. More annoyingly, this happens any time the post comes into view, since I assume it’s being re-rendered.

It looks like the content type served by getyarn.io is application/mp4 instead of video/mp4, so that may be relevant.

Here’s an example URL, escaped for obvious reasons:

https://getyarn.io/yarn-clip/d371f408-aea1-4508-9d56-c60898827e44

Posts: 4

Participants: 4

Read full topic

@jomaxro wrote:

If a TL4 user deletes a small post, it triggers the (post withdrawn by author, will be automatically deleted in 24 hours unless flagged) text, however, small posts can’t be flagged so this seems quite strange/inconsistent. Ideally, TL4 deletes of small posts should be instant.

Posts: 1

Participants: 1

Read full topic