Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

XDEBUG_TRIGGER support #111

Open
dionysiosarvanitis opened this issue Jan 12, 2021 · 3 comments
Open

XDEBUG_TRIGGER support #111

dionysiosarvanitis opened this issue Jan 12, 2021 · 3 comments

Comments

@dionysiosarvanitis
Copy link

Hi! In order to support XDebug 3 we need to set the cookie name toXDEBUG_TRIGGER instead of the legacy XDEBUG_SESSION
Is it possible to accomplish it?

see https://xdebug.org/docs/all_settings#trigger_value

@sebastian-lenz
Copy link

sebastian-lenz commented Mar 3, 2021

The XDebug documentation states that it still supports the old variable names:
https://xdebug.org/docs/all_settings#start_with_request

There is also a legacy fallback to a functionality specific trigger name: XDEBUG_PROFILE (for Profiling), XDEBUG_TRACE (for a Function Trace), and XDEBUG_SESSION (for Step Debugging).

Im leaving this note here cause I had trouble getting XDebug 3 to work and thought the browser plugin was the culprit. When searching for the problem this issue showed up. But as it turns out, setting xdebug.start_with_request=trigger in php.ini works just fine with the plugin.

@mortona42
Copy link

This doesn't seem to be working for me. I have xdebug mode set as develop,debug and start with request as trigger.

@Pronik2009
Copy link

Also doesn't work for my case, but when I add XDEBUG_TRIGGER=some_value as GET parametr - my WEB server start debug session as well. So, seems we ask you add new field in ext options, like already exist for Trace or Profile modes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants