Cannot modify the xblock info on Sumac

Site Operators
1

Hi everyone,

I’m currently trying to customize the PDF XBlock so that it can work on Open edX Sumac. While working on this, I ran into a few issues:

  • After customizing and rebuilding the image locally, I added the PDF XBlock to Advanced Settings.

  • When I create a new module with the pdf block, I can’t open the modal editor to update its information.

  • I noticed that the interface is supposed to switch to the old Studio editor instead of the MFE Authoring, but this does not happen.

  • I also tested with pre-installed XBlocks like SCORM and Google Document, and the same issue occurs (the modal editor won’t open)

Here is some images

Screenshot from 2025-09-20 18-20-20
Screenshot from 2025-09-20 18-20-201867×1003 117 KB

Screenshot from 2025-09-20 16-59-03
Screenshot from 2025-09-20 16-59-031070×310 13.4 KB

Screenshot from 2025-09-20 18-14-41
Screenshot from 2025-09-20 18-14-411867×1003 354 KB

Has anyone faced this issue before on Sumac? If so, how did you fix it?
Any help would be much appreciated.

2

@vuthehuyht could you kindly provide error traces in a code block, rather than a screenshot?

3

Try enabling the legacy_studio.unit_editor waffle flag, either for the course or for the whole Studio. I suspect there is an incompatibility between the PDF XBlock and the new Authoring MFE. If so, one of them will need to be fixed, but I’m not sure where the error lies.

The NoUpstream exception in your third screenshot is unrelated and can be ignored. In fact, we shouldn’t be logging it as an exception since it’s kind of a “normal” status in most cases. CC @kmccormick

2 Likes
4

Thanks, that is the solution I need

5

@braden If I provide the source code of the PDF XBlock, can you point out where it is incompatible?

6

Yes @vuthehuyht , please provide that, and we’ll do our best to find the incompatibility.

7

@kmccormick here is the version I have customized

1 Like
8

I have tried to enable the `legacy_studio.unit_editor` flag but the editor still use the MFE

image

9

It looks like you tried a flag called studio.legacy_studio.unit_editor but I believe it should be just legacy_studio.unit_editor.

1 Like
10

Hey @vuthehuyht , I recently tested the new unit editor with both your PDFXBlock and RaccoonGang’s PdfXBlock and did not encounter any issues. I was testing with Ulmo, so you are probably encountering a bug that existed in the Sumac release but was fixed since then.

Here’s the new unit editor in Ulmo with the PDF block:

image
image2048×1490 375 KB

Here’s what I recommend:

  • For Sumac, ensure that the contentstore.new_studio_mfe.use_new_unit_page waffle flag is set to No (False). This will ensure that you are using the legacy unit editor, which works with the PDF block.
  • When you upgrade to Teak, ensure that legacy_studio.unit_editor is set to Yes (True). This will ensure that you continue using the legacy unit editor.
  • When you upgrade to Ulmo, try setting legacy_studio.unit_editor back to No (False). This will switch you to the new unit editor. If you still see the issue in Ulmo, then let us know.
2 Likes
11

Thanks very much