MultiPHP INI Editor – Basic Mode vs Editor Mode

MultiPHP INI Editor is cPanel’s native tool for adjusting PHP configuration values when CloudLinux PHP Selector isn’t available. It has two modes that confuse first-time users: Basic Mode for common settings, and Editor Mode for full php.ini editing. This guide explains what each does, when to use which, and how the settings propagate.

Where to find it

cPanel → Software → MultiPHP INI Editor. The page opens with a PHP version selector at the top — pick the ea-phpXX you want to edit, then choose Basic Mode or Editor Mode tabs.

Critical detail: settings are per PHP version, not global. If you change memory_limit on ea-php82 and your domain runs ea-php83, the change has no effect. Always edit the version your sites actually use (check via MultiPHP Manager).

Basic Mode — common settings with a form

Basic Mode lists the most commonly tuned PHP values with form fields and a brief description of each:

• allow_url_fopen — Whether PHP can open URLs as files via fopen(). Often needs to be on for plugins/CMSes.
• allow_url_include — Whether PHP can include() remote URLs. Keep OFF (major security risk if on).
• display_errors — Show PHP errors in browser. OFF in production; ON only for debugging.
• file_uploads — Allow file uploads via forms. ON for most sites.
• max_execution_time — Max seconds a script can run before being killed. 30 default; raise to 120-300 for heavy operations.
• max_input_time — Max seconds for parsing input data. 60 default; raise if dealing with very large forms.
• max_input_vars — Max form fields per request. 1000 default; raise to 5000 for complex admin pages.
• memory_limit — Max memory per script. 128M baseline; 256M-512M for WordPress + plugins.
• post_max_size — Max body size for POST requests. Must be ≥ upload_max_filesize.
• session.gc_maxlifetime — How long session data persists. Default 1440 seconds (24 min).
• session.save_path — Where session files live. Default is fine; only change if you know why.
• upload_max_filesize — Max single file upload. 64M is a reasonable target for most sites.

Edit values, click Apply. Changes take effect immediately for new requests (no PHP restart needed for FPM-managed reloads, though Editor Mode may require one — see below).

Basic Mode covers 95% of what most sites need to tune. If a value isn’t listed here, go to Editor Mode.

Editor Mode — raw php.ini editing

Editor Mode shows the actual php.ini file as a text area you can edit directly. Every PHP directive is fair game — including ones not in Basic Mode (disable_functions, opcache settings, mail.add_x_header, etc.).

Use when:

• You need to set a directive not shown in Basic Mode.
• You’re hardening security (disable_functions setup — see disable_functions guide).
• You’re tuning opcache or other advanced settings.
• You need to comment out a directive entirely (Basic Mode can’t do this).

Save changes with the button below the editor. Cache mostly handles itself but FPM restart may be needed for some changes to fully take effect — open a ticket if you don’t see your change reflected after 5 minutes.

Risks of Editor Mode

Editor Mode is powerful and easy to break things with. Bad syntax breaks PHP for ALL sites on that version.

• Copy the existing content into a text file before making changes. Quick rollback if needed.
• One directive at a time if you’re uncertain. Test after each.
• Check syntax. Bad ini syntax = PHP doesn’t start = 500 errors site-wide.
• Don’t paste from random tutorials without understanding each directive.

Settings precedence — what overrides what

PHP configuration has layers. From lowest to highest priority:

• Hard-coded defaults — built into PHP.
• System php.ini — at /opt/cpanel/ea-phpXX/root/etc/php.ini. Edited by MultiPHP INI Editor.
• Conf.d files — PHP also reads /opt/cpanel/ea-phpXX/root/etc/php.d/*.ini for additional configuration (mostly extension settings).
• User-level .user.ini — file you place in your site root to override specific settings for that site only.
• Per-directory .htaccess — for Apache handlers, PHP values can be set via php_value and php_flag directives in .htaccess.
• Per-script ini_set() — explicit ini_set('memory_limit', '256M') in PHP code, highest priority.

MultiPHP INI Editor changes the system layer, affecting all sites using that PHP version. To override for one specific site, use .user.ini or .htaccess. See per-domain PHP settings.

Verifying your changes took effect

Same methods as PHP version verification — phpinfo file, WordPress Site Health, or HTTP headers. Look for the specific values you changed (memory_limit, upload_max_filesize).

If a value shows what you didn’t set: cache or override at a higher precedence layer. Check .htaccess and .user.ini for the domain.

When changes don’t seem to work

1. Wrong PHP version edited. The most common cause. MultiPHP INI Editor shows you the version dropdown at top — must match what your domain actually runs in MultiPHP Manager.

2. Override at higher level. .htaccess or .user.ini may be setting the same value differently. Check both.

3. FPM cached config. Some PHP-FPM setups cache configuration. Open a ticket for an FPM restart if your change isn’t showing after several minutes.

4. Application-level override. WordPress’s WP_MEMORY_LIMIT in wp-config.php can override PHP’s memory_limit (downward only — can’t exceed PHP’s setting).

Common questions

“I edited Basic Mode for ea-php82 but my domain is on ea-php83. Why didn’t it work?” Settings are per-version. Change the version dropdown at top of MultiPHP INI Editor to ea-php83, edit, save.

“Does this affect other users on the server?” No. Edits via cPanel’s MultiPHP INI Editor are applied to your account’s php.ini overlay — they don’t affect other cPanel accounts on the same server.

“What’s the difference between MultiPHP INI Editor in cPanel vs WHM?” WHM’s version (Server Configuration → MultiPHP INI Editor) edits server-wide defaults. cPanel’s version applies to your specific account. On shared hosting you only see the cPanel version.

“Can I enable PHP extensions here?” No — Basic and Editor modes adjust ini values, not extension loading. Extension loading is at server level. On non-CloudLinux servers, available extensions are whatever the server admin installed for that ea-phpXX. Open a ticket if you need a specific extension enabled.

“I changed Editor Mode and now my site shows 500 errors.” Syntax error in the ini you saved. Open Editor Mode again, revert to last-known-good content. If you can’t recover, ticket support with details — we can restore from server-level defaults.

What’s next

• Specific values worth tuning: Common php.ini settings.
• Locking down PHP execution: disable_functions hardening.
• Per-site overrides: .htaccess and .user.ini.
• Pick PHP version first: MultiPHP Manager.

Basic Mode covers most needs with safe form-based editing. Editor Mode unlocks anything PHP supports but requires care. The biggest gotcha across both: settings are per-version, so always confirm you’re editing the version your site actually runs.