# Bug

**URL:** https://meta.discourse.org/c/contribute/bug/1.md?page=161

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

**Page:** 162

---

## [Getting type errors in sidekiq queue](https://meta.discourse.org/t/getting-type-errors-in-sidekiq-queue/81287)

<div class="topic-metadata">

**Author:** [@carlokok](https://meta.discourse.org/u/carlokok)\
**댓글:** 8\
**마지막 업데이트:** [3월 12, 2018, 9:58오전 UTC](https://meta.discourse.org/t/getting-type-errors-in-sidekiq-queue/81287 "2018-03-12T09:58:30Z")

</div>

Getting lots of these (curiously all for 1 user/thread, one I never got notified for, I’m user 1). What’s the best way to get more info for this to resolve it? Wachtrij default Taak Jobs::UserEmail Argumenten \`…

---

## [After upgrade, unable to load categories.json with error](https://meta.discourse.org/t/after-upgrade-unable-to-load-categories-json-with-error/82540)

<div class="topic-metadata">

**Author:** [@Magnetidog](https://meta.discourse.org/u/Magnetidog)\
**댓글:** 4\
**마지막 업데이트:** [3월 8, 2018, 9:43오후 UTC](https://meta.discourse.org/t/after-upgrade-unable-to-load-categories-json-with-error/82540 "2018-03-08T21:43:28Z")

</div>

We upgraded to the latest Discourse build; no major plugin installed, other than the fact we have a subdirectory install. The error I am seeing in the logs is the following: failed to handle exception in exception app …

---

## [Switching a post between PUBLIC and PRIVATE](https://meta.discourse.org/t/switching-a-post-between-public-and-private/81947)

<div class="topic-metadata">

**Author:** [@Biscuit](https://meta.discourse.org/u/Biscuit)\
**댓글:** 6\
**마지막 업데이트:** [3월 8, 2018, 12:33오후 UTC](https://meta.discourse.org/t/switching-a-post-between-public-and-private/81947 "2018-03-08T12:33:57Z")

</div>

Steps to replicate: Create a topic in a category =\> Topic exists as expected. Choose “Make Personal Message” =\> Message becomes a PM as expected. Choose “Make Public” =\> Message becomes public again as expected. Choo…

---

## [Regression in login behavior](https://meta.discourse.org/t/regression-in-login-behavior/81612)

<div class="topic-metadata">

**Author:** [@vikaskedia](https://meta.discourse.org/u/vikaskedia)\
**댓글:** 4\
**마지막 업데이트:** [3월 7, 2018, 5:46오후 UTC](https://meta.discourse.org/t/regression-in-login-behavior/81612 "2018-03-07T17:46:20Z")

</div>

I just upgraded to the latest today. I run the system from http://www.example.com/discourse/ The system is set to only allow logged in users. When users go to http://www.example.com/discourse/ they are being redirecte…

---

## [Discourse Presence no longer showing in composer](https://meta.discourse.org/t/discourse-presence-no-longer-showing-in-composer/82233)

<div class="topic-metadata">

**Author:** [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**댓글:** 1\
**마지막 업데이트:** [3월 5, 2018, 5:52오후 UTC](https://meta.discourse.org/t/discourse-presence-no-longer-showing-in-composer/82233 "2018-03-05T17:52:20Z")

</div>

Discourse Presence - “Who is writing” appears to have a regression - users who are typing no longer appear in the composer. In the image below @supermathie appears at the bottom of the topic, but does not appear in the t…

---

## [A «Title can't have more than 1 emoji» false positive](https://meta.discourse.org/t/a-title-cant-have-more-than-1-emoji-false-positive/82204)

<div class="topic-metadata">

**Author:** [@dmitry\_fedyuk](https://meta.discourse.org/u/dmitry_fedyuk)\
**댓글:** 3\
**마지막 업데이트:** [3월 5, 2018, 2:49오후 UTC](https://meta.discourse.org/t/a-title-cant-have-more-than-1-emoji-false-positive/82204 "2018-03-05T14:49:06Z")

</div>

The title is «What is the difference between Mage::getSingleton() and Mage::getModel() in Magento?»

---

## [Tagging on mobile isn’t working](https://meta.discourse.org/t/tagging-on-mobile-isn-t-working/82155)

<div class="topic-metadata">

**Author:** [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)\
**댓글:** 6\
**마지막 업데이트:** [3월 5, 2018, 9:55오전 UTC](https://meta.discourse.org/t/tagging-on-mobile-isn-t-working/82155 "2018-03-05T09:55:48Z")

</div>

When trying to add a tag, I find that the keyboard doesn’t pop up, and the drop-down is too wide for the screen so doesn’t show any tags: iOS 11, Safari, iPhone X

---

## [Inviting a group to a message does not trigger a notification mail](https://meta.discourse.org/t/inviting-a-group-to-a-message-does-not-trigger-a-notification-mail/50509)

<div class="topic-metadata">

**Author:** [@fefrei](https://meta.discourse.org/u/fefrei)\
**댓글:** 10\
**마지막 업데이트:** [3월 5, 2018, 6:14오전 UTC](https://meta.discourse.org/t/inviting-a-group-to-a-message-does-not-trigger-a-notification-mail/50509 "2018-03-05T06:14:00Z")

</div>

When inviting a group to a message, the confirmation message states that the group has been asked to participate. However, even when group members watch the group inbox, no notification mail is sent.

---

## [Issue adding tags](https://meta.discourse.org/t/issue-adding-tags/81355)

<div class="topic-metadata">

**Author:** [@8BIT](https://meta.discourse.org/u/8BIT)\
**댓글:** 14\
**마지막 업데이트:** [3월 3, 2018, 10:44오전 UTC](https://meta.discourse.org/t/issue-adding-tags/81355 "2018-03-03T10:44:14Z")

</div>

has happened a few times… trying to add a 3-character tag and i can’t seem to do it. the “create new tag” doesn’t always show up.

---

## [Alternative reply by email addresses doesn't allow addresses without reply\_key](https://meta.discourse.org/t/alternative-reply-by-email-addresses-doesnt-allow-addresses-without-reply-key/78255)

<div class="topic-metadata">

**Author:** [@ravor-org](https://meta.discourse.org/u/ravor-org)\
**댓글:** 2\
**마지막 업데이트:** [3월 2, 2018, 4:54오후 UTC](https://meta.discourse.org/t/alternative-reply-by-email-addresses-doesnt-allow-addresses-without-reply-key/78255 "2018-03-02T16:54:05Z")

</div>

Hey there, I tried to configure a mailing-list mirror for several categories. It works fine with the first mail address if find related post with key is disabled but all alternative mail-addresses do require a key. Is i…

---

## [Posts Read Rounding Error](https://meta.discourse.org/t/posts-read-rounding-error/81949)

<div class="topic-metadata">

**Author:** [@JonnyGamer](https://meta.discourse.org/u/JonnyGamer)\
**댓글:** 2\
**마지막 업데이트:** [3월 2, 2018, 10:01오전 UTC](https://meta.discourse.org/t/posts-read-rounding-error/81949 "2018-03-02T10:01:30Z")

</div>

The following shows a simple rounding error When a user has read 1 million posts, discouse displays, “1.0 M posts read” But when 999,500 - 999,999 posts have been read, discourse rounds up and displays 1,000K instead o…

---

## [Group page indexing](https://meta.discourse.org/t/group-page-indexing/81923)

<div class="topic-metadata">

**Author:** [@Stranik](https://meta.discourse.org/u/Stranik)\
**댓글:** 3\
**마지막 업데이트:** [3월 2, 2018, 2:38오전 UTC](https://meta.discourse.org/t/group-page-indexing/81923 "2018-03-02T02:38:55Z")

</div>

Is it possible to index a group page? https://meta.discourse.org/groups In the file https://meta.discourse.org/robots.txt ▶ Summary The page is not closed for indexing As the search engine sees it \</header\> \<div i…

---

## [Category selector is too tall when using "box" style](https://meta.discourse.org/t/category-selector-is-too-tall-when-using-box-style/81826)

<div class="topic-metadata">

**Author:** [@downey](https://meta.discourse.org/u/downey)\
**댓글:** 2\
**마지막 업데이트:** [3월 1, 2018, 10:59오전 UTC](https://meta.discourse.org/t/category-selector-is-too-tall-when-using-box-style/81826 "2018-03-01T10:59:37Z")

</div>

Reproduce: From a default installation with no CSS or other customizations, ensure your site is using “box” for the category style site setting. Ensure you have several categories available from which to choose. Go to …

---

## [Suggested topics category formatting](https://meta.discourse.org/t/suggested-topics-category-formatting/81799)

<div class="topic-metadata">

**Author:** [@Alexander\_Wright](https://meta.discourse.org/u/Alexander_Wright)\
**댓글:** 2\
**마지막 업데이트:** [2월 28, 2018, 5:31오후 UTC](https://meta.discourse.org/t/suggested-topics-category-formatting/81799 "2018-02-28T17:31:56Z")

</div>

Hi, I have some longer category names, and would like them to wrap in the “Suggested Topics” box at the bottom of each topic. This is what I have at the moment: Is there some CSS I can add? I tried this css table wor…

---

## [Upgrade has broken layout of category view](https://meta.discourse.org/t/upgrade-has-broken-layout-of-category-view/81664)

<div class="topic-metadata">

**Author:** [@john-lynch](https://meta.discourse.org/u/john-lynch)\
**댓글:** 6\
**마지막 업데이트:** [2월 28, 2018, 4:15오후 UTC](https://meta.discourse.org/t/upgrade-has-broken-layout-of-category-view/81664 "2018-02-28T16:15:27Z")

</div>

I run a small forum for friends to hang out and discuss stuff. This morning I upgraded Discourse to the latest, and now the category rendering on the main discourse page is busted. I had added a banner image to each cate…

---

## [Receiving "Sorry, an error has occurred." during flagging step of discobot tutorial](https://meta.discourse.org/t/receiving-sorry-an-error-has-occurred-during-flagging-step-of-discobot-tutorial/77233)

<div class="topic-metadata">

**Author:** [@tshenry](https://meta.discourse.org/u/tshenry)\
**댓글:** 6\
**마지막 업데이트:** [2월 28, 2018, 5:55오전 UTC](https://meta.discourse.org/t/receiving-sorry-an-error-has-occurred-during-flagging-step-of-discobot-tutorial/77233 "2018-02-28T05:55:00Z")

</div>

I’ve been testing the new user experience on my Discourse forum and seem to have run into a bug with discobot. Here are the repro steps: Get to the flagging step of the discobot tutorial Click on the flag button in the…

---

## [If all tags are in groups, orphaned "Other Tags" still shows at the bottom of /tags page](https://meta.discourse.org/t/if-all-tags-are-in-groups-orphaned-other-tags-still-shows-at-the-bottom-of-tags-page/81609)

<div class="topic-metadata">

**Author:** [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)\
**댓글:** 3\
**마지막 업데이트:** [2월 28, 2018, 3:31오전 UTC](https://meta.discourse.org/t/if-all-tags-are-in-groups-orphaned-other-tags-still-shows-at-the-bottom-of-tags-page/81609 "2018-02-28T03:31:11Z")

</div>

I just moved all the tags in my discourse site into tag groups. There is still an “Other Tags” heading at the bottom with no tags below it which should not be there. See my tags page and scroll to the bottom and you will…

---

## [Category tags page "(optional) list of allowed tag groups" field selects tags, not groups](https://meta.discourse.org/t/category-tags-page-optional-list-of-allowed-tag-groups-field-selects-tags-not-groups/81701)

<div class="topic-metadata">

**Author:** [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)\
**댓글:** 3\
**마지막 업데이트:** [2월 27, 2018, 8:11오후 UTC](https://meta.discourse.org/t/category-tags-page-optional-list-of-allowed-tag-groups-field-selects-tags-not-groups/81701 "2018-02-27T20:11:32Z")

</div>

See screenshot below. The second field on the category tags tab should allow selection of tag groups, but actually it allows selection of tags just like the field above it. Oops.

---

## [Topic closed temporarily due to community flags overwrites category auto-close timer](https://meta.discourse.org/t/topic-closed-temporarily-due-to-community-flags-overwrites-category-auto-close-timer/77421)

<div class="topic-metadata">

**Author:** [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**댓글:** 2\
**마지막 업데이트:** [2월 27, 2018, 7:35오전 UTC](https://meta.discourse.org/t/topic-closed-temporarily-due-to-community-flags-overwrites-category-auto-close-timer/77421 "2018-02-27T07:35:37Z")

</div>

If a category has an auto-close timer set and a the topic is subsequently closed temporarily due to a large number of community flags, after the topic re-opens the category based auto-close timer is not re-enabled. Repr…

---

## [Out-of-bounds rendering on the all tags drop down on meta](https://meta.discourse.org/t/out-of-bounds-rendering-on-the-all-tags-drop-down-on-meta/81625)

<div class="topic-metadata">

**Author:** [@notriddle](https://meta.discourse.org/u/notriddle)\
**댓글:** 1\
**마지막 업데이트:** [2월 27, 2018, 7:33오전 UTC](https://meta.discourse.org/t/out-of-bounds-rendering-on-the-all-tags-drop-down-on-meta/81625 "2018-02-27T07:33:39Z")

</div>

Look at the :mag: search icon.

---

## [Following a direct link to group activity results in 400 error](https://meta.discourse.org/t/following-a-direct-link-to-group-activity-results-in-400-error/81596)

<div class="topic-metadata">

**Author:** [@HAWK](https://meta.discourse.org/u/HAWK)\
**댓글:** 1\
**마지막 업데이트:** [2월 27, 2018, 5:44오전 UTC](https://meta.discourse.org/t/following-a-direct-link-to-group-activity-results-in-400-error/81596 "2018-02-27T05:44:30Z")

</div>

Following a direct link to a group activity page results in a 400 error. e.g: Plugin authors - Discourse Meta If you navigate via the UI it works fine e.g. /groups \> /groups/plugin\_authors \> /groups/plugin\_authors/act…

---

## [Onebox v1.8.41 is broken :( PR ready :)](https://meta.discourse.org/t/onebox-v1-8-41-is-broken-pr-ready/81572)

<div class="topic-metadata">

**Author:** [@timdiggins](https://meta.discourse.org/u/timdiggins)\
**댓글:** 2\
**마지막 업데이트:** [2월 27, 2018, 1:25오전 UTC](https://meta.discourse.org/t/onebox-v1-8-41-is-broken-pr-ready/81572 "2018-02-27T01:25:02Z")

</div>

v1.8.41 released yesterday was sadly broken (travis, rake, ) Fix broken v1.8.41 by timdiggins · Pull Request #381 · discourse/onebox · GitHub has one version of a fix

---

## [Regression in UI in default theme](https://meta.discourse.org/t/regression-in-ui-in-default-theme/81592)

<div class="topic-metadata">

**Author:** [@vikaskedia](https://meta.discourse.org/u/vikaskedia)\
**댓글:** 8\
**마지막 업데이트:** [2월 26, 2018, 10:59오후 UTC](https://meta.discourse.org/t/regression-in-ui-in-default-theme/81592 "2018-02-26T22:59:06Z")

</div>

On the home page the categories listing is not displayed properly. Here is a screenshot:

---

## ["also referenced in" links](https://meta.discourse.org/t/also-referenced-in-links/81519)

<div class="topic-metadata">

**Author:** [@Bertrand\_Bellenot](https://meta.discourse.org/u/Bertrand_Bellenot)\
**댓글:** 5\
**마지막 업데이트:** [2월 26, 2018, 4:20오후 UTC](https://meta.discourse.org/t/also-referenced-in-links/81519 "2018-02-26T16:20:44Z")

</div>

Hello, One of our user is complaining about a recent change (see topic title). See his original topic: https://root-forum.cern.ch/t/also-referenced-in-links/28055 Are you aware of this? Could you do something to fix i…

---

## [Using no spaces you can make your autobiography scroll very far right. (On mobile, at least)](https://meta.discourse.org/t/using-no-spaces-you-can-make-your-autobiography-scroll-very-far-right-on-mobile-at-least/81495)

<div class="topic-metadata">

**Author:** [@Nindroid](https://meta.discourse.org/u/Nindroid)\
**댓글:** 3\
**마지막 업데이트:** [2월 26, 2018, 12:54오후 UTC](https://meta.discourse.org/t/using-no-spaces-you-can-make-your-autobiography-scroll-very-far-right-on-mobile-at-least/81495 "2018-02-26T12:54:02Z")

</div>

Hi! A better title would be very appreciated. This topic is just to say that if you use textLikeThisButMuchLonger you can make your autobiography scroll to the far right. I don’t really understand this feature, because …

---

## [When tapping on a mention, the usercard has the same capitalization as the mention](https://meta.discourse.org/t/when-tapping-on-a-mention-the-usercard-has-the-same-capitalization-as-the-mention/81507)

<div class="topic-metadata">

**Author:** [@Nindroid](https://meta.discourse.org/u/Nindroid)\
**댓글:** 2\
**마지막 업데이트:** [2월 26, 2018, 12:52오후 UTC](https://meta.discourse.org/t/when-tapping-on-a-mention-the-usercard-has-the-same-capitalization-as-the-mention/81507 "2018-02-26T12:52:34Z")

</div>

Hi. Not a very major bug, but when you tap on a mention, the usercard has the same capitalization. So, for example, @nindroid and @NINDROID are both @Nindroid, but the usercard displays different capitalization for them …

---

## [Smilies in internal links is not shown, bug?](https://meta.discourse.org/t/smilies-in-internal-links-is-not-shown-bug/80818)

<div class="topic-metadata">

**Author:** [@frold](https://meta.discourse.org/u/frold)\
**댓글:** 1\
**마지막 업데이트:** [2월 26, 2018, 11:12오전 UTC](https://meta.discourse.org/t/smilies-in-internal-links-is-not-shown-bug/80818 "2018-02-26T11:12:37Z")

</div>

I dont know how to descripe it. If I link to a internal page, smilies is not shown. I dont know if thats a bug or on purpose? Internal links in a post The original post Just close if this is not a bug…

---

## [Emojis are not rendered from oneboxed topics](https://meta.discourse.org/t/emojis-are-not-rendered-from-oneboxed-topics/81526)

<div class="topic-metadata">

**Author:** [@fhe](https://meta.discourse.org/u/fhe)\
**댓글:** 1\
**마지막 업데이트:** [2월 26, 2018, 10:17오전 UTC](https://meta.discourse.org/t/emojis-are-not-rendered-from-oneboxed-topics/81526 "2018-02-26T10:17:16Z")

</div>

I’ve noticed that when I reference a topic via permalink, the emojis in that quoted topic are not rendered in the preview and the resulting post. I’m using the latest version (v2.0.0.beta3 +140).

---

## [Text glitch on group admin page](https://meta.discourse.org/t/text-glitch-on-group-admin-page/77303)

<div class="topic-metadata">

**Author:** [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)\
**댓글:** 8\
**마지막 업데이트:** [2월 26, 2018, 2:13오전 UTC](https://meta.discourse.org/t/text-glitch-on-group-admin-page/77303 "2018-02-26T02:13:03Z")

</div>

Update: \[PR pending\] When logged in as admin, I see “enter username” on the group editor, but when logged in as a non-admin member, I see “\[en.admin.groups.selector\_placeholder\]”: I’ll see if I can create a PR to fi…

---

## [Cannot backup (connect to postgres) in docker\_dev](https://meta.discourse.org/t/cannot-backup-connect-to-postgres-in-docker-dev/79672)

<div class="topic-metadata">

**Author:** [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**댓글:** 8\
**마지막 업데이트:** [2월 25, 2018, 11:48오후 UTC](https://meta.discourse.org/t/cannot-backup-connect-to-postgres-in-docker-dev/79672 "2018-02-25T23:48:35Z")

</div>

Using the docker\_dev you can’t make a backup from the web interface or from within the container using ./script/discourse backup. Both fail due to postgres permissions issues. This makes using the container to do an impo…

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

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