@stevenpslade wrote:
I want to change some labels by editing
discourse/config/locales/client.en.yml
but not sure the best to do it. A plugin seems like too much to accomplish this.
Posts: 3
Participants: 2
@stevenpslade wrote:
I want to change some labels by editing
discourse/config/locales/client.en.yml
but not sure the best to do it. A plugin seems like too much to accomplish this.
Posts: 3
Participants: 2
@jpalermo wrote:
Hello; I'm the new online community manager for my organization, which means I'm also new to Discourse! I'm wondering if there's a way to message all of our users, or even just selected groups? (We currently have groups based on permissions/category they belong to.)
Posts: 2
Participants: 2
@Oskar wrote:
Hi, the default Discourse header contains a title and the panel with login/user links etc. We've been injecting some extra, external links inside using an inline script in our theme. It's dirty and has been working very well, until 1.6.0 beta 2.
<header class="d-header">title and panel are here</header>
Now, when we inject the same links, we see the following. Is there a way to overwrite this Ember template or a third approach, we can take?
To clarify, injecting the links isn't the issue, the issue is that it somehow breaks the Discourse header, none of the panels open any more.
Posts: 2
Participants: 2
@marcospreviato wrote:
Hi,
How to upgrade discourse to beta releases in AWS Bitnami on t2.micro?
Thanks!
Posts: 5
Participants: 3
@downey wrote:
Reproduce:
Go to https://discourse.example.org/admin/groups/automatic/everyone and change the setting as follows:
Expected result:
The group settings are changed so I can message everyone.
Actual result:
See above for "Name has already been taken" error.
Posts: 5
Participants: 3
@Mat_Leonard wrote:
Was pinning a topic, part of the calendar is cutoff. Using Chrome Version 49.0.2623.112.
Posts: 2
Participants: 2
@pfaffman wrote:
I just submitted this PR:
It is an attempt at relieving Normal People from having to use a scary text editor.
Here's what happens.
If any changes to config file are detected, say so and do nothing.
Otherwise, ask user for values for defaults (see output below).
If they don't like what they entered, let them try again; once values are approved, write them to config file.
Once changes are written to config file, user gets one more chance to ^C (e.g., to start over or edit the config file with a scary text editor).
If a known smtp host is entered (e.g., sparkpost, sendgrid), then default username for that service is provided.
TODO: ask sparkpost people whether they need to set notification_email
TODO:
Here's what it looks like:
pfaffman@sequestered:~/discourse_docker$ ./launcher bootstrap app Getting config hostname: [discourse.example.com]: new.literatecomputing.com developer_emails [me@example.com]: j@pfaffman.com smtp_address [smtp.example.com]: smtp.sparkpostmail.com smtp_user_name [SMTP_Injection]: smtp_password [pa$$word]: reallylongpassword letsencrypt_account_email (change to enable) [your.email@example.com]: user@someplace.com Letsencrypt enabled. That's it! Everything is set. Read carefully before continuing. DISCOURSE_HOSTNAME: new.literatecomputing.com DISCOURSE_DEVELOPER_EMAILS: j@pfaffman.com DISCOURSE_SMTP_ADDRESS: smtp.sparkpostmail.com DISCOURSE_SMTP_USER_NAME: SMTP_Injection DISCOURSE_SMTP_PASSWORD: reallylongpassword LETSENCRYPT_ACCOUNT_EMAIL: user@someplace.com LETSENCRYPT will be enabled. Enter to write these settings to containers/app.yml, 'N' to retry, or ^C to start again: n Getting config hostname: [new.literatecomputing.com]: Unchanged. developer_emails [j@pfaffman.com]: jay@pfaffman.com smtp_address [smtp.sparkpostmail.com]: smtp.sendgrid.net smtp_user_name [apikey]: smtp_password [reallylongpassword]: letsencrypt_account_email (Enter 'OFF' to disable.) [user@someplace.com]: letsencrypt unchanged That's it! Everything is set. Read carefully before continuing. DISCOURSE_HOSTNAME: new.literatecomputing.com DISCOURSE_DEVELOPER_EMAILS: jay@pfaffman.com DISCOURSE_SMTP_ADDRESS: smtp.sendgrid.net DISCOURSE_SMTP_USER_NAME: apikey DISCOURSE_SMTP_PASSWORD: reallylongpassword LETSENCRYPT_ACCOUNT_EMAIL: user@someplace.com LETSENCRYPT will be enabled. Enter to write these settings to containers/app.yml, 'N' to retry, or ^C to start again: Writing changes to containers/app.yml: DISCOURSE_HOSTNAME: new.literatecomputing.com DISCOURSE_DEVELOPER_EMAILS: 'jay@pfaffman.com' DISCOURSE_SMTP_ADDRESS: smtp.sendgrid.net DISCOURSE_SMTP_USER_NAME: apikey DISCOURSE_SMTP_PASSWORD: reallylongpassword LETSENCRYPT_ACCOUNT_EMAIL: user@someplace.com web.ssl.template.yml enabled letsencrypt.ssl.template.yml enabled containers/app.yml updated successfully. Enter to continue or ^C to exit:
If anyone sees problems or has refinements, please let me know.
Would it make more sense to have a
./launcher setup app
command that copied standalong.yml and then does this instead of integrating this config with bootstrap? That would save some rather tedious checking that I do now.
Posts: 1
Participants: 1
@rob1 wrote:
Hi,
Could anyone help to explain step by step how to give moderators a different username color say Red.
Thank you
Rob
Posts: 13
Participants: 4
@prateekvarma wrote:
I wanted to upload my logo for my new discourse setup and I can't seem to find the root directory in my VPS. I used the standard docker installation.
The admin dashboard just says it's in "/images/d-logo-sketch.png", and all the forum posts say it's in /var/www/discourse.... But there is no such folder called www in my var.
Here is a shot from my /var folder from my FTP manager
Posts: 3
Participants: 2
@Yuun wrote:
So, post-vdom'ing of the header, this old code:
<script type='text/x-handlebars' data-template-name='/connectors/header-after-home-logo/add-header-links'> {{#unless showExtraInfo}} <a id="recruiter" href="http://sih.onemadogre.com/t/joining-sih/494">Join us!</a> <a id="about" href="http://sih.onemadogre.com/c/guild-news-announcements/about-the-guild">About SiH</a> {{/unless}} </script>
doesn't work, so I've replaced it with:
<script type="text/discourse-plugin" version="0.2"> api.decorateWidget('home-logo:after', helper => { const minimized = helper.attrs.minimized; if(!minimized) { return helper.h('div#header-links', [ helper.h('a#recruiter', { href:'https://sih.onemadogre.com/t/joining-sih/494', text:'Join Us!' }), helper.h('a#about', { href:'https://sih.onemadogre.com/c/guild-news-announcements/about-the-guild', text:'About SiH' }) ]); } }); </script>
Which almost works (some css needed to reposition div#header-links, but nbd), except that my links just refresh the page.
I realize this is less a Discourse specific question and probably more a "Yuun's making a dumb syntax error" question, but I'd appreciate it if someone could give it a look over nonetheless.
Thanks in advance, generous stranger.
Clarification: my links don't refresh the page, they just always go to the home page. The hover text for each link is correct, but I guess it's being overridden by the home logo's href?
Posts: 3
Participants: 2
@emanuelet wrote:
This plugin fetches the first image of the topic and sets it as the featured image, showing in the topic list and above the main topic.
Repo: https://github.com/startsat60/discourse-plugin-featured-image
Features:
- Automatic setting of the image
- Included styling for topic list
Ideas for future developments:
- Settings to change image dimension or position
- Captions?
Screenshots:
Posts: 1
Participants: 1
@prateekvarma wrote:
Hello,
Just trying my new discourse forum, and i see that all emails, and most references are made using the title tag, and not the domain name.What is the reason behind this?
And how can i use my domain name instead?
Thanks
Posts: 2
Participants: 1
@DeanMarkTaylor wrote:
If you dismiss the search box either by:
- clicking away from the search popup
- OR by navigating to a search result, then to the same category
Then attempt a search again, the "search context" is not applied to the results.
Posts: 1
Participants: 1
@DeanMarkTaylor wrote:
I'm unsure if this is a setting specific to meta... however...
This topic has two tags:
Only one displays in the topics list:
Posts: 3
Participants: 3
@codetaylor wrote:
I was just now running some ./launcher commands and the launcher updated and stopped working properly, displaying usage and terminating regardless of parameters passed.
I think this will solve the issue: https://github.com/discourse/discourse_docker/pull/247
Posts: 4
Participants: 4
@walker wrote:
I changed some build-in template of the welcome letter (the user get when newly registered) but later on I found that new user no longer get any welcome letter. Is it because of the template gets modified? Could you help me to get the welcome letter back?
Posts: 1
Participants: 1
@evert wrote:
`Job exception: PG::UniqueViolation: ERROR: duplicate key value violates unique constraint "index_users_on_email" DETAIL: Key (lower(email::text))=(emeulie@gmail.com) already exists. : UPDATE "users" SET "last_seen_at" = '2016-04-27 06:07:08.139024' WHERE "users"."id" = 2`
Seeing these while I'm logged in on my site. Can I repair that table somehow?
Posts: 3
Participants: 2
@envieme wrote:
I have regularly gone to /admin/upgrade directly and upgraded. Including today evening.
And have ./launcher rebuild app from the command prompt too. Have also rebooted my system.
Yet keep seeing this message on the dashboard that it is up to date. While at the same time showing a mismatch between latest and installed versions.
Posts: 3
Participants: 2
@jesus2099 wrote:
Hello,
I wanted to try and fix a one row of JavaScript code in Discourse but could not dare submit a PR without making sure I did not break anything or making sure it did really fix the problem.
So I found what was said to be the easiest way to start a Discourse dev env up: VAGRANT.md.
In there I read:
Getting Started
- Install Git: http://git-scm.com/downloads (or GitHub for Windows if you want a GUI)
- Install VirtualBox: https://www.virtualbox.org/wiki/Downloads
- Install Vagrant: http://www.vagrantup.com/ (We require Vagrant 1.7.2 or later)
- Open a terminal
- Clone the project:
git clone https://github.com/discourse/discourse.git
- Enter the project directory:
cd discourse
So I followed steps 123 (I already have git and cloned a fork of discourse on my Windows laptop) and installed Virtualbox for my Windows then Vagrant for my Windows.
Until I realised, well:
- Are those steps starting from Vagrant installation shouldn’t have been done from inside Virtualbox?
- My Virtualbox is just empty, what OS should I put here?
- Why install git before Virtualbox if it should be inside?
I am confused.
I have done three first steps but fourth step tells me to open terminal. In Virtualbox? Which VDI?
I must be even dumber than what was expected making those easy dev env install docs.
Are there some official pre‐installed VDI image? Like this seemingly outdated image?Should the doc have been interpreted as following?
Getting Started
- Install VirtualBox: https://www.virtualbox.org/wiki/Downloads
- Download and open this or that VDI file (which contains this or that installed OS with git)
- Install Vagrant from inside VirtualBox: http://www.vagrantup.com/ (We require Vagrant 1.7.2 or later)
- Open a terminal from inside VirtualBox
- Clone your fork of the project:
git clone https://github.com/yourname/discourse.git
- Enter the project directory:
cd discourse
From my point of view (for my low level abilities), some steps were missing.
I have read both the “Discourse as Your First Rails App” blog post and its comments as well.
Posts: 1
Participants: 1
@skx wrote:
I'm importing a series of emails into a new discourse instance. Importing the messages is going well, however using the
discourse_api
gem I'm unable to set the date on a new post.For example the following code imports a new post, using create_topic:
result = client.create_topic( :category => "foo", :title => "This is my descriptive title", :raw => "This is my long/interesting post..." )
As expected this creates the post with the post-date set to "now". I tried adding
created_at
andposted_at
fields which I've seen referred to in various places (but not the API gem), but these were ignored.Is there any way to mangle the date of the new post, short of editing the database? (Bear in mind I'm importing thousand of new entries from mailman archives and a couple of other data-sources (including wordpress).
Posts: 1
Participants: 1