Pivotlar gives you full control over PHP-level behavior for each individual WordPress site — all through a clean, intuitive web interface. No command line, no manual configuration. Just point, click, and configure.
Whether you’re troubleshooting a plugin, uploading large files, or hardening session security, you can adjust important php.ini directives per site directly in the Site Details > PHP Settings tab.
Available PHP INI Settings (Per Site) #
These PHP settings are configurable per site in Pivotlar. Site-level values always take precedence over global (PHP version) settings.
| Setting | Directive | Default Value | Unit |
|---|---|---|---|
| Memory Limit | memory_limit | 256 | MB |
| Max Input Time | max_input_time | 60 | Seconds |
| Default Socket Timeout | default_socket_timeout | 60 | Seconds |
| Max File Uploads | max_file_uploads | 20 | Files |
| Max Input Variables | max_input_vars | 5000 | Variables |
| Upload Max Filesize | upload_max_filesize | 512 | MB |
| Post Max Size | post_max_size | 512 | MB |
| Max Execution Time | max_execution_time | 300 | Seconds |
| Session Cookie Lifetime | session.cookie_lifetime | 0 | Seconds |
| Session GC Max Lifetime | session.gc_maxlifetime | 1440 | Seconds |
| Short Open Tag | short_open_tag | off | Boolean (on/off) |
How to Configure PHP Settings #
- Go to your Site Dashboard in Pivotlar.
- Click into the site you want to configure.
- Navigate to the PHP Configurations tab.
- You’ll see editable fields for each supported PHP directive.

- Adjust values as needed.
- For example:
- Increase
upload_max_filesizeto 1024 MB if uploading large files - Enable
short_open_tagfor legacy themes/plugins
- Increase
- For example:
- Click Update to apply changes.
- The server will automatically reload the PHP-FPM configuration in the background.
Notes & Best Practices #
- Site-specific overrides ensure changes won’t affect other WordPress sites on the same server.
- There is no need to reload PHP manually — Pivotlar handles it behind the scenes.
- For optimal performance and security, avoid setting unreasonably high values unless required by your application.
- Use
session.gc_maxlifetimeandsession.cookie_lifetimeto control session persistence across user sessions. - Enabling
short_open_tagis generally discouraged unless legacy code requires it.
Why Configure PHP Per Site? #
Having the ability to tune PHP settings per site allows you to:
- Accommodate plugin or theme requirements
- Improve performance on resource-heavy sites
- Strengthen session and upload security
- Avoid global changes that could impact other tenants
Need Help? #
Reach out to our support team via support@pivotlar.com