-
Notifications
You must be signed in to change notification settings - Fork 196
patchability of UPLOAD_FILE_MAX_SIZE #1661
Copy link
Copy link
Open
Labels
bugReport of or fix for something that isn't working as intendedReport of or fix for something that isn't working as intendedgood first issueA good task for a newcomer to start withA good task for a newcomer to start withhelp wantedReady to be picked up by anyone in the communityReady to be picked up by anyone in the community
Metadata
Metadata
Assignees
Labels
bugReport of or fix for something that isn't working as intendedReport of or fix for something that isn't working as intendedgood first issueA good task for a newcomer to start withA good task for a newcomer to start withhelp wantedReady to be picked up by anyone in the communityReady to be picked up by anyone in the community
Hi all, so sorry if I've logged this to the wrong place, or I'm being an idiot and there is a way to do this that I'm completely missing
In frontend-app-authoring/src/constants.js#L55 we have a constant "UPLOAD_FILE_MAX_SIZE = 20 * 1024 * 1024"
Insofar as I've found, there's no way to easily override this value without forking the repo and manually editing this value.
This breaks compatibility of the legacy patch (without MFE)
Is it possible that a patch can be implemented for the override of this value?
Or, perhaps a viable patch option would be to read the value of MAX_ASSET_UPLOAD_FILE_SIZE_IN_MB stored in "cms/envs/tutor/production.py" (already patchable via via the legacy openedx-cms-production-settings) to keep the contentstore.new_studio_mfe.use_new_files_uploads_page consistent with the old patch.
Here is a link to a discussion I opened and my findings
https://discuss.openedx.org/t/correctly-patch-max-asset-upload-file-size-in-mb/14572/5
There was another user who asked an equivalent question here, which I linked back to my above post:
https://discuss.openedx.org/t/max-asset-upload-file-size-in-mb-in-sumac-version/14930
Thanks for your consideration :)