Opened 4 years ago
Closed 4 years ago
#32307 closed New feature (wontfix)
Allow change DATA_UPLOAD_MAX_MEMORY_SIZE per view
| Reported by: | lcd1232 | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | 3.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
Right now DATA_UPLOAD_MAX_MEMORY_SIZE is global settings and it cannot be different by a view. For example, I have an internal API and I want to increase this variable only for internal API, but it's not possible.
Note:
See TracTickets
for help on using tickets.
Hi. Thanks for the report.
I'm going to initially say
wontfixhere.This would add a degree of complexity into areas of the framework that are not generally user accessible, such that I don't think it would be acceptable.
As a workaround, either up
DATA_UPLOAD_MAX_MEMORY_SIZEor run a separate private internal instance exposing the view with the requirement for the upped limit.If you'd like to raise the topic on the DevelopersMailingList, you're welcome to do so (but I'd have a look at how
DATA_UPLOAD_MAX_MEMORY_SIZEis used to think how exposing it might be feasible first.)