“Version” parameter for musescore.org
Need I explain? It would be nice to know what version a person is using when they post, that’s all.
Do you still have an unanswered question? Please log in first to post your question.
Need I explain? It would be nice to know what version a person is using when they post, that’s all.
Do you still have an unanswered question? Please log in first to post your question.
Comments
Everyone should mention what version of MuseScore and what OS they are using. We keep asking for that...
In reply to Everyone should mention what… by Jojo-Schmitz
So then a drop-down for selecting the version when creating a post — and filtering posts — would help with that! People would be required to specify what version of MS they’re using and that would probably confuse people trying to seek help for their .com subscriptions.
In reply to So then a drop-down for… by Asher S.
Thanks for this discussion!
On the release of MuseScore 4 I expected .org would create a new set of MS4 folders so MS4 posts wouldn't become mixed with issues regarding previous MuseScore releases.
Drop-downs like we have on Github could help significantly.
A required Version dropdown could store a Version text slug like MS4.1, MS 4.2 ...
Then on post, the slug is prepended to the user's Title text.
And a Post Type could largely ensure that posts go to a meaningful forum area:
• Support and Bugs
• Feature Requests
• General Discussion
• Documentation
Additionally the belatedly proposed dropdown could have contained choices for:
• Online File Sharing
• Subscription
• Payments
• Refunds
• and various other obvious .com issues
... and when the user selects one those they're directed to an appropriate .com area—thus reducing the influx of .com questions. I guess there wasn't adequate planning or resources.
Too late to fix? How would a filter script reassign posts to the correct areas? What happens to SEO? Wouldn't every moved post need a redirect? Seems daunting.