You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2. What new feature or functionality would you like to request?
Sock links in the studio are redirecting to 404 error pages. They are hardcoded in sock_links.html in the legacy studio and StudioFooter.jsx in the MFE. Currently, there is no way to configure them, and the only method to address this issue is to fork the edx-platform and frontend-component-footer repositories, which is difficult and time-consuming to maintain.
3. What product area does this feature affect?
Studio
4. Please describe the scope of the feature
The customization would affect the MFEs that are relying on the studio footer.
5. Please describe why you see a need for this feature
We don't want to show broken links to our users.
6. Please describe the potential impact and/or value of this feature
Controlling the footer links via settings is much easier to maintain than forking the studio footer.
7. Please provide 2-3 use cases and/or user stories in support of this feature
As an operator, when users visit our website, we want to display instance-appropriate URLs.
As a user, I wouldn't want broken links on the page.
8. Any additional information you'd like to provide?
No response
The text was updated successfully, but these errors were encountered:
1. Is there an existing issue for this?
2. What new feature or functionality would you like to request?
Sock links in the studio are redirecting to 404 error pages. They are hardcoded in sock_links.html in the legacy studio and StudioFooter.jsx in the MFE. Currently, there is no way to configure them, and the only method to address this issue is to fork the edx-platform and frontend-component-footer repositories, which is difficult and time-consuming to maintain.
3. What product area does this feature affect?
Studio
4. Please describe the scope of the feature
The customization would affect the MFEs that are relying on the studio footer.
5. Please describe why you see a need for this feature
We don't want to show broken links to our users.
6. Please describe the potential impact and/or value of this feature
Controlling the footer links via settings is much easier to maintain than forking the studio footer.
7. Please provide 2-3 use cases and/or user stories in support of this feature
8. Any additional information you'd like to provide?
No response
The text was updated successfully, but these errors were encountered: