Opened 14 years ago
Closed 14 years ago
#15966 closed defect (bug) (duplicate)
256MB Memory Limit is Hardcoded and Un-Configureable
| Reported by: |
|
Owned by: | |
|---|---|---|---|
| Milestone: | Priority: | low | |
| Severity: | minor | Version: | 3.1 |
| Component: | General | Keywords: | has-patch |
| Focuses: | Cc: |
Description
Memory settings can not be configured in part with Wordpress because some values are hardcoded into the application ('256M' mostly in backend code).
A site administrator should be able to configure the memory limit overall in wp-config.php but the hardencoded values prevent that.
As a solution, the hardcoded values can be replaced with a configuration constant as it is common practice in Wordpress.
I would love to see this in 3.1.
Attachments (1)
Change History (5)
#1
follow-up:
↓ 2
@
14 years ago
- Milestone changed from Awaiting Review to Future Release
- Priority changed from normal to low
- Severity changed from normal to minor
#2
in reply to:
↑ 1
@
14 years ago
Replying to westi:
Extra constants are bad :-(
Magic Numbers are even more bad.
This is so far out of possibility for 3.1
Well the only other options we can give administrators then is to edit code, I see.
Note: See
TracTickets for help on using
tickets.
Extra constants are bad :-(
This is so far out of possibility for 3.1