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

[Bug] Different dashboard options on different PC's #237

Closed
ManCaveMedia opened this issue Apr 22, 2021 · 4 comments
Closed

[Bug] Different dashboard options on different PC's #237

ManCaveMedia opened this issue Apr 22, 2021 · 4 comments

Comments

@ManCaveMedia
Copy link

On one of my PC's I have far more options for settings the dashboard order than on another.
(Downloaded, Uploaded, Availability and some more)
I think it's due to it storing previous settings and not updating the settings with new options.

Is there a way to remove or reset the settings so newer options on the dashboard become available?

@m4ximuel
Copy link
Contributor

VueTorrent does not act as a server. Therefore, VueTorrent's own settings cannot be shared between other PCs.

@ManCaveMedia
Copy link
Author

ManCaveMedia commented Apr 22, 2021

OK, I understand that.
But where are the settings stored? I've deleted several cookies on my laptop but I'm still not able to see/sort/ enable the mentioned options (Downloaded, Uploaded, Availability and some more)

When I open the URL on a different browser on the same laptop or in the same browser on a different PC the options are there...

@ManCaveMedia
Copy link
Author

OK, nevermind...
It took me a couple of times to find the cookie. Since I'm using a reverse proxy and DNS settings I had to find al (previously used) versions of the cookie to delete them all. Seems to be working correctly now.

But is still weird that I never saw the newer options/labels on the dashboard settings when they were added.
I'll leave it up to you to determine whether this needs a fix.

@m4ximuel
Copy link
Contributor

@ManCaveMedia ooh.. I guess you are having the same problem as mentioned here: #121
The problem you mentioned is definitely a bug.

@WDaan WDaan closed this as completed Apr 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants