PHP error guide

Zend Studio legacy Xdebug configuration: meaning and fix

warning deprecated Affects: Xdebug 3.x except the nesting-level legacy page Last verified:

Error summary

Translate remote_enable, remote_host, and remote_port to Xdebug 3 mode/start/client settings. An old Zend Studio setup uses Xdebug 2 remote_* directives under Xdebug 3.

What it means

Translate remote_enable, remote_host, and remote_port to Xdebug 3 mode/start/client settings. An old Zend Studio setup uses Xdebug 2 remote_* directives under Xdebug 3.

What the error means

This message means that an old Zend Studio setup uses Xdebug 2 remote_* directives under Xdebug 3. The exact signature distinguishes zend studio legacy xdebug configuration from a generic application failure.

Why PHP produces it

The engine or service reports “Zend Studio legacy Xdebug configuration” because its required precondition was not met. Translate remote_enable, remote_host, and remote_port to Xdebug 3 mode/start/client settings.

PHP version notes

The zend studio legacy xdebug configuration wording here is based on Xdebug 3.x except the nesting-level legacy page; punctuation and exception class names can differ on older branches or vendor builds.

Most common causes

  • The immediate input or configuration reaches the specific condition: an old Zend Studio setup uses Xdebug 2 remote_* directives under Xdebug 3
  • The code path assumes the prerequisite for zend studio legacy xdebug configuration has already been satisfied.
  • For zend studio legacy xdebug configuration, development and production differ in version, extension, permissions, paths, or service configuration.
  • An earlier operation returned an unchecked value that is consumed by the line reporting zend studio legacy xdebug configuration.

Minimal examples

BAD — reproduces the problem

ini 
xdebug.remote_enable=1
xdebug.remote_host=127.0.0.1

FIXED — safer pattern

ini 
xdebug.mode=debug
xdebug.start_with_request=trigger
xdebug.client_host=127.0.0.1
xdebug.client_port=9003

Step-by-step diagnosis

  1. Copy the complete “Xdebug: [Config] The setting 'xdebug.remote_enable' has been renamed” text and retain the first application stack frame.
  2. Reproduce zend studio legacy xdebug configuration in the same SAPI and environment listed for this page.
  3. Before changing zend studio legacy xdebug configuration, inspect the preceding value or directive and verify its type, path, version, and permissions.
  4. Apply the narrow correction—translate remote_enable, remote_host, and remote_port to Xdebug 3 mode/start/client settings—then repeat the original request once.

Fixes

Correct the failing prerequisite

Translate remote_enable, remote_host, and remote_port to Xdebug 3 mode/start/client settings

ini 
xdebug.mode=debug
xdebug.start_with_request=trigger
xdebug.client_host=127.0.0.1
xdebug.client_port=9003

Fail explicitly at the boundary

Validate the condition before the operation that emits zend studio legacy xdebug configuration, and log a safe diagnostic without credentials or full production paths.

Common mistakes when fixing it

  • Suppressing zend studio legacy xdebug configuration instead of correcting its upstream condition.
  • Testing zend studio legacy xdebug configuration only with the CLI binary when the failing request runs under FPM or Apache.
  • Changing a global setting for zend studio legacy xdebug configuration before confirming the site-specific effective configuration.

How to prevent it

  • Add a focused test that exercises the boundary responsible for zend studio legacy xdebug configuration.
  • Keep runtime versions, extensions, configuration, and deploy artifacts affecting zend studio legacy xdebug configuration reproducible.
  • Validate external data and service return values before they can trigger zend studio legacy xdebug configuration.

Web server / environment notes

fpm, cli, docker, linux. The failure occurs where an old Zend Studio setup uses Xdebug 2 remote_* directives under Xdebug 3

Tags: fpm,cli,docker,linux

Categories