musescore / musescore/MuseScore

Cloud scores deleted on the website still show in New & recent list

Open
#13,839 2 comments 0 reactions 2 assignees View on GitHub

Nobody has claimed this yet.

cloud needs design P2
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Describe the bug
When working with scores that have been saved to the cloud and are thus on musescore.com/my-scores:
If you delete a score from the online score manager, the corresponding file in [whatever hard drive]:\MuseScore4Development\Cloud_Scores is not deleted. Thus, the Home tab still displays thoses scores even though they no longer exist.

To Reproduce

  1. Create a score and save it to the cloud.
  2. Close Musescore 4.
  3. Go to musescore.com/my-scores and delete said score.
  4. Open Musescore and see that the score is still in the home tab.

Expected behavior
I assume MuseScore should notice I deleted the score from the online manager and delete the corresponding file that links to it.

Platform information

  • Windows 10

Additional context
In this report I assumed that the files in [whatever hard drive]:\MuseScore4Development\Cloud_Scores are indeed files that link to the online scores so that we can work on it in real time (the same way an editing software creates a link file that tells it where to look for the actual media file).
BUT, if I misunderstood, these files might be actual score files. In this case, I suggest adding a message that somehow makes the user aware that this file still exists even though they deleted the online version of it.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.