# Contribute

**URL:** https://meta.discourse.org/c/contribute/208.md?page=502

[최신](https://meta.discourse.org/latest.md) · [카테고리](https://meta.discourse.org/categories.md) · [태그](https://meta.discourse.org/tags.md)

**Page:** 503

---

## [Are paid plugins with undisclosed license allowed to exist on meta?](https://meta.discourse.org/t/are-paid-plugins-with-undisclosed-license-allowed-to-exist-on-meta/32819)

<div class="topic-metadata">

**Author:** [@avolve](https://meta.discourse.org/u/avolve)\
**댓글:** 28\
**마지막 업데이트:** [8월 30, 2017, 4:04오후 UTC](https://meta.discourse.org/t/are-paid-plugins-with-undisclosed-license-allowed-to-exist-on-meta/32819 "2017-08-30T16:04:29Z")

</div>

I thought’d I might contribute a perspective from a user/site builder/low level developer. tl:dr this is about plugins, not core development Apologies if deemed a thread jack, as references to plugins came up in the dis…

---

## [Public-facing date for when a user progressed past TL0](https://meta.discourse.org/t/public-facing-date-for-when-a-user-progressed-past-tl0/69021)

<div class="topic-metadata">

**Author:** [@Drew\_Warwick](https://meta.discourse.org/u/Drew_Warwick)\
**댓글:** 1\
**마지막 업데이트:** [8월 30, 2017, 5:05오전 UTC](https://meta.discourse.org/t/public-facing-date-for-when-a-user-progressed-past-tl0/69021 "2017-08-30T05:05:56Z")

</div>

Our Discourse forum is semi-private. A number of our categories are public for viewing, but TL0 users cannot post in any section, send PMs, etc. I’m not sure how many of Discourse’s customers use Discourse for private fo…

---

## [Enabling team/group to mark topic solved when it is \`email in\` and the user is staged](https://meta.discourse.org/t/enabling-team-group-to-mark-topic-solved-when-it-is-email-in-and-the-user-is-staged/68981)

<div class="topic-metadata">

**Author:** [@schungx](https://meta.discourse.org/u/schungx)\
**댓글:** 4\
**마지막 업데이트:** [8월 29, 2017, 1:48오후 UTC](https://meta.discourse.org/t/enabling-team-group-to-mark-topic-solved-when-it-is-email-in-and-the-user-is-staged/68981 "2017-08-29T13:48:56Z")

</div>

When a topic is created via email in, and the user is currently staged, then obviously the owner of the topic is not there to mark a particular post as the solution. Would there be a way for the category’s team/group to…

---

## [No keyboard shortcut for "move to new topic" submission](https://meta.discourse.org/t/no-keyboard-shortcut-for-move-to-new-topic-submission/68984)

<div class="topic-metadata">

**Author:** [@Sujan](https://meta.discourse.org/u/Sujan)\
**댓글:** 0\
**마지막 업데이트:** [8월 29, 2017, 11:35오전 UTC](https://meta.discourse.org/t/no-keyboard-shortcut-for-move-to-new-topic-submission/68984 "2017-08-29T11:35:38Z")

</div>

When you use the Select → “Move to new topic” feature, there is no keyboard shortcut to execute the form submission after selecting a category and giving the new topic its title. Ctrl + Enter would be the expected short…

---

## [When site require approvals for users, email replies do not get sent to staged users](https://meta.discourse.org/t/when-site-require-approvals-for-users-email-replies-do-not-get-sent-to-staged-users/68832)

<div class="topic-metadata">

**Author:** [@schungx](https://meta.discourse.org/u/schungx)\
**댓글:** 5\
**마지막 업데이트:** [8월 28, 2017, 9:32오후 UTC](https://meta.discourse.org/t/when-site-require-approvals-for-users-email-replies-do-not-get-sent-to-staged-users/68832 "2017-08-28T21:32:38Z")

</div>

In notification\_emailer.rb: def perform\_enqueue(type, delay) user = notification.user return unless user.active? || user.staged? return if SiteSetting.must\_approve\_users? && !user.approved? …

---

## [Triggering alerts when topic not solved/handled/replied](https://meta.discourse.org/t/triggering-alerts-when-topic-not-solved-handled-replied/68865)

<div class="topic-metadata">

**Author:** [@schungx](https://meta.discourse.org/u/schungx)\
**댓글:** 2\
**마지막 업데이트:** [8월 28, 2017, 2:57오후 UTC](https://meta.discourse.org/t/triggering-alerts-when-topic-not-solved-handled-replied/68865 "2017-08-28T14:57:20Z")

</div>

Is there a feature to automatically alert staff (or some team) that a topic has not been solved/handled/replied to for a period of time? This will make the solved plugin much more powerful. What would be perfect is an e…

---

## [&hellip is shown as text in choosing the category](https://meta.discourse.org/t/hellip-is-shown-as-text-in-choosing-the-category/68811)

<div class="topic-metadata">

**Author:** [@Pad\_Pors](https://meta.discourse.org/u/Pad_Pors)\
**댓글:** 6\
**마지막 업데이트:** [8월 28, 2017, 1:08오후 UTC](https://meta.discourse.org/t/hellip-is-shown-as-text-in-choosing-the-category/68811 "2017-08-28T13:08:25Z")

</div>

in the create topic panel, when there’s no un-categorized category a text is supposed to be shown: select a category ... but the &hellip is not working after an update:

---

## [(Minor) UX issue on a private message (on responsive)](https://meta.discourse.org/t/minor-ux-issue-on-a-private-message-on-responsive/68893)

<div class="topic-metadata">

**Author:** [@Steven](https://meta.discourse.org/u/Steven)\
**댓글:** 3\
**마지막 업데이트:** [8월 28, 2017, 1:08오후 UTC](https://meta.discourse.org/t/minor-ux-issue-on-a-private-message-on-responsive/68893 "2017-08-28T13:08:03Z")

</div>

I’m always unsure if these kind of topics is better in Contribute \> UX or Contribute \> Bug sorry if this topic is misplaced. I often use my firefox window on responsive and I came across this minor css issue when I want…

---

## [Could the undelete flow be improved?](https://meta.discourse.org/t/could-the-undelete-flow-be-improved/68876)

<div class="topic-metadata">

**Author:** [@gmanjapan](https://meta.discourse.org/u/gmanjapan)\
**댓글:** 1\
**마지막 업데이트:** [8월 28, 2017, 10:00오전 UTC](https://meta.discourse.org/t/could-the-undelete-flow-be-improved/68876 "2017-08-28T10:00:40Z")

</div>

Here’s the flow right now as far as I can tell Type reply Post it Realize something is wrong Delete it so no one responds to the wrong message Now you want to fix it but there’s no way to pick edit and undelete Instea…

---

## [Indicator at post for "x posts in topic" (or "first post in topic")](https://meta.discourse.org/t/indicator-at-post-for-x-posts-in-topic-or-first-post-in-topic/66036)

<div class="topic-metadata">

**Author:** [@Sujan](https://meta.discourse.org/u/Sujan)\
**댓글:** 4\
**마지막 업데이트:** [8월 28, 2017, 9:07오전 UTC](https://meta.discourse.org/t/indicator-at-post-for-x-posts-in-topic-or-first-post-in-topic/66036 "2017-08-28T09:07:12Z")

</div>

The forum I moderate in has lots of “evergreen” topics that get posts over months and topics that are bumped after months by users because the have the same issue. When someone posts at the end of a \>10 posts topic, it …

---

## [Grant Admin without LoggingIn](https://meta.discourse.org/t/grant-admin-without-loggingin/68894)

<div class="topic-metadata">

**Author:** [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)\
**댓글:** 1\
**마지막 업데이트:** [8월 28, 2017, 8:54오전 UTC](https://meta.discourse.org/t/grant-admin-without-loggingin/68894 "2017-08-28T08:54:01Z")

</div>

I’m not sure if this should be done without logging in, but I was able to grant admin without logging in with my account: What I’ve done was to Grant Admin to an user, logout, hit thr hab nk on the email and I verifi…

---

## [Duplicate account icon for suspended users](https://meta.discourse.org/t/duplicate-account-icon-for-suspended-users/68887)

<div class="topic-metadata">

**Author:** [@henrikbg](https://meta.discourse.org/u/henrikbg)\
**댓글:** 9\
**마지막 업데이트:** [8월 27, 2017, 10:25오후 UTC](https://meta.discourse.org/t/duplicate-account-icon-for-suspended-users/68887 "2017-08-27T22:25:13Z")

</div>

On our Discourse forum, we’re reaching a point where we can no longer keep track of all the suspended users and whether or not they’re creating duplicate accounts. Users are bypassing suspensions by creating duplicate ac…

---

## [Prompt users to share their post after they reply or create a new topic](https://meta.discourse.org/t/prompt-users-to-share-their-post-after-they-reply-or-create-a-new-topic/68855)

<div class="topic-metadata">

**Author:** [@mcwumbly](https://meta.discourse.org/u/mcwumbly)\
**댓글:** 2\
**마지막 업데이트:** [8월 27, 2017, 4:25오전 UTC](https://meta.discourse.org/t/prompt-users-to-share-their-post-after-they-reply-or-create-a-new-topic/68855 "2017-08-27T04:25:52Z")

</div>

Something that came up in our recent user research is that infrequent users often visit the site when someone shares a topic via Slack or email. This led me to wonder what it would take to add some kind of prompt after …

---

## [Is it possible to sticky a post in a topic?](https://meta.discourse.org/t/is-it-possible-to-sticky-a-post-in-a-topic/68843)

<div class="topic-metadata">

**Author:** [@Andy02](https://meta.discourse.org/u/Andy02)\
**댓글:** 3\
**마지막 업데이트:** [8월 26, 2017, 11:07오후 UTC](https://meta.discourse.org/t/is-it-possible-to-sticky-a-post-in-a-topic/68843 "2017-08-26T23:07:19Z")

</div>

the 1st post of each topic i’ve posted a workflow and users guide to the topic. after 300+ comments no-one is ever going to browse to the top and read it. is it possible to sticky the top post so it is always visible?

---

## [Category from /new-topic route not displayed in composer](https://meta.discourse.org/t/category-from-new-topic-route-not-displayed-in-composer/68790)

<div class="topic-metadata">

**Author:** [@LeoMcA](https://meta.discourse.org/u/LeoMcA)\
**댓글:** 2\
**마지막 업데이트:** [8월 25, 2017, 11:47오후 UTC](https://meta.discourse.org/t/category-from-new-topic-route-not-displayed-in-composer/68790 "2017-08-25T23:47:15Z")

</div>

Steps to reproduce: Visit https://meta.discourse.org/new-topic?category=bug Observe composer open with Contribute \> Bug prefilled in category selector Close composer Visit https://meta.discourse.org/new-topic?category\_…

---

## [Korean translation mistake](https://meta.discourse.org/t/korean-translation-mistake/68781)

<div class="topic-metadata">

**Author:** [@icanhasr00t](https://meta.discourse.org/u/icanhasr00t)\
**댓글:** 4\
**마지막 업데이트:** [8월 25, 2017, 6:03오후 UTC](https://meta.discourse.org/t/korean-translation-mistake/68781 "2017-08-25T18:03:39Z")

</div>

Not a bug really but … option(s) should be “옵션” not “온셥” as seen in the screenshot above. We are on 1.9.0 beta 7+22. Cheers!

---

## [Reddit new algorithm](https://meta.discourse.org/t/reddit-new-algorithm/68764)

<div class="topic-metadata">

**Author:** [@Ham](https://meta.discourse.org/u/Ham)\
**댓글:** 2\
**마지막 업데이트:** [8월 25, 2017, 10:02오전 UTC](https://meta.discourse.org/t/reddit-new-algorithm/68764 "2017-08-25T10:02:46Z")

</div>

Not sure if this is a good place for it but just an idea. Reddit is working on a new algorithm that tracks what you are not reading and when you refresh the home page or our “latest” it gives you new content you haven’t …

---

## [Feature question: Can discourse be configured to send responses as email](https://meta.discourse.org/t/feature-question-can-discourse-be-configured-to-send-responses-as-email/68729)

<div class="topic-metadata">

**Author:** [@Quintin\_Par](https://meta.discourse.org/u/Quintin_Par)\
**댓글:** 4\
**마지막 업데이트:** [8월 24, 2017, 10:47오후 UTC](https://meta.discourse.org/t/feature-question-can-discourse-be-configured-to-send-responses-as-email/68729 "2017-08-24T22:47:41Z")

</div>

Sorry if I didn’t do a good job googling this. I am not talking about replying via email but a response to this post showing up in my inbox. The only discussion I could find was this: Troubleshoot reply by email

---

## [\[Composer\] Category chooser is 'above' composer message](https://meta.discourse.org/t/composer-category-chooser-is-above-composer-message/68704)

<div class="topic-metadata">

**Author:** [@xrav3nz](https://meta.discourse.org/u/xrav3nz)\
**댓글:** 3\
**마지막 업데이트:** [8월 24, 2017, 5:56오후 UTC](https://meta.discourse.org/t/composer-category-chooser-is-above-composer-message/68704 "2017-08-24T17:56:47Z")

</div>

Reproduction Try to trigger a composer message and: It seems to me that .select-box has a higher z-index than .composer-popup. I will let the experts handle it this time… /cc @j.jaffeux

---

## [Import GitHub image as profile image when authenticating with GitHub](https://meta.discourse.org/t/import-github-image-as-profile-image-when-authenticating-with-github/49132)

<div class="topic-metadata">

**Author:** [@ossia](https://meta.discourse.org/u/ossia)\
**댓글:** 9\
**마지막 업데이트:** [8월 23, 2017, 2:25오후 UTC](https://meta.discourse.org/t/import-github-image-as-profile-image-when-authenticating-with-github/49132 "2017-08-23T14:25:14Z")

</div>

User story: As a new user, when I authenticate with GitHub, my profile image should automatically become whatever my GitHub profile image is. According to @codinghorror this is not currently on the roadmap. I am not 100…

---

## [Unlisting a thread breaks links that have old thread names](https://meta.discourse.org/t/unlisting-a-thread-breaks-links-that-have-old-thread-names/68440)

<div class="topic-metadata">

**Author:** [@Drew\_Warwick](https://meta.discourse.org/u/Drew_Warwick)\
**댓글:** 11\
**마지막 업데이트:** [8월 21, 2017, 6:44오후 UTC](https://meta.discourse.org/t/unlisting-a-thread-breaks-links-that-have-old-thread-names/68440 "2017-08-21T18:44:31Z")

</div>

The Bug: A Discourse topic link looks like this: https://meta.discourse.org/t/welcome-to-meta-discourse-org/1?silent=true Normally the title, the bit between the /t/ and /topicId at the end, does not matter, so I could…

---

## [Incorrect Count on /tags page (included deleted topics - now fixed)](https://meta.discourse.org/t/incorrect-count-on-tags-page-included-deleted-topics-now-fixed/53051)

<div class="topic-metadata">

**Author:** [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**댓글:** 12\
**마지막 업데이트:** [8월 22, 2017, 9:04오후 UTC](https://meta.discourse.org/t/incorrect-count-on-tags-page-included-deleted-topics-now-fixed/53051 "2017-08-22T21:04:21Z")

</div>

Summary: Over at Stonehearth it was noticed by an Admin today that the count on the /tags page is incorrect for some tags. Steps to reproduce: Unknown. Expected Results: Number next to tags matches number of topics s…

---

## [Line break in description next to pin controls](https://meta.discourse.org/t/line-break-in-description-next-to-pin-controls/68534)

<div class="topic-metadata">

**Author:** [@fefrei](https://meta.discourse.org/u/fefrei)\
**댓글:** 0\
**마지막 업데이트:** [8월 22, 2017, 11:17오전 UTC](https://meta.discourse.org/t/line-break-in-description-next-to-pin-controls/68534 "2017-08-22T11:17:44Z")

</div>

While a topic is pinned, the description text for the pin controls breaks quite badly: This is as rendered by Chrome Version 60.0.3112.101 (Official Build) (64-bit) on Windows.

---

## [Unlisted topics become listed via references](https://meta.discourse.org/t/unlisted-topics-become-listed-via-references/61243)

<div class="topic-metadata">

**Author:** [@niemeyer](https://meta.discourse.org/u/niemeyer)\
**댓글:** 9\
**마지막 업데이트:** [8월 22, 2017, 9:27오전 UTC](https://meta.discourse.org/t/unlisted-topics-become-listed-via-references/61243 "2017-08-22T09:27:19Z")

</div>

When an unlisted topic refers to a listed topic, the former is backlinked in the latter, thus becoming “listed”. Ideally topics would lose old and not gain any new back references when becoming unlisted. It seems okay t…

---

## [Temporary Timed Closure of topic not re-opening topic](https://meta.discourse.org/t/temporary-timed-closure-of-topic-not-re-opening-topic/67877)

<div class="topic-metadata">

**Author:** [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)\
**댓글:** 2\
**마지막 업데이트:** [8월 22, 2017, 8:08오전 UTC](https://meta.discourse.org/t/temporary-timed-closure-of-topic-not-re-opening-topic/67877 "2017-08-22T08:08:08Z")

</div>

Version: v1.9.0.beta5 +119 (latest as of 11th Aug) Steps to reproduce: Spanner \> “Set Topic Timer” “Close Temporarily” “When” \> “Pick Date and Time” Select time a minute into the future (I have tried with longer times) …

---

## [Job exception: UserDestroyer::PostsExistError](https://meta.discourse.org/t/job-exception-userdestroyer-postsexisterror/68372)

<div class="topic-metadata">

**Author:** [@Pad\_Pors](https://meta.discourse.org/u/Pad_Pors)\
**댓글:** 10\
**마지막 업데이트:** [8월 22, 2017, 7:48오전 UTC](https://meta.discourse.org/t/job-exception-userdestroyer-postsexisterror/68372 "2017-08-22T07:48:21Z")

</div>

I’m getting this error repeatedly after a recent update: var/www/discourse/app/services/user\_destroyer.rb:18:in \`destroy' /var/www/discourse/app/jobs/onceoff/fix\_primary\_emails\_for\_staged\_users.rb:17:in \`block (2 levels…

---

## [Moving a topic after closure reopens topic](https://meta.discourse.org/t/moving-a-topic-after-closure-reopens-topic/67659)

<div class="topic-metadata">

**Author:** [@henrikbg](https://meta.discourse.org/u/henrikbg)\
**댓글:** 7\
**마지막 업데이트:** [8월 22, 2017, 3:55오전 UTC](https://meta.discourse.org/t/moving-a-topic-after-closure-reopens-topic/67659 "2017-08-22T03:55:51Z")

</div>

We have encountered a bug on our forum which allows a regular to reopen a topic after it’s already been closed. As stated in the title, all one needs to do is move a topic from one category to another and system reopens …

---

## [Server error Code 500](https://meta.discourse.org/t/server-error-code-500/68404)

<div class="topic-metadata">

**Author:** [@smota](https://meta.discourse.org/u/smota)\
**댓글:** 2\
**마지막 업데이트:** [8월 22, 2017, 2:18오전 UTC](https://meta.discourse.org/t/server-error-code-500/68404 "2017-08-22T02:18:45Z")

</div>

Hi expert, when I try so check user suspect I get the following error.

---

## [Discobot not skipping tutorial?](https://meta.discourse.org/t/discobot-not-skipping-tutorial/68498)

<div class="topic-metadata">

**Author:** [@sunnyt7](https://meta.discourse.org/u/sunnyt7)\
**댓글:** 3\
**마지막 업데이트:** [8월 21, 2017, 10:47오후 UTC](https://meta.discourse.org/t/discobot-not-skipping-tutorial/68498 "2017-08-21T22:47:36Z")

</div>

Got this feedback from a user today: I’m running on v1.9.0.beta5 +123. My apologies if it has been updated since then!

---

## [Can't add people to a PM](https://meta.discourse.org/t/cant-add-people-to-a-pm/65950)

<div class="topic-metadata">

**Author:** [@insertusernamehere](https://meta.discourse.org/u/insertusernamehere)\
**댓글:** 17\
**마지막 업데이트:** [8월 21, 2017, 6:05오후 UTC](https://meta.discourse.org/t/cant-add-people-to-a-pm/65950 "2017-08-21T18:05:05Z")

</div>

Whenever I click “Add person”, this comes up Then I type anything, it always comes up with this (because it isn’t registering my inputs) (Can’t add 2nd pic, but whatever I type it just shows @Rishi\_Bokhoree) I can’…

[이전 페이지](https://meta.discourse.org/c/contribute/208.md?page=501)

[다음 페이지](https://meta.discourse.org/c/contribute/208.md?page=503)
