Closed Bug 466738 Opened 16 years ago Closed 16 years ago

Set PHP directives for Community Store

Categories

(Websites :: communitystore.mozilla.org, defect)

Product:
Websites
Component:
communitystore.mozilla.org
Platform:
All
Other
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: abuchanan, Unassigned)

References

Details

We'll need to set some PHP directives for large uploads. These can be set per directory, either in php.ini or apache directives. This should be done for both community-store.authstage.m.c and the upcoming production site upload_max_filesize should be 20M post_max_filesize should be 20M in apache conf, this can be done like... php_value upload_max_filesize 20M php_value post_max_filesize 20M Thanks
More info on this: We are seeing blank uploads for some large files here: http://community-store.stage.mozilla.com/upload. We need to change any configuration for Apache and PHP to allow large file uploads. Off the top of my head I can think of: max_input_time - Uploads could take a few mins on dialup, so 5 mins? post_max_size Could we set these in a .htaccess file? If so, we can do it on our side.
Severity: major → blocker
Memory limit might need to be increased too.
Guys this is probably not a blocker. A critical maybe.
Assignee: server-ops → aravind
added... php_value upload_max_filesize 20M php_value post_max_filesize 20M to docroot/.htaccess in r20293 I think we can change any settings we need for now in .htaccess, so closing this.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Upped memory_limit to 60M in .htaccess file, not sure yet if it will fix it.
Assignee: aravind → nobody
Severity: blocker → critical
Status: RESOLVED → REOPENED
Component: Server Operations → communitystore.mozilla.org
Product: mozilla.org → Websites
QA Contact: mrz → communitystore-mozilla-org
Resolution: FIXED → ---
Target Milestone: --- → 1.0
Blocks: 463311
Upped memory limit to 500m, which fixed the problem.
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
500MB? that sounds pretty excessive... oremj, thoughts?
We needed it that high because users are uploading images and they are being resized. Large images (4-5MB) went beyond 60MB and 250MB. I'm all ears for other options for resizing images that don't need as much memory.
You need to log in before you can comment on or make changes to this bug.