# Bug

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

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

**Page:** 145

---

## [Topic with a large number of polls gives 429 error](https://meta.discourse.org/t/topic-with-a-large-number-of-polls-gives-429-error/107641)

<div class="topic-metadata">

**Author:** [@bartv](https://meta.discourse.org/u/bartv)\
**댓글:** 5\
**마지막 업데이트:** [2월 27, 2019, 7:20오후 UTC](https://meta.discourse.org/t/topic-with-a-large-number-of-polls-gives-429-error/107641 "2019-02-27T19:20:00Z")

</div>

We use polls as a simple moderator voting mechanism for selecting featured artwork. (We used likes for this in the past, but realized we needed ‘downvotes’ for this too). This voting happens in one large topic, which ha…

---

## [Docker\_manager doesn't accept API keys](https://meta.discourse.org/t/docker-manager-doesnt-accept-api-keys/110040)

<div class="topic-metadata">

**Author:** [@yanokwa](https://meta.discourse.org/u/yanokwa)\
**댓글:** 2\
**마지막 업데이트:** [2월 26, 2019, 6:42오후 UTC](https://meta.discourse.org/t/docker-manager-doesnt-accept-api-keys/110040 "2019-02-26T18:42:31Z")

</div>

I’m trying to mimic the upgradeAll call in the docker\_manager with the following command. curl -X POST "https://example.com/admin/docker/upgrade" \\ -H "Content-type: application/x-www-form-urlencoded" \\ -d "api\_key=12…

---

## [Incorrect colors on topic-map flair](https://meta.discourse.org/t/incorrect-colors-on-topic-map-flair/110129)

<div class="topic-metadata">

**Author:** [@jtbayly](https://meta.discourse.org/u/jtbayly)\
**댓글:** 1\
**마지막 업데이트:** [2월 26, 2019, 5:51오후 UTC](https://meta.discourse.org/t/incorrect-colors-on-topic-map-flair/110129 "2019-02-26T17:51:54Z")

</div>

Continuing from here: I have two groups with the same flair icon but in a different color. My flair shows up as the wrong color in the topic map. Here’s what it looks like when I post: But here is what it looks l…

---

## [Duplicate network calls for admin email sent, skipped, bounced, and received](https://meta.discourse.org/t/duplicate-network-calls-for-admin-email-sent-skipped-bounced-and-received/59882)

<div class="topic-metadata">

**Author:** [@blake](https://meta.discourse.org/u/blake)\
**댓글:** 2\
**마지막 업데이트:** [2월 26, 2019, 4:54오후 UTC](https://meta.discourse.org/t/duplicate-network-calls-for-admin-email-sent-skipped-bounced-and-received/59882 "2019-02-26T16:54:39Z")

</div>

Looks like we are making duplicate network calls inside of Admin Emails for admin/email/sent.json admin/email/skipped.json admin/email/bounced.json admin/email/received.json admin/email/rejected.json

---

## [Moderators can see the "show associated accounts" button but can't use it](https://meta.discourse.org/t/moderators-can-see-the-show-associated-accounts-button-but-cant-use-it/108772)

<div class="topic-metadata">

**Author:** [@Chaboi\_3000](https://meta.discourse.org/u/Chaboi_3000)\
**댓글:** 2\
**마지막 업데이트:** [2월 26, 2019, 12:47오후 UTC](https://meta.discourse.org/t/moderators-can-see-the-show-associated-accounts-button-but-cant-use-it/108772 "2019-02-26T12:47:07Z")

</div>

It seems like moderators can see the “show email”/“show associated accounts” button in user preferences of other users but can’t use it. Returning an error saying it’s forbidden(Error: 403) in the console. Here’s a scree…

---

## [Category allowed tags do not reload with category change](https://meta.discourse.org/t/category-allowed-tags-do-not-reload-with-category-change/95406)

<div class="topic-metadata">

**Author:** [@rlikitarczuk](https://meta.discourse.org/u/rlikitarczuk)\
**댓글:** 25\
**마지막 업데이트:** [2월 25, 2019, 12:03오후 UTC](https://meta.discourse.org/t/category-allowed-tags-do-not-reload-with-category-change/95406 "2019-02-25T12:03:15Z")

</div>

Hi Team! I use different tags or tag groups allowed per category. It works fine if you start a new topic in a right category or choose your first category in a new topic. However once you switch to another category in a…

---

## [Admin - Users: tab switching breaks content](https://meta.discourse.org/t/admin-users-tab-switching-breaks-content/109805)

<div class="topic-metadata">

**Author:** [@Lure](https://meta.discourse.org/u/Lure)\
**댓글:** 6\
**마지막 업데이트:** [2월 25, 2019, 8:51오전 UTC](https://meta.discourse.org/t/admin-users-tab-switching-breaks-content/109805 "2019-02-25T08:51:08Z")

</div>

I have noticed a bug in Admin/Users: if you switch tabs (Active, New, Suspended) quickly, you may end up with list of users populated from previous tab. I noticed this when I was switching from Active to Staged and was c…

---

## [Login Button form attribute](https://meta.discourse.org/t/login-button-form-attribute/109828)

<div class="topic-metadata">

**Author:** [@mcnesium](https://meta.discourse.org/u/mcnesium)\
**댓글:** 2\
**마지막 업데이트:** [2월 23, 2019, 8:29오전 UTC](https://meta.discourse.org/t/login-button-form-attribute/109828 "2019-02-23T08:29:38Z")

</div>

In this commit the login button has been added a form attribute to, but that commit removed it again. This prevents some password managers from auto submitting the login form. Related: https://meta.discourse.org/t/logi…

---

## [CSS auto refresh not working?](https://meta.discourse.org/t/css-auto-refresh-not-working/109658)

<div class="topic-metadata">

**Author:** [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)\
**댓글:** 6\
**마지막 업데이트:** [2월 22, 2019, 9:19오후 UTC](https://meta.discourse.org/t/css-auto-refresh-not-working/109658 "2019-02-22T21:19:42Z")

</div>

Lately I’ve noticed that changes I make to CSS in theme components are not reflected in the site until I perform a hard refresh of the browser. The stylesheet used to be automatically updated when the theme CSS was save…

---

## [Error on Delete User in pending-approvals list](https://meta.discourse.org/t/error-on-delete-user-in-pending-approvals-list/107780)

<div class="topic-metadata">

**Author:** [@schungx](https://meta.discourse.org/u/schungx)\
**댓글:** 3\
**마지막 업데이트:** [2월 22, 2019, 5:07오전 UTC](https://meta.discourse.org/t/error-on-delete-user-in-pending-approvals-list/107780 "2019-02-22T05:07:06Z")

</div>

How to reproduce Setup approvals for new users and email-in support Send emails from some new email account to multiple categories New user is staged, and new posts are created for each, in approvals list Go into approv…

---

## [Unable to message email address to create staged user anymore](https://meta.discourse.org/t/unable-to-message-email-address-to-create-staged-user-anymore/109676)

<div class="topic-metadata">

**Author:** [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen)\
**댓글:** 4\
**마지막 업데이트:** [2월 21, 2019, 5:44오후 UTC](https://meta.discourse.org/t/unable-to-message-email-address-to-create-staged-user-anymore/109676 "2019-02-21T17:44:32Z")

</div>

I’m not sure what is happening here, but as of yesterday I and my colleagues are finding that we are no longer able to message email addresses to create staged users. Type a username in the message addressee box and it a…

---

## [Redis template no longer works for separate data container](https://meta.discourse.org/t/redis-template-no-longer-works-for-separate-data-container/109704)

<div class="topic-metadata">

**Author:** [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**댓글:** 7\
**마지막 업데이트:** [2월 21, 2019, 3:22오전 UTC](https://meta.discourse.org/t/redis-template-no-longer-works-for-separate-data-container/109704 "2019-02-21T03:22:15Z")

</div>

It seems that redis changed the default for protected mode so that if you’ve got a separate data container it no longer allows connections. My caveman solution is to add this to data.yml in the hooks section. after\_re…

---

## [Wrong answerCount value from discourse-solved](https://meta.discourse.org/t/wrong-answercount-value-from-discourse-solved/108845)

<div class="topic-metadata">

**Author:** [@ced](https://meta.discourse.org/u/ced)\
**댓글:** 8\
**마지막 업데이트:** [2월 20, 2019, 2:33오전 UTC](https://meta.discourse.org/t/wrong-answercount-value-from-discourse-solved/108845 "2019-02-20T02:33:09Z")

</div>

The plugin set the value of the answerCount from Question schema.org to the number of replies of the topic. But according to google documentation the answerCount should be 0 is there is no acceptedAnswer or suggestedAnsw…

---

## [Moderators can see the "Force Browser Refresh" but can't use it](https://meta.discourse.org/t/moderators-can-see-the-force-browser-refresh-but-cant-use-it/109523)

<div class="topic-metadata">

**Author:** [@Chaboi\_3000](https://meta.discourse.org/u/Chaboi_3000)\
**댓글:** 3\
**마지막 업데이트:** [2월 19, 2019, 1:10오후 UTC](https://meta.discourse.org/t/moderators-can-see-the-force-browser-refresh-but-cant-use-it/109523 "2019-02-19T13:10:36Z")

</div>

As you can see below, moderators can see the Force Browser Refresh, and “use” it, but it doesn’t actually work. The console returns a 404 error when you click the button, but shows a message, Message sent to all clients. …

---

## [\`rake uploads:migrate\_to\_s3\` needs some love](https://meta.discourse.org/t/rake-uploads-migrate-to-s3-needs-some-love/109497)

<div class="topic-metadata">

**Author:** [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**댓글:** 3\
**마지막 업데이트:** [2월 19, 2019, 12:17오전 UTC](https://meta.discourse.org/t/rake-uploads-migrate-to-s3-needs-some-love/109497 "2019-02-19T00:17:55Z")

</div>

The uploads:migrate\_to\_s3 rake task could use some attention. There is no GlobalSetting.use\_s3?, but a GlobalSetting.use\_s3 and the ENV variables have changed, as DISCOURSE\_S3\_BUCKET has been replaced by DISCOURSE\_S3\_U…

---

## [Moderators can see the move posts to PM button but can't use it](https://meta.discourse.org/t/moderators-can-see-the-move-posts-to-pm-button-but-cant-use-it/108737)

<div class="topic-metadata">

**Author:** [@Chaboi\_3000](https://meta.discourse.org/u/Chaboi_3000)\
**댓글:** 3\
**마지막 업데이트:** [2월 18, 2019, 6:09오전 UTC](https://meta.discourse.org/t/moderators-can-see-the-move-posts-to-pm-button-but-cant-use-it/108737 "2019-02-18T06:09:12Z")

</div>

There seems to be a bug where moderators can see the option to move posts to a new PM, but can’t actually use it. Isn’t it reasonable to just remove the option to moderators instead? Here’s the image of what happens if y…

---

## [Restarting container when internet is down causes discourse to fail](https://meta.discourse.org/t/restarting-container-when-internet-is-down-causes-discourse-to-fail/42615)

<div class="topic-metadata">

**Author:** [@carbo](https://meta.discourse.org/u/carbo)\
**댓글:** 8\
**마지막 업데이트:** [2월 18, 2019, 3:01오전 UTC](https://meta.discourse.org/t/restarting-container-when-internet-is-down-causes-discourse-to-fail/42615 "2019-02-18T03:01:27Z")

</div>

It seems that if you have an intranet discourse site, even though it might have internet access, will no longer work if two factors come into play: Your internet access is down (for whatever reason) You decide to resta…

---

## [I can not create a category](https://meta.discourse.org/t/i-can-not-create-a-category/109188)

<div class="topic-metadata">

**Author:** [@Marija\_Babovic](https://meta.discourse.org/u/Marija_Babovic)\
**댓글:** 6\
**마지막 업데이트:** [2월 14, 2019, 11:58오후 UTC](https://meta.discourse.org/t/i-can-not-create-a-category/109188 "2019-02-14T23:58:36Z")

</div>

When I want to create a category, nothing is happening, please see video: https://youtu.be/YYf4vHn2BfU

---

## [Username autocomplete does not go away after typing comma](https://meta.discourse.org/t/username-autocomplete-does-not-go-away-after-typing-comma/109084)

<div class="topic-metadata">

**Author:** [@jsha](https://meta.discourse.org/u/jsha)\
**댓글:** 3\
**마지막 업데이트:** [2월 14, 2019, 1:07오후 UTC](https://meta.discourse.org/t/username-autocomplete-does-not-go-away-after-typing-comma/109084 "2019-02-14T13:07:27Z")

</div>

Steps to reproduce: In a topic, type “Hi @username,\<enter\>” Expected result: Text box contains “Hi @username,” and a newline. Also, the username autocompletion box should go away after typing the comma. Actual result…

---

## [vBulletin v4 importer list conversion breaks markup](https://meta.discourse.org/t/vbulletin-v4-importer-list-conversion-breaks-markup/108979)

<div class="topic-metadata">

**Author:** [@outofcontrol](https://meta.discourse.org/u/outofcontrol)\
**댓글:** 4\
**마지막 업데이트:** [2월 14, 2019, 12:44오전 UTC](https://meta.discourse.org/t/vbulletin-v4-importer-list-conversion-breaks-markup/108979 "2019-02-14T00:44:24Z")

</div>

When importing from vBulletin v4 to Discourse, the following markup gets converted incorrectly, resulting in a rather unsightly post in Discourse: vBulletin post source code (which renders correctly for us in VB \[LIST\]…

---

## [Category selection broken for "Reply as new topic"](https://meta.discourse.org/t/category-selection-broken-for-reply-as-new-topic/108976)

<div class="topic-metadata">

**Author:** [@supermathie](https://meta.discourse.org/u/supermathie)\
**댓글:** 1\
**마지막 업데이트:** [2월 13, 2019, 11:37오전 UTC](https://meta.discourse.org/t/category-selection-broken-for-reply-as-new-topic/108976 "2019-02-13T11:37:17Z")

</div>

To reproduce: Select a bit of text and Quote: Choose to Reply as linked topic Change the category from the original one (note that without searching, only the current category is listed): To so…

---

## [Accidental slide menu on iPhone when swiping right](https://meta.discourse.org/t/accidental-slide-menu-on-iphone-when-swiping-right/108822)

<div class="topic-metadata">

**Author:** [@bartv](https://meta.discourse.org/u/bartv)\
**댓글:** 8\
**마지막 업데이트:** [2월 12, 2019, 5:30오전 UTC](https://meta.discourse.org/t/accidental-slide-menu-on-iphone-when-swiping-right/108822 "2019-02-12T05:30:57Z")

</div>

I just swiped right on my iPhone and got the hamburger menu instead of the previous page. It took a little figuring out under which conditions this happened, but I can reproduce as follows: Tap and hold on the far left…

---

## [Migrate:multisite fails on second site when migrating from scratch](https://meta.discourse.org/t/migrate-multisite-fails-on-second-site-when-migrating-from-scratch/108559)

<div class="topic-metadata">

**Author:** [@jamesh](https://meta.discourse.org/u/jamesh)\
**댓글:** 13\
**마지막 업데이트:** [2월 12, 2019, 3:38오전 UTC](https://meta.discourse.org/t/migrate-multisite-fails-on-second-site-when-migrating-from-scratch/108559 "2019-02-12T03:38:33Z")

</div>

I’ve just started to spin up our discourse instance, and when using multisite:migrate it failed on the second database: This may be caused by the changes in 40fa96777ddad4698df20d6b8a61afcf87743ed7, where a refactorin…

---

## [Moving posts to new PM did not invite all participants](https://meta.discourse.org/t/moving-posts-to-new-pm-did-not-invite-all-participants/108714)

<div class="topic-metadata">

**Author:** [@danekhollas](https://meta.discourse.org/u/danekhollas)\
**댓글:** 14\
**마지막 업데이트:** [2월 11, 2019, 12:59오후 UTC](https://meta.discourse.org/t/moving-posts-to-new-pm-did-not-invite-all-participants/108714 "2019-02-11T12:59:34Z")

</div>

Hi all, let me just preface the new interface for moving posts around is great. :sunny: But, I got recently burnt when moving posts from a topic to a new PM. I moved around 6 post from 3 different people (one of them m…

---

## [Moving a topic doesn't update post's toolbar with relevant tool options](https://meta.discourse.org/t/moving-a-topic-doesnt-update-posts-toolbar-with-relevant-tool-options/108762)

<div class="topic-metadata">

**Author:** [@RobMeade](https://meta.discourse.org/u/RobMeade)\
**댓글:** 0\
**마지막 업데이트:** [2월 9, 2019, 7:58오후 UTC](https://meta.discourse.org/t/moving-a-topic-doesnt-update-posts-toolbar-with-relevant-tool-options/108762 "2019-02-09T19:58:13Z")

</div>

Hi, I noticed recently that if you have a category which does not use the Solved feature, but then edit the topic to be placed into a category that does, the toolbars (expanded from the ellipsis next to the Reply button…

---

## [Uploading a white SVG logo gets it styles removed and becomes black](https://meta.discourse.org/t/uploading-a-white-svg-logo-gets-it-styles-removed-and-becomes-black/108575)

<div class="topic-metadata">

**Author:** [@viktorsmari](https://meta.discourse.org/u/viktorsmari)\
**댓글:** 4\
**마지막 업데이트:** [2월 7, 2019, 11:09오전 UTC](https://meta.discourse.org/t/uploading-a-white-svg-logo-gets-it-styles-removed-and-becomes-black/108575 "2019-02-07T11:09:46Z")

</div>

I am uploading an SVG logo which has these styles included: \<style type="text/css"\> .st0{fill:#FFFFFF;} \</style\> When I view the image after upload I don’t see this section, and the logo becomes black. (The previous S…

---

## [Report charts don't display final week of data](https://meta.discourse.org/t/report-charts-dont-display-final-week-of-data/108497)

<div class="topic-metadata">

**Author:** [@jtbayly](https://meta.discourse.org/u/jtbayly)\
**댓글:** 1\
**마지막 업데이트:** [2월 6, 2019, 2:40오후 UTC](https://meta.discourse.org/t/report-charts-dont-display-final-week-of-data/108497 "2019-02-06T14:40:30Z")

</div>

Go to any report and set your start and end date 8 weeks apart. View the data. So far so good. Now switch to graph form. The last full week will not get a data point on the chart.

---

## [Oauth2 json avatar path not working](https://meta.discourse.org/t/oauth2-json-avatar-path-not-working/108349)

<div class="topic-metadata">

**Author:** [@kueda](https://meta.discourse.org/u/kueda)\
**댓글:** 3\
**마지막 업데이트:** [2월 5, 2019, 6:26오후 UTC](https://meta.discourse.org/t/oauth2-json-avatar-path-not-working/108349 "2019-02-05T18:26:07Z")

</div>

I’m trying to get the oauth2 basic plugin working on a trial version of hosted Discourse. Everything seems to work, except for the oauth2 json avatar path, so I suspect I’m just doing something wrong. The response to the…

---

## [In narrow window sizes, New Topic button has no ARIA description](https://meta.discourse.org/t/in-narrow-window-sizes-new-topic-button-has-no-aria-description/108374)

<div class="topic-metadata">

**Author:** [@dfabulich](https://meta.discourse.org/u/dfabulich)\
**댓글:** 3\
**마지막 업데이트:** [2월 5, 2019, 11:34오전 UTC](https://meta.discourse.org/t/in-narrow-window-sizes-new-topic-button-has-no-aria-description/108374 "2019-02-05T11:34:07Z")

</div>

Resize your browser window to be slightly less than 850px wide. The “+ New Topic” button will collapse to a + button. Using a screen reader like macOS VoiceOver, select the button. (I’ve also reproduced this in JAWS on …

---

## [Site header icons don't use header primary color](https://meta.discourse.org/t/site-header-icons-dont-use-header-primary-color/108093)

<div class="topic-metadata">

**Author:** [@fhe](https://meta.discourse.org/u/fhe)\
**댓글:** 7\
**마지막 업데이트:** [2월 4, 2019, 3:47오후 UTC](https://meta.discourse.org/t/site-header-icons-dont-use-header-primary-color/108093 "2019-02-04T15:47:15Z")

</div>

I’ve installed v2.3.0.beta1 and noticed a ux regression. The site header icons don’t use the header primary color specified in the color scheme:

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

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