musescore / musescore/MuseScore
[MU4 Issue] Name & settings keep reverting to defaults each time I publish a score
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 15.1k
- Forks
- 3.3k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 91
Description
Describe the bug
In at least one of my scores, each time I publish to musescore.com, the title in the initial publish dialog as well as the genre and the rights settings in the dialog that opens after the upload completes keep resetting to default
To Reproduce
Steps to reproduce the behavior:
- Create a score, and don't give it a title
- Save the score
- Publish to musescore.com and accept the default title suggestion, which is the filename)
- Change the title, genre, and rights after upload
- Save the score normally again
- Reload the score
- Publish again
- See error: the initial publish dialog shows the filename as the title, not the one you entered previously at step 4. And when the upload completes, the dialog shows the default genre and rights as well
Expected behavior
The settings I made on the first previous upload should be preserved
Platform information
- OS: Linux
Additional context
The title problem doesn't happen with every score I have, and I think the difference is, whether the title was set in the initial publish dialog or whether it was changed later. It seems whatever you set in the initial publish dialog on first upload, you're stuck with on each subsequent update. The resetting of genre & rights happens every single time though. And for some reason, musescore.com has apparently decided every single score I create is "jazz". I gather that's not the default for everyone, but it is for me it seems.
BTW, it's also the case that if in step 4, I had set the score to unlisted, this also is lost. I understand it's by design, but I'd strongly suggest this design should be changed. What's the point of having an unlisted setting in the first place if it's going to revert to private on every update?
See also https://github.com/musescore/MuseScore/issues/13968, which is about a similar issue but with "save online" instead of "publish".
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue through the publish dialog, following the first-upload and subsequent-update paths described in the report. Compare the title, genre, rights, and visibility values before and after reloading the score; done means those previously selected settings remain available on later publishes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cloud, desktop
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100