Skip to content
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

[Feature Request]: Default General View Settings #1582

Open
1 task
xmoosex opened this issue Mar 16, 2024 · 2 comments
Open
1 task

[Feature Request]: Default General View Settings #1582

xmoosex opened this issue Mar 16, 2024 · 2 comments
Labels

Comments

@xmoosex
Copy link

xmoosex commented Mar 16, 2024

Description

It would be nice to have the option to setup a default view setting that is populated when viewing. This is currently not possible as the view settings are set back to a default value after cookies are refreshed in the browser

Describe the solution you'd like

An option to set whatever your current view settings are as the global default.
An example of this would be the sabzbd global settings where any device viewing the queue list would see the same categories.
I believe this could be implemented by saving the settings in a file (JSON perhaps) that would then be checked every time the user loads into the site for the first time. It would grab the JSON values and create the cookie.

Describe alternatives you've considered

None

Complementary informations

  • Is this feature already implemented in the default WebUI?
@xmoosex xmoosex added Feature New Feature triage Issue hasn't been assessed yet labels Mar 16, 2024
@Larsluph
Copy link
Collaborator

VueTorrent being only a WebUI this can't be done natively.

However, I'm currently working on a workaround to this with #1547 👀

Even with that workaround, you'll have to specify the backend URL after each cleanup.

@xmoosex
Copy link
Author

xmoosex commented Mar 16, 2024

VueTorrent being only a WebUI this can't be done natively.

However, I'm currently working on a workaround to this with #1547 👀

Even with that workaround, you'll have to specify the backend URL after each cleanup.

Thanks for the info! I’ll keep an eye out on #1547

@Larsluph Larsluph added backend and removed triage Issue hasn't been assessed yet labels Apr 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants