MAX_ASSET_UPLOAD_FILE_SIZE_IN_MB in Sumac Version

Site Operators Site Operations Help
, ,
1

Hi everyone,

I deployed Open Edx application on docker with tutor 19.0 sumac version.
I want to increase the “MAX_ASSET_UPLOAD_FILE_SIZE_IN_MB” value. I created and activated the plugin as I used in previous versions.

name: upload-size
version: 1.0.0
patches:
openedx-cms-production-settings: |
MAX_ASSET_UPLOAD_FILE_SIZE_IN_MB = 500
openedx-lms-common-settings: |
UPLOAD_CHUNK_SIZE_IN_MB = 500

tutor plugins enable
tutor local launch

Then when I went into the lms and cms container, I saw that the values were 20 mb. I couldn’t throw files over 20 mb.
app@c4f8536d9f10:~/edx-platform$ cat cms/envs/common.py | grep MAX_ASSET
MAX_ASSET_UPLOAD_FILE_SIZE_IN_MB = 20

And last
I made changes from the “constants.js” file in the frontend-app-authoring component. And I got the build.

export const UPLOAD_FILE_MAX_SIZE = 250 * 1024 * 1024

The situation I’m facing is that the 20mb limit is still showing. After the first file I send is less than 20mb, I can send 250mb in the following files. How can I remove the limit shown?

image
image1030×681 35.2 KB

2

I had the same issue that I posted about here: Correctly patch MAX_ASSET_UPLOAD_FILE_SIZE_IN_MB
While I wasn’t able to figure out a solution for the new MFE, I worked around it by just disabling the Django waffle flag contentstore.new_studio_mfe.use_new_files_uploads_page which reverts to the legacy uploads page. It’s not necessarily a “fix” but at least it renders your existing patch functional