계정 삭제 요청

:information_source: 요약 계정 페이지에 계정 삭제 요청 드롭다운 추가.
:hammer_and_wrench: 저장소 GitHub - VaperinaDEV/discourse-account-deletion-request: Add Account Deletion Request dropdown to account page. · GitHub
:heart: 도움이 되셨나요? > ./support --coffee
:question: 설치 가이드 테마 또는 테마 컴포넌트 설치 방법
:open_book: 디스코urs 테마를 처음 사용하시나요? 디스코urs 테마 사용 입문가이드

안녕하세요 :wave:

이것은 계정 페이지에 계정 삭제 요청 드롭다운을 추가하는 테마 컴포넌트입니다.

이 테마 컴포넌트는 Kris의 멋진 코드(Convert the New Topic button to a have a sub menu - #7 by awesomerobot)를 재사용하여 드롭다운을 추가합니다. 감사합니다! :heart:


드롭다운은 기본 내 계정 삭제가 사라지고 사용자가 해당 버튼을 클릭하여 계정을 삭제할 수 없는 경우에만 표시됩니다. staff에게 숨김 설정을 통해 스태프 사용자에게 드롭다운을 숨길 수 있습니다.

사용자가 계정을 삭제할 수 있는 경우 :arrow_down_small:

사용자가 계정을 삭제할 수 없는 경우 :arrow_down_small:

드롭다운을 클릭하면 두 가지 옵션이 열립니다.

  1. 상세 정보
  2. 계정 삭제 요청

사용자가 개인 메시지를 보낼 수 없는 경우 상세 정보 옵션만 표시됩니다 :arrow_down_small:


상세 정보
사용자가 계정 삭제 요청을 보내면 어떤 일이 일어나는지 설명할 수 있는 모달이 열립니다.

계정 삭제 요청
일부 사전 입력된 텍스트(수신자, 제목 및 설명)와 함께 작성기(개인 메시지)가 열립니다.


설정 및 번역이 몇 가지 있습니다.
테마 컴포넌트를 활성화하기 전에 이 설정을 변경해야 합니다…

테마 설정

테마 번역

28개의 좋아요

Hi, nice idea. Could you add a config option to use anonymization instead of deletion ?

5개의 좋아요

Hello,

Thanks :slightly_smiling_face: You can do it by simple change the translation.

2개의 좋아요

I installed the component from the git https address, added it to currently used theme, set its settings (wrote ‘admins’ in the first customizable field).

Yet no user is able to find the button on his preferences pages ‘account’ page.

Hello, is that a staff user? Because it won’t appears to staff.

Edit: Maybe better to appear it for staff too for testing purpose… I made this change. Now it appears to staff too by default but I added a setting to hide the dropdown for staff users.

2개의 좋아요

I had impersonated as the user also. Whose screen shot was attached.

Now I’ve tested again on admin. But its not appearing.

Do I need to rebuild or something like that before it appears for staff?

It should appear below Save Changes button after you update the theme component.

FWIW It works for me :slight_smile:

Have you attached it to your active themes?

3개의 좋아요

Hadn’t updated the component before, but now it’s updated:

Also applied the component to currently being used theme ‘Light Default’.

Then went into a user’s preferences page thru Admin (myself)'s settings page, but didn’t find the option:

Ah!!
It appears far below. Missed it altogether because its interfering with some other component.
Thank you very much.

I’m giving the screen shot of the same for future users, as to how can this be missed, because of highly bright ‘red’ color of another component:

I’m not an expert on coding even 1%. So to use this component, I’d have to turn that component off. Can you suggest/change something which could move it a bit upwards? Or guide me I can open the component code and make changes to ‘variables’. Not more that!

2개의 좋아요

Oh ok that’s my bad. I use absolute position to put it under the Save Changes button as there is no plugin outlet on that place. I removed the absolute position to fix this now. It will appear above the Save Changes button.

Please update the theme component again.

3개의 좋아요

Oh! You’re great.
Thanks! Otherwise I’d have to choose one of the 2 components.


Now I can use both. Thanks.

P.S. I hope this component button won’t interfere/intercept the default ‘Account Deletion’ button, that is supposed to appear on those user’s pages, which don’t have any posts created by them.

1개의 좋아요

Nope, it won’t appear for users when the default Delete My Account button active.

4개의 좋아요

How does this work for users who don’t have permissions to send PMs? For us PM-ing starts at TL2.

That’s covered in the start post

3개의 좋아요

Thanks! One more question: how do I get linebreaks into my modal description? Because right now I’ve got this:

1개의 좋아요

have you tried the html <br> line break yet?

2개의 좋아요

I’m going through, setting up the Account Deletion Request theme component settings.

I updated about 5 different fields, and then noticed the save/cancel buttons next to each field. So I hit the one closest to the mouse… and the whole page refreshed - losing all my other edits. :cry:

If you’re going to make me do this on a field level, it should work on a field level. If you’re going to refresh the entire page, then I should have one set of buttons for the entire page.

This is the worse of both worlds. :cry:

6개의 좋아요

This is true for all of the fields specifically in the account deletion request theme component.

Might want to move this request to be a comment under the account deletion request theme component page?

2개의 좋아요

I moved this topic to the account deletion request theme component… although, when I pull that component locally, I can’t reproduce the issue.

Do you have a consistent repro here @ganncamp?