![\"image\"](\"https://global.discourse-cdn.com/meta/original/4X/b/3/0/b30281dca989bd06e6b37d629b80b5ff70dcc483.jpeg\")
image2048×1060 449 KB
로컬 개발 인스턴스에서 무관한 토픽 삭제 관련 변경 사항을 테스트하던 중, 토픽을 삭제하려고 했더니 500 Internal Server Error가 반환되었습니다.
\n해당 에러가 발생한 개발 인스턴스는 정확히 이 Discourse 커밋을 실행 중이었습니다:
\n\n\n\n요청은 다음과 같았습니다:
\nDELETE /t/35\n그리고 예외는 discourse-events 플러그인의 :post_destroyed 콜백에서 발생했습니다:
NameError (uninitialized constant DiscourseEvents::Calendar::Extractor)\n\nplugins/discourse-events/plugin.rb:639:in 'block (2 levels) in Plugin::Instance#activate!'\nlib/plugin/instance.rb:676:in 'block in Plugin::Instance#on'\nlib/discourse_event.rb:13:in 'block in DiscourseEvent.trigger'\nlib/discourse_event.rb:12:in 'DiscourseEvent.trigger'\nlib/post_destroyer.rb:91:in 'PostDestroyer#destroy'\napp/controllers/topics_controller.rb:818:in 'TopicsController#destroy'\n해당 콜백은 다음을 호출하려고 시도하는 것으로 보입니다:
\nDiscourseEvents::Calendar::Extractor.destroy(post)\n전체 에러 페이지에는 다음과 같이 보고됩니다:
\nNameError (uninitialized constant DiscourseEvents::Calendar::Extractor)\n브라우저는 PostDestroyer#destroy가 이미 :post_destroyed를 트리거하는 지점에 도달했음에도 불구하고 500 오류를 수신합니다. 따라서 콜백이 예외를 발생시키기 전에 삭제가 이미 적용되었을 수 있습니다.
이것은 개발 환경에서 발생했습니다. DiscourseEvents::Calendar::Extractor는 일반적으로 events 플러그인에 의해 제공되므로, 구현 자체가 누락된 것이 아니라 개발 모드 리로딩/플러그인 상태와 관련이 있을 수 있는지 궁금합니다.
당시 저는 무관한 토픽 삭제 코드 작업을 하고 있었지만, 예외 자체는 discourse-events의 :post_destroyed 핸들러 내부에서 완전히 발생하고 있습니다.
혹시 다른 분들도 개발 인스턴스에서 DiscourseEvents::Calendar::Extractor가 정의되지 않는 상황을 경험해 보셨나요? 이것이 개발 리로딩/플러그인 상태와 관련이 있을 수 있으며, 아니면 :post_destroyed 콜백이 추출기를 다른 방식으로 로드해야 하는 것일까요?
안녕하세요, 네, 괜찮습니다.
\n아니요, 이메일을 전혀 받지 못했습니다. 모든 이메일을 다시 검색해 보았지만, 갑자기 그렇게 된 것 같습니다.
저는 이것이 여기서 중요한 구별점이라고 생각합니다. 기존 구현에서는 이미 일반 사용자가 답글이 없는 경우에만 자신의 주제를 삭제할 수 있도록 제한하고 있습니다:
\n\n\n따라서 더 구체적인 기능 요청은 현재 하드코딩된 24.hours를 설정 가능하도록 하고, 기존 posts_count <= 1 제한을 유지하는 것으로 충분할 수 있습니다. 기본값은 24시간으로 유지하되, 관리자가 더 긴 기간을 선택하거나, 답이 없는 주제의 삭제를 무제한으로 허용할 수 있도록 할 수 있습니다.
GDPR이 이 기능이 필요한 진정한 이유라고 생각하지 않습니다. 삭제권은 절대적이지 않으며, 사용자가 게시한 모든 콘텐츠에 대해 무제한의 셀프 서비스 삭제 옵션을 제공해야 한다는 것을 의미하지 않습니다.
\n기존 24시간 제한의 설정 가능성은 이 기능 자체에 대한 충분한 논거로 보입니다.
","post_number":12,"post_type":1,"posts_count":12,"updated_at":"2026-09-06T00:47:03.155Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":2,"readers_count":1,"score":5.4,"yours":false,"topic_id":411689,"topic_slug":"allow-user-to-delete-their-own-topic-at-any-time","topic_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","topic_html_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","category_id":2,"display_username":"Ethan ","primary_group_name":null,"flair_name":"theme_authors","flair_url":"paintbrush","flair_bg_color":"ddd","flair_color":"111","flair_group_id":73,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Tester","title_is_group":false,"bookmarked":false,"raw":"[quote=“Ed_S, post:8, topic:411689”]\nStill, it might be clearer as a feature request that it’s unanswered topics which you’d like to make deletable.\n[/quote]\n\nI think that’s the important distinction here. The existing implementation already restricts ordinary users to deleting their own topic only when it has no replies:\n\nhttps://github.com/discourse/discourse/blob/5e9779d4cd418af07a6ed01005d558eda76f2f69/lib/guardian/topic_guardian.rb#L383-L385\n\nSo the narrower feature request could simply be to make the currently hardcoded `24.hours` configurable, while retaining the existing `posts_count <= 1` restriction. That could default to 24 hours but allow admins to choose a longer period, or potentially unlimited deletion of unanswered topics.\n\n[quote=“ecki, post:11, topic:411689”]\nIt’s much easier than to deal with GDPR sues later on - let’s have user their data soverenity\n[/quote]\n\nI don’t think GDPR is really the reason this feature is needed. The right to erasure is not absolute, and it doesn’t mean forum software has to provide an unlimited self-service option to delete any content a user has posted.\n\nThe configurability of the existing 24-hour restriction seems like a sufficient argument for the feature on its own.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":160471,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"저는 이것이 여기서 중요한 구별점이라고 생각합니다. 기존 구현에서는 이미 일반 사용자가 답글이 없는 경우에만 자신의 주제를 삭제할 수 있도록 제한하고 있습니다: \n\n\n따라서 더 구체적인 기능 요청은 현재 하드코딩된 24.hours를 설정 가능하도록 하고, 기존 posts_count <= 1 제한을 유지하는 것으로 충분할 수 있습니다. 기본값은 24시간으로 유지하되, 관리자가 더 긴 기간을 선택하거나, 답이 없는 주제의 삭제를 무제한으로 허용할 수 있도록 할 수 있습니다. \n\nGDPR이 이 기능이 필요한 진정한 이유라고 생각하지 않…","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/12","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034483,"name":"Nate Dhaliwal","username":"NateDhaliwal","avatar_template":"/user_avatar/meta.discourse.org/natedhaliwal/{size}/313494_2.png","created_at":"2026-09-06T00:29:53.919Z","cooked":"안녕하세요. 여기서는 게시물이 자동으로 번역되므로, 앞으로는 영어 버전이 필요하지 않습니다.
\n이것은 다음과 유사해 보입니다:
\n\n콘텐츠 제한과 관련하여 이메일을 받으셨나요?
","post_number":3,"post_type":1,"posts_count":3,"updated_at":"2026-09-06T00:29:53.919Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":1,"reads":5,"readers_count":4,"score":6.0,"yours":false,"topic_id":411727,"topic_slug":"ausgesperrt-aus-meinem-forum-dennisshutter-discourse-group-basic-auth-prompt","topic_title":"내 포럼(dennisshutter.discourse.group)에서 잠겨 있음 - 기본 인증 프롬프트","topic_html_title":"내 포럼(dennisshutter.discourse.group)에서 잠겨 있음 - 기본 인증 프롬프트","category_id":6,"display_username":"Nate Dhaliwal","primary_group_name":null,"flair_name":"plugin_authors","flair_url":"plug","flair_bg_color":"dddddd","flair_color":"111111","flair_group_id":48,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Senior Tester","title_is_group":false,"bookmarked":false,"raw":"Hi there, note that your post will be automatically translated here, so an English version is not necessary in the future.\n\nThis looks like:\nhttps://meta.discourse.org/t/trouble-logging-in-to-free-discourse-site/411284\n\nDo you have any emails regarding content restrictions?","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":135392,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"안녕하세요. 여기서는 게시물이 자동으로 번역되므로, 앞으로는 영어 버전이 필요하지 않습니다. \n이것은 다음과 유사해 보입니다: \n\n콘텐츠 제한과 관련하여 이메일을 받으셨나요?","truncated":true,"post_url":"/t/ausgesperrt-aus-meinem-forum-dennisshutter-discourse-group-basic-auth-prompt/411727/3","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034481,"name":"","username":"satonotdead","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png","created_at":"2026-09-06T00:11:44.355Z","cooked":"Don, 정말 좋습니다. 만들어서 공유해 주셔서 감사합니다!
\n\n신뢰할 수 있는 외부 링크에 왜 잠금 아이콘을 사용하는지 궁금합니다. 허용된 링크인데 '잠김’으로 해석될 수 있을 것 같아서요. ![\":sweat_smile:\"](\"https://emoji.discourse-cdn.com/twitter/sweat_smile.png?v=15\" "\\":sweat_smile:\\"")
이 컴포넌트를 사용해 보겠습니다. 외부 링크에 대한 우리의 모든 사용 사례를 커버하는 것 같습니다. 또한, 일반적인 표준이 오른쪽에 아이콘을 배치하는 것임을 알고 있으므로 아이콘을 오른쪽으로 이동시키는 것도 시도해 보겠습니다.
\n항상 그렇듯이 제 생각을 공유하는 것뿐이며, 이를 통해 TC가 개선되기를 바랍니다.
","post_number":6,"post_type":1,"posts_count":6,"updated_at":"2026-09-06T00:12:09.264Z","reply_count":0,"reply_to_post_number":null,"quote_count":1,"incoming_link_count":0,"reads":3,"readers_count":2,"score":15.6,"yours":false,"topic_id":392962,"topic_slug":"external-link-shield-exit-confirmation-trust-gating","topic_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","topic_html_title":"외부 링크 보호 – 종료 확인 및 신뢰 게이트","category_id":120,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"This is great Don, thanks for building and sharing it!\n\n[quote=\"Don, post:1, topic:392962\"]\n* **Trusted external links** → lock icon (success color)\n[/quote]\nI wonder why the trusted external links uses a lock icon? I mean, it can be interpreted as \"locked\" 😅 when they are allowed.\n\nI will try this component; it seems to cover all our use cases for external links. I will also try moving the icons to the right because I understand it is the common standard.\n\nLike always, just sharing my thoughts and glad if the TC can be improved with them.","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":71041,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"Don, 정말 좋습니다. 만들어서 공유해 주셔서 감사합니다! \n\n신뢰할 수 있는 외부 링크에 왜 잠금 아이콘을 사용하는지 궁금합니다. 허용된 링크인데 '잠김’으로 해석될 수 있을 것 같아서요. :sweat_smile: \n이 컴포넌트를 사용해 보겠습니다. 외부 링크에 대한 우리의 모든 사용 사례를 커버하는 것 같습니다. 또한, 일반적인 표준이 오른쪽에 아이콘을 배치하는 것임을 알고 있으므로 아이콘을 오른쪽으로 이동시키는 것도 시도해 보겠습니다. \n항상 그렇듯이 제 생각을 공유하는 것뿐이며, 이를 통해 TC가 개선되기를 바랍니다.","truncated":true,"post_url":"/t/external-link-shield-exit-confirmation-trust-gating/392962/6","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034480,"name":"","username":"Moin","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png","created_at":"2026-09-05T22:16:40.166Z","cooked":"enable_solved_tags 설정이 있습니다. 하지만 이 설정이 “나도” 버튼을 지원하는지는 알 수 없습니다.
새로운 보고 도구는 카테고리별로 설정된 solved 플러그인에 한정되어 있는 것 같습니다. 이로 인해 다른 최근 기능들도 영향을 받는 것일지 궁금해집니다.
\n","post_number":8,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T22:16:40.166Z","reply_count":0,"reply_to_post_number":6,"quote_count":0,"incoming_link_count":0,"reads":5,"readers_count":4,"score":16.0,"yours":false,"topic_id":409045,"topic_slug":"combining-category-types","topic_title":"카테고리 유형 결합","topic_html_title":"카테고리 유형 결합","category_id":2,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Kluges Köpfchen","title_is_group":false,"reply_to_user":{"id":117384,"username":"ecki","name":"Bernd","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png"},"bookmarked":false,"raw":"There is the `enable_solved_tags` setting. But I don't know if that supports the \"me too\" button.\n\nThe new reporting tool seems to be limited to the solved plugin being set up by category. This makes me wonder if other recent features are affected too.\n[quote=\"lindsey, post:1, topic:411397\"]\n**Note:** The Accepted Solutions report and corresponding dashboard card are only shown in communities with at least one [support category](https://meta.discourse.org/t/easily-create-support-categories-using-the-discourse-solved-plugin/398338).\n[/quote]","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":false,"staff":false,"user_id":95552,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"enable_solved_tags 설정이 있습니다. 하지만 이 설정이 “나도” 버튼을 지원하는지는 알 수 없습니다. \n새로운 보고 도구는 카테고리별로 설정된 solved 플러그인에 한정되어 있는 것 같습니다. 이로 인해 다른 최근 기능들도 영향을 받는 것일지 궁금해집니다.","truncated":true,"post_url":"/t/combining-category-types/409045/8","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034479,"name":"","username":"satonotdead","avatar_template":"/user_avatar/meta.discourse.org/satonotdead/{size}/447830_2.png","created_at":"2026-09-05T22:16:29.341Z","cooked":"이 융합에 동의합니다. 일부 주제에는 ‘나도!’ 옵션과 투표 기능이 모두 있어야 합니다. 둘 다 활성화하거나, 하나만 활성화하거나, 또는 둘 다 비활성화할 수 있도록 전환 가능해야 한다고 생각합니다.
\n정확한 처리 방법은 잘 모르겠지만, 이 목적은 여기에서 충분히 지지받고 있습니다.
","post_number":7,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T22:16:29.341Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":6,"readers_count":5,"score":1.2,"yours":false,"topic_id":409045,"topic_slug":"combining-category-types","topic_title":"카테고리 유형 결합","topic_html_title":"카테고리 유형 결합","category_id":2,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"I am agree with this fusion, some topics should have the 'Me too' option and voting as well. I think it should be switchable for enabling both, one or none of them.\n\nNot sure how to properly handle it but the purpose is really supported here.","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":71041,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"이 융합에 동의합니다. 일부 주제에는 ‘나도!’ 옵션과 투표 기능이 모두 있어야 합니다. 둘 다 활성화하거나, 하나만 활성화하거나, 또는 둘 다 비활성화할 수 있도록 전환 가능해야 한다고 생각합니다. \n정확한 처리 방법은 잘 모르겠지만, 이 목적은 여기에서 충분히 지지받고 있습니다.","truncated":true,"post_url":"/t/combining-category-types/409045/7","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034478,"name":"Bernd","username":"ecki","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png","created_at":"2026-09-05T22:12:47.607Z","cooked":"아니, 적어도 나는 그런 것을 본 적이 없습니다(그리고 그것들은 사실 관련이 없습니다). 테스트 게시물에서도 그런 현상은 일어나지 않습니다. 누군가가 ‘유용하게’ 도와주려고 추가한 줄 알았는데, 가끔은 의외로 매우 빠르게 나타납니다.
","post_number":3,"post_type":1,"posts_count":3,"updated_at":"2026-09-05T22:13:13.474Z","reply_count":0,"reply_to_post_number":2,"quote_count":0,"incoming_link_count":1,"reads":9,"readers_count":8,"score":6.8,"yours":false,"topic_id":411729,"topic_slug":"randomly-attached-tags","topic_title":"무작위로 붙은 태그","topic_html_title":"무작위로 붙은 태그","category_id":6,"display_username":"Bernd","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","reply_to_user":{"id":95552,"username":"Moin","name":"","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png"},"bookmarked":false,"raw":"No, at least I haven’t seen that (and also they are not really related). It also does not happen on test posts. I already thought it’s someone „helpful“ adding it but it sometimes shows up surprisingly fast","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":117384,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"아니, 적어도 나는 그런 것을 본 적이 없습니다(그리고 그것들은 사실 관련이 없습니다). 테스트 게시물에서도 그런 현상은 일어나지 않습니다. 누군가가 ‘유용하게’ 도와주려고 추가한 줄 알았는데, 가끔은 의외로 매우 빠르게 나타납니다.","truncated":true,"post_url":"/t/randomly-attached-tags/411729/3","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034477,"name":"","username":"Moin","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png","created_at":"2026-09-05T22:10:36.984Z","cooked":"해갈(Thirst) 태그를 부모 태그로 설정한 태그 그룹에서, 추가하는 태그 중 하나를 선택한 건가요?
","post_number":2,"post_type":1,"posts_count":3,"updated_at":"2026-09-05T22:10:36.984Z","reply_count":1,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":0,"reads":10,"readers_count":9,"score":7.0,"yours":false,"topic_id":411729,"topic_slug":"randomly-attached-tags","topic_title":"무작위로 붙은 태그","topic_html_title":"무작위로 붙은 태그","category_id":6,"display_username":"","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Kluges Köpfchen","title_is_group":false,"bookmarked":false,"raw":"Is one of the tags you add in a tag group where you configured that the thirst one is required as the parent tag?","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":95552,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"해갈(Thirst) 태그를 부모 태그로 설정한 태그 그룹에서, 추가하는 태그 중 하나를 선택한 건가요?","truncated":true,"post_url":"/t/randomly-attached-tags/411729/2","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034476,"name":"Bernd","username":"ecki","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png","created_at":"2026-09-05T22:10:25.257Z","cooked":"나중에 GDPR 소송을 처리하는 것보다 훨씬 쉽습니다. 사용자에게 데이터 주권을 돌려주도록 합시다.
","post_number":11,"post_type":1,"posts_count":12,"updated_at":"2026-09-05T22:10:25.257Z","reply_count":0,"reply_to_post_number":2,"quote_count":0,"incoming_link_count":0,"reads":5,"readers_count":4,"score":1.0,"yours":false,"topic_id":411689,"topic_slug":"allow-user-to-delete-their-own-topic-at-any-time","topic_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","topic_html_title":"사용자가 언제든지 자신의 주제를 삭제할 수 있도록 허용","category_id":2,"display_username":"Bernd","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","reply_to_user":{"id":176316,"username":"Rubi","name":null,"avatar_template":"https://avatars.discourse-cdn.com/v4/letter/r/7ea924/{size}.png"},"bookmarked":false,"raw":"It’s much easier than to deal with GDPR sues later on - let’s have user their data soverenity","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":117384,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"나중에 GDPR 소송을 처리하는 것보다 훨씬 쉽습니다. 사용자에게 데이터 주권을 돌려주도록 합시다.","truncated":true,"post_url":"/t/allow-user-to-delete-their-own-topic-at-any-time/411689/11","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034475,"name":"Bernd","username":"ecki","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png","created_at":"2026-09-05T22:05:49.190Z","cooked":"아, 실제로 태그를 기반으로 솔루션 유형을 만들 수 있나요? 예를 들어 ‘지원 질문으로 표시’ 같은 거요? 그러면 토론 항목에 '나도’나 ‘해결됨’ 버튼이 없게 되니까 그게 좋겠네요.
","post_number":6,"post_type":1,"posts_count":8,"updated_at":"2026-09-05T22:05:49.190Z","reply_count":1,"reply_to_post_number":5,"quote_count":0,"incoming_link_count":1,"reads":6,"readers_count":5,"score":11.2,"yours":false,"topic_id":409045,"topic_slug":"combining-category-types","topic_title":"카테고리 유형 결합","topic_html_title":"카테고리 유형 결합","category_id":2,"display_username":"Bernd","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","reply_to_user":{"id":95552,"username":"Moin","name":"","avatar_template":"/user_avatar/meta.discourse.org/moin/{size}/554653_2.png"},"bookmarked":false,"raw":"Oh can you actually make solution types based on a tag? Something like „mark it a support question“? That would be cool so discussion entries have no „Me too“ or „mark solved“ buttons","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":117384,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"아, 실제로 태그를 기반으로 솔루션 유형을 만들 수 있나요? 예를 들어 ‘지원 질문으로 표시’ 같은 거요? 그러면 토론 항목에 '나도’나 ‘해결됨’ 버튼이 없게 되니까 그게 좋겠네요.","truncated":true,"post_url":"/t/combining-category-types/409045/6","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034474,"name":"Bernd","username":"ecki","avatar_template":"/user_avatar/meta.discourse.org/ecki/{size}/264025_2.png","created_at":"2026-09-05T22:02:43.298Z","cooked":"제가 정기적으로 작성하는 게시물 중 일부에 내가 직접 고른 두 개의 태그를 붙여도, 나중에 특정 세 번째 태그가 자동으로 붙어 있는 문제가 있습니다. 해당 태그는 동의어가 아니며, 카테고리에도 설정되어 있지 않습니다. 이 태그가 어디서 오는 걸까요? 처음에는 내가 추가한 태그와 접두사가 같아서 실수로 선택한 줄 알았지만, 주의를 기울여 보니 그런 게 아니었습니다. 이 태그들이 어디서 유입되는지 확인할 수 있는 로그나 테이블이 있을까요?
","post_number":1,"post_type":1,"posts_count":3,"updated_at":"2026-09-05T22:02:43.298Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":10,"readers_count":9,"score":12.0,"yours":false,"topic_id":411729,"topic_slug":"randomly-attached-tags","topic_title":"무작위로 붙은 태그","topic_html_title":"무작위로 붙은 태그","category_id":6,"display_username":"Bernd","primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"","bookmarked":false,"raw":"I have this annoying problem that some posts I make regularly with 2 hand picked tags later show up with a specific third one. It’s not a synonym and not set on the category. Where can it come from? In the beginning I assumed it was an accidental selection since it has the same prefix as the one I added, but since I pay attention I can say that’s not it. Is there a lot or table where I can find out where they are coming from?","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":117384,"hidden":false,"trust_level":2,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"제가 정기적으로 작성하는 게시물 중 일부에 내가 직접 고른 두 개의 태그를 붙여도, 나중에 특정 세 번째 태그가 자동으로 붙어 있는 문제가 있습니다. 해당 태그는 동의어가 아니며, 카테고리에도 설정되어 있지 않습니다. 이 태그가 어디서 오는 걸까요? 처음에는 내가 추가한 태그와 접두사가 같아서 실수로 선택한 줄 알았지만, 주의를 기울여 보니 그런 게 아니었습니다. 이 태그들이 어디서 유입되는지 확인할 수 있는 로그나 테이블이 있을까요?","truncated":true,"post_url":"/t/randomly-attached-tags/411729/1","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":2034472,"name":null,"username":"DennisShutter","avatar_template":"https://avatars.discourse-cdn.com/v4/letter/d/49beb7/{size}.png","created_at":"2026-09-05T21:39:37.062Z","cooked":"안녕하세요,
\n저는 갑자기 dennisshutter.discourse.group에 있는 무료 Discourse 포럼에서 차단되었습니다. 사이트를 접속하면 정상적인 포럼 페이지 대신 즉시 HTTP 기본 인증 창(„Authentifizierung erforderlich“)이 표시됩니다. 관리자 이메일을 확인해 보았지만 알림이나 경고 메시지를 받지 못했습니다.
제 포럼에는 정책 위반 사항이 없으므로 시스템의 기술적 오류로 추정됩니다. 지원 직원이 이 문제를 확인하여 접근 권한을 다시 활성화해 주실 수 있을까요?
\n감사합니다!
\n기술 직원을 위한 영어 번역:
\nHello,
\nI am suddenly locked out of my free Discourse forum at dennisshutter.discourse.group.
When trying to access the site, it immediately prompts me with a browser Basic Auth login window (“Authentifizierung erforderlich”) instead of the regular forum page. I have checked my admin email and did not receive any notification or warning.
\nSince there are no policy violations on my forum, I assume this is a technical issue. Could a staff member please look into this and help me restore access?
\nThank you!
","post_number":1,"post_type":1,"posts_count":3,"updated_at":"2026-09-06T00:30:05.555Z","reply_count":0,"reply_to_post_number":null,"quote_count":0,"incoming_link_count":2,"reads":13,"readers_count":12,"score":12.6,"yours":false,"topic_id":411727,"topic_slug":"ausgesperrt-aus-meinem-forum-dennisshutter-discourse-group-basic-auth-prompt","topic_title":"내 포럼(dennisshutter.discourse.group)에서 잠겨 있음 - 기본 인증 프롬프트","topic_html_title":"내 포럼(dennisshutter.discourse.group)에서 잠겨 있음 - 기본 인증 프롬프트","category_id":6,"display_username":null,"primary_group_name":null,"flair_name":null,"flair_url":null,"flair_bg_color":null,"flair_color":null,"flair_group_id":null,"badges_granted":[],"version":3,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":null,"bookmarked":false,"raw":"Hallo,\n\nich wurde plötzlich aus meinem kostenlosen Discourse-Forum unter `dennisshutter.discourse.group` ausgesperrt. Beim Aufruf der Seite erscheint sofort ein HTTP-Basisauthentifizierungs-Fenster („Authentifizierung erforderlich“) statt der normalen Forumsseite. Ich habe meine Admin-E-Mail-Adresse geprüft und keine Benachrichtigung oder Warnung erhalten.\n\nDa bei meinem Forum keine Richtlinienverletzungen vorliegen, gehe ich von einem technischen Fehler im System aus. Könnte sich das bitte ein Support-Mitarbeiter ansehen und den Zugang wieder freischalten?\n\nVielen Dank!\n\n\n*English translation for technical staff:*\n\nHello,\n\nI am suddenly locked out of my free Discourse forum at `dennisshutter.discourse.group`.\n\nWhen trying to access the site, it immediately prompts me with a browser Basic Auth login window (\"Authentifizierung erforderlich\") instead of the regular forum page. I have checked my admin email and did not receive any notification or warning.\n\nSince there are no policy violations on my forum, I assume this is a technical issue. Could a staff member please look into this and help me restore access?\n\nThank you!","actions_summary":[],"moderator":false,"admin":false,"staff":false,"user_id":202295,"hidden":false,"trust_level":1,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"안녕하세요, \n저는 갑자기 dennisshutter.discourse.group에 있는 무료 Discourse 포럼에서 차단되었습니다. 사이트를 접속하면 정상적인 포럼 페이지 대신 즉시 HTTP 기본 인증 창(„Authentifizierung erforderlich“)이 표시됩니다. 관리자 이메일을 확인해 보았지만 알림이나 경고 메시지를 받지 못했습니다. \n제 포럼에는 정책 위반 사항이 없으므로 시스템의 기술적 오류로 추정됩니다. 지원 직원이 이 문제를 확인하여 접근 권한을 다시 활성화해 주실 수 있을까요? \n감사합니다! \n기술 직…","truncated":true,"post_url":"/t/ausgesperrt-aus-meinem-forum-dennisshutter-discourse-group-basic-auth-prompt/411727/1","locale":"de","is_localized":true,"language":"de","localization_outdated":true,"customer_flair_customer":null,"event":null,"calendar_details":[],"reactions":[],"current_user_reaction":null,"reaction_users_count":0,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null,"can_vote":false},{"id":2034470,"name":"Dave McClure","username":"mcwumbly","avatar_template":"/user_avatar/meta.discourse.org/mcwumbly/{size}/103861_2.png","created_at":"2026-09-05T21:02:59.534Z","cooked":"우연히도, 그 부분에 대해 여기에서 진행 중인 작업이 있습니다:
\n\n","post_number":30,"post_type":1,"posts_count":19,"updated_at":"2026-09-05T21:02:59.534Z","reply_count":0,"reply_to_post_number":29,"quote_count":0,"incoming_link_count":1,"reads":3,"readers_count":2,"score":20.6,"yours":false,"topic_id":407068,"topic_slug":"easier-account-signup-using-email-codes","topic_title":"이메일 코드를 활용한 간편한 계정 가입","topic_html_title":"이메일 코드를 활용한 간편한 계정 가입","category_id":67,"display_username":"Dave McClure","primary_group_name":"team","flair_name":"team","flair_url":"https://global.discourse-cdn.com/meta/original/3X/e/b/ebee30bd98aef20357e4a177a5a1e45b877ce088.svg","flair_bg_color":"","flair_color":"111","flair_group_id":47,"badges_granted":[],"version":1,"can_edit":false,"can_delete":false,"can_recover":false,"can_see_hidden_post":false,"can_wiki":false,"user_title":"Director of Product","title_is_group":false,"reply_to_user":{"id":132341,"username":"thisisjoshjones","name":"Joshua Jones","avatar_template":"/user_avatar/meta.discourse.org/thisisjoshjones/{size}/303241_2.png"},"bookmarked":false,"raw":"Coincidentally, there's some work in progress on that front here:\n\nhttps://github.com/discourse/discourse/pull/43138","actions_summary":[{"id":2,"count":1}],"moderator":false,"admin":true,"staff":true,"user_id":4263,"hidden":false,"trust_level":3,"deleted_at":null,"user_deleted":false,"edit_reason":null,"can_view_edit_history":true,"wiki":false,"excerpt":"우연히도, 그 부분에 대해 여기에서 진행 중인 작업이 있습니다:","truncated":true,"post_url":"/t/easier-account-signup-using-email-codes/407068/30","locale":"en","is_localized":true,"language":"en","localization_outdated":false,"customer_flair_customer":null,"event":null,"reactions":[{"id":"heart","type":"emoji","count":1}],"current_user_reaction":null,"reaction_users_count":1,"current_user_used_main_reaction":false,"can_accept_answer":false,"can_unaccept_answer":false,"accepted_answer":false,"topic_accepted_answer":null},{"id":2034469,"name":"system","username":"system","avatar_template":"/user_avatar/meta.discourse.org/system/{size}/443519_2.png","created_at":"2026-09-05T21:02:13.771Z","cooked":"In the last 24 hours, the community produced 106 new posts across 33 new topics, collecting 85 likes along the way. The top contributors by likes were:
\nApidevlab shared a frustrating Hetzner VPS bootstrap failure after successful installs on Layer7, and Lilly, Ed_S, and Jagster all asked for the full error log, with Lilly noting that unsupported Podman installs will be hard to get help for. read more
\nIn a more niche integration thread, Nicolsdennis explained how he exposed LiveKit status in a client app, building on earlier design comments from Pmusaraj and Falco. read more
\nNicolsdennis showed off new native voice support in the “mesh” client and a companion app for live-streaming Discourse Voice conversations, complete with screenshots of the voice rooms and LiveKit integration. read more
\nPer1234 shared a ready-to-import Discourse Update Notifier workflow that automatically posts about new Discourse versions, giving members more transparency about UI changes. read more
\nIn a more philosophical thread, Eisammy celebrated Discourse and the Fediverse as alternatives to attention-driven social media, hoping to still be communicating the same way in ten years. read more
\nEmilio asked for a less painful way to permanently delete topics, and Ethsim2 delivered a full implementation: a per-admin opt-in setting that permanently deletes the topic and all replies, with the PR now ready for review. read more
\nHappyhappy received a helpful pointer from Heliosurge to the Category Restrictor plugin as a possible way to let category moderators manage user membership without full admin powers. read more
\nThe new bundled Voice rooms continued to generate excitement, with Jagster finally figuring out that rooms are deleted from the settings tab rather than the forum GUI. read more
\nA discussion about end dates for recurring calendar events led MiniForum to a related feature request: adding recurrence to the per-topic calendar workflow, not just separate Events. read more
\nThisisjoshjones asked whether the new email-code signup flow could also be used on the invitations landing page, calling it a big barrier-lowering improvement for communities. read more
\nEthsim2 opened a PR and shared a detailed screen recording showing how event date edits should update the topic title correctly.
\nStephen reported that expanded markdown tables only allow one checkbox interaction after expansion, flagging the regression for Sam. read more
\nProxyTracer announced a new beta with CAPTCHA challenges, independent clearance tokens, and visual analytics for blocking or challenging proxy and VPN traffic. read more
\nSimonk corrected the AWS SES setup guide, warning that raw message delivery must be disabled for SNS bounce notifications to pass Discourse’s validation checks. read more
\nNateDhaliwal asked how to preset a value for FormKit’s composer field, then discovered that using @data={{hash content=...}} on the <Form> component solves it. read more
Members of the Team group were active across a wide range of threads:
\nMoin helped with a spam user attack thread by asking Ed_S about the moderators_view_ips and moderators_view_emails site settings, then pointed to the hard-coded 24-hour deletion limit in a separate feature request. He also clarified when Discourse Boards appears for self-hosted instances based on the 2026.9 development timeline.
Martin confirmed that a fix for Discourse Events recurrence was already merged via PR #42852, and noted that hover cards for subcategory hashtags were next in Can we make inline links to subcategories more concise?.
\nMcwumbly supported the anonymous search control PR and confirmed that the old admin dashboard will disappear completely once the new dashboard is permanent in Introducing Upcoming Changes.
\nNat proposed and implemented a PR for allow_anonymous_search in Option to enable search for logged in users only?, and also helped diagnose blank Ask AI responses by pointing at timeout issues.
Southpaw thanked HBP for a thorough report and confirmed that a fix is in the works for the check_username rate-limit signup regression.
\nFalco shared a ready PR for granular permissions for cameras and screen sharing in Voice rooms.
\nFrom fighting spam bots to making permanent deletion one click easier, the community came out swinging yesterday — just don’t ask us to delete this summary! ![\":wink:\"](\"https://emoji.discourse-cdn.com/twitter/wink.png?v=15\" "\\":wink:\\"")