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] Checking 'default rom' doesn't work anymore #1154

Closed
gen-angry opened this issue Sep 2, 2024 · 1 comment
Closed

[Bug] Checking 'default rom' doesn't work anymore #1154

gen-angry opened this issue Sep 2, 2024 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@gen-angry
Copy link

RomM version
3.5.0

Describe the bug
When checking on 'default rom' with multiple versions, it generates a javascript console error. Going back out and in the rom shows that the default state did not save either.

It worked fine in 3.4.0

To Reproduce
Steps to reproduce the behavior:

  1. Go to a rom with two different versions
  2. Click on default checkmark

Expected behavior
Default checkmark stays on and it marks a particular rom version as the default version.

Screenshots
Error generated by console when checking a default option
Screenshot 2024-09-01 210420

Desktop (please complete the following information):

  • OS: Win11
  • Browser Firefox
  • Version 129

Additional context
I had cleared all RomM data and re-imported my entire library due to a ton of changes. So the database data itself should be 'updated' fully.

@gen-angry gen-angry added the bug Something isn't working label Sep 2, 2024
@gantoine gantoine self-assigned this Sep 2, 2024
@gantoine
Copy link
Member

gantoine commented Sep 2, 2024

This should be fixed in the upcoming path release.

@gantoine gantoine closed this as completed Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants