https://bugs.contribs.org/show_bug.cgi?id=10774
Bug ID: 10774
Summary: NFR -Use 'php' config values when there are no
specific php-scl settings configured
Classification: Contribs
Product: SME Contribs
Version: Futur
Hardware: ---
OS: ---
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: smeserver-php-scl
Assignee: [email protected]
Reporter: [email protected]
QA Contact: [email protected]
Target Milestone: ---
Created attachment 6189
--> https://bugs.contribs.org/attachment.cgi?id=6189&action=edit
20ResourceLimits
I've seen 2 or 3 topics on the wiki from people who have trouble translating
their built-in php configuration settings to the php-scl versions of php.
I'd like to propose that signal-event php-update look at the 'php'
configuration for possible default values of the supported config values.
Specifically, I think the current config flow works like this:
- if there is an ibay-specific value, use that
- if there is a php-scl specific value (eg for php56), use that
- otherwise use a default
I'm proposing adding a check for existing 'php' configurations:
- if there is an ibay-specific value, use that
- if there is a php-scl specific value (eg for php56), use that
- if there is a php specific value (for 'php'), use that
- otherwise use a default
This would apply to these configuration settings:
> AllowUrlFopen=Off #(On/Off)
> MaxExecutionTime=30
> MaxFileUpload=20
> MaxInputTime=60
> MemoryLimit=128M
> PostMaxSize=20M
> UploadMaxFilesize=10M
This requires updates to 4 templates for each php version:
20ResourceLimits
40DataHandling
60FileUploads
65FopenWrappers
--
You are receiving this mail because:
You are the QA Contact for the bug._______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at https://lists.contribs.org/mailman/public/contribteam/
