-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix: open new editors from non-unit Studio container page #33575
fix: open new editors from non-unit Studio container page #33575
Conversation
Thanks for the pull request, @ArturGaspar! Please note that it may take us up to several weeks or months to complete a review and merge your PR. Feel free to add as much of the following information to the ticket as you can:
All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here. Please let us know once your PR is ready for our review and all tests are green. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- I tested this: Followed the test instructions and verified that the new editors are launched.
- I read through the code
- I checked for accessibility issues
- Includes documentation
Needed to run make cms-static
when testing to get it to work. Shouldn't be a concern in deployments
@jristau1984 @cablaa77 This should resolve TNL-10884. |
@navinkarkera One more PR to label "jira:2u" :) |
Sandbox destroy request received. |
I don't have a Jira project configured for this repo in the private 2U Jira. Contact Ned Batchelder (@nedbat) to set up a project. |
Sandbox destroy request received. |
21 similar comments
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
10 similar comments
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox destroy request received. |
Sandbox deployment successful. Sandbox LMS is available at pr-33575-139931.staging.do.opencraft.hosting Instance config : https://grove-stage-build-logs.nyc3.digitaloceanspaces.com/34602668-5657499809-config.yml |
@jristau1984 @cablaa77 Hi, do you think you could find someone to review this, please? |
This has been accepted by 2U partner support who have historically used this legacy view to help partners that are having react-based editor issues. 2U did not do a technical review of the change, as it looks like it has already been reviewed by the community. |
@mphilbrick211 @jristau1984 I can help review this PR as CC. |
Perfect, thank you @pkulkark! |
@pkulkark Hi, would you be able to spare some CC hours to get this merged? |
@ArturGaspar @tecoholic Sorry for the delay. I'll review this shortly. |
Make the edit button on a container page for a non-unit block (i.e. an individual text, problem or video block) open the new editor when the relevant flag is enabled.
bd12b4b
to
af7ba44
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
- I tested this: I verified that the "edit" button in studio container page opens the new editors for text,video and problem components, as described in the testing instructions
- I read through the code
[ ] I checked for accessibility issuesN/A[ ] Includes documentationN/A
@ArturGaspar 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future. |
2U Release Notice: This PR has been deployed to the edX staging environment in preparation for a release to production. |
2U Release Notice: This PR has been deployed to the edX production environment. |
1 similar comment
2U Release Notice: This PR has been deployed to the edX production environment. |
Make the edit button on a container page for a non-unit block (i.e. an individual text, problem or video block) open the new editor when the relevant flag is enabled.
Description
The Studio Course Container page "Edit" button goes to legacy editors. This pull request fixes that so it goes to the new editors.
Impacts Course Author users.
Testing instructions
Enable the new editors (create waffle flags new_core_editors.use_new_text_editor, new_core_editors.use_new_problem_editor, new_core_editors.use_new_video_editor enabled for everyone).
Find the block id.
Click "Edit" on a block.
See that you are redirected to the new editor.
Find the block id from the last path component of the URL.
block-v1:edX+DemoX+Demo_Course+type@html+block@030e35c4756a4ddc8d40b95fbbfff4d4
.Go to
http://localhost:18010/container/[block id]
.http://localhost:18010/container/block-v1:edX+DemoX+Demo_Course+type@html+block@030e35c4756a4ddc8d40b95fbbfff4d4
.Click the "Edit" button on the top right of the page.
See that you are redirected to the new editor.
Repeat for the 3 block types: text, problem, video.
Deadline
None
Other information
Private-Ref: BB-7941