# Bug

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

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

**Page:** 183

---

## [500 error SSO continuation](https://meta.discourse.org/t/500-error-sso-continuation/60075)

<div class="topic-metadata">

**Author:** [@jesselperry](https://meta.discourse.org/u/jesselperry)\
**댓글:** 7\
**마지막 업데이트:** [3월 29, 2017, 12:58오후 UTC](https://meta.discourse.org/t/500-error-sso-continuation/60075 "2017-03-29T12:58:15Z")

</div>

Continuing the discussion from Reports of user logged out twice today - related to recent auth tokens changes?: For what it’s worth, I just had this error myself with beta 8 release (which was after your most recent fix…

---

## [About topic still counts towards total votes](https://meta.discourse.org/t/about-topic-still-counts-towards-total-votes/59033)

<div class="topic-metadata">

**Author:** [@erlend\_sh](https://meta.discourse.org/u/erlend_sh)\
**댓글:** 4\
**마지막 업데이트:** [3월 29, 2017, 12:12오후 UTC](https://meta.discourse.org/t/about-topic-still-counts-towards-total-votes/59033 "2017-03-29T12:12:53Z")

</div>

Happy to see that the About topic can no longer be voted on, but it appears the vote that I applied to prior to this change still remains, and so the About topic is counting towards my total number of votes.

---

## [Discourse Cookie Store: Omniauth callback sessions are nil](https://meta.discourse.org/t/discourse-cookie-store-omniauth-callback-sessions-are-nil/58096)

<div class="topic-metadata">

**Author:** [@leo.proctor](https://meta.discourse.org/u/leo.proctor)\
**댓글:** 3\
**마지막 업데이트:** [3월 29, 2017, 9:09오전 UTC](https://meta.discourse.org/t/discourse-cookie-store-omniauth-callback-sessions-are-nil/58096 "2017-03-29T09:09:16Z")

</div>

In my custom oauth2 login I’m saving some session values. It was working fine till I recently pulled the latest code from branch tests-passed and noticed that session is always nil in omniauth\_callback\_controller.rb de…

---

## [Double title now (without edit)](https://meta.discourse.org/t/double-title-now-without-edit/60015)

<div class="topic-metadata">

**Author:** [@SidV](https://meta.discourse.org/u/SidV)\
**댓글:** 2\
**마지막 업데이트:** [3월 28, 2017, 9:05오후 UTC](https://meta.discourse.org/t/double-title-now-without-edit/60015 "2017-03-28T21:05:43Z")

</div>

I think this is a consecuence from topic title duplicated in header’s bug. Steps to repro: Open some topic with at least 3 messages (example). Go to message number 3 (or 5, or 10, or whatever you want). Click on tit…

---

## [Facebook login not working?](https://meta.discourse.org/t/facebook-login-not-working/60010)

<div class="topic-metadata">

**Author:** [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)\
**댓글:** 1\
**마지막 업데이트:** [3월 28, 2017, 9:52오전 UTC](https://meta.discourse.org/t/facebook-login-not-working/60010 "2017-03-28T09:52:52Z")

</div>

When attempting to log into my forum with my own Facebook account: This is the first time I’ve encountered this error. I am logged into Facebook and my forum is authorised. I have now tried logging in with Facebook …

---

## [Digest preview html view not working](https://meta.discourse.org/t/digest-preview-html-view-not-working/59700)

<div class="topic-metadata">

**Author:** [@blake](https://meta.discourse.org/u/blake)\
**댓글:** 4\
**마지막 업데이트:** [3월 27, 2017, 6:42오후 UTC](https://meta.discourse.org/t/digest-preview-html-view-not-working/59700 "2017-03-27T18:42:48Z")

</div>

It looks like the html view for the digest preview is not working: The text view appears to work fine:

---

## [Jquery errors in the setup wizard](https://meta.discourse.org/t/jquery-errors-in-the-setup-wizard/59902)

<div class="topic-metadata">

**Author:** [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\
**댓글:** 7\
**마지막 업데이트:** [3월 27, 2017, 2:33오후 UTC](https://meta.discourse.org/t/jquery-errors-in-the-setup-wizard/59902 "2017-03-27T14:33:15Z")

</div>

The forum I’m trying to start now won’t send the initial email. it’s logging: Uncaught ReferenceError: jQuery is not defined at wizard-vendor-c7b999087a3c233eb2346562db6ec6a472a50c50cf676a2ea23304c4091d7716.js:1

---

## [Updating About topic title in category shows inconsistent label](https://meta.discourse.org/t/updating-about-topic-title-in-category-shows-inconsistent-label/59868)

<div class="topic-metadata">

**Author:** [@Steve\_Pavlina](https://meta.discourse.org/u/Steve_Pavlina)\
**댓글:** 2\
**마지막 업데이트:** [3월 26, 2017, 7:03오전 UTC](https://meta.discourse.org/t/updating-about-topic-title-in-category-shows-inconsistent-label/59868 "2017-03-26T07:03:49Z")

</div>

When I change the name of a category and save it, that part works fine. But then when I go to edit the title of the default pinned topic in that same category to update that topic with the new category name – i.e. the au…

---

## [Clicking site logo in Category view does not reload content](https://meta.discourse.org/t/clicking-site-logo-in-category-view-does-not-reload-content/56415)

<div class="topic-metadata">

**Author:** [@Ebs](https://meta.discourse.org/u/Ebs)\
**댓글:** 9\
**마지막 업데이트:** [3월 24, 2017, 8:31오후 UTC](https://meta.discourse.org/t/clicking-site-logo-in-category-view-does-not-reload-content/56415 "2017-03-24T20:31:36Z")

</div>

Hello, Not really sure if this is a bug or intentional. if ‘top menu’ setting is set to ‘categories’ first, clicking the site logo does not refresh the page content. This can be tested here on meta by clicking the vie…

---

## [Missing Key for delete all posts confirmation](https://meta.discourse.org/t/missing-key-for-delete-all-posts-confirmation/59832)

<div class="topic-metadata">

**Author:** [@simon](https://meta.discourse.org/u/simon)\
**댓글:** 2\
**마지막 업데이트:** [3월 24, 2017, 7:52오후 UTC](https://meta.discourse.org/t/missing-key-for-delete-all-posts-confirmation/59832 "2017-03-24T19:52:28Z")

</div>

On version v1.8.0.beta8 +24, in a production environment, I’m getting a missing key for admin.user.delete\_all\_posts\_confirm\_MF.

---

## [Ctrl & Shift Clicking on topics no longer work (Latest View Only)](https://meta.discourse.org/t/ctrl-shift-clicking-on-topics-no-longer-work-latest-view-only/59801)

<div class="topic-metadata">

**Author:** [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**댓글:** 3\
**마지막 업데이트:** [3월 24, 2017, 6:37오후 UTC](https://meta.discourse.org/t/ctrl-shift-clicking-on-topics-no-longer-work-latest-view-only/59801 "2017-03-24T18:37:11Z")

</div>

Earlier today I noticed on Meta that holding Ctrl or Shift while clicking on a topic in /latest not longer caused a new tab/window to open. I thought it was a fluke, but after updating my dev instance I can confirm it t…

---

## [Resurrected topics should go away when last post is deleted](https://meta.discourse.org/t/resurrected-topics-should-go-away-when-last-post-is-deleted/59857)

<div class="topic-metadata">

**Author:** [@iamntz](https://meta.discourse.org/u/iamntz)\
**댓글:** 1\
**마지막 업데이트:** [3월 24, 2017, 5:52오후 UTC](https://meta.discourse.org/t/resurrected-topics-should-go-away-when-last-post-is-deleted/59857 "2017-03-24T17:52:53Z")

</div>

I’m not sure it’s a bug or it’s a feature. Let’s assume this: We have a topic that’s one year (or more) old. Someone add a comment to that topic; The topic will come first on the homepage (this is good); That comment…

---

## [Notification error in backups](https://meta.discourse.org/t/notification-error-in-backups/59836)

<div class="topic-metadata">

**Author:** [@JagWaugh](https://meta.discourse.org/u/JagWaugh)\
**댓글:** 3\
**마지막 업데이트:** [3월 24, 2017, 1:00오후 UTC](https://meta.discourse.org/t/notification-error-in-backups/59836 "2017-03-24T13:00:45Z")

</div>

Since we updated last night, /logs is showing: uninitialized constant BackupRestore::Backuper::Discouse /var/www/discourse/lib/backup\_restore/backuper.rb:263:in \`notify\_user’ /var/www/discourse/lib/backup\_restore/backu…

---

## [Adding a custom emoji broke the site](https://meta.discourse.org/t/adding-a-custom-emoji-broke-the-site/59687)

<div class="topic-metadata">

**Author:** [@adundovi](https://meta.discourse.org/u/adundovi)\
**댓글:** 2\
**마지막 업데이트:** [3월 22, 2017, 2:30오후 UTC](https://meta.discourse.org/t/adding-a-custom-emoji-broke-the-site/59687 "2017-03-22T14:30:57Z")

</div>

I’m not exactly sure how, but it seems that one of admins on my site, while adding a new emoji to the site, managed to tear down the whole discourse. Rebuilding of the container didn’t help. Clearing the cache also. I c…

---

## [Help with the email prefix](https://meta.discourse.org/t/help-with-the-email-prefix/49208)

<div class="topic-metadata">

**Author:** [@alankeny](https://meta.discourse.org/u/alankeny)\
**댓글:** 3\
**마지막 업데이트:** [3월 22, 2017, 8:50오전 UTC](https://meta.discourse.org/t/help-with-the-email-prefix/49208 "2017-03-22T08:50:46Z")

</div>

The description of the variable email prefix says: The \[label\] used in the subject of emails. It will default to ‘title’ if not set. We’ve found that setting email prefix replaces the variable site title throughout the…

---

## [Cannot use back button to exit Site Settings](https://meta.discourse.org/t/cannot-use-back-button-to-exit-site-settings/58824)

<div class="topic-metadata">

**Author:** [@sam](https://meta.discourse.org/u/sam)\
**댓글:** 2\
**마지막 업데이트:** [3월 21, 2017, 8:15오후 UTC](https://meta.discourse.org/t/cannot-use-back-button-to-exit-site-settings/58824 "2017-03-21T20:15:45Z")

</div>

The following sequence traps you in site settings Click hamburger Click Site Settings Type “Test” in box Click back → back → back → … This raises two issues: We are way way too eager on pushState here, we should be…

---

## [Topic title duplicated in header](https://meta.discourse.org/t/topic-title-duplicated-in-header/58599)

<div class="topic-metadata">

**Author:** [@jomaxro](https://meta.discourse.org/u/jomaxro)\
**댓글:** 8\
**마지막 업데이트:** [3월 20, 2017, 4:37오후 UTC](https://meta.discourse.org/t/topic-title-duplicated-in-header/58599 "2017-03-20T16:37:45Z")

</div>

I’ve started noticing this about a week or so ago. I’ve yet to get a consistent repro - but it seems to occur after editing a topic (as TL3 here on Meta, or Moderator at Stonehearth). Here’s what I’ve been seeing: O…

---

## [Bug in inviting users (?) Cannot login, claiming activation already sent (false)](https://meta.discourse.org/t/bug-in-inviting-users-cannot-login-claiming-activation-already-sent-false/59357)

<div class="topic-metadata">

**Author:** [@nordize](https://meta.discourse.org/u/nordize)\
**댓글:** 1\
**마지막 업데이트:** [3월 20, 2017, 11:56오전 UTC](https://meta.discourse.org/t/bug-in-inviting-users-cannot-login-claiming-activation-already-sent-false/59357 "2017-03-20T11:56:26Z")

</div>

Just installed from docker the latest 1.8.0.beta7. I think I stumbled upon a bug. Here’s what I did: checked login required in Settings (it’s a closed discussion forum) sent invite to a user user got the invite and c…

---

## [Discourse app.yml doesn't like email password contain "#"](https://meta.discourse.org/t/discourse-app-yml-doesnt-like-email-password-contain/58437)

<div class="topic-metadata">

**Author:** [@LiveLikeLastDay](https://meta.discourse.org/u/LiveLikeLastDay)\
**댓글:** 14\
**마지막 업데이트:** [3월 17, 2017, 6:24오후 UTC](https://meta.discourse.org/t/discourse-app-yml-doesnt-like-email-password-contain/58437 "2017-03-17T18:24:06Z")

</div>

I’m using discourse V1.8.0.beta5 +202 I tried my Gmail account with contain “#” and rebuild app, but couldn’t send test email at admin/email. I changed my Gmail password without “#” and rebuild app, then send test em…

---

## [Uploaded emojis lost with last update?](https://meta.discourse.org/t/uploaded-emojis-lost-with-last-update/59306)

<div class="topic-metadata">

**Author:** [@Steven](https://meta.discourse.org/u/Steven)\
**댓글:** 5\
**마지막 업데이트:** [3월 17, 2017, 12:32오전 UTC](https://meta.discourse.org/t/uploaded-emojis-lost-with-last-update/59306 "2017-03-17T00:32:27Z")

</div>

On two forums I host, I’ve had an issue, all emojis uploaded on admin panel were lost. They were still on the FTP but seemed to have disappeared on the database. Here is the version where it happened : Discourse 1.8.0.b…

---

## [JSON API parsing error, single quotes used for errors like "\['BAD CSRF'\]"](https://meta.discourse.org/t/json-api-parsing-error-single-quotes-used-for-errors-like-bad-csrf/58869)

<div class="topic-metadata">

**Author:** [@vvanpo](https://meta.discourse.org/u/vvanpo)\
**댓글:** 2\
**마지막 업데이트:** [3월 16, 2017, 11:49오후 UTC](https://meta.discourse.org/t/json-api-parsing-error-single-quotes-used-for-errors-like-bad-csrf/58869 "2017-03-16T23:49:50Z")

</div>

My JSON parser fails when retrieving certain errors, so far I’ve only expierenced it with “\[‘BAD CSRF’\]” being returned when using the /groups/{group\_id}/members.json endpoint (as single-quotes for string delimiters is i…

---

## [User TL3 Requirements page missing on refresh](https://meta.discourse.org/t/user-tl3-requirements-page-missing-on-refresh/59261)

<div class="topic-metadata">

**Author:** [@joebuhlig](https://meta.discourse.org/u/joebuhlig)\
**댓글:** 1\
**마지막 업데이트:** [3월 16, 2017, 4:13오후 UTC](https://meta.discourse.org/t/user-tl3-requirements-page-missing-on-refresh/59261 "2017-03-16T16:13:37Z")

</div>

I was working to adjust the TL3 settings for one of my sites and pulled up the TL3 requirements page for a few TL2 users to use as a gauge. That worked fine but when I refreshed the page to see the edits I had made to th…

---

## [Problems with the new-user webhook](https://meta.discourse.org/t/problems-with-the-new-user-webhook/59133)

<div class="topic-metadata">

**Author:** [@watchmanmonitor](https://meta.discourse.org/u/watchmanmonitor)\
**댓글:** 12\
**마지막 업데이트:** [3월 16, 2017, 3:55오후 UTC](https://meta.discourse.org/t/problems-with-the-new-user-webhook/59133 "2017-03-16T15:55:57Z")

</div>

Continuing the discussion from Discourse Webhooks and Zapier: I want to get notified for every new user which is created in our forum. The setup is below, and my forum is configured as follows: The public can view a …

---

## [Specifying port for embeddable host given an IP results in error](https://meta.discourse.org/t/specifying-port-for-embeddable-host-given-an-ip-results-in-error/59209)

<div class="topic-metadata">

**Author:** [@kennym](https://meta.discourse.org/u/kennym)\
**댓글:** 3\
**마지막 업데이트:** [3월 16, 2017, 3:23오후 UTC](https://meta.discourse.org/t/specifying-port-for-embeddable-host-given-an-ip-results-in-error/59209 "2017-03-16T15:23:53Z")

</div>

When I try to add an embeddable host with the host: http://192.168.1.167:3000 then it tells me that the host is invalid. If I remove the port number, as so: http://192.168.1.167, then everything works. Here’s a video o…

---

## ["Leave Group" button on /groups page doesn't give any feedback](https://meta.discourse.org/t/leave-group-button-on-groups-page-doesnt-give-any-feedback/57359)

<div class="topic-metadata">

**Author:** [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)\
**댓글:** 6\
**마지막 업데이트:** [3월 16, 2017, 3:36오전 UTC](https://meta.discourse.org/t/leave-group-button-on-groups-page-doesnt-give-any-feedback/57359 "2017-03-16T03:36:08Z")

</div>

Steps Click hamburger menu \> Groups Click “Leave Group” to leave a public group that you’re a member of Expected: Button changes to “+ Join Group”, or some similar feedback is displayed to user Actual: Button remains …

---

## [Poll Plugin - Min / Max / Step Ranges](https://meta.discourse.org/t/poll-plugin-min-max-step-ranges/58677)

<div class="topic-metadata">

**Author:** [@RobMeade](https://meta.discourse.org/u/RobMeade)\
**댓글:** 4\
**마지막 업데이트:** [3월 15, 2017, 2:57오전 UTC](https://meta.discourse.org/t/poll-plugin-min-max-step-ranges/58677 "2017-03-15T02:57:18Z")

</div>

Hi, I wouldn’t say this is a huge issue, but something that may be worth being aware of. Whilst experimenting with the poll functionality this evening I initially assumed that the range was set at 1 to 20. I then noti…

---

## [Change Timestamp only for admin?](https://meta.discourse.org/t/change-timestamp-only-for-admin/54094)

<div class="topic-metadata">

**Author:** [@Manfred\_Bayer-Lemerz](https://meta.discourse.org/u/Manfred_Bayer-Lemerz)\
**댓글:** 4\
**마지막 업데이트:** [3월 15, 2017, 2:44오전 UTC](https://meta.discourse.org/t/change-timestamp-only-for-admin/54094 "2017-03-15T02:44:34Z")

</div>

Hallo! When I use the timestamp as admin it works fine. But as Moderator or User with user level 4 the user sees the menu item as above but when he wants to change the date the error message “There was an error chan…

---

## [Let's Encrypt does not respect changes to \`DISCOURSE\_DEVELOPER\_EMAILS\`](https://meta.discourse.org/t/lets-encrypt-does-not-respect-changes-to-discourse-developer-emails/59118)

<div class="topic-metadata">

**Author:** [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**댓글:** 5\
**마지막 업데이트:** [3월 15, 2017, 2:21오전 UTC](https://meta.discourse.org/t/lets-encrypt-does-not-respect-changes-to-discourse-developer-emails/59118 "2017-03-15T02:21:48Z")

</div>

tl;dr: If you need to change the address LETSENCRYPT\_ACCOUNT\_EMAIL you need to delete the lets encrypt directory before running it again. I enabled Let’s Encrypt on a site today. I used a script that copied DISCOURSE\_DE…

---

## [Image Onebox breaks on Wikimedia links](https://meta.discourse.org/t/image-onebox-breaks-on-wikimedia-links/41197)

<div class="topic-metadata">

**Author:** [@phw](https://meta.discourse.org/u/phw)\
**댓글:** 7\
**마지막 업데이트:** [3월 14, 2017, 4:25오후 UTC](https://meta.discourse.org/t/image-onebox-breaks-on-wikimedia-links/41197 "2017-03-14T16:25:19Z")

</div>

If you link to Wikimedia with a link like File:Stones members montage2.jpg - Wikimedia Commons the image onebox is triggered, trying to display this link as an image (which it isn’t, it is just the info page about that i…

---

## [Group Join/Leave button not working](https://meta.discourse.org/t/group-join-leave-button-not-working/58924)

<div class="topic-metadata">

**Author:** [@scombs](https://meta.discourse.org/u/scombs)\
**댓글:** 2\
**마지막 업데이트:** [3월 14, 2017, 3:40오전 UTC](https://meta.discourse.org/t/group-join-leave-button-not-working/58924 "2017-03-14T03:40:13Z")

</div>

Continuing the discussion from Joining a group doesn't take effect unless the browser is hard-refreshed: This issue is back again for me. Not sure it related to the linked “topic list” refresh issue so starting a new t…

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

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