The PHP Manager lets you pick the PHP version per domain, turn OPcache on/off, and open a simple form to tweak per-domain PHP options (upload limits, memory, errors, timezone). Changes apply to the selected site only.

Who can use this

The signed-in account owner. Resellers/admins may adjust it for your account. Parked domains use the main domain’s PHP settings and are not listed here.

Before you start

Check which PHP version your app supports (themes/plugins often require a minimum). If you’re unsure, newer apps usually work best on PHP 8.1–8.3; older apps may need 7.x.

What you see on this page

• A table with your domains (main, addon, subdomain).
• PHP Selector — a dropdown to choose the PHP version per domain.
• OPcache — a speed toggle; when enabled, a Cache Settings button appears.
• PHP Settings — opens a form to change common php.ini values for that domain.

Change PHP version (per domain)

1) Find the domain row.
2) Open PHP Selector and pick a version (e.g., PHP 8.2).
3) Wait a few seconds, then test your site. If something breaks, switch back or update your app/plugins.

Speed up with OPcache

1) Flip the OPcache switch on to cache compiled PHP and reduce load times.
2) Click Cache Settings (visible when OPcache is on) to fine-tune if available.
Tip: After major code updates, OPcache will refresh automatically; if you see “old code,” briefly toggle OPcache off/on or adjust cache settings.

Open PHP Settings (per domain)

1) Click PHP Settings on the domain row.
2) Adjust the fields below as needed.
3) Click Save Changes. Test your site and file uploads after changing limits.

PHP Settings — field guide

• allow_url_fopen — Allow file functions to fetch URLs (needed by some updaters).
• display_errors — Show PHP errors on pages. Off in production; use logs instead.
• file_uploads — Allow file uploads via PHP.
• upload_max_filesize — Max size of one uploaded file (MB).
• max_file_uploads — Max number of files in one request.
• max_execution_time — Max seconds a script may run.
• max_input_time — Max seconds to parse input (POST/GET/upload).
• max_input_vars — Max POST fields (useful for big forms/menus).
• post_max_size — Max size of total POST data (MB). Must be ≥ upload_max_filesize.
• memory_limit — Max RAM a script may use (MB). Should be ≥ post_max_size for large uploads.
• session.gc_maxlifetime — Session lifetime in seconds (e.g., 1440 = 24 min).
• session.save_path — Folder for PHP sessions (leave default unless instructed).
• disable_functions — Comma-separated list to block risky functions (keep defaults unless you know why).
• error_reporting — Error levels (e.g., E_ALL). Use with display_errors off in production.
• date.timezone — Server timezone for PHP date/time; pick your region/city.

Good defaults (safe starting points)

• display_errors: Off
• upload_max_filesize: 64–256M (as needed)
• post_max_size: equal or larger than upload_max_filesize
• memory_limit: 256–512M (heavier apps may need more)
• max_execution_time: 60–120s for imports/updates
• OPcache: On for public sites

Troubleshooting

• White page / 500 error after switching PHP: revert to the previous version; update plugins/themes to versions compatible with your target PHP.
• Uploads fail: increase upload_max_filesize, post_max_size, and possibly memory_limit; make sure post_max_size ≥ upload_max_filesize.
• Forms cut off or menus won’t save: raise max_input_vars (e.g., 3000–5000).
• Session/logins expire too quickly: increase session.gc_maxlifetime (and the app’s own session settings, if any).
• Seeing old code after deploy: toggle OPcache off/on or adjust cache settings; then reload.

Tips

Change one thing at a time and retest. Keep notes of values that worked. If you need a value higher than your plan allows, contact support about limits.