-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow owner to disable guest links #543
Comments
Does that mean you want the ability to re-enable that same link later? |
beeing able to enable and disable links with a switch would be a quite greate feature |
@mtlynch I'm interested in working on this issue. Can I be assigned to it?🤩 |
@x1uc - Sure, that would be great! |
mtlynch
added a commit
that referenced
this issue
Jan 11, 2025
**feat:** Allow owner to disable guest links This PR implements the feature request in [#543](#543). To summarize what has been done: - Added a column (`disabled`) to the `guest_links` table & the `GuestLink` struct. - Updated the `isActive` check for guest links to include the `disabled` field. - Added a column on the guest links front page, with a button to enable/disable the link. - Added new APIs related to managing guest links' disabled state. I’m a beginner, and I believe there may be many areas where my work lacks standardization from your perspective. Please point them out, and I will work on improving. I’m very glad to hear your suggestions, which will not only improve the quality of this project but also enhance my programming skills. ---- Screen  --------- Co-authored-by: Michael Lynch <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I just ran into a situation where I accidentally published a guest link too widely. I wanted to expire it and add a note explaining why it was disabled, but my only option was to delete it.
The text was updated successfully, but these errors were encountered: