# Bug

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

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

**Page:** 158

---

## ['All Groups' option leads to Access Denied page](https://meta.discourse.org/t/all-groups-option-leads-to-access-denied-page/88464)

<div class="topic-metadata">

**Author:** [@Karl\_Romanowski](https://meta.discourse.org/u/Karl_Romanowski)\
**댓글:** 2\
**마지막 업데이트:** [5월 28, 2018, 3:35오전 UTC](https://meta.discourse.org/t/all-groups-option-leads-to-access-denied-page/88464 "2018-05-28T03:35:56Z")

</div>

When ‘enable group directory’ is unchecked and a user lands on a group page via Dev Tracker there is a dropdown with other groups: Selecting ‘all groups’ sends the user to /groups which shows them ‘Access Denied’ Ex…

---

## [Cannot undo (ctrl+z) in create new topic view](https://meta.discourse.org/t/cannot-undo-ctrl-z-in-create-new-topic-view/88387)

<div class="topic-metadata">

**Author:** [@TheBestPessimist](https://meta.discourse.org/u/TheBestPessimist)\
**댓글:** 1\
**마지막 업데이트:** [5월 24, 2018, 4:29오후 UTC](https://meta.discourse.org/t/cannot-undo-ctrl-z-in-create-new-topic-view/88387 "2018-05-24T16:29:16Z")

</div>

As mentioned here: I think there’s a problem with undoing in the topic creator: after i click a button (eg. insert buleted list, bold, italic, etc.) i cannot undo that with a “ctrl+z”

---

## [Unable to revert changes under Admin \> Text Content](https://meta.discourse.org/t/unable-to-revert-changes-under-admin-text-content/88341)

<div class="topic-metadata">

**Author:** [@sebastien](https://meta.discourse.org/u/sebastien)\
**댓글:** 0\
**마지막 업데이트:** [5월 24, 2018, 5:27오전 UTC](https://meta.discourse.org/t/unable-to-revert-changes-under-admin-text-content/88341 "2018-05-24T05:27:25Z")

</div>

Hi Guys, When I try to revert a change on a text field, I get an error saying “translation missing: en.js.trust\_level” If I click on “Save”, it saves “translation missing: en.js.trust\_level.” Not really big deal.

---

## [Return of the &hellip?](https://meta.discourse.org/t/return-of-the-hellip/85405)

<div class="topic-metadata">

**Author:** [@Benjol](https://meta.discourse.org/u/Benjol)\
**댓글:** 1\
**마지막 업데이트:** [5월 23, 2018, 5:05오후 UTC](https://meta.discourse.org/t/return-of-the-hellip/85405 "2018-05-23T17:05:00Z")

</div>

Continuing the discussion from &hellip is shown as text in choosing the category: I think this bug persists in the mouseover on the “Select a category”…

---

## [Toggle menu in Composer](https://meta.discourse.org/t/toggle-menu-in-composer/87172)

<div class="topic-metadata">

**Author:** [@jerry0](https://meta.discourse.org/u/jerry0)\
**댓글:** 4\
**마지막 업데이트:** [5월 23, 2018, 4:27오후 UTC](https://meta.discourse.org/t/toggle-menu-in-composer/87172 "2018-05-23T16:27:09Z")

</div>

I’ve been struggling to understand the toggle menu in composer. The one at the top, next to the detail indicating what is being composed: Having looked at it in detail I’ve realised that there are some buggy problems…

---

## [Onebox relative icon URL bug](https://meta.discourse.org/t/onebox-relative-icon-url-bug/88196)

<div class="topic-metadata">

**Author:** [@dfabulich](https://meta.discourse.org/u/dfabulich)\
**댓글:** 2\
**마지막 업데이트:** [5월 23, 2018, 12:49오후 UTC](https://meta.discourse.org/t/onebox-relative-icon-url-bug/88196 "2018-05-23T12:49:52Z")

</div>

This onebox has a white space in the upper left corner on Chrome, or, on Firefox, it shows a broken image icon. The document contains a \<link\> tag like this: \<link href="icon.jpg?hash=daf03254ad467bb13b79bb3b5a637832…

---

## [How To Fix / Remove All Facebook Logins For Updated AppID](https://meta.discourse.org/t/how-to-fix-remove-all-facebook-logins-for-updated-appid/87831)

<div class="topic-metadata">

**Author:** [@yyhmsg](https://meta.discourse.org/u/yyhmsg)\
**댓글:** 7\
**마지막 업데이트:** [5월 23, 2018, 12:34오후 UTC](https://meta.discourse.org/t/how-to-fix-remove-all-facebook-logins-for-updated-appid/87831 "2018-05-23T12:34:23Z")

</div>

Due to recent fb changes, I created a new app for my forum facebook login (one that didn’t include unnecessary permissions as I had setup before). Upon adding this and trying to login I get: Oops The software powering…

---

## [User.set\_automatic\_groups is not called for all social logins](https://meta.discourse.org/t/user-set-automatic-groups-is-not-called-for-all-social-logins/81579)

<div class="topic-metadata">

**Author:** [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**댓글:** 3\
**마지막 업데이트:** [5월 23, 2018, 6:34오전 UTC](https://meta.discourse.org/t/user-set-automatic-groups-is-not-called-for-all-social-logins/81579 "2018-05-23T06:34:19Z")

</div>

Our Google login provider has the following code: def after\_create\_account(user, auth) data = auth\[:extra\_data\] GoogleUserInfo.create({ user\_id: user.id }.merge(data)) if auth\[:email\_valid\].to\_s == 'true' && data\[…

---

## [Canned Replies CSS (desktop) Highlighting Issue](https://meta.discourse.org/t/canned-replies-css-desktop-highlighting-issue/88122)

<div class="topic-metadata">

**Author:** [@RobMeade](https://meta.discourse.org/u/RobMeade)\
**댓글:** 6\
**마지막 업데이트:** [5월 23, 2018, 1:58오전 UTC](https://meta.discourse.org/t/canned-replies-css-desktop-highlighting-issue/88122 "2018-05-23T01:58:07Z")

</div>

Hi, I’ve noticed an issue we have on the use of canned replies. When you place the mouse over the individual canned reply, it is highlighted, unfortunately, this appears to be using the same colour as that of the chara…

---

## [Staged users remain staged even after activation and must be manually unstaged](https://meta.discourse.org/t/staged-users-remain-staged-even-after-activation-and-must-be-manually-unstaged/70714)

<div class="topic-metadata">

**Author:** [@schungx](https://meta.discourse.org/u/schungx)\
**댓글:** 11\
**마지막 업데이트:** [5월 22, 2018, 3:45오후 UTC](https://meta.discourse.org/t/staged-users-remain-staged-even-after-activation-and-must-be-manually-unstaged/70714 "2018-05-22T15:45:58Z")

</div>

This is similar to: except that when a user is staged, meaning that it came in via email in, and after their account is activated (either by the admin or by sending out an activation email which they reacted to), they…

---

## [Updating deleted post through API returns Internal Server Error](https://meta.discourse.org/t/updating-deleted-post-through-api-returns-internal-server-error/75839)

<div class="topic-metadata">

**Author:** [@simon](https://meta.discourse.org/u/simon)\
**댓글:** 2\
**마지막 업데이트:** [5월 21, 2018, 1:02오전 UTC](https://meta.discourse.org/t/updating-deleted-post-through-api-returns-internal-server-error/75839 "2018-05-21T01:02:40Z")

</div>

Attempting to update a deleted post through the API returns a 500 error. The error is undefined method 'id' for nil:NilClass. It’s coming from web\_hook.rb. The problem is that when publishing with the All Users API key …

---

## [When groups filter has no matches, filter field disappears](https://meta.discourse.org/t/when-groups-filter-has-no-matches-filter-field-disappears/87858)

<div class="topic-metadata">

**Author:** [@Stephen](https://meta.discourse.org/u/Stephen)\
**댓글:** 3\
**마지막 업데이트:** [5월 18, 2018, 7:30오후 UTC](https://meta.discourse.org/t/when-groups-filter-has-no-matches-filter-field-disappears/87858 "2018-05-18T19:30:31Z")

</div>

When filtering the members of a group by username or email using the field above the users list, the following happens: enter text which matches no users: The filter field disappears, and the message improperly s…

---

## [Adding words to Watched Words doesn't check for duplicates](https://meta.discourse.org/t/adding-words-to-watched-words-doesnt-check-for-duplicates/84393)

<div class="topic-metadata">

**Author:** [@barreeeiroo](https://meta.discourse.org/u/barreeeiroo)\
**댓글:** 2\
**마지막 업데이트:** [5월 18, 2018, 8:50오전 UTC](https://meta.discourse.org/t/adding-words-to-watched-words-doesnt-check-for-duplicates/84393 "2018-05-18T08:50:27Z")

</div>

Adding words to “Watched Words” admin setting doesn’t check for duplicated For example, I can censor “Tururu”, and censor “tururu” and a double “Tururu” appears However, if I refresh the page it gets fixed I guess the…

---

## [Incorrect message key in temporarily closed topic](https://meta.discourse.org/t/incorrect-message-key-in-temporarily-closed-topic/87773)

<div class="topic-metadata">

**Author:** [@supermathie](https://meta.discourse.org/u/supermathie)\
**댓글:** 1\
**마지막 업데이트:** [5월 18, 2018, 8:34오전 UTC](https://meta.discourse.org/t/incorrect-message-key-in-temporarily-closed-topic/87773 "2018-05-18T08:34:01Z")

</div>

Temporarily closing a topic in a category set to ‘Close X hours after last post’ leads to an incorrect message key: Reproduction steps: have category with auto-close-based-on-last-post settings such as: create topic…

---

## [Plugin-outlet incorrectly handles multiple plugins at the same outlet](https://meta.discourse.org/t/plugin-outlet-incorrectly-handles-multiple-plugins-at-the-same-outlet/32206)

<div class="topic-metadata">

**Author:** [@dmitry\_fedyuk](https://meta.discourse.org/u/dmitry_fedyuk)\
**댓글:** 21\
**마지막 업데이트:** [5월 18, 2018, 4:32오전 UTC](https://meta.discourse.org/t/plugin-outlet-incorrectly-handles-multiple-plugins-at-the-same-outlet/32206 "2018-05-18T04:32:13Z")

</div>

Wrong code is: Must be Ember.ContainerView.extend({tagName: ''}) instead of Ember.ContainerView. The current wrong code breaks HTML markup in cases where HTML syntax does not allow wrapper DIV tag. An example is adm…

---

## [When Discourse is first loaded, suppressed category topics still show](https://meta.discourse.org/t/when-discourse-is-first-loaded-suppressed-category-topics-still-show/82691)

<div class="topic-metadata">

**Author:** [@dd36](https://meta.discourse.org/u/dd36)\
**댓글:** 2\
**마지막 업데이트:** [5월 18, 2018, 4:22오전 UTC](https://meta.discourse.org/t/when-discourse-is-first-loaded-suppressed-category-topics-still-show/82691 "2018-05-18T04:22:03Z")

</div>

Wasn’t sure whether to report this as a bug. I’ve noticed that when Discourse is first loaded, it shows topics from categories that should be suppressed from Latest. Then when I refresh, it shows correctly. Is this a …

---

## [Wrong assigned username in activity list](https://meta.discourse.org/t/wrong-assigned-username-in-activity-list/73816)

<div class="topic-metadata">

**Author:** [@Ivan\_Rapekas](https://meta.discourse.org/u/Ivan_Rapekas)\
**댓글:** 4\
**마지막 업데이트:** [5월 18, 2018, 3:35오전 UTC](https://meta.discourse.org/t/wrong-assigned-username-in-activity-list/73816 "2018-05-18T03:35:24Z")

</div>

I am a staff user. When I assign somebody to topic using discourse-assign plugin, I always see myself as an assigned person in my activity list (marked as orange twice): Underlined mention should be a username who ha…

---

## [Icon Type is Incorrectly Reported in manifest.json for Android](https://meta.discourse.org/t/icon-type-is-incorrectly-reported-in-manifest-json-for-android/71961)

<div class="topic-metadata">

**Author:** [@FelicianoTech](https://meta.discourse.org/u/FelicianoTech)\
**댓글:** 10\
**마지막 업데이트:** [5월 17, 2018, 8:05오후 UTC](https://meta.discourse.org/t/icon-type-is-incorrectly-reported-in-manifest-json-for-android/71961 "2018-05-17T20:05:32Z")

</div>

In every Discourse site’s manifest.json file, a list of icons are shown. For each icon, a “type” is provided which looks to be the icon’s mime type. Problem is, regardless of which format the icon actually is (ico, jpeg,…

---

## [Group Inboxes in User Messages](https://meta.discourse.org/t/group-inboxes-in-user-messages/86787)

<div class="topic-metadata">

**Author:** [@BlackKnob](https://meta.discourse.org/u/BlackKnob)\
**댓글:** 18\
**마지막 업데이트:** [5월 17, 2018, 4:45오후 UTC](https://meta.discourse.org/t/group-inboxes-in-user-messages/86787 "2018-05-17T16:45:53Z")

</div>

Is there a way to make group inboxes visible in personal messages? It already works like this in admin accounts, but regular members don’t have this option. It there a setting to turn it on?

---

## [Blank upgrade page after updating docker manager to 2.0.0.beta10](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713)

<div class="topic-metadata">

**Author:** [@fhe](https://meta.discourse.org/u/fhe)\
**댓글:** 15\
**마지막 업데이트:** [5월 17, 2018, 4:14오후 UTC](https://meta.discourse.org/t/blank-upgrade-page-after-updating-docker-manager-to-2-0-0-beta10/87713 "2018-05-17T16:14:28Z")

</div>

I’ve just tried to update from Discourse 2.0.0 beta 9 to beta 10 and I’m now faced with a blank page on /admin/upgrade after updating docker manager. I’ve tried to restart the app via ./launcher which didn’t trigger …

---

## [Orientation fix missing in latest stable](https://meta.discourse.org/t/orientation-fix-missing-in-latest-stable/79695)

<div class="topic-metadata">

**Author:** [@RGJ](https://meta.discourse.org/u/RGJ)\
**댓글:** 6\
**마지막 업데이트:** [5월 17, 2018, 12:56오후 UTC](https://meta.discourse.org/t/orientation-fix-missing-in-latest-stable/79695 "2018-05-17T12:56:42Z")

</div>

Saturday morning is always a good moment to research weird problems. I suddenly see things that I’ve overlooked for a long time. The image orientation fix seems to be missing in the stable branch. Can you please, plea…

---

## [Docker Manager "Reset Upgrade" Button is broken](https://meta.discourse.org/t/docker-manager-reset-upgrade-button-is-broken/86910)

<div class="topic-metadata">

**Author:** [@carlokok](https://meta.discourse.org/u/carlokok)\
**댓글:** 5\
**마지막 업데이트:** [5월 17, 2018, 9:27오전 UTC](https://meta.discourse.org/t/docker-manager-reset-upgrade-button-is-broken/86910 "2018-05-17T09:27:17Z")

</div>

Earlier today I started an update of a plugin (discourse-assign) and all it pritned was the header (“this can take a while”). after 10 minutes it still said the same so I tried the reset button, which didn’t do anything.…

---

## [Trust level 4 users cannot set topic timers anymore](https://meta.discourse.org/t/trust-level-4-users-cannot-set-topic-timers-anymore/78638)

<div class="topic-metadata">

**Author:** [@rizka](https://meta.discourse.org/u/rizka)\
**댓글:** 13\
**마지막 업데이트:** [5월 16, 2018, 11:48오후 UTC](https://meta.discourse.org/t/trust-level-4-users-cannot-set-topic-timers-anymore/78638 "2018-05-16T23:48:10Z")

</div>

When we upgraded to 1.9 the trust level 4 users seem to have lost their ability to set timers for topics. So they cannot auto-close topics or close them temporarily. They can close them in a regular manner, though. T…

---

## [Custom footer disappears in group -\> activity -\> topics](https://meta.discourse.org/t/custom-footer-disappears-in-group-activity-topics/87575)

<div class="topic-metadata">

**Author:** [@sarahann](https://meta.discourse.org/u/sarahann)\
**댓글:** 1\
**마지막 업데이트:** [5월 16, 2018, 11:36오후 UTC](https://meta.discourse.org/t/custom-footer-disappears-in-group-activity-topics/87575 "2018-05-16T23:36:35Z")

</div>

I am not sure if this behavior is intentional or not. Prerequisites: Have a custom footer in your Discourse (mine is defined in my theme /common/footer.html) Have a group in your Discourse Repro steps: Click on the…

---

## [Topic Timer autodelete option usable even if I don't have appropriate permissions](https://meta.discourse.org/t/topic-timer-autodelete-option-usable-even-if-i-dont-have-appropriate-permissions/87674)

<div class="topic-metadata">

**Author:** [@Drew\_Warwick](https://meta.discourse.org/u/Drew_Warwick)\
**댓글:** 1\
**마지막 업데이트:** [5월 16, 2018, 10:43오후 UTC](https://meta.discourse.org/t/topic-timer-autodelete-option-usable-even-if-i-dont-have-appropriate-permissions/87674 "2018-05-16T22:43:23Z")

</div>

If I click the wrench at the bottom of a topic, and select Topic Timer, I see the option for auto-delete even though I don’t have the appropriate permissions to delete a topic. (Weirdly, it even lets me schedule the auto…

---

## [PMs should not show up in dashboard "Top Referred Topics"](https://meta.discourse.org/t/pms-should-not-show-up-in-dashboard-top-referred-topics/87646)

<div class="topic-metadata">

**Author:** [@supermathie](https://meta.discourse.org/u/supermathie)\
**댓글:** 1\
**마지막 업데이트:** [5월 16, 2018, 2:56오후 UTC](https://meta.discourse.org/t/pms-should-not-show-up-in-dashboard-top-referred-topics/87646 "2018-05-16T14:56:18Z")

</div>

Right now it’s possible for PMs to show up in Top Referred Topics - we should prevent that.

---

## [Subfolder parameter not used when rendering images in /admin/upgrade](https://meta.discourse.org/t/subfolder-parameter-not-used-when-rendering-images-in-admin-upgrade/87348)

<div class="topic-metadata">

**Author:** [@vikaskedia](https://meta.discourse.org/u/vikaskedia)\
**댓글:** 2\
**마지막 업데이트:** [5월 16, 2018, 6:51오전 UTC](https://meta.discourse.org/t/subfolder-parameter-not-used-when-rendering-images-in-admin-upgrade/87348 "2018-05-16T06:51:32Z")

</div>

The URL for the discourse is: https://www.example.com/folder-name/admin/upgrade The images that are not rendering have the URL: https://www.example.com/plugins/docker\_manager/images/font-awesome-check-circle.png

---

## [Clicking on plugin "Settings" no longer goes to the settings view filtered by only that plugin's settings](https://meta.discourse.org/t/clicking-on-plugin-settings-no-longer-goes-to-the-settings-view-filtered-by-only-that-plugins-settings/87545)

<div class="topic-metadata">

**Author:** [@supermathie](https://meta.discourse.org/u/supermathie)\
**댓글:** 2\
**마지막 업데이트:** [5월 16, 2018, 6:27오전 UTC](https://meta.discourse.org/t/clicking-on-plugin-settings-no-longer-goes-to-the-settings-view-filtered-by-only-that-plugins-settings/87545 "2018-05-16T06:27:14Z")

</div>

Clicking on ‘Settings’ used to show a filtered view of Settings that restricted the items shown to just that plugin, that behaviour no longer happens. It just goes to e.g. https://try.discourse.org/admin/site\_setting…

---

## ["You've notified but they can't see" message pops up too soon](https://meta.discourse.org/t/youve-notified-but-they-cant-see-message-pops-up-too-soon/68963)

<div class="topic-metadata">

**Author:** [@barryvan](https://meta.discourse.org/u/barryvan)\
**댓글:** 5\
**마지막 업데이트:** [5월 15, 2018, 8:23오전 UTC](https://meta.discourse.org/t/youve-notified-but-they-cant-see-message-pops-up-too-soon/68963 "2018-05-15T08:23:44Z")

</div>

When replying to a topic in a restricted category, Discourse (very intelligently) shows you a warning if you @-mention someone who won’t be able to see the topic. It does, however, seem to be a little eager in doing so. …

---

## [Search Icon can appear outside drop-downs](https://meta.discourse.org/t/search-icon-can-appear-outside-drop-downs/87118)

<div class="topic-metadata">

**Author:** [@sarahann](https://meta.discourse.org/u/sarahann)\
**댓글:** 3\
**마지막 업데이트:** [5월 15, 2018, 7:33오전 UTC](https://meta.discourse.org/t/search-icon-can-appear-outside-drop-downs/87118 "2018-05-15T07:33:06Z")

</div>

Repro Steps: go to https://meta.discourse.org/c/feature ( I have the “material design theme” enabled) click the ‘all tags’ button 2a. toggle the button multiple times Notice the search icon fly in from the side click…

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

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