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

Issue: 'Show Male Performers' Setting Not Retained Across Sessions #5065

Closed
gitbork opened this issue Jul 11, 2024 · 1 comment · Fixed by #5165
Closed

Issue: 'Show Male Performers' Setting Not Retained Across Sessions #5065

gitbork opened this issue Jul 11, 2024 · 1 comment · Fixed by #5165
Labels
bug report Bug reports that are not yet verified

Comments

@gitbork
Copy link

gitbork commented Jul 11, 2024

Description:

The 'Show Male Performers' setting in the scraping configuration should persist across application restarts, page reloads, and different browser sessions. Currently, this setting does not remain enabled when loading the application in a new session (e.g., in a different browser) or after a server/application reload.

Steps to Reproduce:

  1. Enable the 'Show Male Performers' setting in the scraping configuration.
  2. Reload the page, restart the application, or open the application in a different browser session.
  3. Observe that the 'Show Male Performers' setting is not retained.

Expected Behavior:

The 'Show Male Performers' setting should remain enabled across sessions and after application restarts.

Actual Behavior:

The 'Show Male Performers' setting does not stay enabled when reloading the application or starting a new browser session.

Screenshot:

image

Additional Notes:

It can be frustrating to have to re-enable this setting repeatedly, especially when other settings retain the user's preferences. Initially, I wondered if this behavior was intentional, but I quickly realized it was likely an oversight. Given the dedication and quality of the development team, I'm confident this issue will be addressed in a future update.

Thank you for the fantastic app! As a queer user, my partner and I greatly appreciate your ongoing efforts and commitment to inclusivity.

@gitbork gitbork added the bug report Bug reports that are not yet verified label Jul 11, 2024
@github-project-automation github-project-automation bot moved this to To triage in Bug fixing Jul 11, 2024
@DogmaDragon
Copy link
Collaborator

Related to #3210, #4982

Do you have cookies enabled? It should persist through reloads and restarts. Only deleting browser cookies/storage, using a different browser or using incognito mode should reset them.

Tagger config is stored in IndexedDB on your browser. But it's on the roadmap at 40 position to improve it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug report Bug reports that are not yet verified
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants