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 Report] Performer aliases are always updated in Tagger even when set to exclude #5565

Open
bayured opened this issue Dec 20, 2024 · 0 comments · May be fixed by #5566
Open

[Bug Report] Performer aliases are always updated in Tagger even when set to exclude #5565

bayured opened this issue Dec 20, 2024 · 0 comments · May be fixed by #5566
Labels
bug report Bug reports that are not yet verified

Comments

@bayured
Copy link
Contributor

bayured commented Dec 20, 2024

Describe the bug
When using the performer tagger view, when saving, aliases are always updated even when unticked or aliases are in the Excluded fields configuration.

To Reproduce
Steps to reproduce the behavior:

  1. Go to the Performer tagger view.
  2. Match a performer that has an alias on the Stash box instance.
  3. Untick the Aliases field in the modal popup.
  4. Save the performer.
  5. Go to the performer. The aliases are updated even with the field not ticked.

Expected behavior
Aliases should not be updated if the field is not ticked.

Stash Version: (from Settings -> About):
v0.27.2-37-g0621d871

Desktop (please complete the following information):

  • OS: Linux/Windows
  • Browser Firefox/Edge/Chrome
  • Version Latest of all
@bayured bayured added the bug report Bug reports that are not yet verified label Dec 20, 2024
@github-project-automation github-project-automation bot moved this to To triage in Bug fixing Dec 20, 2024
@bayured bayured linked a pull request Dec 20, 2024 that will close this issue
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: To triage
Development

Successfully merging a pull request may close this issue.

1 participant