There is a critical issue in the studio portion of the app where users are able to make updates to the information of releases that have already been published. Once a release is published and moves out of draft mode, the expectation is that its information becomes locked to prevent unauthorized or accidental changes. However, the current functionality allows for continued edits, posing a risk to the integrity of published content.
To Reproduce
Steps to reproduce the behavior:
Log into the app and navigate to the Studio section.
Select a release that has already been published.
Attempt to modify the release information (e.g., title, description, tracklist).
Save the changes.
Expected behavior
The app should restrict editing capabilities for releases once they have been published. Ideally, all fields should become read-only, and any attempt to save changes should result in an error message indicating that published releases cannot be edited.
Actual behavior
The app allows users to edit and save changes to releases that are in a published state, without displaying any warnings or error messages.
Screenshots
N/A
Environment:
OS: Win 11
Browser: Brave
Additional context
This issue was discovered during routine content management in the Studio section of the app. It has been verified that this behavior occurs regardless of the user's role or permissions, suggesting it is not related to specific account settings.
As a temporary measure, we have disabled the ability for users to navigate directly to the release page within the studio. This precaution is in place while we address the underlying issue.
Describe the bug
There is a critical issue in the studio portion of the app where users are able to make updates to the information of releases that have already been published. Once a release is published and moves out of draft mode, the expectation is that its information becomes locked to prevent unauthorized or accidental changes. However, the current functionality allows for continued edits, posing a risk to the integrity of published content.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The app should restrict editing capabilities for releases once they have been published. Ideally, all fields should become read-only, and any attempt to save changes should result in an error message indicating that published releases cannot be edited.
Actual behavior
The app allows users to edit and save changes to releases that are in a published state, without displaying any warnings or error messages.
Screenshots
N/A
Environment:
Additional context
This issue was discovered during routine content management in the Studio section of the app. It has been verified that this behavior occurs regardless of the user's role or permissions, suggesting it is not related to specific account settings.